asked on

MSDE INSTALLATION PROBLEM

I have a Windows 2000. When I tried to INSTALL the MSDE in order my Visual C# programs could deal with SQL database, I got this message:

" Microsoft SQL Server Desktop Engine

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."

Well since I a novice both in C# programming and SQL database, I have no idea:

1) what a "strong SA password is.

2) what a SAPWD switch is and how to set it.

I did not find any readme file specific for the MSDE installation. The one that comes with it, it is about the installation of the SQL server.

I intend to access the SQL Server as a LOCAL USER and using WINDOWS INTEGRATED SECURITY.

This is the Connection String that I use in my web.config:

<add key="ConnectionString" value="server=(local); database=MyDatabase; trusted_connection=true" />

3) So what I should do ?

I would be grateful if you could answer these three questions. Thank you.

SOLUTION

Qlemo

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

tedhill

ASKER

Qlemo, I have a doubt about that. If a set a password to MSDE installation, I still could access the SQL Server as a "LOCAL USER" ?

ASKER CERTIFIED SOLUTION

Guy Hengel [angelIII / a3]

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Lowfatspread

angelIII
>local administrators can ALWAYS connect without password to the database.

surely you can drop/diable the BUILTIN/ADMINS role/group even in MSDE , and plug that loop hole!

Low

Guy Hengel [angelIII / a3]

yes, but that is not done by default.

tedhill

ASKER

To install the MSDE I used the Run command: D:\sql2ksp3\MSDE\setup SAPWD=mypassword

But after while it gave me this message:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Microsoft SQL Server Desktop Engine

Setup failed to configure the server. Refer to thr server error log and setup error logs for more information.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The LOG gave me this content:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2005-08-28 20:59:46.94 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
      Dec 17 2002 14:22:05
      Copyright (c) 1988-2003 Microsoft Corporation
      Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)

2005-08-28 20:59:47.00 server Copyright (C) 1988-2002 Microsoft Corporation.
2005-08-28 20:59:47.00 server All rights reserved.
2005-08-28 20:59:47.00 server Server Process ID is 2252.
2005-08-28 20:59:47.00 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2005-08-28 20:59:47.09 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2005-08-28 20:59:47.45 server SQL Server configured for thread mode processing.
2005-08-28 20:59:47.47 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2005-08-28 20:59:47.87 spid3 Warning ******************
2005-08-28 20:59:47.87 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2005-08-28 20:59:48.13 spid3 Starting up database 'master'.
2005-08-28 20:59:50.79 server Using 'SSNETLIB.DLL' version '8.0.766'.
2005-08-28 20:59:50.79 spid5 Starting up database 'model'.
2005-08-28 20:59:50.98 spid3 Server name is 'PEGASUS'.
2005-08-28 20:59:50.98 spid3 Skipping startup of clean database id 5
2005-08-28 20:59:51.01 spid3 Skipping startup of clean database id 6
2005-08-28 20:59:51.01 spid3 Starting up database 'msdb'.
2005-08-28 20:59:52.03 spid5 Clearing tempdb database.
2005-08-28 20:59:53.95 server SQL server listening on Shared Memory.
2005-08-28 20:59:53.95 server SQL Server is ready for client connections
2005-08-28 20:59:54.00 spid5 Starting up database 'tempdb'.
2005-08-28 20:59:54.75 spid3 Recovery complete.
2005-08-28 20:59:54.75 spid3 SQL global counter collection task is created.
2005-08-28 20:59:54.92 spid3 Warning: override, autoexec procedures skipped.
2005-08-28 21:01:42.63 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

( I wonder if it does matter if the IIS service was activated or not during the installation )

What I should do now ?

vikramvk

I am having the exact same problem. I too am getting the error message when I try to install MSDE:
Setup failed to configure the server. Refer to thr server error log and setup error logs for more information.

I have to mention that this works fine on a brand new clean machine. But once I uninstall MSDE and try to re-install I get this error.

Any help will be appreciated.

Thanks,
Vikram

vikramvk

I forgot to mention, I am using the setup.ini file for settings.

Vikram