[ MSI Engine | MSMs |
InstallShield 12 and newer |
InstallShield 11.5 |
DevStudio 9.0 |
IS Dev
8.0 | IS Dev
7.0 | IPWI 2.0 | ISWI 1.x | IS Pro 7.x | IS
Pro 6.x | IS Pro 5.x ]
See also: Microsoft knowledge base article 317328:
Troubleshoot a SQL Server Desktop Engine 2000 Installation and Upgrade
INFO: Availability and Use of MSDE 2000 Merge
Modules
Note: Microsoft no longer recommends the use of these merge modules.
Quote: "Desktop Engine (MSDE 2000) SP3a provides merge modules to support
existing applications that use merge modules. The Setup utilities for new
applications should be written to call the MSDE 2000 Setup utility instead of
directly consuming the MSDE 2000 merge modules." The recommended method to
redistribute MSDE 2000 is to run MSDE's setup.exe from a bootstrapper program
before your actual installation starts.
There are several versions of MSDE 2000 merge modules (listed in chronological order):
- SQL Server 2000 CD includes MSDE merge modules which include several known bugs
- SQL server refresh CD (Nov 2000 - English) build 194.05 includes some bug fixes for the
merge modules
- Knowledge base articles Q274224
and Q281184 include some hot fixes that became available after the refresh
cd was released
- MSDE 2000 SP1 CD includes updated merge modules that will install MSDE on a machine
without having to patch it
- MSDE 2000 SP3 download, includes fix for SQLSlammer worm
- MSDE 2000 SP3a download, includes various fixes and improvements
How to obtain MSDE 2000 SP3a:
Related information:
Shortcut to Service Manager is not Created
- Description:
- When running a setup that includes the MSDE 2000 merge modules, the
shortcut to Service Manager in the Start Menu is not created.
- Workaround:
- 1. From SqlRunXx.msi, save the binary data from the Icon table to a file.
2. In SqlSvr.msm, add the table Icon and created a row with Name =
SvcMangrIco_4BFD7B59_97C9_4908_8AF4_4CB073038239 and Binary data loaded from
the previously saved file.
3. In Sql Svr.msm, I added the table ShortCut and created a row with the
following info:
Shortcut =
SvcMngrShortcut.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616
Directory_ =
StartupFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616
Name = SvcMngr|Service Manager
Component_ =
SvcMngrShortcut.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616
Target = [#sqlmangr.exe.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616]
Arguments = /n
Icon_ = SvcMangrIco_4BFD7B59_97C9_4908_8AF4_4CB073038239
IconIndex = 0
ShowCmd = 1
- Status:
- This problem has been reported for MSDE 2000 SP3 modules.
- Created: 2003-06-19
Setup Fails if Feature Associated with MSDE Modules is not Selected
- Description:
- If the feature including the MSDE merge modules is not selected for
installation, some custom actions are triggered anyway, resulting in a failure
of the installation. The exact error messages and symptoms depend on the MSDE
service pack version you are installing and include errors relating to
"SetServerRegKeyPrivileges" or "Error applying permissions to key".
- Cause:
- Conditions are missing from some of the custom actions in the MSDE merge
modules.
- Workarounds:
- There are several options:
A) Make sure the fetaure associated with the MSDE merge modules is always
selected.
B) Create two msi files, one with the merge modules and one without. Use a
bootstrapper to launch the appropriate msi.
C) Don't include the merge modules. Instead run the MSDE setup in a custom
action is the feature in question is selected, or run MSDE setup from a
bootstrapper program.
D) Edit the MSDE merge modules to fix the conditions, e.g. append one of the
following conditions to the existing condition on the
SetServerRegKeyPrivileges action in SQLBase.msm:
And SQLIsInstalled
And $ComponentSet.1.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 3
Note that Method C) is the preferred solution, as Microsoft now discourages the
use of the MSDE merge modules. If you need to use the merge modules, method B)
would be Microsoft's recommendation. Method D) is not supported and should be
avoided.
- Status:
- This appears to be a design limitation in the MSDE 2000 merge modules
which has been introduced with SP3.
- Created: 2003-03-03 Last update:
2003-06-19
"Setup failed to configure the server." with MSDE 2000 SP3 Merge Modules
- Description:
- When you run your setup that includes the MSDE 2000 SP3 merge modules it
may fail with the following message:
Setup failed to configure the server. Refer to the server error logs and setup
error logs for more information.
This happens if previously uninstalled MSDE and now try to re-install MSDE
with the same instance name.
- Cause:
- The uninstall leaves behind the folder "mssql$<instance_name>"
that includes the core SQL Server database files (master.mdf, mastlog.ldf,
model.mdf, modellog.ldf, msdbdata.mdf and msdblog.ldf).
- Workarounds:
- Delete the obsolete folder. You can modify the merge module to handle this
automatically. 96 rows need to be added RemoveFile table in SQLSVR.MSM
with the following contents:
FileKey: <FileName>.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616.X in which X denotes
the figures 1 to 16 and <FileName> denote the database files mentioned above.
Component_: ServerCoreIX.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 in which X
denotes the figures 1 to 16.
FileName: <FileName> which denotes the database files mentioned above.
DirProperty: DataInstanceData.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616
InstallMode: 2, which according to documentation from Microsoft means remove.
Note that by deleting these files any data the user may have stored in the
database will be lost.
- Status:
- This problem has been reported by several users. Apparently it has been
introduced with SP3. There is no official comment from Microsoft about this
problem.
It has been reported that this problem no longer exists in version SP3a of
these modules.
- Created: 2003-02-15 Last update:
2003-10-03
Error 1334 or 2602 Running a Setup that Includes MSDE 2000 SP3 Merge Modules
- Description:
- When you run your setup that includes the MSDE 2000 SP3 merge modules you
may get one of the following error messages:
Error 2602. The file table entry
'sqlmaint.rll.88C26F26_166C_4CD7_8175_38297C2276D7' has no associated entry in
the Media table.
Error 1334. The file 'sqlmaint.rll.88C26F26_166C_4CD7_8175_38297C2276D7'
cannot be installed because the file cannot be found in cabinet file
'cabs.m23'. This could indicate a network error, an error reading from the
CD-ROM, or a problem with this package.
- Cause:
- In SQLSVR_RES.MSM a wrong sequence number is listed for file sqlmaint.rll
in the file table. As a result the module is not merged to your main setup
correctly. This can be verified by performing a merge module validation with
Orca, which will result in:
ICEM07 ERROR The file 'sqlmaint.rll.88C26F26_166C_4CD7_8175_38297C2276D7'
appears to be out of sequence. It has position 2 in the CAB, but not when the
file table is ordered by sequence number.
It has been reported that REPL.MSM has a similar problem.
- Workarounds:
- Open the merge module with Orca, change the sequence number from 10 to 2.
Note that some setup tools (e.g. InstallShield Developer 8) seem to be able to
merge the module regardsless of this error, so depending on the tool you are
using you may not be affected by this problem.
Wise has released a script to correct the sequence numbers in the module. It's
available in Wise knowledge base article
1759.
- Status:
- This problem has been introduced with SP3. Microsoft has not (yet)
officially
accepted this as a bug.
- Created: 2003-02-05 Last update:
2003-02-15
Setup with MSDE Merge Modules May Fail During Initialization (SQLCAX.DLL)
- Description:
- A setup that includes the MSDE merge modules from the may fail during the initialization
phase. When you create a log file of the installation you find an entry similar to this:
Action start 11:52:49: GetSqlStates.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
Loading extended custom action library sqlcax.dll
Error 126 loading library sqlcax.dll
Action ended 11:52:49: GetSqlStates.2D02443E_7002_4C0B_ABC9_EAB2C064397B. Return value 3.
1: Failed to launch action 'GetSqlStates.2D02443E_7002_4C0B_ABC9_EAB2C064397B', error is
1603
- Cause:
- SQLBASE.MSM includes (among others) the following custom actions: StreamSupportFiles and
GetSqlStates. StreamSupportFiles is responsible for unpacking sqlcax.dll from the Binary
table to a temp directory where custom action GetSqlStates can load it. If GetSqlStates is
called before StreamSupportFiles it will fail with error code 126 "Specified module
could not be found".
Custom actions in merge modules are sequenced based on standard actions.
StreamSupportFiles is called before LaunchConditions and GetSqlStates is called after
AppSearch. If you place AppSearch before LaunchConditions in your main setup (which is
completely legal) the MSDE custom actions will be called in the wrong order.
- Workarounds:
- Move AppSearch after LaunchConditions in your main setup. Or open SQLBASE.MSM in Orca
and adjust the ModuleInstallUISequence and ModuleInstalLExecuteSequence so that
StreamSupportFiles is called before AppSearch. (Remarks: I haven't tested the latter
solution but in theory it should work. You should check all other MSDE modules to see if
they include similar problems)
- Status:
- This problem is documented in Microsoft Knowledge Base article
321283.
InstallShield Developer 8 includes a workaround for this problem.
- Created: 2002-07-08 Last update:
2003-02-18
Setup with MSDE Merge Modules Fails if MSDE 2000 is Already Installed
- Description:
- If you run a setup that includes the MSDE merge modules on a system where MSDE 2000 is
already installed, setup will abort (instead of just skipping the MSDE install).
- Workarounds:
- Remove the detect.instance.clash custom action from the sqlbase.msm module.
- Status:
- This problem has been reported by a user. There are still reports about
this problem in SP3.
- Created: 2001-08-24 Last update:
2003-02-05
ICE03 Validation Error for Package that uses Sqlsvr.msm from MSDE 2000
- Description:
- An msi file that includes the Sqlsvr.msm merge module from MSDE 2000 will show the
following error message upon validation: "ICE03 ERROR Value not a member of the set;
Table: Shortcut, Column: ShowCmd, Key(s):
SvcMngrShortcut.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616".
- Workarounds:
- Edit the msm file with Orca to fix the incorrect entry in the shortcut table as
described in Microsoft Knowledge Base article Q295193.
- Status:
- Documented in Microsoft Knowledge Base article Q295193. FIXED
in the SQL Server Desktop Engine 2000 SP 1 Refresh CD.
- Created: 2001-08-24
Setup with MSDE Merge Modules May Fail on Windows NT 4
- Description:
- A setup that includes the MSDE merge modules from the SQL
Server Desktop Engine 2000 SP 1 Refresh CD may fail to install on Windows NT 4.0.
- Cause:
- The merge modules require that the ProductLanguage property be properly set, e.g. to
1033. Setting it to 0 will cause the failure.
- Workarounds:
- Be sure to set the ProductLanguage property either in your authoring tool or using Orca.
See Microsoft Knowledge Base article Q274224
for more information.
- Status:
- Documented in Microsoft Knowledge Base article Q274224.
This problem was introduced with the SQL Server Desktop
Engine 2000 SP 1 Refresh CD but is not a bug in the merge modules but exposes an error
in the creation of the consuming msi package.
- Created: 2001-08-24
- Description:
- Installing a setup that includes merge modules from the MSDE 2000 package may result in
error message "An internal error occurred during install (failed to load package id).
Contact Microsoft Technical Support."
- Workarounds:
- See Microsoft Knowledge Base article Q274224.
- Status:
- Documented in Microsoft Knowledge Base article Q274224
and fixed in the SQL Server Desktop Engine 2000 SP 1
Refresh CD (but not in the November 2000 refresh CD).
- Created: 2001-01-12 Last update: 2001-08-24
- Description:
- Installing a setup that includes merge modules from the MSDE 2000 package may result in
error message "Setup requires Internet Explorer version 5.0.2314.0 or above."
even if you have the latest IE version already installed.
- Workarounds:
- See Microsoft Knowledge Base article Q274224.
Alternative workaround: Open SQLBase.msm in Orca, go to the DrLocator table
and change [SystemFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B] to
[SystemFolder].
- Status:
- Documented in Microsoft Knowledge Base article Q274224.
According to Microsoft this was fixed in the SQL Server
Desktop Engine 2000 SP 1 Refresh CD (but not in the November 2000 refresh CD). However
users report that it still doesn't detect Internet Explorer 6 and Windows XP properly.
For SP3 there are still reports that this isn't working properly.
- Created: 2001-01-12 Last update: 2003-02-05
- Description:
- Adding DMO.MSM (that comes with MSDE 2000) to a project causes build errors that it
can't find DMO_RES.MSM. Manually adding this module to the project doesn't solve the
problem. Even if you manually add both MSMs you are added to the project, you'll get error
messages when building the package. The same problems applies to other merge modules in
MSDE 2000.
- Cause:
- MSDE 2000 includes some language specific merge modules, like DMO_RES.MSM. However the
language entry in the ModuleSignature table is 0.
The (language independent) DMO.MSM depends on the English (language 1033) version of
DMO_RES.MSM, and doesn't accept the "language neutral" version.
- Workarounds:
- Open DMO_RES.MSM, go to the ModuleSignature table, and change the entry in the language
column fom 0 to 1033. Or get the hot fix from Microsoft.
- Status:
- This problem can be seen by examining the modules with Orca. It affects all merge modules delivered with MSDE 2000 in sub folder
MSM\1033 except Sqlbase.msm. Microsoft has confirmed that this is a problem in MSDE 2000.
A hot fix is available, see knowledge base article Q281184
for more information. FIXED in SQL Server 2000 SP 1.
- Created: 2000-08-17 Last update: 2001-08-24
Errors 2755 and 1641 When Installing MSDE Merge Modules
- Description:
- When you run a setup that includes the MSDE 2000 merge modules from the SQL server refresh CD your setup may abort with error
numbers 2755 and 1641, which means: "Error 2755: Server returned unexpected error
1641 'The installer has started a reboot' attempting to install package ... . ". It
looks like a reboot attempt from one of the merge modules is not properly suppressed. This
happens if the Slqsvr.msm or Sqlagent.msm are included in the setup.
- Workarounds:
- None.
- Status:
- This has been reported for setups running on Windows 2000. It seems to be fixed in the
sqlbase.msm from Microsoft Knowledge Base article Q274224.
- Created: 2001-04-19 Last update: 2001-04-26
- Description:
- Uninstalling or repairing a setup that includes merge modules from the MSDE 2000 package
results in error message "The wizard was interrupted before application name could be
successfully installed."
- Workarounds:
- None.
- Status:
- Fixed in the SQL server refresh CD (Nov 2000 -
English) build 194.05. See Microsoft Knowledge Base article Q275309.
- Created: 2001-01-12
Copyright © by InstallSite Stefan
Krueger. All rights reserved. Legal
information.
Impressum/Imprint
Datenschutzerklärung/Privacy Policy
By using this site you agree to the license
agreement. Webmaster contact
