PDA

View Full Version : Help! Our Install set tries to connect to the network user home directory



janejackman
11-01-2001, 10:18 AM
Help! Our Install set tries to connect to the network user home directory

Has anyone any idea why this is so? It wants to attach to the u: drive on our users pcs but we are not linking to home directories anywhere in the install set up! I a very confused!

Tech support please help!

Jane

hofmann
11-01-2001, 10:41 AM
Hi Jane,

usually the setup has to lookup quite some directories. Try to produce a log file and look where it accesses the drive.

setup.exe /v"/lv c:\log.txt"

Because I use folder redirection and roaming profiles I can see quite some server paths in my setup log.

Regards,

Juergen

janejackman
11-02-2001, 04:22 AM
Juergen,

Thanks for that advice. We tried it just now and we got a couple of log files created inthe temp directory but no log.txt! The files were:-

MSI38440.LOG which contained
Error 1327.Invalid Drive: U:\
=== Logging stopped: 02/11/01 09:11:26 ===

and msievent.log whic contained
29/10/01 11:11:28 (Info ) Product: Windows Installer -- Installation operation completed successfully.

29/10/01 11:12:05 (Info ) Install operation initiated a reboot

29/10/01 11:12:59 (Error ) Product: ParitySC -- Error 1327.Invalid Drive: U:\

29/10/01 11:14:42 (Error ) Product: ParitySC -- Error 1327.Invalid Drive: U:\

31/10/01 16:05:47 (Error ) Product: ParitySC -- Error 1327.Invalid Drive: U:\

02/11/01 09:11:24 (Error ) Product: ParitySC -- Error 1327.Invalid Drive: U:\

So I am still confused!! Any ideas?

Best wishes,

Jane

hofmann
11-02-2001, 04:45 AM
Jane,

a pitty that you don't get the logging running. Could you make a second attempt to produce the log.txt because it really could help a lot.

If you have a setup.exe try to execute

setup.exe /V"/lv c:\log.txt"

You can replace c:\log.txt by a different name. Make sure that you put /V"/lv without any spaces, the only space should be in front of c:\log.txt

If this doesn't work, you could try to create just a msi file. Then run

msiexec /IyourPackag.msi /lv c:\log2.txt

This should create a log.

I also remember a similar problem I had some time ago, but this was a setup build with a different tool. At that time I accidently included a property which content was "d:". This caused the installer to try to access the d: drive during installation, which was absent on some machines. You could check for thist by opening the msi file in Orca or use one of the sample scripts contained in the MSI SDK (you can download it on the Microsoft site). Have a look into the property table. But I guess you can ommit this hazzle, if you manage to get the log produced.

Juergen

janejackman
11-02-2001, 05:02 AM
Hi Juergen! We actually manged to create a log file this time, those damn spaces! The contents were:-

