Archive for the Windows Server Category

Set custom error pages in IIS 7 for .aspx extension

Posted in Windows Server on April 4, 2011 by Aparna Murthy

Today I came across with an error while adding custom error pages in IIS 7, While adding custom error pages for 404 I found every extension is working just fine while adding except .aspx extension, It is come out with the error as follows :

Error :


Server Error “/” Application The resource can not be found


Cause :

Because the custom error pages in IIS7 do not work for .aspx.


Solution :

You need to setup the .NET Error Pages for it as follows :

Start >> Administrative Tool >> IIS >> Websites >> Domain name >> Click on .NET error pages and add it.


Once it is added, Error will be gone!!!!


Horde webmail : Content Encoding Error (content_encoding_error)

Posted in Windows Server on October 12, 2010 by Aparna Murthy

Error while opening the Horde Webmail interface :


Error:Content Encoding Error (content_encoding_error)Server response could not be decoded using encoding type returned by server.


This is typically caused by a Web site hosting presenting a content encoding header of one type, and then encoding the data differently.

To get this fixed, follow the below mentioned steps :

Find the Horde config file ‘conf.php’ on the server:which can be normally found in this path: “C:\Inetpub\vhosts\webmail\horde\config\conf.php”

Search for the following in that config file:

$conf[‘compress_pages’] = true;
Change it into:

$conf[‘compress_pages’] = false;
Save the horde config file & restart the webmail client. And…. you’re done

How to change the Remote Desktop Port

Posted in Windows Server on May 15, 2010 by Aparna Murthy

You can change Remote deskto port using following instructions:
To change the port you have to start Windows Registry Editor.
# Login to your Server with default RDP port that 3389
# Go to : Start -> Run… type ‘regedit’ and press OK
# Then expand the registry folders as follows :
HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > TerminalServer > WinStations > RDP-Tcp
# Then find the following registry subkey :
# On the Edit menu >> click Modify and then on the Edit “DWORD” Value click Decimal which will show you the current port number that is 3389(By default)
#Type the new port number, and then click ‘OK’ button.
Quit Registry Editor and reboot your server.
You need to make sure that new RDP port is opened into Server Firewall if not then it won’t allow you to login.

Rebuild/Reinstall Windows VPS in Virtuozzo Power panel.

Posted in Windows Server on September 5, 2009 by Aparna Murthy


You can rebuild/reinstall your Windows VPS in Virtuozzo Power panel.


You can rebuild your VPS in your VZPP

Login at https://xx.xx.xx.xx:4643/ (replace xx.xx.xx.xx with your VPS IP.)
Click “Maintenance”
Click “Reinstall” tab

Follow onscreen instructions.


Errro while doing RDP to the server. The terminal server has exceeded the maximum number of allowed connections

Posted in Windows Server on July 11, 2009 by Aparna Murthy

When a user tries to connect to a machine using Remote Desktop connection, they might come across this error message.

“The terminal server has exceeded the maximum number of allowed connections”

This is because Windows only allows two connections in RDP, and you’ve either got two people already logged on that machine, or you’ve got disconnected sessions that still thinks they are active. If a user simply closes the remote desktop window when they’re finished, that username will still remain logged on.

If the logged on users are not available, you wont be able to logon to the machine. To overcome this limitation, follow the steps as below.

open a command prompt or type in the RUN prompt

mstsc /v:[] /f -console

eg: mstsc /v: /f -console

You will then be prompted with the login box and proivde the administrator details. Then you will be connected to the Console Session on the server. Now you can reset the disconnected user sessions from Terminal Services Manager. Please note that if you get disconnected from this console session, you have go physically to the machine.

To overcome this issue you need to configure time out in Terminal Services Configuration in order to deactivate disconnected sessions automatically. following are steps to configure TSC(Terminal Services Configuration):

>> Click on “Start”
>> Select “Programs ”
>> Select “Administrative Tools”
>> Select “Terminal Services Configuration ”
>> Select  “Connections”
>> Double Click On “RDP-Tcp”
>> It’ll prompt for a window then Click on “Sessions”
>> Check the First check box before the text “Override user settings” This will activate the option of Enable a Diconnected sessions” below it  and select the time interval from the Drop down list as per your need. (e.g 15 minutes, 30 mintues etc)
>> Click on Apply and ok.