PDA

View Full Version : Strange error message during the setup preparation



Neoptec
10-14-2003, 08:04 AM
Hi, I'm experiencing some strange behaviour from Devstudio right now.

I have upgraded my IS developer 8.02 project without any error.
But when I'm trying to launch the setup, It keeps sending me a strange message.
It happens on the Initialize event

the translated message is :
Cannot access the network folder 91WindowsFolder93

Seeing this, I decided to recreate my setup from scratch but I'm getting the same error.

Any ideas would be great from anyone :)

Thanks in advance.

EDIT: using an MSI installscript project.

The exactly same project recreate as a non MSI installscript project (professional) works perfectly.

RichAquino
10-15-2003, 10:31 AM
Hi,

I think the problem is that there's a string in your project that should be like "[WindowsFolder]" but instead is "91WindowsFolder93". 91 and 93 are the ascii codes for '[' and ']'.

I would suggest that you first look at the Directory table. If that doesn't help, try logging the installation. It may make it clear what part of your project has the corrupted string.

I'd be interested to know how the string became corrupted.

Rich

Neoptec
10-16-2003, 07:11 AM
Ok I have this in my directory table

.:Windows

Looks ok to me
Going to log the setup

Neoptec
10-16-2003, 07:55 AM
=== Verbose logging started: 16/10/2003 14:56:06 Build type: SHIP UNICODE 2.00.2600.1106 Calling process: C:\PROGRA~1\FICHIE~1\INSTAL~1\Driver\9\INTEL3~1\IDriver.exe ===
=== Début de l'écriture dans le journal : 16/10/2003 14:56:06 ===
Début de l'action 14:56:06 : ISVerifyScriptingRuntime.
Fin de l'action 14:56:06 : ISVerifyScriptingRuntime. Valeur renvoyée : 1.
Début de l'action 14:56:06 : ISSetupFilesExtract.
1: Starting to extract setup files
1: Getting SUPPORTDIR property :
1: Extracting SetupFiles to: C:\DOCUME~1\TRUITE~1\LOCALS~1\Temp\{03DDE42C-4A0A-4DFF-9CC4-7B70ABC5E570}
1: Getting ISSetupFile table view
1: Executing ISSetupFile table view
1: Extracting Setup File:
1: C:\DOCUME~1\TRUITE~1\LOCALS~1\Temp\{03DDE42C-4A0A-4DFF-9CC4-7B70ABC5E570}\Licence.txt
1: Settign SUPPORTDIR property to: C:\DOCUME~1\TRUITE~1\LOCALS~1\Temp\{03DDE42C-4A0A-4DFF-9CC4-7B70ABC5E570}
1: Setting ISSETUPFILESCOMPLETED property
Fin de l'action 14:56:06 : ISSetupFilesExtract. Valeur renvoyée : 1.
Début de l'action 14:56:06 : AppSearch.
Fin de l'action 14:56:06 : AppSearch. Valeur renvoyée : 1.
Début de l'action 14:56:06 : LaunchConditions.
Fin de l'action 14:56:06 : LaunchConditions. Valeur renvoyée : 1.
Début de l'action 14:56:06 : FindRelatedProducts.
Fin de l'action 14:56:06 : FindRelatedProducts. Valeur renvoyée : 1.
Début de l'action 14:56:06 : ValidateProductID.
Fin de l'action 14:56:06 : ValidateProductID. Valeur renvoyée : 1.
Début de l'action 14:56:06 : CostInitialize.
Fin de l'action 14:56:06 : CostInitialize. Valeur renvoyée : 1.
Début de l'action 14:56:06 : FileCost.
Fin de l'action 14:56:06 : FileCost. Valeur renvoyée : 1.
Début de l'action 14:56:06 : IsolateComponents.
Fin de l'action 14:56:06 : IsolateComponents. Valeur renvoyée : 1.
Début de l'action 14:56:06 : setUserProfileNT.
Fin de l'action 14:56:06 : setUserProfileNT. Valeur renvoyée : 1.
Début de l'action 14:56:06 : setAllUsersProfile2K.
Fin de l'action 14:56:06 : setAllUsersProfile2K. Valeur renvoyée : 1.
Début de l'action 14:56:06 : ResolveSource.
Fin de l'action 14:56:06 : ResolveSource. Valeur renvoyée : 1.
Début de l'action 14:56:06 : CostFinalize.
Erreur 1606. Impossible d'accéder à l'emplacement réseau 91WindowsFolder93.
Erreur 1606. Impossible d'accéder à l'emplacement réseau 91WindowsFolder93.
Erreur 1606. Impossible d'accéder à l'emplacement réseau 91WindowsFolder93.
Erreur 1606. Impossible d'accéder à l'emplacement réseau 91WindowsFolder93.
Erreur 1606. Impossible d'accéder à l'emplacement réseau 91WindowsFolder93.
Erreur 1606. Impossible d'accéder à l'emplacement réseau 91WindowsFolder93.
Erreur 1606. Impossible d'accéder à l'emplacement réseau 91WindowsFolder93.
Erreur 1606. Impossible d'accéder à l'emplacement réseau 91WindowsFolder93.
Fin de l'action 14:56:10 : CostFinalize. Valeur renvoyée : 3.
1: Failed to launch action 'CostFinalize', error is 1603
=== Verbose logging stopped: 16/10/2003 14:56:10 ===


Not helping much I'm afraid

RichAquino
10-16-2003, 12:05 PM
Hi,

Try this...

1. In the General Information\Project Properties view, change the project file format to XML.
2. Find your ISM, and open it in a text editor.
3. Search for the 91WindowsFolder93 string.

