Hi, Jeff

Thanks for your considerate posting!

From your descriptions and log file, I understood that your MSDE
installation failed in UpgDetectBlankSaLogin() and you could not make it
successfully the second time. Have I understood you? If there is anything I
misunderstood, please feel free to let me know.

Based on my scope, from the log file, it shows the installation of MSDE was
closely finished but it fails to startup the MSDE services. Here are some
suggestions for your on this issue.

First of all, I am not very sure how do you removed MSDE Instance. you used
Add/Remove? The following documents shows how to manually remove MSDE
completely. May be you should also have an application checking this

320873 HOW TO: Manually Remove a Microsoft SQL Server 2000 Desktop Engine
(MSDE 2000) Instance
http://support.microsoft.com/?id=320873

You should make sure the services is running before UpgDetectBlankSaLogin()
returns 3.

Secondly, UpgDetectBlankSaLogin() returns 3 means Black SA password is not
allowed in MSDE SP3. Add this switch in your msde setup file, blankpwd=1.
More detailed information about this switch could be found in the following
KB:

810826 INF: New Switches in MSDE Service Pack 3 Setup
http://support.microsoft.com/?id=810826

814463 How To Specify a Strong SA Password When You Install SQL Server 2000
Desktop Engine (MSDE 2000)
http://support.microsoft.com/?id=814463

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!


Sincerely yours,

Mingqing Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Thanks for your response -

I know how to manually remove an MSDE instance (I had read the article you
suggested). The problem is that it won't be me removing MSDE; it will be my
nontechnical users. And they won't be able to follow a procedure that
requires registry changes. (Note that the article includes"Use Add/Remove
Programs in Control Panel to remove the SQL Server 2000 Desktop Engine (MSDE
2000) instance before you try to manually remove the instance." That's what
I did to remove the instance.)

I may be able to write an uninstaller that does this, but it would have to
start by programmatically running the Microsoft MSDE uninstaller (the one
that gets run when you use Add/Remove Programs). What is the command to run
the MSDE uninstaller from a program? Are there command line parameters??

Shouldn't the Microsoft MSDE uninstaller completely uninstall the instance??
It appears to fall short of that obvious objective.

You said that I "should make sure the services is running before
UpgDetectBlankSaLogin() returns 3." How do I do that in the middle of the
(Microsoft) MSDE Install??

I'm installing MSDE (both times!) with a non-blank password. It's the
identical install both times (and it must be that way). It works the first
time but not the second (after removal).

Sorry, but your suggestions did not resolve my problem.

- Jeff


""Mingqing Cheng [MSFT]"" <v-mingqc (AT) online (DOT) microsoft.com> wrote

Hi Jeff,

First of all, please understand that I could not repo it on my machine.
There must be something that was not deleted completely for your MSDE. Here
are some possible root cause for this kind of error

CAUSE 1: BCM
-------------------------
If you have BCM installed, reomve the BCM and then try to see whether it
will work in the second time. Based on my research, in most cases, it will
prevent service from started.

CAUSE 2:
-------------------------
one of the possible problems was due to the TEMP folder being incorrectly
used as indicated in the 1st error. For successful installations, the TEMP
folder should not be C:\WINNT\TEMP\SqlSetup\Temp but rather the TEMP folder
under your user account, e.g.
C:\DOCUME~1\Admin~1\LOCALS~1\Temp\SqlSetup\Temp. This problem could be
because you were trying to run MSDE2K SP3 setup through a Terminal Server
session.

CAUSE 3:
-------------------------
Try to run the following command in the second time to see whether it works

setup.exe BLANKPWD=1 SECURITYMODE=SQL /l*v c:\MSDEsetup.log

CAUSE 4:
-------------------------
Try to see whether the following KB could help

PRB: "Setup Failed to Configure the Server" Error Message When You Install
MSDE
http://support.microsoft.com/?id=816499

If the new MSDE instance name is the same as the previously removed MSDE
instance name, and the data files of the previous MSDE instance still exist
in the Data folder MSDE installation will fail. You'd better

