PostGreSQL not starting (or WSUS server) after DNS issue

Running Windows 2003 servers in domain environment.   Did have problem where DNS was playing up because servers had somehow got pointed to a linux DNS server instead of to themselves.  Resolved that and DNS now working fine.

Two follow up problems though.   Running Media Wiki on PostgreSQL - PostGreSQL now not starting.   In PGAdmin, error when trying to start is "Error connecting to the server : fatal : the database is shutting down".

The service is installed, but not started - if I try and start it in the Services manager, it says "The PostGreSQL 8.3 service started and then stopped"

I think I am at the point (unless someone else has an idea) of uninstalling and reinstalling PostGreSQL.   Problem is that I can't find my mediawiki db to make sure that a) it doesn't get uninstalled, or b) so I can make a copy of it first

Second problem is my WSUS server (on same box) won't start, and the console says "Error connecting to WSUS server"   Click Reset Server Node to connect to the server again.   No response.

Event Viewer error follows:


The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,

Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.

System.IO.IOException -- The handshake failed due to an unexpected packet format.


Stack Trace:
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Net.TlsStream.CallProcessAuthentication(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **

System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.


Stack Trace:
   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

For more information, see Help and Support Center at



Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 5/8/2009 9:40:44 AM
Event time (UTC): 5/7/2009 11:40:44 PM
Event ID: 6bcf01fc5b054beba1d9041a0e1b7240
Event sequence: 1
Event occurrence: 1
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/1/ROOT/ApiRemoting30-470-128862132446562500
    Trust level:  
    Application Virtual Path: /ApiRemoting30
    Application Path: C:\Program Files\Update Services\WebServices\ApiRemoting30\
    Machine name: CAN01
Process information:
    Process ID: 4736
    Process name: w3wp.exe
Exception information:
    Exception type: HttpException
    Exception message: The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.
Request information:
    Request URL: http://can01/ApiRemoting30/WebService.asmx 
    Request path: /ApiRemoting30/WebService.asmx
    User host address:
    Is authenticated: False
    Authentication Type:  
    Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
    Thread ID: 7
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: False
    Stack trace:    at System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection)
   at System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags)
Custom event details:

For more information, see Help and Support Center at

Who is Participating?
mcsweenConnect With a Mentor Sr. Network AdministratorCommented:
The last couple event errors relating to WSUS lead me to belive "Network Service" which is what WSUS is running as does not have write permissions to the directories it needs.  Try changing the logon name for all WSUS services to a local admiistrator on that server and see if you can get the services to start.  If that works then I would back track to see what permissios are needed on which directories to get it running correcty; or  you could just leave the local admin running the service.

**As a major security concern make sure this administrative account is an admin only on the server running WSUS, do not make this a Domain Administrator.  If fact if you are not accessing resources on another box with WSUS (all content is stored locally) I woud use a local account instead of a domain account.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.