|
|
Hello,
I currently cannot manage the WSUS on my machine. Each time I try to
connect to the machine, the WSUS management console reports that it
cannot connect and that it might help to check if the SQL-Server is running.
The eventlog shows the following error frequently:
Source: MSSQL$MICROSOFT##SSEE
Eventid: 18456
User: NT-AUTORITÄT\NETZWERKDIENST (should be NT-AUTHORITY\NETWORK SERVICE)
Description: Login failed for user 'NT-AUTORITÄT\NETZWERKDIENST'.
[CLIENT: <named pipe>]
I tried to rerun the setup, but it fails with the following log:
-----------------------------------LOG--------------------------------
2008-12-21 16:03:31 Success MWUSSetup
Validating pre-requisites...
2008-12-21 16:03:31 Error MWUSSetup
ExecuteQuery: Failed to execute SQL query USE SUSDB IF EXISTS (select *
FROM master..sysdatabases WHERE name= N'SUSDB' AND suser_sname(sid) is
null) EXEC dbo.sp_changedbowner N'TEST\frad' (Error 0x80040E14)
2008-12-21 16:03:31 Error MWUSSetup
ExecuteQueryGetNoResults: Failed to execute query USE %s IF EXISTS
(select * FROM master..sysdatabases WHERE name= N'%s' AND
suser_sname(sid) is null) EXEC dbo.sp_changedbowner N'%s' (Error 0x80040E14)
2008-12-21 16:03:31 Error MWUSSetup
CUpgradeDriver::PerformPreSetupActions: Failed to reset database owner
name for SUSDB to owner TEST\frad (Error 0x80040E14)
2008-12-21 16:03:31 Error MWUSSetup
CSetupDriver::LaunchSetup: Failed to perform pre-setup actions (Error
0x80040E14)
2008-12-21 16:03:31 Error MWUSSetup
CProgressManager::EnableCancel: GetDlgItem returning error (Error
0x80070578: Ungültiges Fensterhandle)
-----------------------------------LOG--------------------------------
I have no idea how to repair this. Can somebody help?
Thanks,
Florian
|
|
"Florian Rittmeier" <program[ at ]web.de> wrote in message
news:eXgG%2373YJHA.1964[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text] > Hello,
>
> I currently cannot manage the WSUS on my machine. Each time I try to
> connect to the machine, the WSUS management console reports that it cannot
> connect and that it might help to check if the SQL-Server is running.
>
> The eventlog shows the following error frequently:
> Source: MSSQL$MICROSOFT##SSEE
> Eventid: 18456
> User: NT-AUTORITÄT\NETZWERKDIENST (should be NT-AUTHORITY\NETWORK SERVICE)
> Description: Login failed for user 'NT-AUTORITÄT\NETZWERKDIENST'. [CLIENT:
> <named pipe>]
You don't say in your post whether this is a *NEW* installation, or an
installation that used to work, but doesn't work now.
If you recently changed the language of the server, this could account for
the "NT-AUTORITÄT\NETZWERKDIENST" account being non-existent, whereas the
English "NT-AUTHORITY\NETWORK SERVICE" account is likely the account created
in the database. If the English-language version of WSUS were installed,
then the English account would have been created, and no account for the
non-English account would exist.
So, if that were the case, the simplest solution would be to change the
language back to English.
Although, I would also expect both accounts to have the same =SID=, in which
case language should not be an issue - but it may be. In fact, we do know
that changing language declarations on an existing WSUS Server will break
the server, and the repair is to reset the server to English (where an
English WSUS was installed).
If you really need this server to run in non-English mode, then you should
still switch back to English, perform a complete uninstall of WSUS
(including the WID which is documented in Appendix A of the Operations
Guide) and IIS. Change the language, and then reinstall IIS and WSUS.
> I tried to rerun the setup, but it fails with the following log:
I would expect the setup to fail, given that the installation already
exists, particularly that the database exists. Notice your error is not that
the database doesn't exist, but rather that the *account* does not exist.
Trying to reinstall on an existing database server will fail, if the
installer cannot make a successful connection to the current database --
particularly if the TEST\frad account does not have access to the database
and/or is not a member of the local Administrators account.
> Validating pre-requisites...
> ExecuteQuery: Failed to execute SQL query
> ExecuteQueryGetNoResults: Failed to execute query
> CUpgradeDriver::PerformPreSetupActions: Failed to reset database owner
> name for SUSDB to owner TEST\frad (Error 0x80040E14)
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
Hello Lawrence,
[Quoted Text] > You don't say in your post whether this is a *NEW* installation, or an
> installation that used to work, but doesn't work now.
Sorry, this is an installation that has worked before. Prior to the
first occurrence of the problem a colleauge copied the WSUS folder to a
seperate disk, which is now mounted at the old place. This was done to
increase the disk space of the system.
> So, if that were the case, the simplest solution would be to change the
> language back to English.
Sorry again, we never changed any language settings. The system language
is german. I only tried to translate the account name as I assume that
english is the expected language for this ng. :-)
>> I tried to rerun the setup, but it fails with the following log:
>
> I would expect the setup to fail, given that the installation already
> exists, particularly that the database exists. Notice your error is not
> that the database doesn't exist, but rather that the *account* does not
> exist. Trying to reinstall on an existing database server will fail, if
> the installer cannot make a successful connection to the current
> database -- particularly if the TEST\frad account does not have access
> to the database and/or is not a member of the local Administrators account.
>
>> Validating pre-requisites...
>
>> ExecuteQuery: Failed to execute SQL query
>
>> ExecuteQueryGetNoResults: Failed to execute query
>
>> CUpgradeDriver::PerformPreSetupActions: Failed to reset database owner
>> name for SUSDB to owner TEST\frad (Error 0x80040E14)
I assumed that the setup might help to perform a repair installation,
which hopefully corrects the permissions (of folders and database). The
TEST\frad account is domain admin (and therefore local admin). I assumed
that it should have the required priviledges to reset the database
owner. Uninstall is also not possible, that setup just reports that an
error occured (not giving any hint or logfile).
Do you have any suggestions how to proceed and get a working WSUS back?
Regards,
Florian
|
|
"Florian Rittmeier" <program[ at ]web.de> wrote in message
news:el3PfkJZJHA.6108[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] >> You don't say in your post whether this is a *NEW* installation, or an
>> installation that used to work, but doesn't work now.
> Sorry, this is an installation that has worked before. Prior to the first
> occurrence of the problem a colleauge copied the WSUS folder to a seperate
> disk, which is now mounted at the old place. This was done to increase the
> disk space of the system.
"Prior to the first occurrence.." is a BIG clue. When something that work,
breaks, it's almost always attributable to something that somebody did, and
in this case, you have the added benefit of having already identified that
event (most scenarios I've seen are oblivious to what caused the change in
behaviror).
When issues involve copying/moving the WSUSContent folder, it's almost
always attributable to incorrect permissions on the new "WSUSContent"
folder. In addition, we also have a scenario where we've introduced the
variable of a mounted filesystem, which is not a scenario that's been tested
(to my knowledge), nor is it a scenario that's really needed.
Unmount the volume. Assign a drive letter to the physical volume containing
the WSUSContent folder, and use 'wsusutil movecontent -skipcopy' to reset
WSUS to point to the actual location of the new content. (There's no need to
use mounted volumes to "fool" WSUS into thinking the content is in the same
location it used to be.) Then refer to the WSUS Operations Guide to obtain
the correct permissions settings for the WSUSContent folder, subfolders, and
files.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
|