Re: Installing MSDE from VB.NET
From: Jeff (jeff_nospam_at_eNetPortals.com)
Date: 11/11/04
- Next message: Veets: "Re: MSDTC Problems"
- Previous message: Jeff: "Re: Installing MSDE from VB.NET"
- In reply to: Michael Cheng [MSFT]: "RE: Installing MSDE from VB.NET"
- Next in thread: Jeff: "Re: Installing MSDE from VB.NET"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 11 Nov 2004 14:59:46 GMT
Michael -
I'm not alone! Quoting from a post (yesterday) to the MSDE newsgroup:
"There is some weird issue in the MSDE install package that causes the
sqlredis action to hang if anything is waiting for the parent process to
exit."
That seems to be the same issue I encountered, both with running setup from
VB.NET and with running setup from VB6. Unfortunately, no answer was
provided in that group.
So what is causing the MSDE install package issue? What must I do to fix
it? What successful workaround can you suggest (please remember that my
program needs to know when MSDE installation has been completed)?
- 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
Project.
>
> 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!
>
>
>
- Next message: Veets: "Re: MSDTC Problems"
- Previous message: Jeff: "Re: Installing MSDE from VB.NET"
- In reply to: Michael Cheng [MSFT]: "RE: Installing MSDE from VB.NET"
- Next in thread: Jeff: "Re: Installing MSDE from VB.NET"
- Messages sorted by: [ date ] [ thread ]