![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am trying to integrate our application with the MSDE 2000 SP3 and use the MSI based installation with merge files. This sounds great in theory, but it doesn't work at all. I thought it was due to my lack of MSI knowledge, but looking at http://www.installsite.org/pages/en/bugs_msi.htm and the various KB-articles about MSDE setup proves different. MS is aware of these problems and discourages the use of merge modules (quote from the SP3a readme: "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."). I have fixed a lot of bugs, but there is still one that keeps me from getting it to work ("Error 1157 loading library sqlcax.dll" that is). I stopped putting more effort in the installation procedure, but I cannot distribute my application this way. MSI is quite difficult to manage and without tooling, such as Wise it was nearly impossible to create a working script. But it seems that Microsoft doesn't understand MSI themselves, because in SP3a there are still problems (I even get the idea that it is getting worse each service pack). Does this mean that MS discourages the use of MSI completely? I am pretty disappointed in MS about this installation method. MSDE installation is praised in MS articles about MSDE (integrated installation using merge modules), but it is discouraged when you actually want to use it. Does MS intend to fix these problems by releasing a new set of merge modules? If Microsoft creates a setup using Wise that installs MSDE it can find out easily what is going wrong (I am willing to prepare such a script if that is useful). My logfile can be viewed at http://home.ict.nl/~ramklein/MSI-output.txt for further reference. I would love to hear someone from MS to comment on these problems... |
#3
| |||
| |||
|
|
From: "Ramon de Klein" <RamonDeKlein (AT) hotmail (DOT) com Newsgroups: microsoft.public.sqlserver.setup Subject: MSDE 2000 SP3 merge modules Date: Thu, 3 Jul 2003 13:16:36 +0200 Organization: ICT Solutions B.V. Lines: 30 Message-ID: <be13aq$b1m$1 (AT) www-2 (DOT) dev.ict.nl NNTP-Posting-Host: pc1527.dev.ict.nl X-Trace: www-2.dev.ict.nl 1057231002 11318 192.168.15.66 (3 Jul 2003 11:16:42 GMT) X-Complaints-To: abuse (AT) ict (DOT) nl NNTP-Posting-Date: Thu, 3 Jul 2003 11:16:42 +0000 (UTC) X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Path: cpmsftngxa09.phx.gbl!TK2MSFTNGP08.phx.gbl!news-out.cwix.com!newsfeed.cwix.co |
|
Xref: cpmsftngxa09.phx.gbl microsoft.public.sqlserver.setup:4155 X-Tomcat-NG: microsoft.public.sqlserver.setup I am trying to integrate our application with the MSDE 2000 SP3 and use the MSI based installation with merge files. This sounds great in theory, but it doesn't work at all. I thought it was due to my lack of MSI knowledge, but looking at http://www.installsite.org/pages/en/bugs_msi.htm and the various KB-articles about MSDE setup proves different. MS is aware of these problems and discourages the use of merge modules (quote from the SP3a readme: "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."). I have fixed a lot of bugs, but there is still one that keeps me from getting it to work ("Error 1157 loading library sqlcax.dll" that is). I stopped putting more effort in the installation procedure, but I cannot distribute my application this way. MSI is quite difficult to manage and without tooling, such as Wise it was nearly impossible to create a working script. But it seems that Microsoft doesn't understand MSI themselves, because in SP3a there are still problems (I even get the idea that it is getting worse each service pack). Does this mean that MS discourages the use of MSI completely? I am pretty disappointed in MS about this installation method. MSDE installation is praised in MS articles about MSDE (integrated installation using merge modules), but it is discouraged when you actually want to use it. Does MS intend to fix these problems by releasing a new set of merge modules? If Microsoft creates a setup using Wise that installs MSDE it can find out easily what is going wrong (I am willing to prepare such a script if that is useful). My logfile can be viewed at http://home.ict.nl/~ramklein/MSI-output.txt for further reference. I would love to hear someone from MS to comment on these problems... |
![]() |
| Thread Tools | |
| Display Modes | |
| |