Now I have these errors. ASP seems to be having trouble starting the app
pools?
Event ID 1000 Source Application Error
Faulting application w3wp.exe, version 6.0.3790.3959, faulting module
unknown, version 0.0.0.0, fault address 0x00430043.
Event ID 1073 Source ASP.NET
Failed to initialize the AppDomain:/LM/W3SVC/1/ROOT/SimpleAuthWebService
Event ID 1088 Source ASP.NET
Failed to execute request because the App-Domain could not be created.
Error: 0x80070005 Access is denied.
----- Original Message -----
From: James Kerr
To: NT System Admin Issues
Sent: Monday, July 14, 2008 9:37 AM
Subject: Re: WSUS Problem after dcpromo
I made all the changes you and Bonnie had suggested and I seem to have made
some progress but when I just rebooted the server I saw the following errors
in the app log.
The DSS Authentication Web Service is not working.
The SimpleAuth Web Service is not working.
The Client Web Service is not working.
The Server Synchronization Web Service is not working.
The API Remoting Web Service is not working.
The Reporting Web Service is not working.
Self-update is not working.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named pipe>]
----- Original Message -----
From: Ken Schaefer
To: NT System Admin Issues
Sent: Sunday, July 13, 2008 10:28 PM
Subject: RE: WSUS Problem after dcpromo
Hi,
Here are the steps to get WSUS v3 working after you DCPromo an existing box
that has WSUS v3 on it
http://groups.google.com.au/group/microsoft.public.windows.server.update_services/browse_thread/thread/68265a7f0f79d6c3/b088234586d39671?hl=en&lnk=gst&q=WSUS+3+stops+working+after+DC+Promo#b088234586d39671
The last post in the thread (from me) has the three things you need to do.
Cheers
Ken
From: Ken Schaefer [mailto:[EMAIL PROTECTED]
Sent: Saturday, 12 July 2008 3:50 PM
To: NT System Admin Issues
Subject: RE: WSUS Problem after dcpromo
You need to change the SQL Server service account (or the Windows Internals
database service account) to "LocalSystem"
That is the #1 problem with WSUS v3 breaking after you dcpromo an existing
WSUS server.
For the second error - just google. You just need to reset some permissions
for Network Service.
Cheers
Ken
From: James Kerr [mailto:[EMAIL PROTECTED]
Sent: Saturday, 12 July 2008 5:43 AM
To: NT System Admin Issues
Subject: WSUS Problem after dcpromo
I promoted a stand alone server that happend to also be our WSUS server
yesterday and something blew up. I cannot access the WSUS console and
computers trying to connect to it are being denied. I pasted the errors I am
seeing in the logs. The first two are related to starting the console and
WSUS and the other is from computers connecting to it for updates. Looks
like a permissions issue but has anyone on this list had this happen to them
before? I am going to start looking into more details now.
James
Event ID 7053 Source Windows Server Update
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.NullReferenceException -- Object reference not set to an instance of
an object.
Source
Microsoft.UpdateServices.UI.SnapIn
Stack Trace:
at
Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ResetScopeNode()
For more information, see Help and Support Center at
Event ID 7032 Source Windows Server Update
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.
Source
System
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.
Source
Microsoft.UpdateServices.Administration
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 ID 1309 Source ASP.NET 2.0xxx
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 7/11/2008 3:24:06 PM
Event time (UTC): 7/11/2008 7:24:06 PM
Event ID: 700aab84d3c94a06b7a280b3a1d83682
Event sequence: 1
Event occurrence: 1
Event detail code: 0
Application information:
Application domain:
/LM/W3SVC/1/ROOT/SimpleAuthWebService-4673-128602778458743806
Trust level:
Application Virtual Path: /SimpleAuthWebService
Application Path: c:\Program Files\Update
Services\WebServices\SimpleAuthWebService\
Machine name: xxxxxx
Process information:
Process ID: 3640
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
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://server/SimpleAuthWebService/SimpleAuth.asmx
Request path: /SimpleAuthWebService/SimpleAuth.asmx
User host address: 192.168.101.xxx
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 1
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
~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
