MSDE 2000 Set-up: Invalid instance name

Thanks in advance.

I installed SQL 2000 Client Portion in my local computer: No server functionality. I selected my computer name as an instance name. Installation went OK.

Now, I am trying to install MSDE in my computer. Error comes in early part of installation: It says, "The instance name specified is not valid"

Please, any advise and suggestion.

Try deinstalling the SQL Client (why did that ask for an instance name when you didn't install the server - are you sure about deselecting the server?)

Install MSDE after the SQL Client was deinstalled. MSDE 2000 comes with a readme which explains the command line options for the setup. Read it carefully.

--
SvenC

|||

Thanks.

By the way, I have SQL 2005 Server in my computer.

Maybe, this is why.

|||

Yes, presumably MSDE tries to use the same instance name already in use by SQL 2005. Why would you want both versions on one machine?

Well, you can do it, but check the MSDE readme how to configure a different instance name. In the connection string you will use servername\instancename to access the named instance.

--
SvenC

MSDE 2000 installation

Hi,
I'm creating an install disk that our company is distributing to a selected
group of our immediate direct customers. We are using the SQL server database
in house and we are creating a program that these customers can enter
contract data at their own PC, print the data in a report format and then
send us the contracts with the remittance report. We are developing an
executable program that uses a SQL server database with 6 tables in house.
I'm using installshield to create a disc that the user will load onto their
own PC. We want to be able to populate these tables by having the user's log
onto our web site and doing a update for the latest table updates. So far
I've been pursuing the idea of using MSDE 2000 for the user's PC's, however,
is this the wisest decision. Would it be better (simpler) to use a different
database on the user's PC's and use a driver to import data from our SQL
server tables to the database on the PC. If MSDE 2000 is the best bet, where
does MDAC version 2.6 come in the picture or does it. I know this is fairly
lengthy message, but I could use some direction on thisMSDE is an alternative for MS Access. It is more robust and can scale up to
SQL Server SE or EE. It has royalty free re-distribution rights; however,
the caveat is that you can not use the SQL Server Administrative tools. You
must code your own administrative features into your application yourself.
It can be more complex; however, it may be worth your time.
MDAC automatically gets installed when you install MSDE onto the client.
Sincerely,
Anthony Thomas
"Randers" <Randers@.discussions.microsoft.com> wrote in message
news:B5893843-1A3D-4207-94BF-8480B9FEB5AF@.microsoft.com...
Hi,
I'm creating an install disk that our company is distributing to a selected
group of our immediate direct customers. We are using the SQL server
database
in house and we are creating a program that these customers can enter
contract data at their own PC, print the data in a report format and then
send us the contracts with the remittance report. We are developing an
executable program that uses a SQL server database with 6 tables in house.
I'm using installshield to create a disc that the user will load onto their
own PC. We want to be able to populate these tables by having the user's log
onto our web site and doing a update for the latest table updates. So far
I've been pursuing the idea of using MSDE 2000 for the user's PC's, however,
is this the wisest decision. Would it be better (simpler) to use a different
database on the user's PC's and use a driver to import data from our SQL
server tables to the database on the PC. If MSDE 2000 is the best bet, where
does MDAC version 2.6 come in the picture or does it. I know this is fairly
lengthy message, but I could use some direction on this