• Home
  • Consulting
  • Contact Us
    • About this site
    • Contact Wayne
    • Media Room
    • Wayne’s Bio

SBSFAQ.COM

Supporting IT Pro's & MSP's since 2000

  • Blog
  • FAQs
  • Reviews
  • Downloads

MS KB 934525 Breaks WSS 3.0 sites here s how I fixed it

October 11, 2007 by Wayne Small 3 Comments

This morning I applied the current MS patches to a number of my servers. On some they worked fine, but on this server my blog server the patch horked up Sharepoint Services 3.0.

I was getting the following error

Event Type: Error

Event Source: Windows SharePoint Services 3

Event Category: Topology

Event ID: 6800

Date: 11/10/2007

Time: 7:31:59 AM

User: N/A

Computer: SERVERNAME

Description:

The database WSS_Content on SERVERNAME\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I picked a section of the error message that would not likely generate too many false positives and searched on the following

“is not accessible to missing Windows Internal Database signatures.”

Found a number of references to people having this error earlier in the year and how they resolved it. Not sure though why it caused me trouble now.

Vlad has seen it too. http://www.vladville.com/fixing-sharepoint-30-with-kb932091

I ran through that process, but the Sharepoint Configuration Wizard would not work still. It kept failing on step 9 of 10.

Digging into the logs seemed to suggest that my administrator account didn’t have permission. I’ve actually renamed my administrator account to something else. After some digging and help from some friends (thanks Damian) I was still no closer to the solution. Damian thought it might be related to orphaned sites on my WSS 3.0 installation. I had a gut feel that it was the renamed admin account. I renamed the account BACK to administrator, rebooted and re-ran the Sharepoint Configuration wizard and finally after 4 hours of messing around, it works!

At the end of all this I’m still in my pre-patch situation. I had both an NTBackup and StorageCraft image of the server before I started patching this morning. However after 4 hours of messing around, I need to get some work done. I’ll look again at the patch on the weekend to see if I want to bash my head against the wall some more.

Correction I was incorrect the new patch is in place. I was misreading the MU screen.

Watch out for it this patch it’s not nice!

Share this:

  • Click to share on Facebook (Opens in new window)
  • Click to share on Twitter (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to print (Opens in new window)

Filed Under: Blog

About The Author

Wayne has been working with Microsoft Server products in the SMB market for over 20 years. He has a passion for technology and been a Microsoft MVP for over 15 years. Read More…

Comments

  1. Anonymous says

    October 14, 2007 at 1:36 pm

    I have seen similiar issues on my Sharepoint installs that were made even worse because of the fact that I aldo had Sharepoint GRoupboard installed.

    I’m putting together my own story of woe on my (now recovered Sharepoint) blog at :

    http://supportweb.ciaops.net.au/blog

    Thanks
    Robert Crane
    Saturn Alliance

    Reply
  2. Anonymous says

    October 20, 2007 at 7:00 am

    I ran into this today. Tried to install Hotfix 937901 (want to add external storage). I had the same symptoms listed here. Solutions to similar problems that other people had that _didn’t_ work were:

    1. Pull dw20w.msp out of another hotfix and apply it manually.

    2. Fixing permissions in the SQL Management tool. (I also had “NT AUTHORITY\NETWORK SERVICE could not log in” errors.)

    3. Running stsadmin -o execsvcadmjobs

    What *did* work was not misinterpreting the error message. It failed at step 9/10, sometimes after long periods of time. And the error message mentioned having to start the SPsearch indexing service manually. What it didn’t mention was that you had to do it immediately (not that you’d have to start it manually later).

    svsadm -o spsearch

    was all I needed.

    Reply
  3. Steven Sainsbury says

    November 28, 2007 at 3:29 am

    I ran the following command on my sharepoint server and it resolved the problem…

    Stsadm o upgrade inplace url http://sharepointsite

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Connect Online With Us

  • Facebook
  • Twitter

Reviews

Splashtop – Cost Effective Remote Control Software

September 22, 2017 By Wayne Small 2 Comments

Western Digital DL4100 NAS

March 3, 2015 By Wayne Small Leave a Comment

SBS 2011 Configuring Certification Guide (70-169)

August 7, 2012 By Wayne Small 4 Comments

Site News

Exchange Bug Stops Mail Delivery in 2022

January 2, 2022

Huge bug found in Intel CPU that could permit hackers to steal your data

January 4, 2018

Recent Posts

  • MS Exchange Zero Day and RemotePowerShell Disabling on Admin accounts
  • Setup changes for Exchange 2016 and Exchange 2019
  • Bluetooth Mouse and Keyboard Randomly Stop Responding
  • Exchange Bug Stops Mail Delivery in 2022
  • How to open and search extremely large text log files

Tags

Antivirus Backup Business Focus Cloud Computing Community Conferences Disaster Recovery Exchange 2010 Exchange Server Future Products Hyper-V Installation Microsoft Migration Patches Personal Rants SBS 4.5 SBS 2000 SBS 2000 SP1 SBS 2003 SBS 2003 Premium SBS 2003 R2 SBS 2003 R2 Premium SBS 2003 R2 Standard SBS 2003 SP1 Premium SBS 2003 SP1 Standard SBS 2003 Standard SBS 2008 SBS 2008 R2 SBS 2011 SBS 2011 Essentials SBS 2011 Standard Security Service Packs ShadowProtect SMB Community Software Software I use StorageCraft Training TrendMicro Troubleshooting Virtualisation Windows Server 2012 Essentials

Terms of Use

Privacy Policy

Copyright © 2023 · Magazine Pro Theme on Genesis Framework · WordPress · Log in