Archive for March, 2010
Event Type: Error
Event Source: TermServDevices
Event Category: None
Event ID: 1114
Description: Error communicating with the Spooler system service. Open the Services snap-in and confirm that the Print Spooler service is running.
These errors are generally nothing to worry about. However if you wish to resolve them you have two options. Typically there is no need for a server to have this enabled unless you need to print to a local printer from a remote desktop session. So the first option is to disable Windows Printer Mapping for Terminal Services:
1. Click Start -> click Run -> enter “tscc.msc” without quotes -> click OK
2. Click Connections -> double click RDP-Tcp
3. Click the Client Settings tab
4. Place a check next to “Windows printer mapping” under the “Disable the following” heading.
5. Click Apply -> Close
The second option to resolve these errors is to start the Print Spooler service so Terminal Services can communicate with it properly:
1. Click Start -> Run -> enter “services.msc” without quotes -> Click OK
2. Scroll down until you find “Print Spooler”
3. If the startup type is Manual or Disabled, right click the service -> Properties
4. Click the Start button -> Click OK
You may run across the situation where SQL has been locked down to the “sa” user and the password was lost/forgotten. In this situation you can start SQL in single user mode which allows you to connect with Windows authentication again.
1. Open the Configuration Manager tool from the “SQL Server 2005| Configuration” menu
2. Stop the SQL Server Instance you need to recover
3. Right click the MSSQL Server instance and choose properties
4. Navigate to the “Advanced” tab, and add “;–m” to the end of the list in the “Startup parameters” option
* NOTE: make sure there is no space between “;” and “-m”, the registry parameter parser is sensitive to such typos. You should see an entry in the SQL Server ERRORLOG file that says “SQL Server started in single-user mode.”
5. Click the “OK” button and restart the SQL Server Instance
6. You will now be able to access SQL using Windows authentication to reset the “sa” user’s password.
7. Finally Remove the “;-m” from the startup parameters using the Configuration Manager and restart SQL
By default IIS 7 does not allow ISAPI and CGI through .Net 1.1. So if you are working with older code on IIS 7 you will need to follow these steps to resolve the issue:
1. Open IIS and click the server name
2. Double click “ISAPI and CGI Restrictions”
3. Right click ASP.NET v1.1 and select “allow”
The HTTP redirection role is not installed in Server 2008 by default. However this can be installed very easily using the following steps:
1. Click Start -> Administrative Tools -> Server Manager
2. Select “Roles” from the left
4. Check the box next to “HTTP Redirection”
5. Click Next -> Install
Now the “HTTP Redirect” heading will be available in IIS under the server name and under each individual site. There is no need to restart IIS to apply this change.
For instructions on creating a redirect with the newly installed role please refer to the following article:
Setup a Redirect in IIS 7