locked
Agent install Error: Microsoft ESENT keys are required to install this application. RRS feed

  • Question

  • Hello,

    I'm trying to install the R2 agent manually on a Windows 2008 x32 bit system and I get the following error:  "Microsoft ESENT keys are required to install this application. Please see the release notes for more information."  Anyone know what this means?

    Thanks,
    Tom

    Tuesday, July 28, 2009 6:51 PM

Answers

  • None of the above options worked for us.  However, we discovered our installation bits on our DSL were corrupt. We got fresh bits and all is good now.

    thanks

    • Marked as answer by martit01 Tuesday, August 4, 2009 6:49 PM
    Tuesday, August 4, 2009 6:48 PM

All replies

  • Hi,

    are you installing the Agent with elevated permissions? (Make a shortcut to the cmd-prompt, right click it, select run as administrator and run the msi-file from there)
    Best regards, Marnix Wolf (Thoughts on OpsMgr)
    Tuesday, July 28, 2009 6:57 PM
  • Also check this KB article: http://support.microsoft.com/kb/969569/EN-US
    Best regards, Marnix Wolf (Thoughts on OpsMgr)
    • Proposed as answer by hindsnc Thursday, March 10, 2011 11:22 AM
    Tuesday, July 28, 2009 6:59 PM
  • Yes, I'm a local Admin on the machine. But, I also tried it using the elevated permissions through the command prompt and running the msi, but still gettin the same error.

    Tuesday, July 28, 2009 7:31 PM
  • I tried to follow the KB article, but it said this command was only for systems which already had the application installed.

    msiexec /I{768DB8BD-CB3A-43F4-9A4C-BA2921D27AD3}
    Tuesday, July 28, 2009 7:34 PM
  • Hi.

    has this server already had an Agent installation before?
    Best regards, Marnix Wolf (Thoughts on OpsMgr)
    Tuesday, July 28, 2009 7:41 PM
  • I do not believe so. When I browse out to HKEY_Local Machine\Software\Microsoft, I don't see Microsoft Operations Manager there.  However, now that I think about it....., our OSD image comes standard with a x64 bit SCOM R2 agent. This is one of our nonstandard x32 systems. So, the x64 agent probably got removed somewhere along the way and I'm now stuck with this error when trying to install the x32 scom agent.
    Tuesday, July 28, 2009 8:01 PM
  • OK, let me try something in one of my test environments

    Best regards, Marnix Wolf (Thoughts on OpsMgr)
    Tuesday, July 28, 2009 8:48 PM
  • Great, thanks Marnix.....
    Tuesday, July 28, 2009 8:49 PM
  • Hi Martit01

    Sorry but I can not reproduce this. I run multiple Windows 2008 servers, x32 and x64 but whatever I try, this error doesn't show up.


    I would check on the dll version of ESENT.dll on the faulty server and compare it to a working W2K08 x32 server. Also check the registry entries of this dll (HK_LM\System\CurrentControlSet\Services\ESENT, also subkey ~Performance and HK_LM\System\CurrentControlSet\Services\EventLog\Application\ESENT) and compare them to a working W2K08 x32 server.

    When ever there are any mismatches you could THINK of exporting the settings of the working server into the faulty one. But that could wreck more havoc than doing good. So be careful about it. But really be carefull and be sure to have valid backups.

    Perhaps some one else on this forum has good advice on it (I'll mail this thread to some one who has great knowledge on OpsMgr) otherwise a supportcall to Microsoft is in order.

    Wish I had other news.
    Best regards, Marnix Wolf (Thoughts on OpsMgr)
    Tuesday, July 28, 2009 9:16 PM
  • Hi Martit01

    As promised I got some one else in to it as well.

    This is what he (Graham Davies) said:

    Never seen this to be honest - the kb article you mention is about the only reference I can google which does suggest that potentially an agent did exist on that machine in the past.

    Other things to possibly look at (clutching at straws here):
    - any related ESENT errors in the application or system log
    - any anti-virus running on the machine that could be interfering with the install. Can they turn off for a test?
    - does any log file get created when they try and install the agent? It doesn't sound like it is getting that far. Perhaps find out at which stage it fails.



    Best regards, Marnix Wolf (Thoughts on OpsMgr)
    Wednesday, July 29, 2009 5:44 AM
  • Try logging in on the server with the local Administrator account. That worked for me.
    Wednesday, July 29, 2009 8:42 AM
  • Hi Try it with this one:

    msiexec /I{25097770-2B1F-49F6-AB9D-1C708B96262A}


    Greets
    Wednesday, July 29, 2009 2:39 PM
  • None of the above options worked for us.  However, we discovered our installation bits on our DSL were corrupt. We got fresh bits and all is good now.

    thanks

    • Marked as answer by martit01 Tuesday, August 4, 2009 6:49 PM
    Tuesday, August 4, 2009 6:48 PM
  • Running from command prompt elevated fix this issue for me.

    Thanks.

    Thursday, February 2, 2012 4:12 PM
  • Nice.

    For our case ( several 2012R2 servers and scom 2016 Agent ) the HKLM\System\CurrentControlSet\Services\EventLog\Application\ESENT was lost . Very strange. After recreating key (export/import from working server)   agent was installed successfully.

    Maybe some agent update (deployed via SCCM ) messed with it ? 

     


    • Edited by Andres P Friday, April 27, 2018 11:09 AM
    Friday, April 27, 2018 11:08 AM
  • Yup, same here. Copied a new MSP and worked for the SCOM 2016 UR 6  Management Server Role

    "I live and die by the command line" -JL 2010 © ©

    Thursday, March 14, 2019 1:04 PM