Method 1: Move the Previous MSDE Data Folder
Method 2 : Change the Data Folder Location
Method 3: Manually Remove the Previous Instance of MSDE (As I have
suggested)

I think you could easily remove previous MSDE Data Folder and Delete the
Data (Please remind to Backup these files if necessary, which is also
recommand when there is a big business impact)

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!


Sincerely yours,

Mingqing Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Hi Jeff,

I wanted to post a quick note to see if you would like additional
assistance or information regarding this particular issue. We appreciate
your patience and look forward to hearing from you!

Sincerely yours,

Mingqing Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Yes I would.

Please see my last post. (Problem not yet resolved; can't get the service
to start. "How can I get the reinstalled instance started??")

- Jeff


""Mingqing Cheng [MSFT]"" <v-mingqc (AT) online (DOT) microsoft.com> wrote

Hi Jeff,

Have you tried that four steps I provided to you? I wonder how the testing
is going. Could you answer my questions seperately for each resolutions?
Without your further information, it's very hard for me to continue with
the troubleshooting.

1. Have you had BCM installed? If so, remove it and then try to see whether
it works now
2. What's your temp table settings?
3. How about the setup command "setup.exe BLANKPWD=1 SECURITYMODE=SQL
/l*v c:\MSDEsetup.log", could this work for you in the second time?
4. In your program, after MSDE was uninstalled, could you programatically
remove MSDE data foler? If so, try to see whether this works.


Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!


Sincerely yours,

Mingqing Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Hi -

You apparently never got my September 14 post, so here it is again (see
below). Your suggested steps are specifically addressed at the end of it.

Interesting: When I access this newsgroup with Outlook Express, my
September 14 post appears; when I access it via the MS web niterface, it
does not.

Perhaps the post didn't make it because of the log file attachment. So I'll
send the attachment in a separate post.

- Jeff


My September 14 post:

Hi -

I seem to be making progress, but the problem is not yet solved. I now am
able to do an uninstall/reinstall of MSDE so the (reinstall) log file
(attached) reports success. Now, however, I am unable to start the
reinstalled instance as a service.

The change I made to get a successful reinstall was to have my install
program install (and reinstall) MSDE with a blank password. With a blank
password, the reinstall reports success; with a non-blank password, it
fails. I was planning to have my app change the password when it is first
run.

But, again, I can't get the service to start. Here's what I did:

