Skip to main content
Solved

Having trouble installing FME Desktop


Installation of fme-desktop-b16494-win-x64.msi ended prematurely.

 

Logging states:

 

 

MSI (c) (AC:40) [14:57:23:216]: Doing action: MSIFILENAMESCRIPT

 

Action 14:57:23: MSIFILENAMESCRIPT.

 

Action start 14:57:23: MSIFILENAMESCRIPT.

 

MSI (c) (AC:08) [14:57:23:232]: Cloaking enabled.

 

MSI (c) (AC:08) [14:57:23:232]: Attempting to enable all disabled privileges before calling Install on server

 

MSI (c) (AC:08) [14:57:23:232]: Connected to service for CA interface.

 

MSI (c) (AC:6C) [14:57:23:279]: Failed to marshal script action.

 

MSI (c) (AC:6C) [14:57:23:279]: Failed to marshal script action.

 

Action ended 14:57:23: MSIFILENAMESCRIPT. Return value 3.

 

MSI (c) (AC:40) [14:57:23:279]: Doing action: FatalError

 

Action 14:57:23: FatalError.

 

Action start 14:57:23: FatalError.

Best answer by lenaatsafe

Hi @edwindaems

this question probably needs to be submitted as a support request via https://support.safe.com/knowledgeSubmitCase 

I've asked one of our developers who is working on installers to take a look at your log. Let me share his thoughts/suggestions with you:

  • This error is caused by the VBScript custom action failing to run due to some corruption on the OS.  This post here: http://www.advancedinstaller.com/forums/viewtopic.php?t=20115 explains that it is likely due to a corrupted registration of OLEAUT32.dll.  They recommend trying to register oleaut32.dll.  The relevant commands should be:
regsvr32 /u oleaut32.dll
regsvr32 oleaut32.dll

If the problem persists, please submit a support request and we will do further investigation.

View original
Did this help you find an answer to your question?

2 replies

mygis
Supporter
Forum|alt.badge.img+13
  • Supporter
  • June 6, 2016

Hi @edwindaems,

 

1. Could you please let us know the OS you are using?

2. Do you have administrative rights?

3. Have you tried re-downloading the installer? Perhaps it has been corrupted when downloading.

Cheers,


Forum|alt.badge.img
  • Best Answer
  • June 7, 2016

Hi @edwindaems

this question probably needs to be submitted as a support request via https://support.safe.com/knowledgeSubmitCase 

I've asked one of our developers who is working on installers to take a look at your log. Let me share his thoughts/suggestions with you:

  • This error is caused by the VBScript custom action failing to run due to some corruption on the OS.  This post here: http://www.advancedinstaller.com/forums/viewtopic.php?t=20115 explains that it is likely due to a corrupted registration of OLEAUT32.dll.  They recommend trying to register oleaut32.dll.  The relevant commands should be:
regsvr32 /u oleaut32.dll
regsvr32 oleaut32.dll

If the problem persists, please submit a support request and we will do further investigation.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings