Installation McAfee ePO Server fail with error code 1904

[rokasporch]

Hello,

ive got the following error message:

MSI (s) (18:04) [03:05:11:072]: Product: McAfee ePolicy Orchestrator -- Error 1904.Module C:\Program Files (x86)\McAfee\ePolicy Orchestrator\SiteManager64.dll failed to register. HRESULT -2147024770. Contact your support personnel.

Error 1904.Module C:\Program Files (x86)\McAfee\ePolicy Orchestrator\SiteManager64.dll failed to register. HRESULT -2147024770. Contact your support personnel.

Any ideas?

Thanks & Regards

Robert

[cdinet]

What version of epo?  Did you run setup as administrator?  Did you disable any AV scanning and especially access protection during the install?

[rokasporch]

What version of epo? - ePO 5.10

Did you run setup as administrator? - yes

Did you disable any AV scanning and especially access protection during the install? - no AV present

[cdinet]

You might want to open a ticket with McAfee then so we can walk through the install with you to find out why it can't register the dll.  That might require running procmon while running the install to see what might be blocking it.  Do you have any 3rd party security software installed on the server that monitors software installs?

[rokasporch]

Hi cdinet,

no there is no 3rd party software installed what can be blocked.

This windows system is fresh installed and where reset every day.

So i prever to investigate a little bit more in front of the S/R.

Is there anything what i can test or do?

[cdinet]

What do you mean reset every day?

[rokasporch]

the windows vm will be reset and installed new every day.

[cdinet]

That is absolutely not recommended for an epo server, as extension and software changes will not be retained, and you would need to reinstall epo every day.  Even if it is included on the image, it will not match with the database.  Definitely not recommended or supported in that scenario.

[rokasporch]

This is going into a wrong direction.

I know that it is not recommended or needed for an ePO Server to get reseted and installed every day.

That is not the point and please leave the point out.

What is interested, that the installation fails with this error message.

Is there a possibility without an Ticket to look while it fails?

[cdinet]

Not without some detailed logging and procmon possibly, which is going to require a service request.  You may want to leave that point out regarding the reinstall, but I can assure you, epo won't function properly in that scenario, even if the database is included in that reset.  There are so many other things involved.  I am obligated to inform you of that.