1. Installed MSDE (blank password)
2. Rebooted --> the service started automatically
3. Uninstalled MSDE using Add/Remove Programs in the Control Panel
4. Deleted the Data directory for the instance
5. Rebooted -->
Problem: I got a Net Service Configuration Error
"The specified service does not exist
as an installed service."
For users wanting to simply remove my app and MSDE,
how do I prevent this message??
6. Reinstalled MSDE (blank password)
7. Rebooted (I didn't get the above Net Service Configuration Error)

At this point, the log file reports success and the instance (ENP356) shows
as an installed service (MSSQL$ENP356), but it's stopped. When I try to
start it using the Microsoft Management Console, I get:

"The MSSQL$ENP356 service on Local Computer started and then stopped. Some
services stop automatically if they have no work to do, for example, the
Performance Logs and Alerts service."

I also tried starting the service with net start. I opened a cmd window and
ran:

net start MSSQL$ENP356

The following lines were then displayed:

The MSSQL$ENP356 service is starting.
The MSSQL$ENP356 service could not be started.
The service did not report an error.

More help is available by typing NET HELPMSG 3534.

OK, so when I typed NET HELPMSG 3534, the following (not very helpful) line
was displayed:

The service did not report an error.

How can I get the reinstalled instance started??

- Jeff

Regarding your suggested causes:

1. BCM

I assume you mean business contact manager that's usually a part of Outlook.
I have Office 2003 Pro and tried to 'Add or Remove Features' (by selecting
'Change' in the Office Add/Remove Programs list entry) I was unable to find
either 'BCM' or 'Business Contact Manager' so I assume that I don't have it
installed. If there's something else I need to check, please let me know
what it is.

On the other hand, I have a Broadcom internal modem in my computer that
apparently uses a program listed in Add/Remove Programs as 'BCM V.92 56K
Modem'. I assume that's not what you meant by BCM, but I deleted it anyway.
It just reinstalls when I reboot.

2. Temp Folder Setting

On my machine, System Properties Environment Variables list both TEMP and
TMP as:

%USERPROFILE%\Local Settings\Temp

So it would seem that My machine already complies with your suggestion for
this point. If I have misunderstood or if there is something else I need to
check, please let me know.

3. Blank Password -- see above.

4. KB Article 816499

As I described above, I deleted the data folder before the reinstall. Made
no difference.


""Mingqing Cheng [MSFT]"" <v-mingqc (AT) online (DOT) microsoft.com> wrote

Hi Jeff,

There is something wrong with the server synchronization so that I didn't
see your Sept 14 post until now, you posted it again. I am sorry for the
inconvenience it may cause to you.

Thanks for all of your steps and I made further research on it.

I found the following descriptions in your log files
-------------------
MSI (s) (00:34): Disallowing installation of component:
{436D7A23-36BE-11D2-ACBB-0080C7FCBB84} since the same component with higher
versioned keyfile exists

MSI (s) (00:34): Disallowing installation of component:
{10048711-2C96-11D2-9A97-006097C4E452} since the same component with higher
versioned keyfile exists
MSI (s) (00:34): Disallowing installation of component:
{1CA051B0-1B70-11D2-9ADD-006097C4E452} since the same component with higher
versioned keyfile exists
MSI (s) (00:34): Disallowing installation of component:
{FFFDF420-AFF5-11D2-9AE4-006097C4E452} since the same component with higher
versioned keyfile exists
MSI (s) (00:34): Disallowing installation of component:
{1CA051B2-1B70-11D2-9ADD-006097C4E452} since the same component with higher
versioned keyfile exists
-------------------

It looks like an known issue for us. See the chapter "Remove Windows
Installer References to Installed Products" in the following documents

HOW TO: Manually Remove a Microsoft SQL Server 2000 Desktop Engine (MSDE
2000) Instance
http://support.microsoft.com/?id=320873

It provides a tools Msizap.exe
(http://msdn.microsoft.com/library/de...-us/msi/setup/
msizap_exe.asp). Try to run this application to remove msde related msi
installer registry key after removing it from Add/Remove Programs. Run the
codes like below and see the more detailed descriptions in KB: 320873

MSIZAP.EXE T {E09B48B5-E141-427A-AB0C-D3605127224A}

Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!


Sincerely yours,

Mingqing Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Thanks, but ....

I'm quite familiar with the MS 'Manually Remove' process/article. The
problem is that it will be my nontechnical end users who will be trying to
remove MSDE, not me. As I said/asked in my FIRST post (September 8) in this
rather lengthy thread:

"What must I do to get the re-installation to run smoothly (and
successfully) for my unsophisticated end-users?? While I can go into the
registry and
remove everything referring to my named MSDE instance, my users will not do
so."

Further (please let me know whether this is incorrect), I cannot
redistribute MSIZAP to my end users, even if they were inclined to run it.

In the interest of clarification, here again is what I'm trying to
accomplish:

I'm distributing MSDE with a VB.NET commercial app. For users that install
this software and then decide they don't want it (or if something goes wrong
during or after the install), I want them to be able to uninstall it by
simply removing it, using the MS Add/Remove Programs applet in the Control
Panel. If they then want to reinstall the software, I want them to be able
to do so by simply re-running the same install.

This is not an unreasonable or uncommon scenario. Current status: The 1st
install runs fine. The Remove (using Add/Remove Programs) runs without
error. The second install runs "successfully," but only if I install with a
blank password. And, even when I do that, I have not been able to get the
service to start after the second install (per my most recent post(s)).

I need a solution or workaround, not for me, but for my end users.

- Jeff


""Mingqing Cheng [MSFT]"" <v-mingqc (AT) online (DOT) microsoft.com> wrote

Did you receive my September 20 post??

- Jeff