MS won’t let you do it, doesn’t mean you can’t.
I created a MOSS 2007 farm for a project the other day and today the developers come back and say there are all sorts of errors on the server. Yay. I tried a few things then decided to pull the WFE’s out of the farm and re-join them. Then I got this error;
Failed to connect to the configuration database.
An exception of type System.ArgumentException was thrown. Additional exception information: Error during encryption or decryption. System error code 997.
That’s weird, the farm account has the appropriate permissions to the database server – what’s going on. A little Google came up with this from Microsoft (http://support.microsoft.com/kb/927156);
This issue occurs if the Network Service account is used as the farm account. In this situation, when you remove Windows SharePoint Services 3.0 from a stand-alone farm, or when you remove SharePoint Server 2007 from a Windows SharePoint Services 3.0 farm environment, the following registry subkey that is used to encrypt passwords that are contained in the Windows SharePoint Services 3.0 configuration database (configdb) is deleted:HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ FarmAdmin\
Therefore, when you try to join a Web application that exists in the configuration database that does not use the Network Service account, the Web application account credentials cannot be decrypted. This occurs because the required registry subkey is deleted.
To work around this issue, run Psconfig.exe at the command line to create a new Windows SharePoint Services 3.0 configuration database. To do this, follow these steps:
- Click Start, click Run, type cmd in the Open box, and then click OK.
- At the command line, change to the following directory:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
- At the command prompt, type the following command to create a new configuration database:psconfig -cmd configdb -create -server ServerName -database ConfigDBName -user Domain\User -password Password
- Rerun the SharePoint Products and Technologies Wizard.
These instructions fix the issue but since there hadn’t been much work done in the environment already, I just created a new farm. Fresh 🙂
Not sure how this happened, but one of our client’s domains was running about 23 minutes ahead of time. Short of it having a flux-capacitor this needed to be fixed;
NB: Thanks to the very informative article at Microsoft (http://support.microsoft.com/kb/816042) and Windows Networking (http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Time-Service.html)
Open up regedit on the PDC and navigate to;
This is the how the time service should be updated, change this to NTP (for sync’ing externally) NT5DS will check the server’s own CMOS clock.
Change this from 10 to 5.
Now this is your source of time. I use pool.ntp.org,0x1 (note the 0x1 is required when you use the DNS name); if using IP address (in this case pool.ntp.org), you can use 188.8.131.52.
Then restart your W32Time service; updates can take up to an hour so you can force update by using
- w32tm /resync /rediscover
Then just double-check your eventlogs and ensure that are no errors/warnings.
Sometimes, in haste, you install SQL a little too fast and miss installing a feature you actually need. Case in point, today I built a new SQL 2005 Server and attempted to create a new maintenance plan – ERROR.
“‘Agent XPs component is turned off as part of the security configuration for this server”
So instead of reinstalling SQL, there is a simple script fix which I found here (http://www.treeratfishing.com/2008/01/15/enabling-agent-xps-on-sql-2005/)
- sp_configure ‘show advanced options’, 1;
- sp_configure ‘Agent XPs’, 1;
You can now create Maintenance Plans.
We use Dell XPS1330 laptops in our environment so these bad-boys come with Nvidia 8400GT cards.
When installing Windows7 beta (build 7000) to a system with an Nvidia graphics card, the default graphics driver installs. To update this, Nvidia recommend you update the driver via Windows Update (http://www.nvidia.com/object/windows_7.html) this installs the 179.23 driver
The problem with this driver is that it corrupts the display (not sure if it’s restricted to single or multiple displays; we use multiple).
To fix this annoying problem, there are more recent drivers available (179.28) from Nvidia’s site (http://www.nvidia.com/Download/index.aspx?lang=en-us), that resolve the issue. I have Win7 x64, so used the Vista x64 ones.
The advantage to downloading the Nvidia ones is that they also install Cuda/Physx.
Good lord, why would they change this?
In Vista SP1, Microsoft disabled the ability to use the /console switch for logging onto the console session when using Remote Desktop. The ‘fix’ is to use mstsc /admin
Locate your Great Plains CD and run the setup.exe
The following components need to be installed prior to Great Plains installation.
NOTE: The installation will quickly run through these components with the exception of .NET. If you have .NET 2 or 3 or any .NET Service Packs installed, Dexterity Shared Components will fail and installation cannot continue.
RESOLUTION: Uninstall all .NET Framework installs other than .NET 1 or 1.1 SP1. You can install these again post-install, but GP10 will not install until this has been performed.
Choose the features your require to be installed.
If you don’t already have a SQL database backend, leave Do Not Create A Data Source unticked, otherwise tick.
Great Plains will need to be aware that you already have a SQL database hosted on your SQL server.
In Administrative Tools, open Data Sources (ODBC):
Create new System DNS, Select SQL Native Client driver, Server name: servername Description: Great Plains, Username: username, Password: password
Installation will run through.
GP Service Pack
When installation is complete, run all GP10 Service Packs available from Microsoft’s site. You will require a MSDN or equivalent login to acquire these. This service pack will require a system reboot.
When starting Great Plains, you will be prompted to run GP Utilities.
Run this and update the update the companies if they aren’t already.
Use the drop-down menu to “Update modified forms and reports”, and click Process.
Modify the DYNAMICS.SET file
The Dynamics.set file located at C:\Program Files\Microsoft Dynamics\GP\DYNAMICS.SET may be incorrect in your environment and may need to be copied from the server hosting the GP database. This will happen if you have custom reports and such.
Basically this is the same file as GP installs by default with the following syntax;
:C:Program Files/Microsoft Dynamics/GP/Forms.dic
:C:Program Files/Microsoft Dynamics/GP/Reports.dic
That’s it, you have installed GP10.