Wednesday, 25 November 2009
Thursday, 30 April 2009
[SPDatabaseGbwSequence] [ERROR] [4/30/2009 10:43:38 AM]: Upgrade object too new (build version = 22.214.171.12441, schema version = 126.96.36.199). Current server (build version = 188.8.131.5218, schema version = 184.108.40.206).
During the SharePoint wizard running after installing WSS and MOSS Sp2. The site still functions. Im looking into what hotfix has been installed that caused the schema to be upgraded and why SP2 is using the old schema. The install failed but the sites still function. Watch this space and I will let you know of a fix/workaround.
Found the problem. It was GroupBoard. When you install Group Board it updates the schema. The fix is simple, uninstall group board, re-run the wizard, re-install GroupBoard and the problem is gone.
If you go to http://translate.google.com/translate?hl=en&sl=de&u=http://technet.microsoft.com/de-de/library/cc288269.aspx&ei=6zD5SZqxOqjhtgfl9o2uDw&sa=X&oi=translate&resnum=6&ct=result&prev=/search%3Fq%3Dsharepoint%2Bhotfix%2BSPDatabaseGbwSequence%2Bschema%2Bversion%26hl%3Den%26rlz%3D1C1_____enUS323US323 you can see the fix. Only the German technet site talks about the error, the english one (http://technet.microsoft.com/en-us/library/cc288269.aspx) doesn't have the exact error message.
If that doesn't work, try forcing the upgrade by ding the following:
- "STSADM.EXE -o upgrade -inplace -forceupgrade –url http://site" for each web application you have.
- then run wizard "psconfig -cmd upgrade -inplace b2b -wait –force"
Wednesday, 29 April 2009
Download links are :
Please test it out on a dev or test environment before installing it on a prod. Also, if it fails, just follow the steps I set out for SP1 crash (stsadm -o upgrade -forceupgrade)
Thursday, 23 April 2009
1, Modify the master page:
Create the InitNoPresence.js file. To do this, follow these steps:
a. Copy the contents of the Init.js file to the InitNoPresence.js file on the front-end Web server.Note The Init.js file is located in the Drive:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Layouts\1033 folder.
b. Start Notepad, and then open the InitNoPresence.js file.
c. In the section of the InitNoPresence.js file that contains the ProcessDefaultOnLoad function,
Change ProcessImn(); with // ProcessImn(); (comment it out)
Go to SharePoint designer, modify the master page by replacing
2. Install feature
Larry Riemann and Randy Drisgill have written a cool feature that does it for you, go to http://www.codeplex.com/SPAXO and install it.
Friday, 17 April 2009
Wednesday, 8 April 2009
This error doesn't always appear during content deployment, it can also appear during site creation. I came across it the other day while content deployment was happening. After a bit of playing around with SharePoint, it turned out not to be a SharePoint error. The SQL box had run out of space. After deleting some unwanted databases, ran content deployment again and it worked fine.
Saturday, 4 April 2009
- Create new site/sub site
99% of these people's problems was the master page couldn't be found (hence the "page not found" error). To fix this, you can either edit the site in SharePoint Designer (which is now free) and fix the master page (by either editing it, or uploading it, or publishing it), or create a feature that sets the master page and activate that feature.
If you have this problem and it's not the master page, please let me know and I can see if I can help.