Agent install Error: Microsoft ESENT keys are required to install this application.
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
July 28th, 2009 9:51pm

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)
Free Windows Admin Tool Kit Click here and download it now
July 28th, 2009 9:57pm

Also check this KB article: http://support.microsoft.com/kb/969569/EN-USBest regards, Marnix Wolf (Thoughts on OpsMgr)
July 28th, 2009 9:59pm

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.
Free Windows Admin Tool Kit Click here and download it now
July 28th, 2009 10:31pm

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}
July 28th, 2009 10:34pm

Hi.has this server already had an Agent installation before?Best regards, Marnix Wolf (Thoughts on OpsMgr)
Free Windows Admin Tool Kit Click here and download it now
July 28th, 2009 10:41pm

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.
July 28th, 2009 11:01pm

OK, let me try something in one of my test environmentsBest regards, Marnix Wolf (Thoughts on OpsMgr)
Free Windows Admin Tool Kit Click here and download it now
July 28th, 2009 11:48pm

Great, thanks Marnix.....
July 28th, 2009 11:49pm

Hi Martit01Sorry 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)
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2009 12:16am

Hi Martit01As 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)
July 29th, 2009 8:44am

Try logging in on the server with the local Administrator account. That worked for me.
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2009 11:42am

Hi Try it with this one: msiexec /I{25097770-2B1F-49F6-AB9D-1C708B96262A} Greets
July 29th, 2009 5:39pm

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
Free Windows Admin Tool Kit Click here and download it now
August 4th, 2009 9:48pm

Running from command prompt elevated fix this issue for me. Thanks.
February 3rd, 2012 11:14am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics