I've been trying to install the MSDE 2000 MSMs as part of a.NET deployment
project that installs my .NET application. I got the MSMs from the SQL
Server Developer Edition (Jan 2002 DVD) but keep getting the following
warnings when I add them to my application's deployment project from within
VS .NET:
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'SQLSVR1033.88C26F26_166C_4CD7_8175_38297C2276D7'
WARNING: Unable to find module dependency with signature
'MSVCRT.51D569E0_8A28_11D2_B962_006097C4DE24'
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'MSVCRT.51D569E0_8A28_11D2_B962_006097C4DE24'
WARNING: Unable to find module dependency with signature
'MSSTKPRP.7EBEDD3E_AA66_11D2_B980_006097C4DE24'
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'DTS1033.9240E1C0_49D2_40A2_93CE_E62CD8B48DDC'
WARNING: Unable to find module dependency with signature
'REPL1033.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128'
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'TOOLS1033.ACD7EC22_4989_4067_B267_6DB5716695BC'
WARNING: Unable to find module dependency with signature
'SQLAGENT1033.BF65A835_E76E_4CA5_8B97_E8FD33E7C475'
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'SEM1033.EF490CFB_7BC2_4102_8395_426CE5870B18'
WARNING: Unable to find module dependency with signature
'SQLBASE.2D02443E_7002_4C0B_ABC9_EAB2C064397B'
WARNING: Unable to find module dependency with signature
'DMO1033.6496AA57_4ABB_4A5B_A0A9_E712ECFA8092'
The MSI package builds anyway but fails to install, generating the error:
"The installer was interrupted before AppName could be installed. You need
to restart the installer and try again. Click close to exit."
From other postings in in InstallShield and the SQLServer newsgroups, I
thought that perhaps the resource
MSMs (e.g. xxxx_res.msm) needed to have their language id changed from 0
(neutral) to 1033 (English) to agree with the Module Dependecy information
in the parent MSMs. So I edited each of the xxxx_res.msm files using ORCA
and changed the language id in the module signiture table to 1033. But it
didn't make any difference at all. I still get the same warnings as before I
made the changes and the MSI continues to fail with the same error. Just to
test my basic .MSI package I removed all the MDE MSMs and rebuilt any
everything installs without error.
Does anyone have an idea what the conflict/problem might be using these MSMs
with the
VS.NET installer that comes with the Visual Studio IDE? I'm using
the V1 (final) version. Thanks in advance for any help or suggestions.