Skip to end of metadata
Go to start of metadata

Many different errors can be fixed by simply running a .NET repair. Performing a .NET Repair will vary based on what version of Windows Server you’re running.

Server 08 and Below (ASPNET REGIIS)

  1. Open a Command Prompt as an administrator and navigate to:
    1. C:\Windows\Microsoft.NET\Framework\v4.0.30319
    2. Run the following command: aspnet_regiis.exe -iru
      1. This can be run as:
        1. aspnet_regiis.exe -i
        2. aspnet_regiis.exe -ir
        3. aspnet_regiis.exe -iru
        4. It is advised that you run each iteration of this command once.

Server 2012 and Up (DISM Tool)

  1. Open a Command Prompt as an administrator and run each of these separately:
    1. Dism/online /Disable-Feature /FeatureName:IIS-ASPNET45
    2. dism /online /enable-feature /featurename:IIS-ASPNET45  (This can take a moment – wait until you see a progress bar appear and reach 100%)

Clearing .NET Temp Files

Additionally, clearing the ASP.NET Temp folder has been known to remedy some unhandled exception errors such as the getconnectionobjectsbygroups error. Often times if policy or permissions changes have been made to an AD  on a server that has been up for a long time, it will be necessary to manually flush the temporary files that hold ephemeral data pertaining to how GlobalSearch interfaces with IIS and .NET. To do this:

  1. Open command prompt as an administrator
  2. Run the command: iireset /stop
  3. Browse to C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files in the windows files explorer
  4. Clear the temp files in this location that pertain to Smart Search
  5. Run the command iisreset /start

Write a comment…