WCF - The page you are requesting cannot be served because of the extension configuration

The page you are requesting cannot be served because of the extension configuration.

Today I was getting bored. So just for time pass I was uninstalling and installing IIS repeatedly. Just for fun. Sounds crazy right? But I was doing it.

Finally at the second half my team lead asked me to create a sample WCF service and host in IIS with some useless functionality. J

Well, I created WCF, hosted in IIS. When I browsed .svc page, I received following error –

HTTP Error 404.3 – Not Found

The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

This was the point when I was happy!! J

Cause of the Problem – If you have Visual studio installed, then uninstall and install IIS again, then you will get above error. Due to uninstall of IIS, extension mappings for WCF SVC file were removed.

Windows Azure Connect – Enabling local machine or domain controller for windows azure connect

Enabling local machine or domain controller for windows Azure Connect.

After post of Enabling Azure Connect for VM Role, today, I will discuss about enabling local machine or domain controller for windows Azure Connect.

To enable local machines to connect to your Windows Azure roles, you need to install the connect endpoint software (connect agent). Login to local machine which you want to use for Azure Connect and follow al the steps mentioned below –

Windows Azure Connect for VM Role

Windows Azure Connect for VM Role.

Today I will discuss the procedure of enabling Azure connect for Azure VM role.  I am here  assuming that, you have VHD which will be used as a VM role.

Windows Azure Connect Endpoint Software enables Windows Azure users to set up secure, IP-level network connectivity between their Windows Azure hosted services and local (on-premises) resources. To avail Azure Connect, you will need to send request from Azure management portal.

 

Windows Powershell - Run powershell script at startup under different domain user account logon

Run powershell script at startup under different domain user account logon.

This was the problem with which I struggled a lot. As usual my companies GOD, none other than CLIENT, wanted to run this SharePoint powershell script on start up of machine.

The challenge was, the powershell script should run on startup, but not with Local System account, rather a domain user account that will be in the administrator group on the machine.

Alright here we go!!

Problem Statement – Execute or run powershell script at startup under domain user account.

Applicable Technology is Windows XP and higher, Windows Server 2003 and higher.

Ok. The solution lies more likely in running the powershell script as a Windows Service. The steps to achieve this is as follows –