https://support.microsoft.com/en-us/kb/3159706 28 Pimiento OP s3hubert May 12, 2016 at 5:33 UTC 1st Post Hi Guys, Many thanks for the info ken2johnson, works like a charm ! Follow the post install instructions in this link and WSUS should be up and running again. Thanks ahead of time Comment by fasteddie565-- December 22, 2009 # Reply Which download are you refering to? I despise MS. http://webinweb.net/connect-to/wsus-unable-to-connect-to-sql-database.html
Follow the post install instructions in this link and WSUS should be up and running again. Environment WSUS Cause Restructures the SQL database Resolution Option 1:Revert back or remove KB update. WSUS stopped working Best Answer Sonora OP ken2johnson May 10, 2016 at 6:58 UTC KB3148812 was recently replaced with KB3159706. Connection string: Data Source=GTCMPM;Initial Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100 For more information, see Help and Support Center at http://go.microsoft....link/events.asp.
Which likely has left the system in an inconsistent, if not unstable state. Browse other questions tagged sql-server database sql wsus or ask your own question. Implement SBS 2011 Moved the company from SBS 2003 to SBS 2011. Like many others, I was surprised by KB3148812 (Update enables ESD decryption provision in WSUS in Windows Server 2012 and Windows Server 2012 R2), which broke my WSUS.
Check out this article regarding the above issue: http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/e918a191-ef6d-4c4b-b83a-7a4ae20a5217View this "Best Answer" in the replies below » 5 Replies Mace OP Best Answer Denis Kelley Dec 28, Vince Comment by Vince-- April 22, 2009 # Reply Nice to hear you solved the problem :) Cheers! Either the database is not available or you do not have the correct privileges to access the database. Connect To Windows Internal Database Server 2012 Given the above "successful" procedure, I would suggest that KB2720211 still needs to be installed so that the database gets the appropriate schema/certificate updates, and make note of the procedure discussed
Same thing happens after install. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. at Microsoft.UpdateServices.Internal.ResetStateMachineAgent.ProcessSqlException(Int32& numRetry, Int32 sqlExceptionNumber, String errorMessage) at Microsoft.UpdateServices.Internal.ResetStateMachineAgent.WakeUpWorkerThreadProc() at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) Publishing operation failed because the console and remote server versions do not matchMicrosoft SQL Server 2008 System CLR Types are missing during installationMicrosoft updates only arrive once a monthMigrate a local Reply ↓ Markus Wochnik June 17, 2016 at 23:57 Thank you for this!I almost cried because of that problem :O Reply ↓ Roul June 18, 2016 at 11:26 wow, the gratest
Review of my T-shirt design Why are Stormtroopers stationed outside the Death Star near the turbolaser batteries adjacent to Bay 327? Connect To Windows Internal Database Sql Management Studio Same thing happens after install. Right-click on SUSDB –> Tasks –> Detach 4. The choices are SQL Server 2000 (80), SQL Server 2005 (90), or SQL Server 2008 (100).
All this gives us is the WHAT. :-) However, per this guidance, let's start by running a wsusutil checkhealth and then looking in the AppEventLog again for anything else of relevance. 0 One last thing that is odd is I didn't see a SQL entry in the services list at all. Connect To Wsus Database With Management Studio Click OK. 6. Wsus Login Failed For User 'nt Authority Network Service' share|improve this answer answered Jun 26 '09 at 15:00 Aaron Alton 875810 add a comment| up vote 0 down vote I love those Microsoft messages: "Try starting SQL Server".
Reason: Failed to open the explicitly specified database 'SUSDB'. have a peek at these guys Comment by Stefan-- August 2, 2010 # Reply Worked like a charm. But what happens if you change your mind later and you want to change the location of that internal database to a different drive? I am running Windows Server 2003 Standard Edition SP1 with WSUS 2.0 supported by MSDE thats built-in to WSUS 2.0. Can't Connect To Wsus Database
To change the compatibility level, select a different option from the list. Adam is a Microsoft Windows PowerShell MVP, 2015 powershell.org PowerShell hero and has numerous Microsoft IT pro certifications. Reply Adam Bertram February 1, 2016 2:13 pm Thanks, fixed! check over here Worked like a charm!
It has always worked great until now so I'm almost sure it is related to the move to hyper v somehow. Susdb Recovery Pending Wsus Comment by Anthony-- August 31, 2009 # Reply Thanks Anthony! So now how did I fix this?
If you believe you have received this message in error, please check with your system administrator For some reason, when my WSUS server applied patches to itself, that is the error Usually: %Program Files%\Microsoft SQL Server\90\Tools\binn. 2. This server supports version 612 and earlier. Connect To Wsus 2012 Database With Management Studio Could not open new database ‘SUSDB'.
The login failed. How would people living in eternal day learn that stars exist? QuoteError connecting to the Windows Server Update Services database There was an error connecting to the Windows Server Update Services database. this content Notify me of new posts via email.
Back to the instance connection. Not the answer you're looking for? asked 7 years ago viewed 14104 times active 6 years ago Blog Stack Overflow Gives Back 2016 Related 0WSUS appears to be functioning, however errors are reported in Application Log (DSS Check out this article regarding the above issue: http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/e918a191-ef6d-4c4b-b83a-7a4ae20a52172 Datil OP Jstear Dec 28, 2012 at 7:00 UTC Looks like you don't have appropriate permissions to access
Contact Me Suggestions? Check the options for “Drop Connections” to remove all active connections to that DB. I was able to connect to the sql server by omiting the \mssqlserver portion and just typing in the name of my server Back to top Back to Configuration Manager 2012 Worked perfectly with just a downtime of a minute :) Thanks!