=== Verbose logging started: 02/11/01 09:53:00 Build type: SHIP ANSI 1.20.1827.00 Calling process: C:\WINDOWS\SYSTEM\MSIEXEC.EXE ===
MSI (c) (1B:CF): Resetting cached policy values
MSI (c) (1B:CF): ******* RunEngine:
******* Product: c:\windows\TEMP\_is4305\ParitySC.msi
******* Action:
******* CommandLine:
MSI (c) (1B:CF): No info for thread FFC279CF
MSI (c) (1B:CF): Did not find item Products\(NULL)
MSI (c) (1B:CF): Searching for item Products\(NULL) in per-user non-managed key
MSI (c) (1B:CF): Did not find item Products\(NULL)
MSI (c) (1B:CF): Searching for item Products\(NULL) in per-machine key
MSI (c) (1B:CF): Did not find item Products\(NULL)
MSI (c) (1B:CF): Did not find item Products\(NULL)
MSI (c) (1B:CF): End dialog not enabled
MSI (c) (1B:CF): Original package ==> c:\windows\TEMP\_is4305\ParitySC.msi
MSI (c) (1B:CF): Package we're running from ==> c:\windows\TEMP\29ba8a.msi
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-user non-managed key
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-machine key
MSI (c) (1B:CF): Did not find item Products\8AE33BF5905CF5248B5C7EB1AA00EB48
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-user non-managed key
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-machine key
MSI (c) (1B:CF): Did not find item Products\8AE33BF5905CF5248B5C7EB1AA00EB48
MSI (c) (1B:CF): Machine policy value 'TransformsSecure' is 0
MSI (c) (1B:CF): User policy value 'TransformsAtSource' is 0
MSI (c) (1B:CF): Transforms are not secure.
MSI (c) (1B:CF): Product Code passed to Engine.Initialize: ''
MSI (c) (1B:CF): Product Code from property table before transforms: '{5FB33EA8-C509-425F-B8C5-E71BAA00BE84}'
MSI (c) (1B:CF): Product Code from property table after transforms: '{5FB33EA8-C509-425F-B8C5-E71BAA00BE84}'
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-user non-managed key
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-machine key
MSI (c) (1B:CF): Did not find item Products\8AE33BF5905CF5248B5C7EB1AA00EB48
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-user non-managed key
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-machine key
MSI (c) (1B:CF): Did not find item Products\8AE33BF5905CF5248B5C7EB1AA00EB48
MSI (c) (1B:CF): Note: 1: 2729
MSI (c) (1B:CF): Note: 1: 2729
MSI (c) (1B:CF): Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (c) (1B:CF): Machine policy value 'DisableMsi' is 0
MSI (c) (1B:CF): Machine policy value 'AlwaysInstallElevated' is 0
MSI (c) (1B:CF): User policy value 'AlwaysInstallElevated' is 0
MSI (c) (1B:CF): Running product '{5FB33EA8-C509-425F-B8C5-E71BAA00BE84}' with user privileges: It's not assigned.
MSI (c) (1B:CF): TRANSFORMS property is now:
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\Application Data
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\Favorites
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\NetHood
MSI (c) (1B:CF): Found shell folder U:\ by spelunking through the registry.
MSI (c) (1B:CF): Found shell folder by spelunking through the registry.
MSI (c) (1B:CF): Note: 1: 2103 2: 27
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\Recent
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\SendTo
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\ShellNew
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\All Users\Application Data
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\Local Settings\Application Data
MSI (c) (1B:CF): Found shell folder by spelunking through the registry.
MSI (c) (1B:CF): Note: 1: 2103 2: 39
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\Start Menu\Programs\Administrative Tools
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\Start Menu\Programs\StartUp
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\Start Menu\Programs
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\Start Menu
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\Desktop
MSI (c) (1B:CF): SHFOLDER::SHGetFolderPath returned: C:\WINDOWS\FONTS
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-user non-managed key
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-machine key
MSI (c) (1B:CF): Did not find item Products\8AE33BF5905CF5248B5C7EB1AA00EB48
=== Logging started: 02/11/01 09:53:03 ===
MSI (c) (1B:CF): Machine policy value 'DisableRollback' is 0
MSI (c) (1B:CF): User policy value 'DisableRollback' is 0
MSI (c) (1B:CF): Doing action: INSTALL
Action start 09:53:03: INSTALL.
MSI (c) (1B:CF): UI Sequence table 'InstallUISequence' is present and populated.
MSI (c) (1B:CF): Running UISequence
MSI (c) (1B:CF): Doing action: IsLaunchConditions.6FC97963_2511_11D4_BB8A_00C04F20D375
Action start 09:53:03: IsLaunchConditions.6FC97963_2511_11D4_BB8A_00C04F20D375.
MSI (c) (1B:CF): Creating MSIHANDLE (1) of type 790542 for thread -4032049
Action ended 09:53:03: IsLaunchConditions.6FC97963_2511_11D4_BB8A_00C04F20D375. Return value 1.
MSI (c) (1B:CF): Doing action: CheckForDCOM.6FC97963_2511_11D4_BB8A_00C04F20D375
Action start 09:53:03: CheckForDCOM.6FC97963_2511_11D4_BB8A_00C04F20D375.
MSI (c) (1B:CF): Creating MSIHANDLE (7) of type 790542 for thread -4032049
Action ended 09:53:03: CheckForDCOM.6FC97963_2511_11D4_BB8A_00C04F20D375. Return value 1.
MSI (c) (1B:CF): Skipping action: InstallDCOM.6FC97963_2511_11D4_BB8A_00C04F20D375 (condition is false)
MSI (c) (1B:CF): Skipping action: IsForceReboot.6FC97963_2511_11D4_BB8A_00C04F20D375 (condition is false)
MSI (c) (1B:CF): Doing action: LaunchConditions
Action start 09:53:03: LaunchConditions.
Action ended 09:53:03: LaunchConditions. Return value 1.
MSI (c) (1B:CF): Doing action: CheckForMDAC.5D1BD0D5_2526_11D4_BB8A_00C04F20D375
Action start 09:53:03: CheckForMDAC.5D1BD0D5_2526_11D4_BB8A_00C04F20D375.
MSI (c) (1B:CF): Creating MSIHANDLE (8) of type 790542 for thread -4032049
Action ended 09:53:03: CheckForMDAC.5D1BD0D5_2526_11D4_BB8A_00C04F20D375. Return value 1.
MSI (c) (1B:CF): Skipping action: InstallMDAC.5D1BD0D5_2526_11D4_BB8A_00C04F20D375 (condition is false)
MSI (c) (1B:CF): Skipping action: IsForceReboot.5D1BD0D5_2526_11D4_BB8A_00C04F20D375 (condition is false)
MSI (c) (1B:CF): Doing action: SetupInitialization
Action start 09:53:03: SetupInitialization.
Internal Error 2898. ExpressDefault, Tahoma, 0
Internal Error 2898. TahomaBold10, Tahoma, 0
Action ended 09:53:03: SetupInitialization. Return value 1.
MSI (c) (1B:CF): Doing action: FindRelatedProducts
Action start 09:53:03: FindRelatedProducts.
MSI (c) (1B:CF): Note: 1: 2262 2: Upgrade 3: -2147287038
Action ended 09:53:03: FindRelatedProducts. Return value 1.
MSI (c) (1B:CF): Doing action: AppSearch
Action start 09:53:03: AppSearch.
MSI (c) (1B:CF): Note: 1: 2262 2: AppSearch 3: -2147287038
Action ended 09:53:03: AppSearch. Return value 1.
MSI (c) (1B:CF): Skipping action: CCPSearch (condition is false)
MSI (c) (1B:CF): Skipping action: RMCCPSearch (condition is false)
MSI (c) (1B:CF): Doing action: ValidateProductID
Action start 09:53:03: ValidateProductID.
Action ended 09:53:03: ValidateProductID. Return value 1.
MSI (c) (1B:CF): Doing action: CostInitialize
Action start 09:53:03: CostInitialize.
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-user non-managed key
MSI (c) (1B:CF): Searching for item Products\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-machine key
MSI (c) (1B:CF): Did not find item Products\8AE33BF5905CF5248B5C7EB1AA00EB48
Action ended 09:53:03: CostInitialize. Return value 1.
MSI (c) (1B:CF): Doing action: FileCost
Action start 09:53:03: FileCost.
MSI (c) (1B:CF): Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (c) (1B:CF): Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (1B:CF): Note: 1: 2262 2: IniFile 3: -2147287038
MSI (c) (1B:CF): Note: 1: 2262 2: MoveFile 3: -2147287038
MSI (c) (1B:CF): Note: 1: 2262 2: DuplicateFile 3: -2147287038
Action ended 09:53:03: FileCost. Return value 1.
MSI (c) (1B:CF): Doing action: IsolateComponents
Action start 09:53:03: IsolateComponents.
MSI (c) (1B:CF): Note: 1: 2262 2: IsolatedComponent 3: -2147287038
MSI (c) (1B:CF): Note: 1: 2262 2: BindImage 3: -2147287038
MSI (c) (1B:CF): Note: 1: 2262 2: Patch 3: -2147287038
Action ended 09:53:03: IsolateComponents. Return value 1.
MSI (c) (1B:CF): Doing action: ResolveSource
Action start 09:53:03: ResolveSource.
MSI (c) (1B:CF): Resolving source.
MSI (c) (1B:CF): Resolving source to launched-from source.
MSI (c) (1B:CF): Setting launched-from source as last-used.
MSI (c) (1B:CF): SOURCEDIR ==> c:\windows\TEMP\_is4305\
MSI (c) (1B:CF): SOURCEDIR product ==> {5FB33EA8-C509-425F-B8C5-E71BAA00BE84}
Action ended 09:53:03: ResolveSource. Return value 1.

