Error on Web Console - Unexpected Website Error (C:\Windows\Microsoft.NET\Framework\...)

Issue:
On opening the Web Console the following errors are displayed.
Unexpected Website Error
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET\root\6faafa1c\92094bad
\App_Web-orionmasterpage.master.b6031896.lqrhb0id.0.cs(305): error CS0433: the type 'Orion-Contriols_PageHeader' exists in both
'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET\root\6faafa1c\92094bad\App_Web_otu5ty5l.dll' and
'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET\root\6faafa1c\92094bad\App_Web_dz0dqaye.dll'

Cause Presence of .Net temp files (C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET\) causes the error.

NOTE: How to Start/Stop Orion Services.
 
Solution 1:
1. Login as local administrator
2. Stop all Orion Services using Orion Service Manager.
3. Delete Orion Web Site in IIS
4. Stop IIS (World Wide Web Publishing Service). How to Start/Stop IIS Services.
5. Delete all folders under C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET\
6. Rename Orion Web Site from C:\Inetpub\SolarWinds to C:\Inetpub\SolarWinds_old
7. Start IIS.
8. Re-run the Web part of the Configuration Wizard and check Website.
9. Start all Orion Services using Orion Service Manager. 
10. Orion website is re-created which solves the issue.


Solution 2:
1. Login as local administrator
2. Stop all Orion Services using Orion Service Manager.
3. Stop IIS (World Wide Web Publishing Service). How to Start/Stop IIS Services.
4. Delete all folders under C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET\
5. Start IIS.
6. Re-run the Web part of the Configuration Wizard and check Website.
7. Start all Orion Services using Orion Service Manager. 
8. Orion website is re-created which solves the issue.

SolarWinds NPM - Installer package has invalid signature/Invalid signature on executable file

Issue: You get an error similar to the following:

• Agent deployment failed. Installer package has invalid signature (NPM during Agent Deployment)
• Invalid signature on executable file (SAM when running the "Configure Server" button for AppInsight for Exchange)

Cause:  This is caused when the Certificate Authority (CA) certificate for the issuing CA of the certificate used to sign the executable file for the remote configuration is missing from the "Local Computer\Trusted Root Certification Authority" store for the server. Normally, the certificate will be imported into the store automatically if it is missing, unless the system has been "locked down" using security settings to prevent this.

Note: Windows 2012 R2 natively includes the intermediate certificate needed to validate the code signing certificate used. Other non-Windows 2012 R2 servers should have their root certificates updated automatically by Windows Update, provided the server has internet access and is allowed to download abd install Windows updates on a regular basis.


If this is the case, you will need to manually download the Root CA certificate and install it into the "Local Computer\Trusted Root Certification Authority" store on the Exchange server. The entire Verisign root certificate package can be downloaded from this link. http://www.verisign.com/support/roots.zip. If you wish to download just the missing Root CA certificate (not recommended), use the following link:http://www.verisign.com/repository/roots/root-certificates/PCA-3G5.pem.

1. Open a new MMC.
2. Click File > Add/Remove Snap-in…
3. Add the Certificates Snap-in.
   
   
4. Select Computer Account, and then click Next.
   
   
5. Ensure Local Computer is selected. (The computer this console is running on)’
6. Click Finish.
   
   
7. Click OK to add the snap-in into the MMC window.
8. Expand the certificate store tree.
9. Right click the Trusted Root Certification Authorities store.
10. Select All Tasks/Import to import the previously downloaded certificate(s).
    
    
11. Follow the prompts of the wizard to import the certificate(s).
12. Verify the Verisign Class 3 Public Primary Certification Authority – G5 certificate is present in the Trusted Root Certification Authorities store (It is recommended that you import all missing Root CA certificates).
    
    
13. Re-run the Configure Server button in AppInsight for Exchange and the process should complete successfully.
    
    

At this point, the Verisign Root CA certificate(s) can be removed from the Exchange server, if desired. (Not Recommended).