I got the following error while trying to create a list based on a custom template:
The language is not supported on the server - Office SharePoint Server2007 installation
I came across this post but that did not seem to resolve my problem even after restarting the server.
Comparing other servers in the farm, I noticed that HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0 was actually missing InstalledLanguages.
So I saved the following to a .reg file, double-clicked and voila! It worked like a charm:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\InstalledLanguages]"1033"="12.0.4518.1016"
Sunday, March 16, 2008
SharePoint 2007 (MOSS): DST is the root of all evil!
I'm leading a project to convert our MCMS implementation to MOSS. Migrations have been working great until recently. What changed, one might wonder?
It's this time of the year where daylight savings reeks havoc! The issue is the Windows Sharepoint Timer Service (you can find it under Admin Tools --> Services) could take an hour or longer to run your jobs.
So if you create Web applications, for instance, in a farm, it would take MOSS an hour to actually provision these sites. So before you drive yourself crazy, here are some tricks (if you don't want to take the risk of applying SP1, or MS hotfixes, which are often unreliable!):
Look at the job definitions under Operations and verify the job in question is listed.
If it is, then you can force it by running the following command:
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o execAdmSvcJobs
Remember that you need to run this command on all your Web servers in the farm.
It's this time of the year where daylight savings reeks havoc! The issue is the Windows Sharepoint Timer Service (you can find it under Admin Tools --> Services) could take an hour or longer to run your jobs.
So if you create Web applications, for instance, in a farm, it would take MOSS an hour to actually provision these sites. So before you drive yourself crazy, here are some tricks (if you don't want to take the risk of applying SP1, or MS hotfixes, which are often unreliable!):
Look at the job definitions under Operations and verify the job in question is listed.
If it is, then you can force it by running the following command:
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o execAdmSvcJobs
Remember that you need to run this command on all your Web servers in the farm.
Subscribe to:
Posts (Atom)