Re: Failed KB909544 install



I had the same issue but not due to KB909544. or at least I do not think so.
However I could not start the MSSQL$SHAREPOINT service either. I tried
several fixes and suggestions and then finally gave up as it was becoming
more time consuming than to just resinstall SharePoint Services. So that's
was I did. I made sure I had the latest backup for Companyweb and removed
SharePoint then reinstalled it. Well what do you know. No more errors.
Not saying this is your fix but if like myself you feel it is becoming more
of a pain in the @%$ than it would be to reinstall then take a look at these
KB articles to help you out.

http://support.microsoft.com/kb/829114/en-us
http://support.microsoft.com/kb/829112/en-us



"Cameron" <CamHartis@xxxxxxxxx> wrote in message
news:1149001461.904973.147760@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have been attempting to troubleshoot this identical issue as reported
by Nicolas Noakes on Jan 25, 2006:

"We are running SBS 2003 Standard Edition with SP1, and WSUS (Windows
Server Update Services). All was well until I tried to install the
folloing update, which failed:

Update for SQL Server 2000 Desktop Engine (SharePoint) on Windows
Server
2003 (KB909544)

I now cannot start the MSSQL$SHAREPOINT service - it starts and
immediately stops again.

I cannot find the update file for KB909544 on the Microsoft Download
Centre website, and obviously it cannot be reinstalled via WSUS of the
Windows Update website because it is identified as already installed.

It does not seem that the database for KB909544 vesion of MSDE will be
able to be read by previous versions (refer to the kb article), and I
see a error about the master database having an "invalid schema" in the
sql log file. I therefore suspect that the database has been upgraded,
but not the MSDE engine."

We have reinstalled all of WSS in an attempt to correct this issue,
after reapplying the same patch, we receive the same error. We do not
have a very large companyweb site, however, we do have several clients
who are using this site quite extensively.



.



Relevant Pages

  • RE: transfer companyweb config db
    ... configuration database for sharepoint services to a new location on the sql ... You may mistake SQL server conception. ... Move the Monitoring Database ... >project web access not working correctly is to use a config database on ...
    (microsoft.public.windows.server.sbs)
  • I broke Sharepoint :(
    ... SBS was installed and the server was up and running including the default ... After 2 days I was looking at SQL backups I relaised that Sharepoint ... database and the other instances were not migrated accross. ...
    (microsoft.public.windows.server.sbs)
  • Re: Service Account Password Change
    ... app pools and changed the passwords, when I got to the sharepoint admin ... the sharepoint domain account didnt have the database admin ... Our dev environment is a domain member server running sharepoint portal ... > Detach from the config database in SharePoint Central Administration ...
    (microsoft.public.sharepoint.portalserver)
  • Steps for Migrating WSS 3.0 from Windows Internal Database to Microsoft SQL 2005
    ... done the stupid things I did when I started playing with Sharepoint ... when I first installed it and assuming that it would find the SQL 2005 ... Windows Internal Database). ... Reboot the server to finish up any uninstall scripts. ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: Failing Application?
    ... logon the server, and you find the following error message in Event Log: ... Check the database connection information and make sure that the database ... this problem could be caused because the SharePoint ... Timer Service failed to contact the SharePoint database while the SBS is ...
    (microsoft.public.windows.server.sbs)