While trying to install WSS 3.0 SP1 (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx) the installation get stuck at task 9 of 10 of SharePoint Products and Technology Configuration Wizard. When tried to access the server, encountered the following error:
Server error: http://go.microsoft.com/fwlink?LinkID=96177
When look into the “Event Viewer”, found the following error description:
The schema version (3.0.149.0) of the database DATA
DATABASE_NAME on DATABA_SESERVER_NAME is not consistent with the expected database schema version (3.X.X.X) on DATABASE_NAME. Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match.
Resolution:
The first thing we did was either remove content database from the web application which are having the error or Detach the database. This doesn’t seem to work. So we run the command
stsadm –o upgrade –inplace –url Central_Administration_URL –forceupgrade
and we were back in the business J.
jake said
your post really saved my sites!! i actually thought of reinstalling my VPC image containing all those sites and its configuration, but luckily this saved my work!! Thanks to you and your great post!!
Sal said
Easier to fix if you don’t inherit applications, but… Make sure that your content DB and configuration DB are on the same server before applying SP!!!
Fabien said
That saved my night! Thanks!
Azeem said
Many thanks for the post. It worked. Thanks to you and Google!
Cheers
Shane said
Thanks alot – worked a charm
Bobby said
Worked wonderfully. Thought I had to recreate my sites but saved alot of time. Thanks alot!
Juan Pablo said
Thank’s a lot. Work’s great!
Christian said
You saved my life, I was gonna cry and die here, but then you saved me, you are my hero.
Vincent said
unfortunality you are not my hero
I have done an windows update on server 2003, then sharepoint has become down.
I ran the command line:
stsadm.exe –o upgrade –inplace –url http://sharepoint:23059 –forceupgrade
but it returns –> Command line error.
rinku said
For me also it returns the command line error. Any reply plz?????
AngelK said
This worked for me
STSADM.EXE -o upgrade -inplace -forceupgrade -url http://development
giapTD said
You save my life!
thank so much.
Lakmal Kankanamge said
Ohhh You are my hero… You save my life brother……
Klaus Gero Luth said
Same Problem raises, when you install Februray Cummulative Update 2010 on MOSS 2007 SP2 or (!) KB979445
only stsadm -o upgrade -inplace -url {Central Admin URL} helps, no chance to upgrade the content databases separetly
Great: http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/cc9efc81-7ab0-4d85-a5b5-b41685c71ae3
jothi said
Hey thanks a lot!! you saved my time:)
Rupak Sharma said
Shrinking the database solved the problem
Ensoy!!!!!!!!!!!!!!!
Patav said
Thanks for the nice post. Your solution works for some servers but for one server, I am getting the following error ” An update conflict has occurred, and you must re-try this action. The object SPFarm Name=SharePoint_config_test is being updated by domain\username, in the OWSTIMER process, on machine sharepointservername. View the tracing log for more information about the conflict.”
I have also posted my question on the microsoft forum ( http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/fa980693-9749-451c-8a30-376838a505e8)
I would appreciate any help on this.
Thanks…
Pablo said
Try a stsadm -o execadmsvcjobs on each server then run it again
Pravesh SHarda said
Just Run the Sharpoint Products and Tech. Configration wizard once
Patav said
I tried to run SharePoint Configuration wizard but it is giving me following error “An exception of type System.Data.SqlClient.SqlException was thrown.
Additional information:Login failed for user domain\user”. Please Advise.
Farhan Faiz said
Check for user login and password that is accessing SQL server. Check in CA.
bouchaet said
The command stsadm -o upgrade -inplace -forceupgrade works out for me. However, it did so only once InfoPath2010 was un-installed from the server.
Yenko said
Hey… how you do that???
Resolution:
The first thing we did was either remove content database from the web application which are having the error or Detach the database. This doesn’t seem to work. So we run the command
stsadm –o upgrade –inplace –url Central_Administration_URL –forceupgrade
and we were back in the business J
How and where you do this?? i want to get back to business too!!
please email me!!!
yenko@scan-inc.org
Farhan Faiz said
Use your database server to do this. We have SQL server 2005 as s our database server and we deattach the database.
Also, use stsadm from command line.
Adrian Morales said
Many thanks for the post. It worked. Thanks to you and Google!
Save my Saturday!!!! Thanks from Mexico
Cheers
Curtasan Levent said
Worked perfectly, I can’t thank you enough!
Sean Smith said
It worked thanks, although this type of error/problem is just one example of why Sharepoint is total rubish. No doubt the end user features are great but I can’t help thinking that the design and engineering side of the product rate at about 2/10,,,, cheers
Yenko said
Hello,
We are about to install Sharepoint 2010 on a 64bit Server Windows 2008 64 bit… but we are going to set Active Directory on a 32 bit server with Windows server 32 bit.
my questions are:
Does any of you know if it is recommended to have Sharepoint Enterprise 2010 and Active Directory installed on the same server? or they have to be on separate servers? Also, do any of you know if there is any conflict in communication between Windows Server 2008 32Bit and Windows Servers 2008 64 Bit?
Thanks,
Yenko
Anonymous said
Thank you for the excellent post, this resolved my issue quickly , Great!