index > SharePoint - Setup, Upgrade, Administration and Operation > Mixed up version numbers on MOSS 2007

Mixed up version numbers on MOSS 2007

I am trying to determine the versionI am running on one of my MOSS 2007 servers. It is a Single server (DB and WFE are on tehsame server). In the Central Adminunder the Operation > Servers on FarmI seeVersion 12.0.0.6219 under Farm Information which indicates that SP1 has been installed to me. But when I look inCentral Admin under the Site Actions > Site Settings the Version says 12.0.0.4518 which indicates no Service pack was installed. I fear that some type of half updated was completed on this server. Does anyone know what this could mean as far as what version I am running or is something is wrong here?

revilord Monday, February 02, 2009 5:39 PM

Hi,

If the installation did not succeed, you can run the SharePoint Products and Technologies Configuration Wizard again, or you can use the following procedure to complete the configuration at the command prompt.

To force a software update:

Open a Command Prompt window and at the command prompt change to the following directory:

%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin

Type the following command:

psconfig -cmd upgrade -inplace b2b -wait -force

for more information, please refer to: Deploy software updates for Windows SharePoint Services 3.0 (http://technet.microsoft.com/en-us/library/cc288269.aspx)

Let me know if you need further assistance.

-lambert

Posting is provided "AS IS" with no warranties, and confers no rights.

Marked As Answer byrevilord Friday, February 06, 2009 8:46 PM

Lambert Qin Wednesday, February 04, 2009 6:07 AM

Just a thought, but when you updated to SP1 level, did you run both the WSS 3.0 SP1 and (then) the MOSS 2007 SP1 ?

WSS FAQ sites: WSS 2.0: http://wssv2faq.mindsharp.com WSS 3.0 and MOSS 2007: http://wssv3faq.mindsharp.com
Total list of WSS 3.0 and MOSS 2007 Books (including foreign language titles) http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/V%20Books.aspx

Mike Walsh MVP Tuesday, February 03, 2009 5:51 AM

That could be the case, I am trying to figure out what has been done to the system. From the Update.log an update was attempted but it failed.Here are the last lines from the update.log.

[SPManager] [INFO] [12/10/2008 5:08:08 PM]: Finished upgrading SPFarm Name=SharePoint_Config.
[SPManager] [INFO] [12/10/2008 5:08:08 PM]: Inplace Upgrade session finishes. root object = SPFarm Name=SharePoint_Config, recursive = True. 1 errors and 8 warnings encountered.
[SPManager] [DEBUG] [12/10/2008 5:08:08 PM]: Removing exclusive upgrade regkey by setting the mode to none
[SPManager] [DEBUG] [12/10/2008 5:08:14 PM]: SyncUpgradeTimerJob: Upgrade timer job failed. Return -1.

Since the update was done a while back I don't think I can restore from backup and I can't seem to reinstall WSS 3.0 SP1. I keep getting incorrect version error messages. There is no way to uninstall SP1 to the DB so unless I can fix the update I think the system is screwed.

It looks like the database was updated but but the system is not. On the Web Server > Control Panel > Add/Remove Programs > MS Office Server > Information the version is 12.0.4518 but under the database Select * from Versions returns the version 12.0.0.6219.

revilord Tuesday, February 03, 2009 6:42 PM

Hi,

To force a software update:

Open a Command Prompt window and at the command prompt change to the following directory:

%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin

Type the following command:

psconfig -cmd upgrade -inplace b2b -wait -force

for more information, please refer to: Deploy software updates for Windows SharePoint Services 3.0 (http://technet.microsoft.com/en-us/library/cc288269.aspx)

Let me know if you need further assistance.

-lambert

Posting is provided "AS IS" with no warranties, and confers no rights.

Marked As Answer byrevilord Friday, February 06, 2009 8:46 PM

Lambert Qin Wednesday, February 04, 2009 6:07 AM

Lambert,

Thanks for the help, I think you were right on the money.I ran the command (psconfig.exe -cmd upgrade -force) before I read your suggestion but I left out the inplace b2b parameter. Everything seemed to go ok though. All version now read (12.0.0.6219) which means that SP1 is now installed correctly.

I read what inplace does

[-inplace <v2v|b2b>]

If specified, the SharePoint Products and Technologies Configuration Wizard will perform an in-place upgrade. If v2v is specified, then an in-place version to version upgrade is performed. If b2b is specified, then an in-place build to build upgrade is performed.

but I am not sure what it does or if I should run it again.

revilord Friday, February 06, 2009 8:45 PM

I'm seeing the exact same entries in the upgrade log, and have tried all suggestions here. I'm still failing, though. In the PSCDiagnostics log file I see an error stating "The B2B upgrader timer job failed." I've been searching for solutions for that, but so far nothing that's as exact of a match to my problem as what I see here. Any other suggestions?

Oh...it was the February Cumulative I was applying. Applied the WSS first, then the MOSS, then ran the GUI verson of psconfig. My Central Admin server upgraded fine, and is showing all servers at version 12.0.0.6341, yet my WFEs are showing version 12.0.0.6324.

Any help will be greatly appreciated!

Thanks!
Jim

norski0 Thursday, September 17, 2009 6:40 PM

You can use google to search for other answers

Custom Search

More Threads

• Outcome column does not get updated to "completed" when tasks are completed from Outlook

• Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION))

• Find Server Farm Name

• Invite Users to a Discussion

• Inconsistent SSP (shared services providers) behaviour ?

• Assign Tasks from a List in Sharepoint

• Error when trying to connect new Web Application to exiting Content Database

• Issues with Excel/Sharepoint Integration (unable to insert new data rows)

• Upgrade from WSS 3.0 to MOSS 2007 Standard, Enterprise

• Sharepoint 3.0 "Cannot connect to configuration database"