Hi,
can u explain further , cause everytime i try to run my installation, it always give me a 2602 error code ...
There are many bugs associated with the MSDE merge modules; most of these bugs are described here:
http://www.installsite.org/pages/en/bugs_msi.htm#wimsm
First, I shall describe possible workarounds for 2 of these bugs. However, I do not recommend using the MSDE merge modules, but rather specifying MSDE as a Prerequisite for your application (see bellow).
The problem that appears in your case is caused by a different bug than the one I was referring to in my previous post. A workaround for the "error 2602" bug is to open the "SQLSVR_RES" merge module in Orca and change the sequence number from 10 to 2 in the "File" table.
A workaround for the "setup initialization failure" bug (the one I was referring to in my previous post) involves the following steps:
a) Open the MSI package for your application (after merging the MSDE merge modules) in Orca.
b) In the "InstallExecuteSequence" table, sort the entries after the Sequence number (click the corresponding column).
c) Locate the Custom Actions whose IDs begin with "GetSqlStates" and "StreamSupportFiles" (this one has an incorrect sequence number).
d) The Action whose ID starts with "StreamSupportFiles" must come
before the Action whose ID starts with "GetSqlStates". Thus, change the sequence of the "StreamSupportFiles" Action to the first
free sequence number prior to "GetSqlStates". For the package I have tested, this free sequence number was 99.
e) Repeat the above steps for the "InstallUISequence" table.
f) Save the MSI file and quit Orca.
In order to include MSDE as a Prerequisite for your application (the approach I would recommend), follow these steps:
1. Copy the files from the MSDE distribution ("setup.exe", "setup.ini" etc) and the "Setup" directory to the folder where your MSI package is built. The "Msi" and "MSM" folders do not need to be copied.
2. In Advanced Installer switch to the Media page, "Prerequisites" tab and click "New". Select the MSDE "setup.exe" bootstrapper.
3. In the "New Prerequisite" dialog -> "Properties" tab, make the following changes:
a) Display Name: MSDE 2000 (change it as necessary)
b) Location: "File in package"
c) Command Line: SAPWD="AStrongSAPwd" (set the desired password and specify additional parameters such as "INSTANCENAME" or "SECURITYMODE")
4. In the "New Prerequisite" dialog -> "Install Conditions" tab, make the following changes:
a) Criteria: "Registry Value"
b) Registry Value:
Code: Select all
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup\CurrentVersion\CurrentVersion
c) Minimum: 8.0
You can find a complete list of SQL Server versions here:
http://www.krell-software.com/mssql-builds.asp
5. In the "Media" tab (of the Media page) make sure that "Create EXE setup file", "Leave install files outside", "Archive installation files into CAB files" and "Include CAB files into the MSI database" are selected.
6. After building the project, you will need to distribute all the MSDE setup files ("setup.exe", "setup.rll" etc) including the "Setup" folder, in addition to the setup files of your package generated by Advanced Installer (EXE, INI, MSI). In a future version, AI will support specifying multiple files for a Prerequisite and then you will be able to create a single EXE package that includes all the required files.
Hope this helps.
Regards,
Denis