AWG Blogs

  • Coding without IF statements - Found below linked article that provides tips on how to avoid using IF statements, with one of the benefits being readability. The tips largely are based o...
    1 day ago
  • Microservices - A species would be a combination of roles [DCI?], instead of being characterized as an animal, which would not necessarily be the best description. At a ...
    2 weeks ago
  • CoR compared to Pipe and Filter - Java World implies the pipes-and-filters architectural style described by Parnas Software systems often employ the equivalent of pipes (e.g., email filter...
    7 months ago
  • Getting ADB Working for SPH-M840 - Had a SPH-M840 Galaxy Ring Virgin Mobile 3G Android version 4.1.2, attempting to install apps from Android Studio failed to detect device. Installed SAMSUN...
    1 year ago
  • How to check if I have write permissions to an Oracle table - SELECT CASE WHEN COUNT(*) > 0 THEN 'YES' ELSE 'NO' END AS PERMISSIONS FROM ( SELECT privilege FROM ( select * from dba_tab_privs where (grantee = 'MY_USE...
    1 year ago
  • Flyweight vs Singleton - Implementations seems to be virtually identical, differing only in style, where the flyweight object is created and held by associated objects (containers:...
    2 years ago
  • init-param vs context-param - see for background. Gist: context-param variables are global and accessible thro...
    2 years ago
  • rbenv vs RVM - RVM is responsible not only for changing Ruby versions, but for installing rubies and managing gemsets, as well. ...Along with rbenv [to manage ruby versi...
    2 years ago

Saturday, October 16, 2010

WSS Inaccessible after Windows Updates

After a scheduled Windows Update, several WSS sites became inaccessible. The Application Event Log contained events like:Unknown SQL Exception 33002 occured. Additional error information from SQL Server is included below.

Access to module dbo.proc_GetRunnableWorkItems is blocked because the signature is not valid.

I got similar errors when attempting to open any of the tables of the affected content databases in the embedded SQL Server (SSMS to \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query).
Relatedly, WSS creates copious logs at
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS whenever anything goes wrong with one of the WSS services, which fills up the hard drive. This may have had something to do with the failed update.

Anyway, after much googling and trying various solutions, some of which did more harm than good, I followed one suggestion and tried running the following command:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>PSCO
NFIG -cmd upgrade -inplace b2b -wait -force

After some time, the operation completed and all my sites were oparational!

No comments:

Post a Comment