Start a Conversation

Unsolved

This post is more than 5 years old

R

4752

November 16th, 2018 07:00

OMSA 9.2 upgrade via OME

I deployed OMSA 9.2 via OME to upgrade from 9.1 on 175 servers. The report says the install was successful but when I attempt to connect to OMSA I get a "This page can't be displayed" error. The only way that I've found to fix the problem is to login to each server, uninstall 9.2, reinstall 9.1 and then upgrade to 9.2. Needless to say this is going to be a huge headache on that many servers. Has anyone else had this problem?

Thanks,

Robert

10 Elder

 • 

6.2K Posts

November 16th, 2018 10:00

Hello

The correct arguments are not likely being used. Page 308 of the OpenManage Essentials User's Guide has an entry for performing OMSA upgrades. There is a note about required arguments. You can find OME documentation on the OpenManage Essentials support page. You may also be able to locate this information from within OME by clicking on the help/question mark icon that appears near the top right of most pages.

http://www.dell.com/openmanagemanuals/

Thanks

1 Rookie

 • 

78 Posts

November 16th, 2018 10:00

Daniel,

I've upgraded OMSA via OME numerous times simply by creating a deployment task, pointing to the installer and using a pre-defined query for the targets. It appears that the problem is the DSM SA Connection Service won't start and gives an "Error 6: The handle is invalid" when I attempt to start it manually.

Robert

November 19th, 2018 14:00

I have the same issue on an aging T710.  My other 8 servers upgraded without issue.  First time in a long time an ODMA upgrade failed if memory serves.

 

1 Rookie

 • 

78 Posts

November 20th, 2018 05:00

I wish I only had 8 servers to fix! It appears not be an issue with a specific model of server - I've got 510, 520, 610, 620, 630, 710, 720, 730's and the install broke all of them. I've upgraded OMSA via OME since at least version 7.4 and don't remember any problems this bad.

2 Intern

 • 

685 Posts

November 20th, 2018 20:00

Please get in touch with Dell Support regarding this. They would take a closer look and help in resolving the problem.

14 Posts

November 21st, 2019 23:00

Have a similar situation with OMSA 9.3. Seems to be related to the PATH environment variable which contained "C:\Program Files\Dell\SysMgt\iSM\shared\bin" at the beginning. Thus Windows used some files from the OMSA directory instead of system directory.

1 Rookie

 • 

45 Posts

January 13th, 2020 05:00

Hi,

same for us. More then 10 Servers are affected. Really annoying.

Would be great if Dell could check the issue.

OMSA 9.3

Clean deinstall and new install, doesn't help.

 

Br

Sew

1 Rookie

 • 

45 Posts

January 29th, 2020 00:00

Could someone form Dell pls give a feedback.

Moderator

 • 

3.9K Posts

January 29th, 2020 01:00

Hi @SergejM,

 

I may need more of the details that you are facing.

 

Are you upgrading OMSA 9.3 from OME? What version of OME are you using?

You mentioned you are facing the same issue, what exact error message that you are getting?

1 Rookie

 • 

45 Posts

February 4th, 2020 02:00

Hi,

it depends. OME was installed in differnt ways (SCCM/SUU/OME).

It is obviously not a Problem of OME, but a Problem of the OMSA.

Same for me: "It appears that the problem is the DSM SA Connection Service won't start and gives an "Error 6: The handle is invalid" when I attempt to start it manually."

Clean deinstall, new install, still the same error.

All the people here have the same error. Do you need more information?

 

Br

Sergej

Moderator

 • 

3.9K Posts

February 4th, 2020 20:00

Hi @SergejM,

 

Mentioned clean uninstall, what have you uninstalled? Only OMSA? 

 

During the installation, was there any other components installed? 

 

Have you tried running as administrator on CMD and stop/start the DSM SA Connection Services? Is there any other DSM services running?

1 Rookie

 • 

45 Posts

February 14th, 2020 06:00

Hi,

 

OMSA was completely uninstalled from control panel.

All services except one, which was mention on top are running.

 

The Problem is solved with OMSA 9.4.

 

So thank you

No Events found!

Top