This can happen when files/directories have the “read only” attribute associated with them. There are many causes for this so I won’t go into that. However there is a quick way to fix this using DiskPart utility that is built in to Windows by default.

1. First open a command prompt. (Start -> Run -> cmd).

2. Type the command “diskpart” without the quotes

3. Once you see the “DISKPART>” prompt you will need to determine which disk the affected files are on. To do this type the following command at the DISKPART prompt.

list disk

4. From the image you can see that this computer only has one disk “0”. Select this disk with the following command and make sure to replace the # with the appropriate drive number.

select disk #

5. Type the following command to print the volumes contained on the server. My example only has one.

detail disk

6. Select the appropriate volume with this next command, replacing the # with your specific volume number from step 5.

select volume #

7. Lastly type the following command to clear the read only attributes from the affected fiels.

Attributes volume clear readonly

1. Open Terminal Services configuration:
Start -> Administrative tools -> Terminal Services configuration

2. Right click “RDP-Tcp” on the right side and choose properties

3. Click Edit -> choose a already installed SSL -> OK
-If no SSL’s show up here, you can search for instructions on creating a self signed certificate

4. Set Security layer to “SSL”

5. Set Encryption level to “High” and hit OK

Make sure to adjust the settings for your local remote desktop client to allow for this authentication under Options >> Security. If you connect to various servers/computers you can use “attempt authentication” or “require authentication” if every computer you connect to has SSL configured for RDP.

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.
printerMapping
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

3. Under the “Web Server (IIS)” heading click “Add Role Services”

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

First try to restart the Plesk service to see if that clears the issue:

/etc/init.d/psa restart

If you see any of the following errors that means the Plesk password is out of sync with the MySQL database which holds that info:
*Unable to connect to database
*login.php3: Unable to connect to database: Permission denied
*ERROR 1045: Access denied for user: ‘admin@localhost’ (Using password: YES)

This does happen from time to time which is why Plesk provides a tool to re-sync this:

export PSA_PASSWORD=’NEW_PASSWORD’ ; /usr/local/psa/admin/sbin/ch_admin_passwd; unset PSA_PASSWORD

Of course make sure to replace NEW_PASSWORD with the current working one, or a new one if needed.

Full Error:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{A9E69610-B80D-11D0-B9B9-00A0C922E750}
to the user NT AUTHORITY\NETWORK SERVICE SID (serviceID). This security permission can be modified using the Component Services administrative tool.

1. First take note of the GUID from your specific error (numbers between {}).

2. Open the registry editor (Start -> Run -> regedit)

3. Click the computer name at the top of the menu on the left. Then choose Edit -> Find and paste the GUID from step #1

4. This will show you the specific service having the issue. In this example the service was “IIS Admin Service”

5. Open up Component Services (Start -> Administrative Tools -> Component Services)

6. Expand Component Services -> Computers -> My Computer -> DCOM Config

7. Right click the specific service you found in step #4 and select Properties -> Security tab

8. In the first area “Launch and Activation Permissions” check the “Customize” radio button and then “Edit”

9. Add the specific user that encountered the error and give it local launch and activate permissions. You can find this service in the error message and in this example it is the Network Service user:
NT AUTHORITY\NETWORK SERVICE

10. Restart IIS to apply the change

Sqluserfail

Run the following query on the database in question to “resync” this login information:

EXEC sp_change_users_login 'Auto_Fix', 'UserName', NULL, 'Password'

Make sure to replace UserName and Password with the appropriate login information. If you don’t know the current password and the user already exists, simply run the command without the NULL and Password fields.

By default ASP.net 2.0 uses garbage collection that is designed for a multi-processor environment. If your server does not have multiple CPUs or you are seeing excessive Out of Memory exceptions, disabling this garbage collection should bring memory usage down.

First open the aspnet.config file with a text editor like Notepad. This file can be found here:
.NET Framework 2.0:
%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\Aspnet.config

.NET Framework 1.1:
%SystemRoot%\Microsoft.NET\Framework\v1.1.4322\Aspnet.config

Within the <runtime> tags add the following:
<gcServer enabled=”false”/>

Save the file and you are good to go.