I am excited to be working on a new site that will be based on WordPress for my church. I am in the early stages of the process but expect to have something put together relatively quickly.
Once thing I like about using WordPress is that is makes it easy to rapidly design and deploy a site, then depending on the requirements of the site own we can investigate any custom plugins or themes that may be required.
I have been working on web applications since the mid 90s and the technology has changed so much. Things that we wanted to do in the 90s are now possible to do and easy to do!
I will be publishing some updates and helping to build the the social network of our church, Stewart Avenue Lutheran. I was married at SALC and also had both of my children baptised there and we attend Sunday School and many other events. Helping my church feels so good to me and I am so honored to be able to help.
Reblogging this post that is very useful from http://blog.sqlauthority.com/2009/02/14/sql-server-restore-master-database-an-easy-solution/
SQL SERVER – Restore Master Database – An Easy Solution
February 14, 2009 by pinaldave
Today we will go over two step easy method to restore ‘master’ database. It is really unusal to have need of restoring the master database. In very rare situation this need should arises. It is important to have full backup of master database, without full backup file of master database it can not be restored.
It is necessary to start SQL Server in single user mode before master database can be restored. It is very easy to start SQL Server server in single user mode. Follow the tutorial SQL SERVER – Start SQL Server Instance in Single User Mode.
Once SQL Server instance is running in single user mode, immediately connect it using sqlcmd and run following command to restore the master database.
RESTORE DATABASE master FROM DISK = 'C:BackupLocationmaster.back' WITHREPLACE;
I have tested it couple of times and it has worked fine for me. If you encounter any error please leave a comment and I will do my best to solve it.
Reference : Pinal Dave (http://blog.SQLAuthority.com)
This is a common error I have run across and can be solved by making a change on the client’s machine eConnect config file. This post is a reminder for me if I see this on a new image of a machine using eConnect.
Error message “There was an error writing to the pipe: The pipe is being closed.” occurs on eConnect for Microsoft Dynamics GP 2010.
Add receiveTimeout=”infinite” to the Microsoft.Dynamics.GP.eConnect.Service.exe.config file for the eConnect Integration service. The binding section should resemble this:
<binding name="eConnectNamedPipeConfig" closeTimeout="00:10:00" sendTimeout="00:10:00" receiveTimeout ="infinite" transferMode="Buffered" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="2147483647" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647"><readerQuotas maxDepth="60" maxStringContentLength="2147483647"maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" /><security mode="Transport"><transport protectionLevel="EncryptAndSign" /></security>