Rich

jamali
10-17-2003, 01:45 AM
Hi Guys,

It seems that you are not the only one having this issue with Dev Studio 9, We are facing the same problem but with a minor difference that it is :

Action start 16:09:39: CostFinalize.
Error 1606.Could not access network location 91SystemFolder93.

This happens when we make a component's exe file the key file , that exe contains a NT Service. When the exe is not made the key file, Setup runs fine but fails to register the Service. However when the exe is made the key file, the Error 1606 comes up.

We also checked the Dev Studio 9 XML based ism file for 91 or 93 or anything before or after SystemFolder but cant find anything like 91 or 93. infact what was there is something like :

<td>SystemFolder</td>

which are tags from HTML/XML

Since the ism file structure has changed in Dev Studio 9, i have a feeling that this might be comming from the XML parsing of the ism file as everything gets storted there. But unless confirmed i suppose it is an assumption

We created a setup in InstallShield Developer 8 SP2 and it was tested on a clean box and it was working ok, then the setup was
upgraded and the same probelm occured. We even tried creating a new setup with InstallShield Dev Studio 9 and the same problem is happening.

We also checked the tables refered by CostFinalize and they seems to contain the correct values, Then we decided to attempt to debug the msi file ( Using MSI Debugger inegrated in Dev Studio9 ) created by the Setup and noticed that the Dev Studio 9 crashed.

Our Build info of InstallShield is as under

---------------------------------------------------------------------------
InstallShield (R) DevStudio Script Compiler
Version 9.0.0.333
Copyright (C) 1990-2003 InstallShield Software Corporation
-----------------------------------------------------------------------------

Any info on this will be a great help,

thanks

Syed

jamali
10-17-2003, 02:13 AM
Changed the project file to binary, without exe being the key file setup was fine but failed to register the service. When the exe was made the key file same problem appeared.


Since the last line in the verbose log is
Action ended 16:09:46: CostFinalize. Return value 3.

1: Failed to launch action 'CostFinalize', error is 1603
=== Verbose logging stopped: 10/16/2003 16:09:46 ===

The returned error 1603 is described in Platform SDK: Windows Installer / Logging of Action Return Values as :


.Error Code = ERROR_INSTALL_FAILURE
.Values returned by Function Call = 1603
.Value that Appear in the Log = 3
.description = Fatal error



Any comments will be a great help


thanks in advance

Neoptec
10-17-2003, 02:29 AM
I don't have the string 91WindowsFolder93 in it :(

I only have this: <td>WindowsFolder</td>

This behaviour is brand new to DevStudio since my Installation works perfectly with Developer 8.02.

It's when I'm upgrading the project or when I'm rebuild ing it from scratch with an MSI Installscript project.

As I mentionned before, I have recreate this one (yeah I love recreate projects...) with a non MSI Installscript project and everything's goes smoothly.

It's quite urgent as we've finished the tests and I'm the only one keeping the project from shipping.

BTW thanks very much for your quick answers and your concerns.

jamali
10-17-2003, 02:36 AM
Please verify if the problem we are facing has something to do with the exe being made the key file

thanks

Neoptec
10-17-2003, 02:38 AM
Well all my exes are in differents components and are key files.
I'm going to check this one thanks.

Neoptec
10-17-2003, 02:43 AM
Ok, still not working after the key files removing.

Stefan Krueger
10-17-2003, 04:49 AM
I recommend you open the generated .msi file in Orca and look for those problem strings:

91WindowsFolder93
91SystemFolder93

Please specify what project file format you use (binary or XML) and whether you switched between the formats.

Neoptec
10-17-2003, 04:57 AM
I used XML right from the start.

It is located in the property table :

Property = DIRPROPERTY1
Value = 91WindowsFolder93

EDIT: When I edit the value ---> same problem but with [WindowsFolder]...

jamali
10-17-2003, 05:19 AM
the initial file format was in XML, later it was converted to binary
problem observed using both file formats

Stefan Krueger
10-17-2003, 05:21 AM
What project type are you using:
- Basic MSI
- InstallScript MSI
- InstallScript (pure, no MSI)

jamali
10-17-2003, 05:28 AM
This is the Type of the Project I have used
Install Script MSI project

Syed Alam

Neoptec
10-17-2003, 05:30 AM
MSI Installscript project as I already mentionned.

buntonn
10-17-2003, 05:45 AM
You may have better luck posting this in the InstallShield DevStudio 9 (Windows Installer Projects) forum. Some MSI setup users probably don't look in this forum very often.

Stefan Krueger
10-17-2003, 05:48 AM
You may have better luck posting this in the InstallShield DevStudio 9 (Windows Installer Projects) forum.
I agree with that.

BTW I'm unable to reproduce this problem. The <td>WindowsFolder</td> in the XML appears to be okay.

jamali
10-17-2003, 06:18 AM
Done,

In the InstallShield DevStudio 9 (Windows Installer Projects) forum. there should be a thread :
Error 1606:Could not acces network location 91SystemFolder93. or 91WindowsFolder93.


i am also downloading SDK and will check with ORCA to workout
what is happening, thanks to every one for all the help & support

cheers

jamali
10-17-2003, 06:24 AM
Done,

In the InstallShield DevStudio 9 (Windows Installer Projects) forum. there should be a thread :
Error 1606:Could not acces network location 91SystemFolder93. or 91WindowsFolder93.


i am also downloading SDK and will check with ORCA to workout
what is happening, thanks to every one for all the help & support

cheers