Wednesday 2 December 2009

WSUS – Error 33002 – Access to module dbo.spConfiguration is blocked because the signature is not valid

This one has showed up on a few of our WSUS v3 based SBS 2003 R2 boxes after the last post update reboots. And, there are _lots_ of them:

Event Type:    Error
Event Source:    MSSQL$MICROSOFT##SSEE
Event Category:    (2)
Event ID:    33002
Date:        12/1/2009
Time:        5:40:43 PM
User:        NT AUTHORITY\NETWORK SERVICE
Computer:   SBS
Description:
Access to module dbo.spConfiguration is blocked because the signature is not valid.

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

Another example of the error:

Event Type:    Error
Event Source:    MSSQL$MICROSOFT##SSEE
Event Category:    (2)
Event ID:    33002
Date:        12/1/2009
Time:        5:40:43 PM
User:        NT AUTHORITY\NETWORK SERVICE
Computer:    SBS
Description:
Access to module dbo.spReturnStateMachineTransitionEventLogEntriesFromError is blocked because the signature is not valid.

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

The only thing to come up in our searches to fix the problem were to do the following:

  1. Start –> Run –> Services.msc [Enter]
  2. Right click and Restart Windows Internal Database.
  3. Right click and Restart Update Services.
    • image
  4. Verify that there are no more errors in the logs.

The solution was found on Experts-Exchange: Event ID: 33002 Access blocked because signature is not valid.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

2 comments:

Anonymous said...

I was with the same problem, and looking in the internet i found this page.
It really works fine for me, now evertithing is ok.

Anonymous said...

I continue to have this problem from time to time. A restart of the server, or restarting the services fixes it. I'm wondering if anyone has found a more permanent fix.