Error 18456 Wsus
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: WSUS
Sql Error 18456 Wsus
console & service can't start. "Reason: Failed to open wsus database login failed for user the explicitly specified database 'SUSDB'" Windows Server > WSUS Question 0 Sign in to vote kb3148812 Our WSUS server (Windows Server 2012 R2) hanged when it was installing updates on itself. I rebooted it in a harsh way, it started normally
Uninstall Kb3148812
and finished installing the updates. However, now I can't start the WSUS management console due to a connection error. The WSUS server service itself doesn't start as well. The Application server contains multiple events18456, sourceMSSQL$MICROSOFT##WID, message "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified
Kb3159706 Wsus
database 'SUSDB'. [CLIENT:
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help wsus login failed for user 'nt authority network service' Ask a Question Ask for Help Receive Real-Time Help
Kb3148812 Wsus
Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand download kb3159706 Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > https://social.technet.microsoft.com/Forums/office/en-US/233a6b37-5919-4a9e-9538-aa0e7bd7111a/wsus-console-service-cant-start-reason-failed-to-open-the-explicitly-specified-database?forum=winserverwsus WSUS 3 SP1 Event ID:18456 Login failed for user 'NT AUTHORITY\NETWORK SERVICE' Want to Advertise Here? Solved WSUS 3 SP1 Event ID:18456 Login failed for user 'NT AUTHORITY\NETWORK SERVICE' Posted on 2011-01-27 MS SQL Server 2005 Windows Server 2003 1 Verified Solution 25 Comments 6,324 Views Last Modified: 2012-05-10 https://www.experts-exchange.com/questions/26775307/WSUS-3-SP1-Event-ID-18456-Login-failed-for-user-'NT-AUTHORITY-NETWORK-SERVICE'.html I am running WSUS 3 SP1 and have no issues until just yesterday. I noticed yesterday that I could not open the WSUS admin console (MMC). It errored out with the following informaiton: --------------------------------------------------------------------------------------- The WSUS administration console was unable to connect to the WSUS Server Database. Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL. System.Data.SqlClient.SqlException -- Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Source .Net SqlClient Data Provider Stack Trace: at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException) at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet) at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, UpdateScope updatesToInclude, ComputerTargetScope computersToInclude, UpdateServerStatusPropertiesToGet propertiesToGet) at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetReplicaStatus(UpdateSources updateSources) at Microsoft.UpdateServices.UI.SnapIn.Common.CachedUpdateServerStatus.GetFreshObjectForCache() at Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.RefreshCache() at Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.GetFromCache() at Microsoft.UpdateServices.UI.SnapIn.Pages.ServerSummaryPage.backgroundWorker_DoWork(Object sender, DoWor
still can't get a successful ConfigMgr software update sync from my WSUS server. The latest issue is now I couldn't access the Windows Internal Database to run any kind of maintenance script. When trying http://www.adamtheautomator.com/solution-unable-connect-wsus-database/ to connect either via sqlcmd or Management Studio via my logged in Windows credentials I was receiving the error system cannot find the file specified when attempting to connect with the server name nb:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query http://www.wsus.info/index.php?showtopic=8415 and the error login failed when connecting with the server name nb:\\.\pipe\MICROSOFT\##WID\tsql\query . Also, event ID 18456 - Token-based server access validation failed with an infrastructure error… was being generated in the Application event error 18456 log along with Login failed for user…. server is in script upgrade mode in the C:\Windows\WID\Log\error.log.Microsoft support suspected problems with the WID so we had to get SQL access to it. To anyone that's trying to access the WSUS Windows Internal Database via SQL Server Management Studio Express and cannot get connected, here's what I had to go through:Download and install SQL Server Management Studio Express.Open error 18456 wsus up SQL Server Configuration Manager and go to Native Client 11.0 Configuration -> Client Protocols and ensure TCP/IP is enabled.Connect to database on command line via sqlcmd -S np:\\.\pipe\MICROSOFT##WID\tsql\queryExecute the queryPgSQL SELECT session_id from sys.dm_Exec_requests where status <> 'sleeping' and session_id <> @@spid SELECT @@spid --This gets the allowed user SPID sp_who 53 --The 53 was my @@spid. This is used to figure out the account that has access123SELECT session_id from sys.dm_Exec_requests where status <> 'sleeping' and session_id <> @@spidSELECT @@spid --This gets the allowed user SPIDsp_who 53 --The 53 was my @@spid. This is used to figure out the account that has accessFor some reason, this fixed the connection issue and we were now able to connect!AboutLatest Posts Adam BertramChief Automator at Adam the Automator, LLCAdam Bertram is an independent consultant, technical writer, trainer and presenter. Adam specializes in consulting and evangelizing all things IT automation mainly focused around Windows PowerShell. Adam is a Microsoft Windows PowerShell MVP, 2015 powershell.org PowerShell hero and has numerous Microsoft IT pro certifications. He authors IT pro course content for Pluralsight, is a regular contributor to numerous print and online publications and presents at various user groups and conferences.You can fin
2 Server issues View New Content Page 1 of 1 You cannot start a new topic This topic is locked Can not connect to WUS 3.0 server Can not connect to WUS 3.0 server #1 Wade Hampton Newbie Group: New Members Posts: 2 Joined: 19-Sep-06 Posted 19 Sep 2006, 09:31 I sucessfully installed WUS 3.0 using the MSDE SQL. It is installed on a Server 2003 Standard Ed. machine. Approx. 24 hrs after the install, I can no longer connect to the server. When the MMC is launched it does not automatically connect to my WUS server and when I attempt to connect it says "Can not connect to "server name" . The server may be using another port or different Secure Socket Layer setting" I've tried changing the port number from 443 to 80 with the same results. Has anyone else experienced this? 0 Back to top of the page up there ^ MultiQuote Reply #2 jb8578 Member Group: Regular Members Posts: 42 Joined: 26-Jul-06 Posted 19 Sep 2006, 13:10 Did you set it up to use port 80 or port 8530 ? The default is port 80. Did you set it up to use SSL? If not then you need to check the box that says "do not use ssl...." If it cant resolve the server name, that might be a DNS issue. I setup the server and WSUS3 on the same day and had to enter a static mapping in DNS for it to connect. 0 Back to top of the page up there ^ MultiQuote Reply #3 Sky147 Newbie Group: New Members Posts: 2 Joined: 20-Sep-06 Posted 21 Sep 2006, 02:57 I have the same problem after upgrading from WSUS 2.0 to WSUS 3.0 I get the error "Cannot connect to 'Server'. The server may be using another port or different Secure Sockets Layer setting." I am sure that I configured port 80 and also have put the correct accounts in the WSUS administrator group. Any help would be appreciated 0 Back to top of the page up there ^ MultiQuote Reply #4 Sky147 Newbie Group: New Members Posts: 2 Joined: 20-Sep-06 Posted 21 Sep 2006, 04:32 Sky147, on Thu 21st Sep 2006, 10:57 am, said:I have th