Re: URGENT: Hotfix 941422 on WSS 3.0 causes WSS to fail



On Oct 16, 4:32 pm, "callahan" <cacalla...@xxxxxxxxxxxxxxxxxxx> wrote:
Is there anywhere for the hotfix where that requirement is documented?
-callahan"MSherman" <MSher...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message

news:0286C5A0-E45B-4FCF-817B-4C17001A7FB0@xxxxxxxxxxxxxxxx

You get that error if you don't re-run the "SharePoint Products &
Technologies Configuration Wizard" after you installed the hotfix.

"shikarishambu" wrote:

Ok, this Hotfix that "does not require any prerequisities or reboot"
broke
my server.

Called MSFT and was told that it is a pay per support incident and WSS is
a
24 hr callback support.

So, I went ahead and removed and re-installed Sharepoint. And, that
worked

"shikarishambu" <shikarishamb...@xxxxxxxxxxx> wrote in message
news:usDPm4AEIHA.5328@xxxxxxxxxxxxxxxxxxxxxxx
I installed the hotfix, ran the Configuration wizard. It said, it failed
to
upgrade. And, after that WSS does not come up

I see the following errors in the Windows Event Log:
1:
Database 'SharePoint_AdminContent_e4e47c8a-6938-4f6c-afc6-890ed3cdf4b5'
on
SQL Server instance 'DBSERVER' is not empty and does not match current
database schema.

2:
The Execute method of job definition
Microsoft.SharePoint.Administration.SPUpgradeJobDefinition (ID
785ec386-b65d-482c-ab96-71a44a38f36e) threw an exception. More
information
is included below.

The specified SPContentDatabase
Name=SharePoint_AdminContent_e4e47c8a-6938-4f6c-afc6-890ed3cdf4b5
Parent=SPDatabaseServiceInstance has been upgraded to a newer version
of
SharePoint. Please upgrade this SharePoint application server before
attempting to access this object.

3:
The schema version (3.0.149.0) of the database WSS_Content on
OMNCLTDB01
is not consistent with the expected database schema version (3.0.150.0)
on
OMNCLTSP01. 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.

How do I fix these issues or remove the hotfix.

Thanks

I am having the exact same issues running the new WSS Service Pack
1...very frusrating, and I can't restore the config databases!!! It
is actually designed this way!
.



Relevant Pages

  • Re: SharePoint Services 3.0 unable to display content
    ... When connecting to the original configuration database, ... The virtual server that is referenced here is not in the config database. ... I am 100% about the WSS. ... Microsoft Windows SharePoint Services 2.0 ...
    (microsoft.public.sharepoint.windowsservices)
  • Restore WSS sites after disaster
    ... I lost the system disk of a server with a couple of WSS ... The database files files were located on a different disk. ... It seems that in order to restore a WSS site (with stsadm -o restore etc. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: WSS 2.0 to 3.0 - different servers
    ... So, No, to "if I can perform a gradual upgrade when WSS 2.0 is on one ... server and WSS 3.0 is on another." ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: EventID1000: #50070:Unable to Connect to Database - WSS 2.0
    ... Microsoft Support Engineer by contacting Microsoft Customer Support ... Subject: EventID1000: #50070:Unable to Connect to Database - WSS 2.0 ... lot work for server that has lots of virtual servers/sites. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Upgrade from MSDE to SQL
    ... Hard to say whether the database is of any use to you now you are partway ... upgrade just in case. ... But FIRST I would in any case see if adding SQL Server ...
    (microsoft.public.sharepoint.windowsservices)