Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MSDE 2000, SP3, Visual Studio.net

95 views
Skip to first unread message

John Oakes

unread,
Jan 28, 2003, 9:37:17 AM1/28/03
to
I'm attempting to build an installer using Visual Studio.NET that includes
the MSDE merge modules (the SP3 ones that just became available.) I added
all of the merge modules to the deployment project and added their locations
to the search path, and the project built successfully with no warning or
errors. However, when I run the installer I get "The installer was
interrupted before SP3Test could be installed..." I ran this will logging
and looked for a return value 3, these are the last few lines before return
value 3:

MSI (c) (5C:6C): Doing action:
GetSqlStates.2D02443E_7002_4C0B_ABC9_EAB2C064397B
Action start 15:08:46: GetSqlStates.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
MSI (c) (5C:6C): Creating MSIHANDLE (1) of type 790542 for thread 2412
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{2FB60C18-F441-48FD-A024-55DF1ED55E2E}
Failed to determine supports files directory in LoadSqlLibrary
Action ended 15:08:46: GetSqlStates.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
Return value 3.

Any ideas? Thanks!

John


Preston Landers

unread,
Jan 28, 2003, 6:17:12 PM1/28/03
to
Unfortunately I don't have any ideas -- as I am running into the exact
same problem you are!

Trying to include the new MSDE Service Pack 3 merge modules in a brand
new Installshield/MSI installer. Builds ok, but when I run the
install, it just quits mysteriously (no error.) Running with logging
gets me a similar error:

Failed to determine supports files directory in LoadSqlLibrary

The installer quits and the msiexec.exe process hangs out there until
I kill it.

I hope someone posts a solution here, either that or Microsoft
corrects their packages and makes it usable as a merge module.

thanks
Preston Landers


"John Oakes" <jo...@networkproductions.net> wrote in message news:<OizlnotxCHA.2712@TK2MSFTNGP12>...

Preston Landers

unread,
Jan 28, 2003, 6:53:07 PM1/28/03
to
Hey, I found the answer actually.

See this page:

http://www.installsite.org/pages/en/bugs_msi.htm

Basically, you need to adjust the order of MSI events in your setup.
Just put AppSearch after LaunchConditions in the Sequence editor (this
is in Installshield, not sure about the VS.NET tools.)

hope this helps,
Preston Landers

"John Oakes" <jo...@networkproductions.net> wrote in message news:<OizlnotxCHA.2712@TK2MSFTNGP12>...

Preston Landers

unread,
Jan 28, 2003, 7:09:53 PM1/28/03
to
Hmmm ok -- I did get past this problem (see my solution in another
article) but I am having another one now. Perhaps you are running
into this too (or someone else is.)

I must specify the SqlSecurityMode=SQL parameter (actually, its a
property).

However, when running the install, I get:

"A strong SA password is required for security reasons. Please use
SAPWD switch to supply the same. Refer to readme for more
details. Setup will now exit."

Okay, fine. I'll set an SA password. However, the SAPWD switch only
applies to running the installer from the command line.

This page and others:

http://support.microsoft.com/default.aspx?scid=KB;en-us;q281983

lists the equivelent MSI properties for SQL Server setup options.
However, SAPWD is not listed here? Anyone have any idea how to set
the SA password through MSI properties? I'm about to make some stuff
up and try "SqlSAPassword" but that's just blind guessing.

thanks
Preston

"John Oakes" <jo...@networkproductions.net> wrote in message news:<OizlnotxCHA.2712@TK2MSFTNGP12>...

John Oakes

unread,
Jan 28, 2003, 11:25:18 PM1/28/03
to

Hey Preston,

Thanks for the information! I'm not at my work computer right now but will
try it in the morning. As to the SA password question, I used orca to look
at an MSI I created with VS.NET, and I think it might be SqlSaPwd. Try
that!

John

"Preston Landers" <pib...@yahoo.com> wrote in message
news:1136f745.03012...@posting.google.com...

Preston Landers

unread,
Jan 29, 2003, 11:48:10 AM1/29/03
to
Hey John,

I appreciate the information! It certainly did work and we are now in
bidness. I hope changing the action ordering helps with your problem.

thanks!!
Preston Landers


"John Oakes" <jo...@networkproductions.net> wrote in message news:<uB$4Q50xCHA.1620@TK2MSFTNGP11>...

John Oakes

unread,
Jan 29, 2003, 1:36:58 PM1/29/03
to

Ok, I changed the action order for my MSI file and now I can install it.
However, uninstalling is a different story. I just get "Fatal Error During
Installation" every time I try to uninstall it. Any ideas? Does your
uninstall work?

John


"Preston Landers" <pib...@yahoo.com> wrote in message
news:1136f745.03012...@posting.google.com...

Preston Landers

unread,
Jan 29, 2003, 5:31:31 PM1/29/03
to
I was having another problem that caused a "fatal error" on install,
because I was using SQL Authentication.

That is detailed here:

http://groups.google.com/groups?dq=&hl=en&lr=&ie=UTF-8&oe=UTF-8&group=microsoft.public.sqlserver.setup&safe=off&selm=1136f745.0301291020.3d8b8bbe%40posting.google.com

Since you are having a problem uninstalling, that probably doesn't
apply to you.

Have you tried running the uninstall progarm with full logging? That
will probably reveal the source of the error.

The logging flag is /L*v"C:\path\to\log.txt"

You may have to run your setup with a /U flag (and the logging flag)
to get it to log during uninstall.

hope this helps,
Preston


"John Oakes" <jo...@networkproductions.net> wrote in message news:<ubyCPT8xCHA.1900@TK2MSFTNGP10>...

John Oakes

unread,
Jan 29, 2003, 10:37:03 PM1/29/03
to
Thanks, I found the problem. I changed the StreamSupportFiles sequence in
one table in the MSI file, but I also had to change it in one more table.
It works now!


"Preston Landers" <pib...@yahoo.com> wrote in message
news:1136f745.03012...@posting.google.com...

0 new messages