HansHoskens
1 Nickel

OME Update failure

Jump to solution

I have an issue with OME, it keeps on starting an update and it keeps on giving a FailsValidation in the UI Logs. The issue causes OME console not to do anything anymore like discovery and inventory or sending devices/alerts to SupportAssist.

An export of the UI logs of OME gives back some errors, I added the .html file in the post.

In the event viewer of the OME server I traced back the following log:

Dell.ManagementEssentials.Exceptions.ItaDataAccessorException: Message ID "retrieveTask" too long to be processed by the DA Service. ---> System.TimeoutException: Unable to confirm that the memory message was sent before the timeout expired.

   at A.c8830eb6471e20c17408e4edc56dbee61.c53375e2a24b6e8ee6fc903b09597527f(String ceb48334b78e0e764e3e7892f6114d323, Nullable`1 c8cd7d5a7cd9e9d83621f88c9fd6d0074, Mutex c4d2dacddde69f04884e9002bffc31beb, Boolean cc4979a75f8b842360aa6e162c8a4c029)

   at A.c8830eb6471e20c17408e4edc56dbee61.c53375e2a24b6e8ee6fc903b09597527f(String ceb48334b78e0e764e3e7892f6114d323, Nullable`1 c8cd7d5a7cd9e9d83621f88c9fd6d0074)

   at A.c9e327a3ca308300e52f0cba9f5fa8ec4.ca1f65ba4cfd871d549320016a2de19ba(String c0140dff06d5e3a38c275a5a862226722, c41a5570612cc8f74915e5f9b6d5b003f c85929ce61371a8e5457e41219eb87be5, TimeSpan c2a3639b8236ceae1f06072c208d9a307)

   --- End of inner exception stack trace ---

   at A.c9e327a3ca308300e52f0cba9f5fa8ec4.ca1f65ba4cfd871d549320016a2de19ba(String c0140dff06d5e3a38c275a5a862226722, c41a5570612cc8f74915e5f9b6d5b003f c85929ce61371a8e5457e41219eb87be5, TimeSpan c2a3639b8236ceae1f06072c208d9a307)

   at A.c9e327a3ca308300e52f0cba9f5fa8ec4.ca1f65ba4cfd871d549320016a2de19ba(c576ef8bc46e19392bed2822c9ca966a3 c0140dff06d5e3a38c275a5a862226722, TimeSpan c2a3639b8236ceae1f06072c208d9a307)

   at A.c576ef8bc46e19392bed2822c9ca966a3.ce10aa38053a7d43544c579bdd5554b6a()

   at Dell.OME.TaskManager.Task.c618f8da26bdf0e50b388ee4c5fab8d01(Int32 c5b6d5c8322e1950a28d7f3f5dcde3a28)

   at Dell.OME.TaskManager.Task.c1c2af20d279a93a3f4fbe6174ae7e2d8(Int32 c5b6d5c8322e1950a28d7f3f5dcde3a28)

   at SmartConsole.Service.DataService.GetDeviceConfigurationApplyToUndiscoveredTask(Int32 taskId)

 

 

System.TimeoutException: Unable to confirm that the memory message was sent before the timeout expired.

   at A.c8830eb6471e20c17408e4edc56dbee61.c53375e2a24b6e8ee6fc903b09597527f(String ceb48334b78e0e764e3e7892f6114d323, Nullable`1 c8cd7d5a7cd9e9d83621f88c9fd6d0074, Mutex c4d2dacddde69f04884e9002bffc31beb, Boolean cc4979a75f8b842360aa6e162c8a4c029)

   at A.c8830eb6471e20c17408e4edc56dbee61.c53375e2a24b6e8ee6fc903b09597527f(String ceb48334b78e0e764e3e7892f6114d323, Nullable`1 c8cd7d5a7cd9e9d83621f88c9fd6d0074)

   at A.c9e327a3ca308300e52f0cba9f5fa8ec4.ca1f65ba4cfd871d549320016a2de19ba(String c0140dff06d5e3a38c275a5a862226722, c41a5570612cc8f74915e5f9b6d5b003f c85929ce61371a8e5457e41219eb87be5, TimeSpan c2a3639b8236ceae1f06072c208d9a307)

Thanks in advance.

Tags (1)
0 Kudos
1 Solution

Accepted Solutions

RE: OME Update failure

Jump to solution

Hi, thanks for the query.

Try restarting OME services (specifically DA service) from Services and see if the issue gets resolved.

Thanks,
Shivendra

0 Kudos
3 Replies

RE: OME Update failure

Jump to solution

Hi, thanks for the query.

Try restarting OME services (specifically DA service) from Services and see if the issue gets resolved.

Thanks,
Shivendra

0 Kudos
HansHoskens
1 Nickel

RE: OME Update failure

Jump to solution

Hi,

I tried restarting the services but it already was stuck at 'Stopping'  and all other tasks are greyed out. Tried it with PS but no succes. Tried rebooting and still the service got stuck at stopping when the update started running.


I believe it is solved now by setting the startup type to manual of the DA Service, rebooting and then starting the service (and putting the startup type back to automatic). Now OME starts inventory and collections again and so does SupportAssist.


Thank you very much!


kind regards,

Hans

0 Kudos

RE: OME Update failure

Jump to solution

Glad that it worked out. Thanks for the update.

Thanks,
Shivendra

0 Kudos