Re: Installing MSDE from VB.NET

From: Jeff (jeff_nospam_at_eNetPortals.com)
Date: 11/11/04 

Date: Thu, 11 Nov 2004 14:50:43 GMT

Hi Michael -

While there may be a VB.NET approach to solving this problem, I think it's
an MSDE problem. The same hanging behavior occurs when I run MSDE setup
from a VB6 program using the approach detailed in:

How To Use a 32-Bit Application to Determine When a Shelled Process Ends
(http://support.microsoft.com/kb/q129796/)

When I do that, the install hangs, and I use task manager to kill it. The
last line of the resulting log file is:

Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlredis.exe
/q:a"

When I check the above path, I find no sqlredis.exe file. Even when I run
setup manually (by going to the MSDE directory and running setup with
specified parameters) for a successful install, there is no sqlredis.exe in
the above path.

Note: The install works (from the VB6 program) when I simply shell to the
setup.exe command, but I must have a way to determine that the install has
completed. That's why I tried the method detailed in the above-referenced
Microsoft article.

Also, Michael, your suggested approach relies on MSDE merge modules.
Microsoft now tells developers to not use merge modules, and MSDE no longer
comes with them. So how is that helpful??

What am I missing?? How can I install MSDE successfully from within a
VB.NET app?

Thanks for your help.

- Jeff

""Michael Cheng [MSFT]"" <v-mingqc@online.microsoft.com> wrote in message
news:Gs7ey%23%23xEHA.3436@cpmsftngxa10.phx.gbl...
> Hi Jeff,
>
> I think this issue was more VB.NET related. I would like to suggest you
> raise the question in the vb.net newsgroup and here is some excerpt from
an
> VB.NET support engineer.
>
> How to use MSDE Merge Modules in VS.Net Setup project
> =======
> To create a simple Setup Project:
>
> 1. Open VS.Net and create a new Windows Application project.
> 2. Open the menu "File" | "Add Project" | "New Project". Select "Setup
> Project" under "Setup and Deployment Projects".
> 3. Add the "Primary Output" of the Windows Application to the Setup Projec
t.
>
> To add the MSDE merge modules to the Setup Project:
>
> 4. Right click the Setup Project (e.g. "Setup1") in the Solution Explorer
> and select "Add" | "Merge Module".
> 5. Locate to the "MSM" folder which contains all the ".MSM" files.
> (Typically, this path is X:\MSDE\MSM where X is the drive letter of your
CD
> drive.)
> 6. Press "CTRL + A" to select all the files in that folder. Click the
> "Open" button to add them to your Setup Project.
> 7. Repeat the steps 5 and 6 with the folder "MSM\1033". Add all the
".MSM"
> files in the folder "MSM\1033" to the Setup Project as well.
> 8. Build the Setup Project.
>
> To use Orca to manually modify the MSI:
>
> 9. Locate the MSI output of the Setup Project and use Orca to open it.
> 10. Go to the InstallExecuteSequence table.
> 11. By default, the Sequence of the action "GetSqlStates.XXXXXX" is 103.
> Let''s change it to 421, so that it is sequenced after the
> "StreamSuportFiles.XXXXXX" action.
> 12. Go to the InstallUISequence table. Change the sequence of
> "GetSqlStates.XXXXXX" to 421 as well.
>
> For detailed information on the order of the 2 actions, you may refer to
> the following article:
>
> PRB: The MSDE Installation May Fail and Error 126 Is Logged When You Are
> Using Windows Installer Software
> http://support.microsoft.com/?id=321283
>
> 13. Go to the Property table. Add the following 2 rows:
>
> Property Value
> SqlInstanceName InstanceName
> SqlSaPwd password
>
> Here we specify "InstanceName" as the name of the MSDE instance and
> "password" as the password for the SA account. For more property options,
> you may visit the following link:
>
> Using SQL Server Desktop Engine Merge Modules
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/dis
> tsql_8yeq.asp?frame=true
>
> 14. Go to the InstallExecuteSequence again.
> 15. Change the sequence of "InstallInitialize" from 1800 to 1799.
> 16. Change the sequence of "RemoveExistingProducts" from 1825 to 1800.
> 17. Save the MSI file and close Orca.
>
>
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
>
> Sincerely yours,
>
> Michael Cheng
>
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---------------------------------------------------------------
> Get Secure! - http://www.microsoft.com/security
>
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
>