continued....

janejackman
11-02-2001, 05:03 AM
And the rest of the message......


MSI (c) (1B:CF): Doing action: CostFinalize
Action start 09:53:03: CostFinalize.
MSI (c) (1B:CF): Note: 1: 2262 2: Patch 3: -2147287038
MSI (c) (1B:CF): Note: 1: 2262 2: Condition 3: -2147287038
MSI (c) (1B:CF): Searching for item Features\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-user non-managed key
MSI (c) (1B:CF): Searching for item Features\8AE33BF5905CF5248B5C7EB1AA00EB48 in per-machine key
MSI (c) (1B:CF): Did not find item Features\8AE33BF5905CF5248B5C7EB1AA00EB48
MSI (c) (1B:CF): Note: 1: 1327 2: U:\
Internal Error 2835. ErrorIcon, SetupError
MSI (c) (1B:CF): Product: ParitySC -- Error 1327.Invalid Drive: U:\

Action ended 09:53:09: CostFinalize. Return value 3.
MSI (c) (1B:CF): Doing action: SetupCompleteError
Action start 09:53:09: SetupCompleteError.


So the problem seems to be Internal Error 2835. ErrorIcon. What part of an install set does this come from? I do appreciate your help. Thanks very much.

Regards,

Jane

hofmann
11-02-2001, 05:47 AM
:( Do be honest I get a little bit lost now. So probably somebody of Installshield should comment on this.

However, I still believe that the problem is not the Icon Error.
I have the impression (but I'm really moving on thin ice now) that the installer is not able to finish its CostFinalize because it can not access certain Folders (CSIDL_PRINTHOOD and CSIDL_MYPICTURES I believe). At least it found u: by "spelunking through the registry". I had similar problems on one machine, where the CSIDL_PERSONAL registry key pointed to an invalid location.

Perhaps you can try to locate where the U: comes from in the registry and why it is not acccessible, or you could map u: temporarily to see if the install succeeds than.

Sorry for not being of much help with this...

Juergen

janejackman
11-02-2001, 06:14 AM
Juergen,

We found in the registry that CSIDL_PERSONAL registry key is pointed to an invalid location. We are now working on a little reg fix that can eb applied before and after the install.

Thanks for your help in this matter. If you are ever in Egham, UK we will buy you a few beers!

Jane

hofmann
11-02-2001, 06:25 AM
I will surely come back to the beers some time! (Is it also possible to get some bears?)

Chandima
11-02-2001, 09:53 AM
You da man!