Posts Tagged ‘WSUS’

How to move WSUS MSDE database files to another drive using OSQL

September 14th, 2010


How to move WSUS MSDE database files to another drive using OSQL


Small Business Server 2003


The WSUS DB is getting too large for the drive it is on and you want to move it.


This will work for any MSDE database, you just need to know the name of the DB, and stop the relevant services tied to it (not SQL, of course!)

Copy this to a batch file or to a command line.  This makes the assumptions:

  • MSDE install is in default location, and instance was named WSUS
  • You want to move the DB to directory d:\wsusdb

If these are not true you need only tweak the commands below to match your end goal.

net stop “update services”
net stop w3svc
cd “C:\Program Files\Microsoft SQL Server\MSSQL$WSUS\Binn”
osql -E -S %computername%\wsus -Q “exec sp_detach_db ‘SUSDB'”
md d:\WSUSDB
move “C:\Program Files\Microsoft SQL Server\MSSQL$WSUS\Data\SUS*.*” d:\wsusdb
osql -E -S %computername%\wsus -Q “exec sp_attach_db @dbname=N’SUSDB’, @filename1=N’D:\WSUSDB\SUSDB.mdf’, @filename2=N’D:\WSUSDB\SUSDB_log.ldf'”
net start “update services”
net start w3svc

taken from:

Tags: ,
Posted in Uncategorized | Comments (0)

WSUS 2.0 and WSUS 3.0 Crash Consistently

March 29th, 2007


WSUS 2.0 and WSUS 3.0 Crash Consistently
Keywords: Winodws Server Update Services 2 or 3, Windows Software Update Services, WSUS, WSUS 2, WSUS 3, WSUS Self-Update , WSUS SimpleAuth Web Service, WSUS Client Web Service


Windows Server 2003 current service pack and all patches


After installing WSUS 2.0 or 3.0 the service seems to work for a short period of time and then “hang”. If you restart IIS and the Update Service it will allow clients to connect to WSUS for another short period of time. In your application event logs you get the following Errors:

WSUS 3.0

Event 12002 The Reporting Web Service is not working.
Event 12032 The Server Synchronization Web Service is not working.
Event 12022 The Client Web Service is not working.
Event 12042 The SimpleAuth Web Service is not working.
Event 12052 The DSS Authentication Web Service is not working.
Event 13042 Self-update is not working.

WSUS 2.0
Event 506 The SelfUpdate Tree is not working. Clients may not be able to update to the latest WUA client software and communicate with the WSUS Server.

Additionally if you look in your security event logs you will see the following:

Failure Audit | Security | Logon/Logoff | Event ID 534 | User : System |

Logon Failure:
Reason: The user has not been granted the requested
logon type at this machine
Logon Type: 8
Logon Process: Advapi
Authentication Package: Negotiate
Workstation Name: YOURDOMAIN
Caller Domain: NT AUTHORITY
Caller Logon ID: (0x0,0x3E4)
Caller Process ID: 1612


If you problem is exactly as described above then the problem is that NETWORK SERVICE does not have the rights to log on as a service in the comptuers Local Security Policy.
To fix this you will need to determine if the group policy is being set at the domain level or at the machine level. The easiest way to do this is to do the following:

1. Open the control panel
2. Open Administrative Tools
3. Execute “Local Security Policy”
4. Navigate to: Local Policies -> User Rights Assignment -> Log on as a service
5. Double-click “Log on as a service” to open its properties
6. Is NETWORK SERVICE listed? If yes this solution will not fix your problem. If no continue.
7. You will want to click “Add User or Group” and then type Network Service. It would be good if you also added ASPNET if it is missing.
8. If “Add User or Group” is greyed out, this is because the policy is being set through the domain and is being inherited. You will want to use Active Directory Users and Computers or Group Policy Management to edit the policy that your server is inheriting this from.
9. After you add NETWORK SERVICE, you should reboot the computer and everything should work. When you reboot go back in and verify that NETWORK SERVICE is sitll in there.

Note: NETWORK SERVICE also should be delegated the right “Replace a process level token”.

Tags: , ,
Posted in Uncategorized | Comments (0)

Windows Update Error number: 0x8024400A

January 17th, 2007


Windows Update Error number: 0x8024400A


Windows Server 2003 Standard Edition, SP1


Windows update would not run and the computer would not send a status report to a WSUS server. When Visiting Windows Update to get updates manually it would give the following page/error:

[Error number: 0x8024400A]
Windows Update has encountered an error and cannot display the requested page. You may find the following resources helpful in resolving the problem:


I found a resource that solved my problem:

From the command prompt:
regsvr32 MSXML3.DLL

Then go into services and restart the Automatic Updates service.

After Automatic Updates successfully restarts open IE and try windows updates again.

Other wsus problems:

WU client failed Searching for update with error 0x80244010

Solution: Clear all browser history, including cookes, temporary internet files, forms, etc.

Also, Found an article that said there is a percentage of comptuers ~20% that there is an unknown error with clients scanning into the wsus server due to compression on IIS 6.0 ‘s part. Error WU client failed Searching for update with error 0x8024400a is thrown in the c:\windows\windowsupdate.log file. If you go to c:\windows\system32\inetsrv on the WSUS server and rename the suscomp.dll to suscomp.dll.old, then restart IIS clients will randomly start scanning in.

If none of that works try each of these from the command prompt and restart :

regsvr32 wuapi.dll
regsvr32 wuaueng.dll
regsvr32 wuaueng1.dll
regsvr32 wucltui.dll
regsvr32 wups.dll
regsvr32 wups2.dll
regsvr32 wuweb.dll

Still not working?

Stop the Automatic Updates Service
Delete the folder c:\windows\SoftwareDistribution
rename the windows update log: c:\windows\windowsupdate.log to windowsupdate.log.old
Start the Automatic Updates Service
Go to a command prompt and type: wuauclt /detectnow

Tags: ,
Posted in Uncategorized | Comments (0)