hi,
Here is our System Center 2012 App Controller SP1 environment:-
2 x App Controller servers, running on Windows 2008 R2. Clustered using an F5 with sticky sessions. Sites are secured with certificate, CN=cluster name, SAN=server names. F5 also has certificate bound to cluster configuration too.
Clients:-
- Windows 7 (x86) OS, with IE9: Can connect to both cluster address and server addresses without issue.
- Windows 7 (x64) OS, with IE9: Blank screen on connecting to cluster address (right click shows Silverlight menu). Can connect to server addresses direct without issue.
- Windows 8 (x64) OS, with IE10: Blank screen on connecting to cluster address (right click shows Silverlight menu). Can connect to server addresses direct without issue.
Debugging:-
We used IE10's F12 option to see errors, and found the following:-
HTML1524: Invalid DOCTYPE. The shortest valid doctype is "<!DOCTYPE html>".
<removed cluster address>, line 1 character 1
SEC7111: HTTPS security is compromised by
http://go.microsoft.com/fwlink/?LinkId=161376
<removed cluster address>
SCRIPT5022: Unhandled Error in Silverlight Application
Code: 2104
Category: InitializeError
Message: 2104 An error has occurred.
<removed cluster address>, line 58 character 13
The HTTPS security is compromised error seems to relate to mixed security boundaries, and refers to the "Display mixed content" setting within IE being set to disabled, however all browsers have the same setting of prompt, and there are no prompts anyway... The link referred is the Silverlight installer splash screen by the looks of things.
The second error (2104) is described as due to a lack of MIME types setup for .xaml, .xap, and .xbap within the website, but these are all setup by default within IIS 7.5. I have tried enabling Content Expiration without any effect.
We've tried using the compatibility modes from IE7 through to IE10 without any effect.
We've tried removing Silverlight from the Windows 8 clients, rebooted, reconnected to the App Controller site and let it download and install Silverlight again same situation afterwards.
Users are all local admins of their machines; if they move to Windows 7 (x86) everythings OK, but back to the x64 OSs and they cannot not connect to the cluster address again.
Does anyone have any thoughts or pointers as to where else to look?
Update: We've just noticed that when we remove Silverlight from the x64 OSs, and connect to the cluster, we actually get sent the x86 version of Silverlight (Silverlight.exe), rather than the x64 one that is required. If we go direct to the servers instead we get the correct Silverlight_x64.exe. It seems that this may be an F5 issue, though would be glad to hear anyone's thoughts as to how to resolve it.
Thanks
Steve
Other recent topics
