OK well I rebooted the server, OEM Task Manager has started again. I tried to then stop/start the service and was able to without error...but. I then tried to run a Task of upgrading a servers BIOS, the task ran for over an hour. I checked on the server itself and nothing was happening so I stopped the running task. I then tried to stop/start the Task Manager service and got the same error as I posted above (Error 183...). So I rebooted again, Task Manager service is running again so I tried to perform a Remote Task of deploying OMSA 7 to 1 server, task sat running for again an hour. Same thing stopped the task, tried to stop/start the Task Manager service and Error 183, rebooted the server. So it seems mt Task Manager is one nolonger working but then after stopping a pending or running task the Task Manager wll not restart without Error 183.

Hi Ron...

Can you try this and see what kind of results you see:

- Stop the task manager then do IISRESET

- The start the task manager

Let me know how that changes the behavior you are seeing.

thx

Rob

Did not change anything. Stopped the Task Manager service, ran IISREST and was successful restarted the Task Manager and still Error 183.

FYI I am running version 1.0.1.1253 and this issue seems to have started after this upgrade. I can not perform and upgrades or software deployments now.

Ron,

Ok, let's try one more thing.  There is a restart services button on the OME prefs page.  It will restart all of our services, but it also deletes the ODBC database connection we use.  Then the services will re-create.  We've seen a few cases where this connection can be the cause of this problem.

Thanks,

Rob

I tried doing that and no change. I RDP into the OEM server and the Task service was not started, I then tried manually starting it and same Error 183.

Hard to say....the 101 upgrade should be ok.  We've been doing a ton of them and not seen anything specific to this.  But anything is possible.

I hate to say it, but it looks like you will have to call into support.

One thing you may consider is backing up your database (which may, in fact, be ok) and then uninstall-reinstall 101.  You can re-target the database with a process something like this:

en.community.dell.com/.../19440364.aspx

Sorry I could not sort this one in the forum Ron :(

Regards,

Rob

The only change was when we upgraded to 1.0.1.1253 nothing else has changed unless a specific MS patch that came down has caused this.

Sigh...ok.

Hey Ron, have you had any changes to your database infrastructure lately?  I'm trying to see what might have sparked this problem...

Rob