Renamed WSUS 3.0 Server getting Event Log error John M. Polston 5/25/2007 9:11:02 PM I've searched high and low for this so I apologize if it's already been asked and answered. I had to rename my WSUS 3.0 Server in which I am running the Windows Internal Database and now I am getting the following in the Application Event Log. Any ideas or fix would be greatly appreciated. Type: Failure Audit Source: MSSQL$MICROSOFT##SSEE Category: 4 Event ID: 18456 User: NETWORK SERVICE Description: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named pipe>]

RE: Renamed WSUS 3.0 Server getting Event Log error John M. Polston 5/30/2007 3:55:03 PM Anyone? "John M. Polston" wrote: [Quoted Text] > I've searched high and low for this so I apologize if it's already been asked > and answered. > > I had to rename my WSUS 3.0 Server in which I am running the Windows > Internal Database and now I am getting the following in the Application > Event Log. Any ideas or fix would be greatly appreciated. > > Type: Failure Audit > Source: MSSQL$MICROSOFT##SSEE > Category: 4 > Event ID: 18456 > User: NETWORK SERVICE > Description: > Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named pipe>] > >

Re: Renamed WSUS 3.0 Server getting Event Log error "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/30/2007 4:58:03 PM "John M. Polston" <JohnMPolston[ at ]discussions.microsoft.com> wrote in message news:54CFA7A4-4B45-41D3-9064-B7426383FD6D[ at ]microsoft.com... [Quoted Text] >> I've searched high and low for this so I apologize if it's already been >> asked >> and answered. >> >> I had to rename my WSUS 3.0 Server in which I am running the Windows >> Internal Database and now I am getting the following in the Application >> Event Log. Any ideas or fix would be greatly appreciated. >> >> Type: Failure Audit >> Source: MSSQL$MICROSOFT##SSEE >> Category: 4 >> Event ID: 18456 >> User: NETWORK SERVICE >> Description: >> Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named >> pipe>] > Anyone? Well... you renamed the WSUS 3.0 server.... no doubt that's the cause. The registry has a value "SqlServerName" in the key HKLM\Software\Microsoft\Update Services\Server\Setup which points to the database server using the environment variable %computername%. The question would be... did this environment variable get updated? Or. is this registry value using a hardcoded machine name? -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Renamed WSUS 3.0 Server getting Event Log error John M. Polston 5/30/2007 5:51:03 PM Lawrence, below is the value in the registry that I have. SqlServerName: %computername%\MICROSOFT##SSEE The SqlUserName value is blank/null. JP "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "John M. Polston" <JohnMPolston[ at ]discussions.microsoft.com> wrote in message > news:54CFA7A4-4B45-41D3-9064-B7426383FD6D[ at ]microsoft.com... > > >> I've searched high and low for this so I apologize if it's already been > >> asked > >> and answered. > >> > >> I had to rename my WSUS 3.0 Server in which I am running the Windows > >> Internal Database and now I am getting the following in the Application > >> Event Log. Any ideas or fix would be greatly appreciated. > >> > >> Type: Failure Audit > >> Source: MSSQL$MICROSOFT##SSEE > >> Category: 4 > >> Event ID: 18456 > >> User: NETWORK SERVICE > >> Description: > >> Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named > >> pipe>] > > > Anyone? > > Well... you renamed the WSUS 3.0 server.... no doubt that's the cause. > > The registry has a value "SqlServerName" in the key > HKLM\Software\Microsoft\Update Services\Server\Setup > which points to the database server using the environment variable > %computername%. > > The question would be... did this environment variable get updated? > Or. is this registry value using a hardcoded machine name? > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > >

Re: Renamed WSUS 3.0 Server getting Event Log error "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/10/2007 5:03:31 AM "John M. Polston" <JohnMPolston[ at ]discussions.microsoft.com> wrote in message news:6C4785C2-B49E-40F5-AD5E-83843452364B[ at ]microsoft.com... [Quoted Text] >> >> I had to rename my WSUS 3.0 Server in which I am running the Windows >> >> Internal Database and now I am getting the following in the >> >> Application >> >> Event Log. Any ideas or fix would be greatly appreciated. >> >> Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named >> >> pipe>] >> Well... you renamed the WSUS 3.0 server.... no doubt that's the cause. >> >> The registry has a value "SqlServerName" in the key >> HKLM\Software\Microsoft\Update Services\Server\Setup >> which points to the database server using the environment variable >> %computername%. >> >> The question would be... did this environment variable get updated? >> Or. is this registry value using a hardcoded machine name? > Lawrence, below is the value in the registry that I have. > > SqlServerName: %computername%\MICROSOFT##SSEE > > The SqlUserName value is blank/null. The other possibility here is that the username ASPNET and/or the group "WSUS Administrators" are tied to the old machinename in the database . Use the following script to remove and re-add the ASPNET and WSUS Administrators groups. Then run the upgrade again. You will need to replace <DBLocation> with the folder where the database is installed, and <ContentDirectory> with the local storage folder. sqlcmd.exe -S <DBLocation> -E -Q "USE SUSDB DECLARE [ at ]asplogin varchar(200) SELECT [ at ]asplogin=name from sysusers WHERE name like '%ASPNET' EXEC sp_revokedbaccess [ at ]asplogin" sqlcmd.exe -S <DBLocation> -E -Q "USE SUSDB DECLARE [ at ]wsusadminslogin varchar(200) SELECT [ at ]wsusadminslogin=name from sysusers WHERE name like '%WSUS Administrators' EXEC sp_revokedbaccess [ at ]wsusadminslogin" sqlcmd.exe -S <DBLocation> -E -Q "USE SUSDB DECLARE [ at ]asplogin varchar(200) SELECT [ at ]asplogin=HOST_NAME()+'\ASPNET' EXEC sp_grantlogin [ at ]asplogin EXEC sp_grantdbaccess [ at ]asplogin EXEC sp_addrolemember webService,[ at ]asplogin" sqlcmd.exe -S <DBLocation> -E -Q "USE SUSDB DECLARE [ at ]wsusadminslogin varchar(200) SELECT [ at ]wsusadminslogin=HOST_NAME()+'\WSUS Administrators' EXEC sp_grantlogin [ at ]wsusadminslogin EXEC sp_grantdbaccess [ at ]wsusadminslogin EXEC sp_addrolemember webService,[ at ]wsusadminslogin" sqlcmd.exe -S <DBLocation> -E -Q "backup database SUSDB to disk=N'<ContentDirectory>\SUSDB.Dat' with init" -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....