Start a Conversation

Unsolved

This post is more than 5 years old

28581

October 27th, 2015 10:00

Unhandled Error in the Application

Just upgraded to OME 2.1 (from 1.3) and I'm getting the following error every now and then via the web portal (FireFox):

[Arg_TargetInvocationException]
Arguments:
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See go.microsoft.com/fwlink;Version=5.1.40728.00&File=mscorlib.dll&Key=Arg_TargetInvocationException

System.Reflection.TargetInvocationException: [Arg_TargetInvocationException]
Arguments:
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See go.microsoft.com/fwlink;Version=5.1.40728.00&File=mscorlib.dll&Key=Arg_TargetInvocationException ---> System.Exception: The data cache did not refresh correctly.
Method timed out: LoadDeviceCapabilities(...)

   at SmartConsole.DataCache.FaultTolerateTimeouts(Dictionary`2 waitHandles)
   at SmartConsole.DataCache.Load()
   at SmartConsole.DataCache. b__1eb()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at SmartConsole.Update.UpdateManager.<>c__DisplayClassd. b__b()
[Arg_TargetInvocationException]
Arguments:
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See go.microsoft.com/fwlink;Version=5.1.40728.00&File=mscorlib.dll&Key=Arg_TargetInvocationException
System.Reflection.TargetInvocationException: [Arg_TargetInvocationException]
Arguments:
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See go.microsoft.com/fwlink;Version=5.1.40728.00&File=mscorlib.dll&Key=Arg_TargetInvocationException ---> System.Exception: The data cache did not refresh correctly.
Method timed out: LoadDeviceCapabilities(...)

   at SmartConsole.DataCache.FaultTolerateTimeouts(Dictionary`2 waitHandles)
   at SmartConsole.DataCache.Load()
   at SmartConsole.DataCache. b__1eb()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at SmartConsole.Update.UpdateManager.<>c__DisplayClassd. b__b()

* * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * *

The data cache did not refresh correctly.
Method timed out: LoadDeviceCapabilities(...)

System.Exception: The data cache did not refresh correctly.
Method timed out: LoadDeviceCapabilities(...)

   at SmartConsole.DataCache.FaultTolerateTimeouts(Dictionary`2 waitHandles)
   at SmartConsole.DataCache.Load()
   at SmartConsole.DataCache. b__1eb()

* * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * *
Local Stack Trace:

SmartConsole.ErrorHandler >> Show
Dell.OME.OMEProxyManager >> ShowError
SmartConsole.Update.UpdateManager+<>c__DisplayClassd >> b__b
System.Threading.ThreadHelper >> ThreadStart_Context
System.Threading.ExecutionContext >> Run
System.Threading.ExecutionContext >> Run
System.Threading.ThreadHelper >> ThreadStart




























































96 Posts

October 28th, 2015 00:00

Hi TroyD-Fortegra,

Thanks for your post!

Here are few questions which will help us to understand this issue:

1. Whats the configuration for your OME server, i.e. how many processor and memory?

2. Is OME installed on a local or remote database? If local, is it Enterprise or Express install for SQL?

3. How many devices you had in OME 1.3 before upgrade?

4. Is this exception is evident, every time you launch OME?

Thanks

Ranveer

October 28th, 2015 09:00

1. 4 virtual processors and dynamic memory set at min 2048 w/max of 4096

2. local db with SQL Server 2012.  As far as version...it looks like whatever was installed at the time of OME because if I had installed it, I would have installed Express with Advanced tools and that's not installed on my server...

3. I only have 3 servers set up to be updated by OME

4. As stated earlier, it happens every once in a while, there is no rhyme or reason that I can tell as of now...

96 Posts

October 29th, 2015 01:00

Thanks for the updates!

Here, everything looks ok as per the setup you have and number of devices discovered in it. But, just to bring into notice that latest release of OME2.1 has updated the minimum memory requirement to 6Gb, so you can try out increasing the size as recommend.

Also, try to repair the installed OME setup and see if that helps.

Thanks
Ranveer

No Events found!

Top