Re: new MSDE install fails with "instance name specified is invalid"

From: Andrea Montanari (andrea.sqlDMO_at_virgilio.it)
Date: 03/08/04


Date: Mon, 8 Mar 2004 13:03:12 +0100

hi Bob,
"Bob P." <anonymous@discussions.microsoft.com> ha scritto nel messaggio
news:111B62D3-B753-4A78-88BD-7309173DFE4F@microsoft.com...
> I am trying to put SQL Server 2000 and MSDE on same local machine. I
installed 2000
> Developer (from VS Tools for Office)using "typical" install level, using
the LocalSystem
>Account, so no password required. When I run C:\sql2ksp3\MSDE\setup.exe
(generated by
>Office 2003 disk), the first thing that happens is dialog box that says
"instance name
>specified is invalid" and the setup is cancelled. When I tried to do the
MSDE install before
>the 2000, I got a "Strong SA password is required - use SAPWD switch to
supply the
>same", so I installed the 2000 and then came back to try MSDE, if only
because I couldn't
>figure out how to get Online Books going to find out about how to supply
SAPWD. There is
>no other instance of 2000, and none of MSDE, on the machine. I thought the
2000 instance
>was unnamed. (?)
>
> I am an almost complete rookie about SQL Server. Any help on instance name
would be
> appreciated, or the SAPWD which may be waiting for me. Thanks !

the first SQL Server instance you installed hase become the default instance
becouse you did not provide instance name...
in order to install other SQL Server and/or MSDE instancese, they must be
"named" instances...
please see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for further info about all parameters accepted by the setup.exe installer
bootstrap of MSDE...
you can download Books On Line for free from
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

hth

-- 
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm        http://italy.mvps.org
DbaMgr2k ver 0.6.0  -  DbaMgr ver 0.52.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply


Relevant Pages

  • Re: MSDE licensing rules
    ... > The only problem I ran into was when to setup MSDE. ... > approach is to only install it, with an instancename, when there is no ... Andrea Montanari (Microsoft MVP - SQL Server) ...
    (microsoft.public.sqlserver.msde)
  • Re: Administering MSDE with Enterprise Manager
    ... SETUP SAPWD="wombat" created 'Windows Only Authentication'. ... the MSDE machine from those on the machine that I was connecting from. ... > A. You can only use SQL Server tools and services in conjunction ... >> created during MSDE's install. ...
    (microsoft.public.sqlserver.connect)
  • Re: Administering MSDE with Enterprise Manager
    ... SETUP SAPWD="wombat" created 'Windows Only Authentication'. ... the MSDE machine from those on the machine that I was connecting from. ... > A. You can only use SQL Server tools and services in conjunction ... >> created during MSDE's install. ...
    (microsoft.public.sqlserver.msde)
  • Re: Administering MSDE with Enterprise Manager
    ... SETUP SAPWD="wombat" created 'Windows Only Authentication'. ... the MSDE machine from those on the machine that I was connecting from. ... > A. You can only use SQL Server tools and services in conjunction ... >> created during MSDE's install. ...
    (microsoft.public.sqlserver.setup)
  • Re: Named Instance, Connectivity Question
    ... with SQL Server 2000 Client ... I installed MSDE 2000 under Named Instance. ... yes, you can install only a named instance, only a default instance, or upt ...
    (microsoft.public.sqlserver.msde)