While installing PDF Create 2!, a window pops up that says, ADD PRINTER CAUSE OF FAILURE. Below is the verbose log file....... Any suggestions.......

Action start 12:36:04: InstallFinalize.
MSI (s) (08:F4) [12:36:04:860]: Running Script: C:\WINDOWS\Installer\MSIE2.tmp
MSI (s) (08:F4) [12:36:04:891]: User policy value 'DisableRollback' is 0
MSI (s) (08:F4) [12:36:04:891]: Machine policy value 'DisableRollback' is 0
MSI (s) (08:F4) [12:36:04:891]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=954295425,LangId=0,Platform=0,ScriptType=1,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (08:F4) [12:36:04:891]: Executing op: ProductInfo(ProductKey={6870FD05-9324-4E8A-90EB-6DBDAC29B74F},ProductName=ScanSoft PDF Create 2.0,PackageName=ScanSoft PDF Create 2.0.msi,Language=0,Version=34209792,Assignment=1,ObsoleteArg=0,,,PackageCode={DBF96BDE-0C0F-4DB1-A0FA-91C47FB514F9},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)
MSI (s) (08:F4) [12:36:04:891]: Executing op: DialogInfo(Type=0,Argument=0)
MSI (s) (08:F4) [12:36:04:891]: Executing op: DialogInfo(Type=1,Argument=ScanSoft PDF Create 2.0)
MSI (s) (08:F4) [12:36:04:906]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (08:F4) [12:36:04:906]: Executing op: SetBaseline(Baseline=0,)
MSI (s) (08:F4) [12:36:04:906]: Executing op: SetBaseline(Baseline=1,)
MSI (s) (08:F4) [12:36:04:906]: Executing op: ProductInfo(ProductKey={59973D03-28D0-43C7-A9C1-189093EBEDD4},ProductName=ScanSoft PDF Create! 2,PackageName=ScanSoft PDF Create! 2-eng.msi,Language=1033,Version=33554432,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={DDD9ADAB-A500-4621-BD5F-7E961F36DBBC},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)
MSI (s) (08:F4) [12:36:04:906]: Executing op: SetBaseline(Baseline=0,)
MSI (s) (08:F4) [12:36:04:906]: Executing op: SetBaseline(Baseline=1,)
MSI (s) (08:F4) [12:36:04:906]: Executing op: CustomActionSchedule(Action=AddPrinterRoolback,ActionType=1345,Source=BinaryData,Target=DeleteDocuComPDFDriver6,)
MSI (s) (08:F4) [12:36:04:906]: Executing op: CustomActionSchedule(Action=AddDocuComPDFDriver,ActionType=3073,Source=BinaryData,Target=AddDocuComPDFDriver,CustomActionData=C:\Program Files\ScanSoft\PDF Create! 2\)
MSI (s) (08:38) [12:36:04:938]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIED.tmp, Entrypoint: AddDocuComPDFDriver
Action ended 12:36:09: InstallFinalize. Return value 3.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
The crucial part of the log - the part which shows which Custom Action returned '3' - is missing. The entry for InstallFinalize shows that value because, in effect, it inherits it from the failing CA.

Use ProcMon as you install. I'm pretty confident it'll show you some ACCESS DENIED errors, most likely in the registry, because the account you're using has insufficient rights to write entries in the relevant keys.
Answered 07/10/2008 by: VBScab
Red Belt

Please log in to comment
0
please look at this log: Its pointing to DocucomPDFCreate custom action:

Action start 11:50:07: InstallFinalize.
MSI (s) (C4:98) [11:50:07:132]: Executing op: ProductInfo(ProductKey={59973D03-28D0-43C7-A9C1-189093EBEDD4},ProductName=ScanSoft PDF Create! 2,PackageName=ScanSoft PDF Create! 2-eng.msi,Language=1033,Version=33554432,Assignment=0,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={DDD9ADAB-A500-4621-BD5F-7E961F36DBBC},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)
MSI (s) (C4:98) [11:50:07:148]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\kutadav\Application Data
MSI (s) (C4:98) [11:50:07:148]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (C4:98) [11:50:07:148]: Executing op: DialogInfo(Type=1,Argument=ScanSoft PDF Create! 2)
MSI (s) (C4:98) [11:50:07:148]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (C4:98) [11:50:07:148]: Executing op: SetBaseline(Baseline=0,)
MSI (s) (C4:98) [11:50:07:148]: Executing op: SetBaseline(Baseline=1,)
MSI (s) (C4:98) [11:50:07:148]: Executing op: ActionStart(Name=AddPrinterRoolback,,)
MSI (s) (C4:98) [11:50:07:148]: Executing op: CustomActionSchedule(Action=AddPrinterRoolback,ActionType=1345,Source=BinaryData,Target=DeleteDocuComPDFDriver6,)
MSI (s) (C4:98) [11:50:07:148]: Executing op: ActionStart(Name=AddDocuComPDFDriver,,)
MSI (s) (C4:98) [11:50:07:148]: Executing op: CustomActionSchedule(Action=AddDocuComPDFDriver,ActionType=3073,Source=BinaryData,Target=AddDocuComPDFDriver,CustomActionData=C:\Program Files\ScanSoft\)
MSI (s) (C4:C0) [11:50:07:179]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIAC.tmp, Entrypoint: AddDocuComPDFDriver
MSI (s) (C4:98) [11:51:12:648]: User policy value 'DisableRollback' is 0
MSI (s) (C4:98) [11:51:12:648]: Machine policy value 'DisableRollback' is 0
Action ended 11:51:12: InstallFinalize. Return value 3.

It doesnot specify where exactly it failing.
Answered 07/10/2008 by: KVS
Yellow Belt

Please log in to comment
0
You missed my point. It doesn't really matter about the log. You need to determine WHY whatever action is involved is failing and the only way to do THAT is to monitor it as it executes. For that, you need a process/file/registry monitor. Anything else is just guess-work.
Answered 07/11/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity