ASP.NET v2.0 Not Appearing in IIS

Lately I’ve started performing more server builds with MOSS 2007 installs and I’ve noticed a trend.

SharePoint requires the ASP.NET v2.0 to be registered in the IIS Web Service Extensions and set to “Allowed.” If this is not the case, the SharePoint installation will error out – simple as that. It seems pretty common to find .NET 2.0 installed but not displaying in IIS. I’ve found the solution a number of times over across the ‘net (quick and easy!) but not the answer to “why did this happen on this server but not the other?”

I haven’t narrowed it down to the exact particulars of the situation that causes it. I have noticed though that if you decide to be proactive during your server build (in my case Windows Server 2003) and allow Windows/Microsoft Update to install the .NET framework before you add the IIS/App server role, you’ll run into this.

I haven’t had a chance to do thorough enough testing to be sure if it’s the Windows/Microsoft Update method of installation that causes this (probably not), or if it’s installing it before adding it as an IIS Application server (most likely), or the combination of the two. Too avoid having to fix the issue, I’ve just started patching/updating the server, adding the server role, then manually installing the redistributable installation for the .NET framework. If you use this method, ASP.NET v2.0 automatically registers itself as an IIS Web Server Extension and you’re ready for the SharePoint installation. Otherwise, you’ll need to manually register it using this command:

%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i

More details on the aspnet_regiis command here.

After that, you can navigate to: Start > All Programs > Administrative Tools > IIS Manager

Expand the server name if needed, and select the “Web Service Extensions” note.  You should now see ASP.NET v.2x and have the ability to select it and click “Allow”.