I saw this error before, you have to make sure every web front has run the 
upgrade before the configuration

Ken
 





From: [email protected]
[mailto:[email protected]] On Behalf Of Noja, Fadi

Sent: Thursday, 30 April 2009 12:11 PM

To: [email protected]

Subject: RE: Error with SP2 [SEC=UNCLASSIFIED]





 

I don’t have that error message in the logs.  When I try the
force upgrade, it spits out an error saying htat the instance is not empty and
does not match current database schema. 

 

It also wasn’t an upgrade from 2003.  It was a farm that was
built from scratch with 2007 on it.

 

I looked into it, the current schema is saying it’s version 3.0.1.0
and it’s trying to upgrade it to v 2.0.0.0.  So I think we’ve installed a
hotfix at one point that has upgraded the schema and in SP2 they’ve put the old
schema in it.

 









From: [email protected] [mailto:[email protected]]
On Behalf Of Michael Nemtsev

Sent: Thursday, 30 April 2009 12:04 PM

To: [email protected]

Subject: RE: Error with SP2 [SEC=UNCLASSIFIED]



 



The actual installation is doing few things. Wizard apply majority
of changes.





Referring
to your SQL version is look like that you have right version, not outdated.





 





Your
current issue is not caused by SP2 specifically. It's common issue, which are
about leaving sites in inconsistet state (did you migrate this site previously
from SharePoint 2003?). I had rhis issue with SP1 :)





 





Do
you have any records in event log? something like this one





"The schema version of the database
WSS_Content on SHAREPOINT1\OfficeServers is not consistent with the expected
database schema version on SHAREPOINT1. 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."





 





To
fix this use "STSADM.EXE -o upgrade -inplace -forceupgrade –url http://site"; 
for each web application you have.





and
then run wizard "psconfig -cmd upgrade -inplace b2b -wait –force"





 







Michael
Nemtsev

Readify | Microsoft MVP

http://msmvps.org/blogs/laflour

T:
0424 184 978 | E: [email protected]













From: [email protected] [[email protected]] On
Behalf Of Noja, Fadi [[email protected]]

Sent: Thursday, 30 April 2009 11:52 AM

To: [email protected]

Subject: RE: Error with SP2 [SEC=UNCLASSIFIED]







SP2 installation ran fine, only the Wizard spat that error out.

 









From: [email protected]
[mailto:[email protected]] On Behalf Of Michael Nemtsev

Sent: Thursday, 30 April 2009 11:39 AM

To: [email protected]

Subject: RE: Error with SP2 [SEC=UNCLASSIFIED]



 



What I'd try to do is 





1) run prescan tool to check if there is something wrong with DB





2)
detach and attach sharepoint database in Centra
Admin. To make sure that your db schema is correct\





 





and
after that tried to install SP2 again





 







Michael
Nemtsev

Readify | Microsoft MVP

http://msmvps.org/blogs/laflour

T:
0424 184 978 | E: [email protected]













From: [email protected] [[email protected]] On
Behalf Of Noja, Fadi [[email protected]]

Sent: Thursday, 30 April 2009 10:57 AM

To: [email protected]

Subject: Error with SP2 [SEC=UNCLASSIFIED]







I’ve
just tried installing SP2 and am getting this error

 

[SPDatabaseGbwSequence]
[ERROR] [4/30/2009 10:43:38 AM]: Upgrade object too new (build version =
12.0.0.6341, schema version = 2.0.0.0). Current server (build version =
12.0.0.4518, schema version = 3.0.1.0).

 

Now
the build version is right, but the schema version for SP2 is older than the
one I currently have.  So it’s causing it to fail.  Has anyone seen
this before?

 

Fadi











Support
procedure: https://www.codify.com/lists/support

List address: [email protected]





Subscribe:
[email protected]





Unsubscribe:
[email protected]





List
FAQ: http://www.codify.com/lists/ozmoss





Other
lists you might want to join: http://www.codify.com/lists















Support
procedure: https://www.codify.com/lists/support

List address: [email protected]





Subscribe:
[email protected]





Unsubscribe:
[email protected]





List
FAQ: http://www.codify.com/lists/ozmoss





Other
lists you might want to join: http://www.codify.com/lists











Support
procedure: https://www.codify.com/lists/support

List address: [email protected]





Subscribe:
[email protected]





Unsubscribe:
[email protected]





List
FAQ: http://www.codify.com/lists/ozmoss





Other
lists you might want to join: http://www.codify.com/lists













Support
procedure: https://www.codify.com/lists/support

List address: [email protected]





Subscribe:
[email protected]





Unsubscribe:
[email protected]





List
FAQ: http://www.codify.com/lists/ozmoss





Other
lists you might want to join: http://www.codify.com/lists











Support
procedure: https://www.codify.com/lists/support

List address: [email protected]





Subscribe:
[email protected]





Unsubscribe:
[email protected]





List
FAQ: http://www.codify.com/lists/ozmoss





Other
lists you might want to join: http://www.codify.com/lists









Support procedure: https://www.codify.com/lists/support
List address: [email protected]
Subscribe: [email protected]
Unsubscribe: [email protected]
List FAQ: http://www.codify.com/lists/ozmoss
Other lists you might want to join: 
http://www.codify.com/lists--------------------------------------------------------------------------------
Support procedure: http://www.codify.com/lists/support
List address: [email protected]
Subscribe: [email protected]
Unsubscribe: [email protected]
List FAQ: http://www.codify.com/lists/ozmoss
Other lists you might want to join: http://www.codify.com/lists

Reply via email to