Skip to content
October 28, 2011 / kiranpatils

Challenges faced during up-gradation of Sitecore instance from IIS 6.0 to IIS 7.5

Before couple of months back, we upgraded our Sitecore instance from IIS 6.0 to IIS 7.5, It went smooth except few things, which are not Sitecore specific. But general .NET/IIS7.5/Windows Server 2008 related.

Just wanted to share with you. So, If during your up-gradation you don’t invest the time which we already! (Obviously, You can share any new things which you faced during your up-gradation process).

Challenge1 : Error: The requested name is valid, but no data of the requested type was found when calling Dns GetHostByAddress

Whenever we were opening Sitecore login page we used to get this error and to solve this error we need to enable “use NETBIOS over TCPIP” [Source :]

Challenge2 : The ‘Microsoft.ACE.OLEDB.12.0’ provider is not registered on the local machine.

We tried everything suggested which Google suggested us from following articles:

Basically they suggested us to change the application to 32 bit and do run it! But it was not the solution in our case, as we wanted to take full benefit of Integrated Pipeline mode also we earlier learnt that Sitecore works best in ASP.NET 64
bit mode. So, we were sure that we have to find some another solution. So, we delved again in to Google ocean and found pearl from it! Basically you need to install 64 bit drivers to make it working! [Source :]

Just a note : after installing drivers, it’s good to manually restart IIS using command prompt!

Challenge3 IIS related : few things which we found (and learnt) were related to IIS Only!

  1. iisreset practice : Right click and then do iisrest! As per Windows Server 2008 architecture command prompt automatically dosen’t run in Admin mode. You have to forcefully to do it! (sometime annoying. But it makes sure you are doing IISRESET when you really need to do!)
  2. IIS Log files : When you run Sitecore 6.x in Integrated Pipeline Mode, You will notice that ALL IIS log entries contain the log entry for the resquest to the layout (aspx) page (instead of the actual sitecore item .e.g /ContactUs.aspx). To solve this error you need to write your own IIS Module, How to do it? Refer following article: Just a note :The IIS  Module uses app.Context.RewritePath(originalPath); method which is a heavy method to use. So, before adding this module, give yourself a though. Do you really need (or use) this log entries for any purpose? Can’t you live without them? If Yes, I would strongly recommend not to add it!
  3. Global.asax’s Application_BeginRequest was not getting called every time : And we had our custom security code in that method. So, if it won’t get called our application will not work. After digging a bit we found that it’s behavior of IIS and to solve it we did following change in our web.config:

<modules runAllManagedModulesForAllRequests=”true”>

For more information on this read :

Good to read :
IIS Performance analysis by Microsoft :

Happy Up-gradation! 🙂


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: