1603 (Fatal Error) caused by vbs Custom Actions
I have a few MSI's that contain custom action (type 38) that call vbs code. 99.9% of the time this works.
However, every now and then I come across a machine that throws a 1603 (Fatal Error) when it comes across these custom actions.
I believe it has something to do with a corrupt Windows Scripting Host (WSH) on the target system. I can't recall if reinstalling WSH resolves the issue. All computers in question are running Windows XP SP2.
Has anyone else come across this situation and found a solution that doesn't involve a rebuild? [:)]
However, every now and then I come across a machine that throws a 1603 (Fatal Error) when it comes across these custom actions.
I believe it has something to do with a corrupt Windows Scripting Host (WSH) on the target system. I can't recall if reinstalling WSH resolves the issue. All computers in question are running Windows XP SP2.
Has anyone else come across this situation and found a solution that doesn't involve a rebuild? [:)]
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
AngelD
17 years ago
What did a verbose log say?
Do you get the error on all or some machines?
Do you get the error on all or some machines?
Posted by:
goosey1
17 years ago
Hi,
Thanks for your interest. The error occurs on very few machines.
Here's the verbose log from Microsoft's RAW image viewer MSI.
----
MSI (s) (B8:14) [16:13:39:362]: Doing action: CheckHKEY_USERSFileExts
Action ended 16:13:39: RegisterProduct. Return value 1.
MSI (s) (B8:FC) [16:13:39:382]: Failed to marshal script action.
MSI (s) (B8:FC) [16:13:39:382]: Failed to marshal script action.
Action start 16:13:39: CheckHKEY_USERSFileExts.
MSI (s) (B8:14) [16:13:39:382]: Machine policy value 'DisableRollback' is 0
MSI (s) (B8:14) [16:13:39:382]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
Action ended 16:13:39: CheckHKEY_USERSFileExts. Return value 3.
---
I have found that re-registering oleaut32.dll fixes the problem. (ie. regsvr32 oleaut32.dll)
What worries me is what else is wrong with the machine because oleaut32.dll is a pretty core file. [8|]
Thanks for your interest. The error occurs on very few machines.
Here's the verbose log from Microsoft's RAW image viewer MSI.
----
MSI (s) (B8:14) [16:13:39:362]: Doing action: CheckHKEY_USERSFileExts
Action ended 16:13:39: RegisterProduct. Return value 1.
MSI (s) (B8:FC) [16:13:39:382]: Failed to marshal script action.
MSI (s) (B8:FC) [16:13:39:382]: Failed to marshal script action.
Action start 16:13:39: CheckHKEY_USERSFileExts.
MSI (s) (B8:14) [16:13:39:382]: Machine policy value 'DisableRollback' is 0
MSI (s) (B8:14) [16:13:39:382]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
Action ended 16:13:39: CheckHKEY_USERSFileExts. Return value 3.
---
I have found that re-registering oleaut32.dll fixes the problem. (ie. regsvr32 oleaut32.dll)
What worries me is what else is wrong with the machine because oleaut32.dll is a pretty core file. [8|]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.