Shell MSDE setup problem

[Chris Austin]

I am trying to use the Shell command to run the MSDE setup.

Shell("MSDE\setup.exe SAPWD=blah INSTANCENAME=TEST SECURITYMODE=SQL")
This works in that it runs the setup, but the setup always pauses with a few
seconds to go (as far as I can tell just before the MDAC install).

If I then stop my VB.Net app, then the setup continues. Why is this
happening and what can I do to resolve it?

The same command works perfectly from the command prompt, so it seems that
the shell command isn't allowing the shelled app to launch another process
(MDAC install).



Chris Austin

 

[Ken Tucker [MVP]]

Hi,

Take a look at this toolkit
http://www.microsoft.com/downloads/...03-c4ba-4d98-bb0b-2c9d6414071f&DisplayLang=en

Ken
----------------------------------
I am trying to use the Shell command to run the MSDE setup.

Shell("MSDE\setup.exe SAPWD=blah INSTANCENAME=TEST SECURITYMODE=SQL")
This works in that it runs the setup, but the setup always pauses with a few
seconds to go (as far as I can tell just before the MDAC install).

If I then stop my VB.Net app, then the setup continues. Why is this
happening and what can I do to resolve it?

The same command works perfectly from the command prompt, so it seems that
the shell command isn't allowing the shelled app to launch another process
(MDAC install).



Chris Austin

 

[Chris Austin]

Thanks, but I have already looked at this toolkit and decided I couldn't use
it for 2 reasons:

1) I need to give the user the option of selecting either an existing SQL
Server instance (local or remote) or installing a new MSDE instance

2) This is still a release candidate and not usable for public distribution.
I need to supply this setup next week.

So back to the original problem, why does the setup pause when shelled from
an app, but not when called from the command line with exactly the same
parameters.

Chris

 

[CJ Taylor]

I am trying to use the Shell command to run the MSDE setup.

Shell("MSDE\setup.exe SAPWD=blah INSTANCENAME=TEST SECURITYMODE=SQL")
This works in that it runs the setup, but the setup always pauses with a few
seconds to go (as far as I can tell just before the MDAC install).

If I then stop my VB.Net app, then the setup continues. Why is this
happening and what can I do to resolve it?

The same command works perfectly from the command prompt, so it seems that
the shell command isn't allowing the shelled app to launch another process
(MDAC install).

Maybe dumb, but try using Process.Start instead of shell. I know its kinda
stupid because it *should* be doing the exact same thing, but every now and
then you find these little quirks. Shell should start the application out
of process, but it will only return an error level, nothing you can use to
necessarily monitor the application.

IT's just a hunch, but at least something to try. Plus its managed, which
may take care of some of the bs for you.

 

[Helene Day]

How about you shell a file such as msdesetup.bat
and the file would have the following:
start MSDE\Setup.exe SAPWD=blah INSTANCENAME=TEST SECURITYMODE=SQL

 

[Ken Tucker [MVP]]

Hi,

http://www.red-gate.com/sql/sql_packager.htm


Ken
-----------------
Thanks, but I have already looked at this toolkit and decided I couldn't use
it for 2 reasons:

1) I need to give the user the option of selecting either an existing SQL
Server instance (local or remote) or installing a new MSDE instance

2) This is still a release candidate and not usable for public distribution.
I need to supply this setup next week.

So back to the original problem, why does the setup pause when shelled from
an app, but not when called from the command line with exactly the same
parameters.

Chris