This post is a collection of the most common issues and resolutions I see with the SCOM 2007 R2 Web Console:
Windows Auth on a non RMS. The most common issue is typically where customers install the Web Console using Windows Authentication, on some server that is not the RMS. Initially when SCOM released – this wasn't a supported configuration. Later, post SP1, instructions were released on how to make this work – but it took some changes in Active Directory for constrained delegation for Kerberos. Now – this can be done, but in real practice, I have found it to be hit-or-miss. In some domains – no issues…. in others, it breaks easily, or only works some of the time. In general, my recommendation is to use Forms Based authentication with SSL for Web Consoles that are not installed on the RMS. If you want to give constrained delegation a shot – there are several articles on the web, including mine:
Unexpected error immediately after install. Another common issue, is that you install the Web Console using Forms Based authentication, but get an “unexpected error”:
Unexpected error
There was an error displaying the page you requested.Try the following:
Restart the web browser
Refresh the page
If you are still not able to view the requested page, try contacting your administrator or Helpdesk
This is caused by installing the Web Console using Forms based authentication, but not having SSL set up yet. Marnix wrote a great post on this topic: http://thoughtsonopsmgr.blogspot.com/2010/03/scom-web-console-with-form-based.html
Bottom line – we recommend setting up SSL on IIS for the Web Console…. but if you dont have this set up yet – you need to edit the Web.Config file and change:
<authentication mode="Forms">
<forms requireSSL="true" />
</authentication>to
<authentication mode="Forms">
<forms requireSSL="false" />
</authentication>
Web Console takes a long time to load and ASP.NET logs Event ID: 1309
You might see the web console take a very long time to load, and eventually even time out with:
Event message: The request has been aborted.
Exception information:
Exception type: HttpException
Exception message: Request timed out.
You might also get the following event in your application event log:
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 4/07/2010
Time: 1:18:54 AM
User: N/A
Computer:
Description:
Event code: 3001
Event message: The request has been aborted.
Event time: 4/07/2010 1:18:54 AM
Event ID: 0fde28a70ef54acf9e269f9bed4eb70f
Event sequence: 6
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2/ROOT-1-129114331599062251
Trust level: Full
Application Virtual Path: /
Application Path: C:\Program Files\System Center Operations Manager 2007\Web Console\
Machine name:
Process information:
Process ID: 4460
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: HttpException
Exception message: Request timed out.
Request information:
Request URL: http://omms1.opsmgr.net:51908/login.aspx?ReturnUrl=The request has been aborted.fDefault.aspx
Request path: /login.aspx
User host address:
User: Domain\Username
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace:
This can be caused by an IIS configuration – the SCOM Web Console website was configured to use AnonymousAND Windows Integrated Authentication, when ideally it should be configured to use ONLY Windows Integrated Authentication.
To resolve – you can uncheck Anonymous Authentication and then perform an iisreset.
Cannot install/uninstall the web console.
Often times – this is an issue for Web Consoles that were upgrade from SP1 to R2. Many times – this is due to old path information in the registry.
1. Go to registry editor on web console server.
2. Locate “My Computer\HKEY_CLASSES_ROOT\Installer\Products\DF6E5EFF035E66C49971553D96AA0E4D
3. Back up the registry key in step 2
4. Go to patches value and delete entry for “patches” REG_MULTI_SZ
5. Continue with the upgrade/uninstall/install.
Error message when you try to access the Web console: "HTTP Error 401.2 – Unauthorized. You are not authorized to view this page due to invalid authentication headers"
See: http://support.microsoft.com/kb/970043
Other good articles:
How to set up SSL for your SCOM R2 Web Console? How to configure the SCOM R2 Web Console to use SSL only
All common customization options for the Web Console via the Web.Config file: http://blogs.technet.com/michaelpearson/archive/2009/11/30/opsmgr-r2-web-console-web-config-settings.aspx
How to change the Web Console to force it to open a specific default view, instead of the default overview: http://blogs.technet.com/kevinholman/archive/2009/11/09/how-to-force-the-web-console-to-open-a-specific-view-instead-of-the-default-monitoring-overview.aspx
Really making a web console powerful – check out Savision LiveMaps: http://thoughtsonopsmgr.blogspot.com/2009/11/savision-live-maps-version-41-for.html
How to install IIS on Server 2008 for the Web Console: http://blogs.technet.com/kevinholman/archive/2008/09/26/how-to-install-iis-on-server-2008-to-support-opsmgr-web-console-and-reporting.aspx
Upgrade issues with the web console and upgrading to R2: http://blogs.technet.com/kevinholman/archive/2009/05/23/my-experience-upgrading-to-opsmgr-r2-rtm.aspx