CFF KB - Carrz-Fox-Fire Promotions Knowledge Base

CFF KB is all about 1 thing: The Sharing of Knowledge and the Power we gain from it.
  • Breadrumbs:
  • IIS shared config - object reference not set to an instance of an object

  • CFF Knowledge Base - Share With Facebook CFF Knowledge Base - Share on Twitter CFF Knowledge Base - Share on Reddit CFF Knowledge Base - Share on Digg It CFF Knowledge Base - Share on Stumble Upon It CFF Knowledge Base - Share on Delicious
    Share With Friends (Updated 6-8-2010)
  • Article ID:
    4246
  • Date Created
    Tuesday, April 26, 2022
  • Last Updated
    Tuesday, April 26, 2022
  • This Article Has been Viewed
    281 times
  • Short Desc
    ISS Shared Configuration can cause catastrophic issues within IIS Management if there is a difference in the child servers setup compared to the primary server.
  • Details
    Using Shared Configuration in IIS can at times cause the following error.

     
    object reference not set to an instance of an object


  • Recreate Issue
    Scenario #1:
    In this scenario, we will look at a server with many websites. When you use the Shared Configuration, one or more of the following are true.

    #1a: A website is [Stopped] on the primary server but is [Started] on the child servers.
    #1b: A website is named differently on the primary server than on the child servers.
  • Resolve Issue
    Scenario #1:
    #1a: Click on the [Sites] folder in the troubled child server.
    Select the site which is disabled on the primary server.
    On the Right-panel
    Under [Manage Website]
    Click [Stop]
    Next, [Restart] IIS

    #1b: Click on the [Sites] folder in the troubled child server.
    Select the site which has the naming issue,
    On the Right-panel
    Under [Manage Website]
    Click [Restart]
    Next, [Restart] IIS

    #1b should not be causing an issue, the shared config should update the site name to match the primary server, and that site should automatically start working. However, it seems that is not the case. I will research this issue and post an update to this KB Article when information becomes available.