Posts Tagged ‘SBS 2003’

dyndns mailhop outbound setup for small business server 2003

September 28th, 2011

I had to configure a Small Business Server 2003 for the dyndns mailhop outbound service.  I did a lot of searching finding good instructions.  I found this post which had all the steps necessary for me.

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

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)

MSSQL$SBSMONITORING service consumes excessive memory.

April 23rd, 2008


MSSQL$SBSMONITORING service consumes excessive memory causing performance degradation or a large number of emails notifying of excessive memory usage.


sqlservr.exe excessive memory usage, MSSQL$SBSMONITORING excessive memory, MSSQL$SBSMONITORING memory leak , SBS MSSQL$SBSMONITORING memory leak


Microsoft Small Business Server 2003 SP2


After the small business server runs for a period of time one of the sqlservr.exe processes starts consuming excessive memory up to 1,500,000 K (1.5GB). The daily reports that SBS sends, has an allocated memory error with the following text:

A large amount of memory is committed to applications and processes. Consistently high memory usage can cause performance problems.

To determine which processes and applications are using the most memory, use Task Manager. Monitor the activity of these resources over a few days. If they continue to use a high level of memory and are less critical processes or services, try stopping and then restarting them.

You can disable this alert or change its threshold by using the Change Alert Notifications task in the Server Management Monitoring and Reporting taskpad.


There is not really a true fix for this. The following MS KB Article explains the theory behind how SQL allocates memory. this article doesn’t have the informaiton to actually change the memory thresholds. For most SBSs you should not need a large amount of memory dedicated to the monitoring service. Because of this it would be acceptable to set some thresholds for that service. I found a few pages that pointed to the following code to set the memory min and max.

**Note if you have a high traffic server you will want to research what allocations to make for this service. I set mine to a minimum of 0 and max of 512. The following code does set the memory allocation in MB.

Taken from:

Open a command prompt and enter the following (The switches are Case Sensitive):
osql -E -S sbsserver\

You will enter the osql command prompt. Run the commends below (replace
with the amount of memory):

EXEC sp_configure ‘show advanced options’, 1

EXEC sp_configure ‘min server memory’,

EXEC sp_configure ‘max server memory’,

After doing the above steps, you may run the commands to check the
configured memory usage:

EXEC sp_configure

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)