Yes it is a DC.

I just went through all my users and groups and do not see OMEAdministrators group.

Think I should uninstall and reinstall?

Hi Dave,

Is the OME server, by chance, a Windows Domain Controller?

If so, you need to put the user in the OMEAdministrators group manually.  This might be in the online help or User Guide.

If not a DC, is this a fresh install or upgrade?

Thanks,

Rob

Possibly,

But double check the user's guide under the special steps needed for a DC to make sure you didn't miss any steps.

Thanks,

Rob

It looks like I did not select the OME user during the SQL installation. I don't see where I should go to change the user associated with the SQL Server Config.

I'm looking at the three SQL services: SQL Server, Server Agent, and Server Browser.

SQL Server is running under account: MSSQL$SQLEXPRESSOME

SQL Agent is running under account: Built in Network Service

SQL Browser is running under account: Built in Local Service

Do you know if this is where I should change the login SQL account?

If so, which one?

Ok...so...

If the SQL Server service is running you shouldn’t have to change it.

OME wouldn’t have installed if it could not connect with SQL Server.

OME wouldn’t have installed unless it had a valid user to connect with SQL Server.

You do not need to change the SQL login account.

 

You might check the “OmeHostService.log” file in “c:\windows\temp” to make sure it is working.

If that service isn’t working it won’t create the OME user groups.

Thanks,

Rob

The SQL Agent and Browser are not running and both stopped.

Here is a link to the .log file: https://dl.dropboxusercontent.com/u/17522322/OmeHostService.log

I think the issue to related to SQL login. Seems to be the only thing I missed.

Do you know where I should change the login? Is it both the Agent and Browser that need to have the user added?

Hi,

So, it looks like the OME groups did not get created during the installation. The log file that you have attached is not accessible. Can you look into the installutil logs under windows\temp folder and see if you find something very obvious. You may want to try an uninstallation and reinstallation of OME as well if that helps.

Can you confirm this:

This looks like you have done a typical installation of OME with SQL express installed on the same DC? Is that right? 

Sorry for the delay in responding.

I can confirm the OME groups did not get created.

I uninstalled OME and reinstalled and the groups still were not created.

Before I reinstalled OEM I also uninstalled and reinstalled SQL Express (via OME Prereq screen) to ensure that the user that I created in the Managed Service Account was selected as the login account for SQL.

I looked thru the logs and don't see anything.

I just tried a repair to see a clean log file. It can be viewed here:

https://dl.dropboxusercontent.com/u/17522322/InstallUtil.log

I'm at a complete loss at this point. Not sure what else to do.

Any suggestions would be greatly appreciated.

Ok....

There is nothing wrong in the install log file.

There is an exception being thrown in the host service when it is trying to create the windows groups.

This looks like the error we fixed where the “Administrator” account was renamed, disabled, or on a non-english box.  Could this be the case for you?

 Dell.ManagementEssentials.Service.HostService.exe Error: 0 : System.Security.Principal.IdentityNotMappedException: Some or all identity

 

references could not be translated.

   at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)

   at System.Security.Principal.NTAccount.Translate(Type targetType)

   at Dell.OME.SecurityService.SecurityService.UpdateWindowsGroups(SqlConnection sqlConnection)

   at Dell.OME.SecurityService.SecurityService.UpdateWindowsGroups()

   at Helpers.Extensions.StaticThreads.<>c__DisplayClass1. b__0()

 

 What version of OME are you using?   The latest is v2.0.

Thanks much,

Rob

delltechcenter.com/ome

Yes the admin account has been renamed.

The install file is OpenManageEssentials_1_3_A01.

I'll get the 2.0 file and give that on a try.

Any other suggestions?

Yeah, try 2.0.  I think that's the version that fixed that particular bug.

Rob

That did the trick.

Thanks

Awesome...thanks for taking the time to update the thread.

Regards,

Rob