Hi,

I'm packaging an application and when I run the install with the mst file I've made, I get the following error:
"1001 InstallUtilLib.dll unknown error". This happens when I first try to unistall, and after that I get this errormessage all the time, also when I try to reinstall
Anybody got some good tips for me?
The application also register some files with Regasm.exe, is there any way for me to find out which files that get registered under installation, and which ones that are already installed on the machine?
I'm using Wise packages studio btw.
here is some of the code from the log:


MSI (s) (C8:3C) [13:52:30:655]: Executing op: IniWriteRemoveValue(Section=General,Key=UNICODELOGIN,Value=TRUE,Mode=0)
WriteIniValues: File: application.ini, Section: General, Key: UNICODELOGIN, Value: TRUE
MSI (s) (C8:3C) [13:52:30:655]: Executing op: IniWriteRemoveValue(Section=General,Key=RootUrl,Value=http://application_server_share,Mode=0)
WriteIniValues: File: application.ini, Section: General, Key: RootUrl, Value: http://application_server_share
MSI (s) (C8:3C) [13:52:30:655]: Executing op: ActionStart(Name=ISSelfRegisterFiles,,)
Action 13:52:30: ISSelfRegisterFiles.
MSI (s) (C8:3C) [13:52:30:701]: Executing op: CustomActionSchedule(Action=ISSelfRegisterFiles,ActionType=3073,Source=BinaryData,Target=ISSelfRegisterFiles,CustomActionData=M:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\~5B.tmp)
MSI (s) (C8:C0) [13:52:30:701]: Invoking remote custom action. DLL: M:\WINDOWS\Installer\MSI5E.tmp, Entrypoint: ISSelfRegisterFiles
InstallShield 13:52:30: Initializing Property Bag...
InstallShield 13:52:30: Getting file count from property bag
InstallShield 13:52:30: File Count : 1
InstallShield 13:52:30: Sorting Based On Order...
InstallShield 13:52:30: This setup is running on a 32-bit Windows...No need to load ISBEW64.exe
InstallShield 13:52:30: Registering file M:\Program Files\vendor_name\Shared\https50.ocx (32-bit)
InstallShield 13:52:30: Begin Comitting Property Bag
InstallShield 13:52:30: Write KeyList count
InstallShield 13:52:30: Finished Comitting Property Bag
MSI (s) (C8:3C) [13:52:30:967]: Executing op: ActionStart(Name=_F33A3DBE5EC2CB759D64A895403FD778.commit,,)
Action 13:52:30: _F33A3DBE5EC2CB759D64A895403FD778.commit.
MSI (s) (C8:3C) [13:52:30:967]: Executing op: CustomActionSchedule(Action=_F33A3DBE5EC2CB759D64A895403FD778.commit,ActionType=3585,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=commit /LogFile= "M:\Program Files\vendor_name\application_name\Bin\BWMSAPICategory52_NET.dll" "M:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{3BEE632D-E423-4EBD-B983-406B73B6BCFB}\_isconfig.xml")
MSI (s) (C8:3C) [13:52:30:967]: Executing op: ActionStart(Name=_F33A3DBE5EC2CB759D64A895403FD778.rollback,,)
Action 13:52:30: _F33A3DBE5EC2CB759D64A895403FD778.rollback.
MSI (s) (C8:3C) [13:52:30:967]: Executing op: CustomActionSchedule(Action=_F33A3DBE5EC2CB759D64A895403FD778.rollback,ActionType=3329,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=rollback /LogFile= "M:\Program Files\vendor_name\application_name\Bin\BWMSAPICategory52_NET.dll" "M:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{3BEE632D-E423-4EBD-B983-406B73B6BCFB}\_isconfig.xml")
MSI (s) (C8:3C) [13:52:30:967]: Executing op: ActionStart(Name=_F33A3DBE5EC2CB759D64A895403FD778.install,,)
Action 13:52:30: _F33A3DBE5EC2CB759D64A895403FD778.install.
MSI (s) (C8:3C) [13:52:30:983]: Executing op: CustomActionSchedule(Action=_F33A3DBE5EC2CB759D64A895403FD778.install,ActionType=3073,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=install /LogFile= "M:\Program Files\vendor_name\application_name\Bin\BWMSAPICategory52_NET.dll" "M:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{3BEE632D-E423-4EBD-B983-406B73B6BCFB}\_isconfig.xml")
MSI (s) (C8:40) [13:52:30:983]: Invoking remote custom action. DLL: M:\WINDOWS\Installer\MSI5F.tmp, Entrypoint: ManagedInstall
Info 2835.The control ErrorIcon was not found on dialog SetupError.
Error 1001.InstallUtilLib.dll: Unknown error.
MSI (s) (C8!DC) [13:54:23:248]:
MSI (s) (C8:40) [13:54:23:310]: Leaked MSIHANDLE (48) of type 790531 for thread 5852
MSI (s) (C8:40) [13:54:23:310]: Note: 1: 2769 2: _F33A3DBE5EC2CB759D64A895403FD778.install 3: 1
Info 2769.Custom Action _F33A3DBE5EC2CB759D64A895403FD778.install did not close 1 MSIHANDLEs.
Action ended 13:54:23: InstallFinalize. Return value 3.


Any advice, please?

Thank you in advance
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
Complete guess...does the installing account have access to the network server/share which is mapped to the M: drive? Does that mapping exist at install time?
Answered 01/07/2010 by: VBScab
Red Belt

Please log in to comment
0
There is noe problem installing when I don't use transform.
There is a slight difference I see, and that is: I have to give two network paths during installation. When I run the transform (not silent) it seems like one of then goes back to default again, which is under program files on the local machine.

M:\ is my local drive, and local administrator is installing. I've also tried installing with a domain administrator permissions.
I've been searching through the logs, and I start to suspect that it might have something to do with registration of files and services. I think the installation rolls back about the the the file/service registration is about to happen.
Is there a way I can prove or disprove this? Maybe a path to certain services or dll's is missing in the transform, and then cause an error trying to register these?

Here is an extract from my msi with transform log:


Action ended 09:23:21: BW_REGASM. Return value 1.
Action 09:23:21: BW_RootUrl. Dialog created
MSI (c) (E4:C0) [09:23:21:101]: PROPERTY CHANGE: Deleting MsiSelectionTreeSelectedFeature property. Its current value is 'WorkstationInstallation'.
MSI (c) (E4:C0) [09:23:21:101]: PROPERTY CHANGE: Deleting MsiSelectionTreeSelectedAction property. Its current value is '3'.
MSI (c) (E4:C0) [09:23:21:101]: PROPERTY CHANGE: Deleting MsiSelectionTreeChildrenCount property. Its current value is '1'.
MSI (c) (E4:C0) [09:23:21:101]: PROPERTY CHANGE: Deleting MsiSelectionTreeInstallingChildrenCount property. Its current value is '1'.
MSI (c) (E4:C0) [09:23:21:101]: PROPERTY CHANGE: Deleting MsiSelectionTreeSelectedCost property. Its current value is '554'.
MSI (c) (E4:C0) [09:23:21:101]: PROPERTY CHANGE: Deleting MsiSelectionTreeChildrenCost property. Its current value is '63223'.
MSI (c) (E4:C0) [09:23:21:101]: PROPERTY CHANGE: Deleting MsiSelectionTreeSelectedPath property. Its current value is 'M:\Program Files\SUPPLIERNAME\SOFTWARENAME\'.
Action 09:23:22: ReadyToInstall. Dialog created
MSI (c) (E4:C0) [09:23:22:804]: Note: 1: 2727 2:
MSI (c) (E4:C0) [09:23:23:304]: Note: 1: 2727 2:


And here is the log without the transform: (and this one works)
Action start 14:34:37: BW_REGASM.
MSI (c) (20:AC) [14:34:37:349]: PROPERTY CHANGE: Adding BW_REGASM property. Its value is 'M:\WINDOWS\\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe'.
Action ended 14:34:37: BW_REGASM. Return value 1.
Action 14:34:37: BW_RootUrl. Dialog created
MSI (c) (20:AC) [14:34:37:364]: PROPERTY CHANGE: Deleting MsiSelectionTreeSelectedFeature property. Its current value is 'WorkstationInstallation'.
MSI (c) (20:AC) [14:34:37:364]: PROPERTY CHANGE: Deleting MsiSelectionTreeSelectedAction property. Its current value is '3'.
MSI (c) (20:AC) [14:34:37:364]: PROPERTY CHANGE: Deleting MsiSelectionTreeChildrenCount property. Its current value is '1'.
MSI (c) (20:AC) [14:34:37:380]: PROPERTY CHANGE: Deleting MsiSelectionTreeInstallingChildrenCount property. Its current value is '1'.
MSI (c) (20:AC) [14:34:37:380]: PROPERTY CHANGE: Deleting MsiSelectionTreeSelectedCost property. Its current value is '554'.
MSI (c) (20:AC) [14:34:37:380]: PROPERTY CHANGE: Deleting MsiSelectionTreeChildrenCost property. Its current value is '63223'.
MSI (c) (20:AC) [14:34:37:380]: PROPERTY CHANGE: Deleting MsiSelectionTreeSelectedPath property. Its current value is 'M:\Program Files\SUPPLIER\SOFTWARENAME\'.
MSI (c) (20:AC) [14:34:47:380]: PROPERTY CHANGE: Modifying BW_ROOTURL property. Its current value is 'http://'. Its new value: 'http://SERVERNAME/SHARENAME'.
MSI (c) (20:AC) [14:34:48:614]: PROPERTY CHANGE: Modifying BWUNICODE property. Its current value is 'FALSE'. Its new value: 'TRUE'.
Action 14:34:49: ReadyToInstall. Dialog created
MSI (c) (20:AC) [14:34:49:942]: Note: 1: 2727 2:
MSI (c) (20:AC) [14:34:50:442]: Note: 1: 2727 2:


There is also many lines in the log running MSI with the mst file which ends with something like this: ...Note: 1: 2262 2: #_BaselineCost 3: -2147287038
Does this indicate a problem, or is it normal?
Answered 01/08/2010 by: jgb
Orange Belt

Please log in to comment
0
(see also https://www-secure.symantec.com/connect/forums/specified-path-unavailable-error-1001installutillibdll#comment-3426351)

would there be any cases where registrypermissions would be a problem running an msi with a transform file when the msi without a transform file would run fine?
the msi runs fine without the transform.
don't think I'll find anything about this vendor or application in any forums... it's not a big company and they are making updates and small adjustmenst as we go along ... :-(

if you care to see the logs from a successful installation (without transform) and a log from a non successful installation (with transform) I could send you the logs by e-mail. I don't want to post them on the web...
Answered 01/08/2010 by: jgb
Orange Belt

Please log in to comment
0
You say on your Symantec Connect post on this subject that the transform creates a couple of network shares. If the installing account has no network access (i.e. if you are using pretty much any deployment system like Altiris or SCCM/SMS), this will fail since the System account has no access to network resources.
Answered 01/11/2010 by: VBScab
Red Belt

Please log in to comment
0
Resolved

It was Wise putting a lot of rubbish in my transform. used Orca instead, and now it looks better.
It ruined the trestructure under the program files directory, and added a lot of strange custon actions.

I've added more details on Symantec Connect Post

If anyone has any good tips about using Wise and avoiding these problems, I'd appreciate hearing them
Answered 01/12/2010 by: jgb
Orange Belt

Please log in to comment
0
[Removed]
Answered 01/13/2010 by: VBScab
Red Belt

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