WSUS database problems signature is not valid
|
Prev: SBS 2003 to 2008 Migration Mode - trouble getting into migration m
Next: Anybody seen this error before in SBS 2008? "Archived Email Site does not exist"
From: Miguel Sanchez on 4 Sep 2009 00:26 Hi there: Setup WSUS 3.0 plain SBS server 2003 premium R2 This the Sequence that started the problems: a) Power outages one after the other. The UPS was too depleted in the second one to bring down the server gracefully b) SUSDB became corrupted so I had to use the backup c) WSUS was back with no problems d) Upgraded to WSUS 3.0 SP2 e) Decided to do a cleanup WSUS f) Stopped WSUS web service in IIS g) purged and deleted the uneeded patches h) applied patches to the server among them Windows Internal Database Service Pack 3 (KB955706 and Service Pack 3 de Microsoft SQL Server 2005 (KB955706) i) Restarted the server and voila: FIRST Event Origin: MSSQL$MICROSOFT##SSEE Event category : (2) Event Id: 17137 Date: 03/09/2009 Time: 09:18:00 p.m. User: NT AUTHORITY\Servicio de red Machine : ************* Description: Starting up database 'SUSDB'. THEN Event type: Error Event Origin: MSSQL$MICROSOFT##SSEE Event category : (2) Event Id: 33002 Date: 03/09/2009 Time: 09:24:43 p.m. User: NT AUTHORITY\Servicio de red Machine: ********** Description:: Access to module dbo.spConfiguration is blocked because the signature is not valid. Final Note: since then I have restarted the WSUS web service. Any ideas will be welcomed Regards Miguel Sanchez
From: Cliff Galiher on 4 Sep 2009 05:20 In this order: 1) Restore a backup again. Something didn't take. 2) Configure your UPS to auto-shutdown servers when below a certain battery level. If properly configured, the server would've been gracefully shut down even while the UPS was online BEFORE the power outage because, as you pointed out, the battery level would've still been too low. -Cliff "Miguel Sanchez" <santaki2(a)hotmail.com> wrote in message news:#r1VofRLKHA.4136(a)TK2MSFTNGP04.phx.gbl... > Hi there: > Setup > WSUS 3.0 plain > SBS server 2003 premium R2 > > This the Sequence that started the problems: > a) Power outages one after the other. The UPS was too depleted in the > second one to bring down the server gracefully > b) SUSDB became corrupted so I had to use the backup > c) WSUS was back with no problems > d) Upgraded to WSUS 3.0 SP2 > e) Decided to do a cleanup WSUS > f) Stopped WSUS web service in IIS > g) purged and deleted the uneeded patches > h) applied patches to the server among them Windows Internal Database > Service Pack 3 (KB955706 and Service Pack 3 de Microsoft SQL Server 2005 > (KB955706) > i) Restarted the server and voila: > FIRST > Event Origin: MSSQL$MICROSOFT##SSEE > Event category : (2) > Event Id: 17137 > Date: 03/09/2009 > Time: 09:18:00 p.m. > User: NT AUTHORITY\Servicio de red > Machine : ************* > Description: Starting up database 'SUSDB'. > > THEN > Event type: Error > Event Origin: MSSQL$MICROSOFT##SSEE > Event category : (2) > Event Id: 33002 > Date: 03/09/2009 > Time: 09:24:43 p.m. > User: NT AUTHORITY\Servicio de red > Machine: ********** > Description:: Access to module dbo.spConfiguration is blocked because the > signature is not valid. > > Final Note: since then I have restarted the WSUS web service. > Any ideas will be welcomed > Regards > Miguel Sanchez > > >
From: Miguel Sanchez on 4 Sep 2009 10:33 Cliff: Should I just restore the SUSBD and log? Regards Miguel Sanchez "Cliff Galiher" <cgaliher(a)gmail.com> escribi� en el mensaje news:uRlYrDULKHA.1380(a)TK2MSFTNGP02.phx.gbl... > In this order: > > 1) Restore a backup again. Something didn't take. > > 2) Configure your UPS to auto-shutdown servers when below a certain > battery level. If properly configured, the server would've been > gracefully shut down even while the UPS was online BEFORE the power outage > because, as you pointed out, the battery level would've still been too > low. > > -Cliff > > > "Miguel Sanchez" <santaki2(a)hotmail.com> wrote in message > news:#r1VofRLKHA.4136(a)TK2MSFTNGP04.phx.gbl... >> Hi there: >> Setup >> WSUS 3.0 plain >> SBS server 2003 premium R2 >> >> This the Sequence that started the problems: >> a) Power outages one after the other. The UPS was too depleted in the >> second one to bring down the server gracefully >> b) SUSDB became corrupted so I had to use the backup >> c) WSUS was back with no problems >> d) Upgraded to WSUS 3.0 SP2 >> e) Decided to do a cleanup WSUS >> f) Stopped WSUS web service in IIS >> g) purged and deleted the uneeded patches >> h) applied patches to the server among them Windows Internal Database >> Service Pack 3 (KB955706 and Service Pack 3 de Microsoft SQL Server 2005 >> (KB955706) >> i) Restarted the server and voila: >> FIRST >> Event Origin: MSSQL$MICROSOFT##SSEE >> Event category : (2) >> Event Id: 17137 >> Date: 03/09/2009 >> Time: 09:18:00 p.m. >> User: NT AUTHORITY\Servicio de red >> Machine : ************* >> Description: Starting up database 'SUSDB'. >> >> THEN >> Event type: Error >> Event Origin: MSSQL$MICROSOFT##SSEE >> Event category : (2) >> Event Id: 33002 >> Date: 03/09/2009 >> Time: 09:24:43 p.m. >> User: NT AUTHORITY\Servicio de red >> Machine: ********** >> Description:: Access to module dbo.spConfiguration is blocked because the >> signature is not valid. >> >> Final Note: since then I have restarted the WSUS web service. >> Any ideas will be welcomed >> Regards >> Miguel Sanchez >> >> >>
From: Miguel Sanchez on 4 Sep 2009 14:11 Done, restored the susdb and log,the service is up and running after restarting the SQL server. I'm running the cleanup wizard and it is taking quite some time. Is it normal? Regards and Thank you Miguel "Cliff Galiher" <cgaliher(a)gmail.com> escribi� en el mensaje news:uRlYrDULKHA.1380(a)TK2MSFTNGP02.phx.gbl... > In this order: > > 1) Restore a backup again. Something didn't take. > > 2) Configure your UPS to auto-shutdown servers when below a certain > battery level. If properly configured, the server would've been > gracefully shut down even while the UPS was online BEFORE the power outage > because, as you pointed out, the battery level would've still been too > low. > > -Cliff > > > "Miguel Sanchez" <santaki2(a)hotmail.com> wrote in message > news:#r1VofRLKHA.4136(a)TK2MSFTNGP04.phx.gbl... >> Hi there: >> Setup >> WSUS 3.0 plain >> SBS server 2003 premium R2 >> >> This the Sequence that started the problems: >> a) Power outages one after the other. The UPS was too depleted in the >> second one to bring down the server gracefully >> b) SUSDB became corrupted so I had to use the backup >> c) WSUS was back with no problems >> d) Upgraded to WSUS 3.0 SP2 >> e) Decided to do a cleanup WSUS >> f) Stopped WSUS web service in IIS >> g) purged and deleted the uneeded patches >> h) applied patches to the server among them Windows Internal Database >> Service Pack 3 (KB955706 and Service Pack 3 de Microsoft SQL Server 2005 >> (KB955706) >> i) Restarted the server and voila: >> FIRST >> Event Origin: MSSQL$MICROSOFT##SSEE >> Event category : (2) >> Event Id: 17137 >> Date: 03/09/2009 >> Time: 09:18:00 p.m. >> User: NT AUTHORITY\Servicio de red >> Machine : ************* >> Description: Starting up database 'SUSDB'. >> >> THEN >> Event type: Error >> Event Origin: MSSQL$MICROSOFT##SSEE >> Event category : (2) >> Event Id: 33002 >> Date: 03/09/2009 >> Time: 09:24:43 p.m. >> User: NT AUTHORITY\Servicio de red >> Machine: ********** >> Description:: Access to module dbo.spConfiguration is blocked because the >> signature is not valid. >> >> Final Note: since then I have restarted the WSUS web service. >> Any ideas will be welcomed >> Regards >> Miguel Sanchez >> >> >>
From: Miguel Sanchez on 10 Sep 2009 15:56
It took 23hrs to complete, but now is running fine. Miguel "Miguel Sanchez" <santaki2(a)hotmail.com> escribi� en el mensaje news:%23CD5zsYLKHA.4316(a)TK2MSFTNGP04.phx.gbl... > Done, restored the susdb and log,the service is up and running after > restarting the SQL server. I'm running the cleanup wizard and it is taking > quite some time. Is it normal? > Regards and Thank you > Miguel > > "Cliff Galiher" <cgaliher(a)gmail.com> escribi� en el mensaje > news:uRlYrDULKHA.1380(a)TK2MSFTNGP02.phx.gbl... >> In this order: >> >> 1) Restore a backup again. Something didn't take. >> >> 2) Configure your UPS to auto-shutdown servers when below a certain >> battery level. If properly configured, the server would've been >> gracefully shut down even while the UPS was online BEFORE the power >> outage because, as you pointed out, the battery level would've still been >> too low. >> >> -Cliff >> >> >> "Miguel Sanchez" <santaki2(a)hotmail.com> wrote in message >> news:#r1VofRLKHA.4136(a)TK2MSFTNGP04.phx.gbl... >>> Hi there: >>> Setup >>> WSUS 3.0 plain >>> SBS server 2003 premium R2 >>> >>> This the Sequence that started the problems: >>> a) Power outages one after the other. The UPS was too depleted in the >>> second one to bring down the server gracefully >>> b) SUSDB became corrupted so I had to use the backup >>> c) WSUS was back with no problems >>> d) Upgraded to WSUS 3.0 SP2 >>> e) Decided to do a cleanup WSUS >>> f) Stopped WSUS web service in IIS >>> g) purged and deleted the uneeded patches >>> h) applied patches to the server among them Windows Internal Database >>> Service Pack 3 (KB955706 and Service Pack 3 de Microsoft SQL Server >>> 2005 (KB955706) >>> i) Restarted the server and voila: >>> FIRST >>> Event Origin: MSSQL$MICROSOFT##SSEE >>> Event category : (2) >>> Event Id: 17137 >>> Date: 03/09/2009 >>> Time: 09:18:00 p.m. >>> User: NT AUTHORITY\Servicio de red >>> Machine : ************* >>> Description: Starting up database 'SUSDB'. >>> >>> THEN >>> Event type: Error >>> Event Origin: MSSQL$MICROSOFT##SSEE >>> Event category : (2) >>> Event Id: 33002 >>> Date: 03/09/2009 >>> Time: 09:24:43 p.m. >>> User: NT AUTHORITY\Servicio de red >>> Machine: ********** >>> Description:: Access to module dbo.spConfiguration is blocked because >>> the signature is not valid. >>> >>> Final Note: since then I have restarted the WSUS web service. >>> Any ideas will be welcomed >>> Regards >>> Miguel Sanchez >>> >>> >>> > > |