Do you happen to have a group policy that requires FIPS compliance? This error seems to fit that pattern. OME 1.2 is not FIPS compliant, though we are looking at this for the next version.
SYS LOG: A fatal error occurred while creating an SSL client credential. The internal error state is 10013.
I have run a "repair" on the OME install and have also applied patch 1.2.1 to no avail. This is a clean installation on a new server build - as clean as it gets!
"Severity" "Start Time" "Source" "Description" "Critical" "11/18/2013 10:09:43 AM" "DataCache.Load()" "It has load errors" "Warning" "11/18/2013 10:09:43 AM" "ProxyManager.FaultTolerate()" "Fault tolerance on communication exception in progress -> Count: 1" "Critical" "11/18/2013 10:09:43 AM" "DataCache.LoadCheck()" "Exception loading the cache occurred: System.ServiceModel.CommunicationException: [HttpWebRequest_WebException_RemoteServer] Arguments: NotFound Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer ---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer] Arguments: NotFound Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer ---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer] Arguments: NotFound Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult) at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClassa. b__9(Object sendState) at System.Net.Browser.AsyncHelper.<>c__DisplayClass4. b__0(Object sendState) --- End of inner exception stack trace --- at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state) at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result) --- End of inner exception stack trace --- at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result) at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result) at SmartConsole.DataServiceReference.DataServiceClient.DataServiceClientChannel.EndGetActiveUser(IAsyncResult result) at SmartConsole.DataServiceReference.DataServiceClient.SmartConsole.DataServiceReference.IDataService.EndGetActiveUser(IAsyncResult result) at SmartConsole.DataServiceReference.DataServiceClient.OnEndGetActiveUser(IAsyncResult result) at System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result)" "Critical" "11/18/2013 10:09:43 AM" "DataCache.LoadCheck()" "Data Cache load error: SmartConsole.DataServiceReference.GetActiveUserCompletedEventArgs" "General Information" "11/18/2013 10:09:25 AM" "App.xaml" "DataCache load starting..." "General Information" "11/18/2013 10:09:24 AM" "App.xaml" "Splash screen instantiated..." "General Information" "11/18/2013 10:09:24 AM" "App.xaml" "Application_Startup: Starting..."
That was it! Thanks. I disabled FIPS under local security policy | local policies | security options | system cryptography: use fips... (set to disabled) and restarted server. Boooom, I'm in. Thank you!
It's possible since we are a fed org. Which GPO policy could I look at to confirm this? Secondly, is OME 1.1 FIPS compliant? I may opt to install that version instead...
As a side note, one of my counterparts recently upgraded to OME 1.2 without any problems that I'm aware of. It's possible his GPO push is different.
1.1 might be. We did some work in 1.2 that might have caused this. It's currently being looked at.
For your counterpart, perhaps they have slightly different GPO push as you say.
I am having trouble uploading a screen shot. But you go to Local Security Policy | Local Policies | Security Options. You may see an entry that says "System cryptography: Use FIPS compliant...."
I'm experiencing the same problem when trying to load OME 1.2. My install is on SBS 2011. I've checked the FIPS setting in Group Policy on my server and it is Disabled. Again, OME seems to freeze at the splash screen when I try to load the application in IE. I've tried from the server and from a WIN 7 workstation that has IE 11 now and previously had IE9. Thanks
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
November 18th, 2013 08:00
Hi there,
Do you happen to have a group policy that requires FIPS compliance? This error seems to fit that pattern. OME 1.2 is not FIPS compliant, though we are looking at this for the next version.
Can you review and report back?
Thx
Rob
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
November 14th, 2013 11:00
HI and thanks for the post.
Does the UI come up when you launch it locally from the OME server?
Do you have silverlight installed on the remote box and what are the specs?
Thx
Rob
thickage1971
11 Posts
0
November 14th, 2013 11:00
UI hangs on the server as well.
Intel Xeon 3.00GHz, 8 GB RAM, 260 GB HD available.
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
November 14th, 2013 13:00
See if you can click on the splash screen and maybe some logs will be displayed.
Give that a try.
Rob
thickage1971
11 Posts
0
November 15th, 2013 05:00
DataCache.LoadCheck(): Data Cache load error: SmartConsole.DataServiceReference.GetActiveUserCompletedEventArts is the first error.
Then a few more DataCache.LoadCheck() errors...
thickage1971
11 Posts
0
November 15th, 2013 06:00
Also, I see the following critical errors in event viewer:
I have run a "repair" on the OME install and have also applied patch 1.2.1 to no avail. This is a clean installation on a new server build - as clean as it gets!
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
November 15th, 2013 12:00
Ok, this snippet not so helpful.
R-Click export the log displayed after clicking the splash screen. Perhaps there will be more useful detail.
Thx!
Rob
thickage1971
11 Posts
0
November 18th, 2013 07:00
"Severity" "Start Time" "Source" "Description"
"Critical" "11/18/2013 10:09:43 AM" "DataCache.Load()" "It has load errors"
"Warning" "11/18/2013 10:09:43 AM" "ProxyManager.FaultTolerate()" "Fault tolerance on communication exception in progress -> Count: 1"
"Critical" "11/18/2013 10:09:43 AM" "DataCache.LoadCheck()" "Exception loading the cache occurred: System.ServiceModel.CommunicationException: [HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer ---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer ---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer
at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)
at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClassa. b__9(Object sendState)
at System.Net.Browser.AsyncHelper.<>c__DisplayClass4. b__0(Object sendState)
--- End of inner exception stack trace ---
at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)
at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)
--- End of inner exception stack trace ---
at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result)
at SmartConsole.DataServiceReference.DataServiceClient.DataServiceClientChannel.EndGetActiveUser(IAsyncResult result)
at SmartConsole.DataServiceReference.DataServiceClient.SmartConsole.DataServiceReference.IDataService.EndGetActiveUser(IAsyncResult result)
at SmartConsole.DataServiceReference.DataServiceClient.OnEndGetActiveUser(IAsyncResult result)
at System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result)"
"Critical" "11/18/2013 10:09:43 AM" "DataCache.LoadCheck()" "Data Cache load error: SmartConsole.DataServiceReference.GetActiveUserCompletedEventArgs"
"General Information" "11/18/2013 10:09:25 AM" "App.xaml" "DataCache load starting..."
"General Information" "11/18/2013 10:09:24 AM" "App.xaml" "Splash screen instantiated..."
"General Information" "11/18/2013 10:09:24 AM" "App.xaml" "Application_Startup: Starting..."
thickage1971
11 Posts
0
November 18th, 2013 08:00
That was it! Thanks. I disabled FIPS under local security policy | local policies | security options | system cryptography: use fips... (set to disabled) and restarted server. Boooom, I'm in. Thank you!
thickage1971
11 Posts
0
November 18th, 2013 08:00
It's possible since we are a fed org. Which GPO policy could I look at to confirm this? Secondly, is OME 1.1 FIPS compliant? I may opt to install that version instead...
As a side note, one of my counterparts recently upgraded to OME 1.2 without any problems that I'm aware of. It's possible his GPO push is different.
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
November 18th, 2013 09:00
Ok...
1.1 might be. We did some work in 1.2 that might have caused this. It's currently being looked at.
For your counterpart, perhaps they have slightly different GPO push as you say.
I am having trouble uploading a screen shot. But you go to Local Security Policy | Local Policies | Security Options. You may see an entry that says "System cryptography: Use FIPS compliant...."
Thanks,
Rob
jteel
1 Rookie
•
93 Posts
0
November 22nd, 2013 15:00