Invalid Instance Name while trying to install MSDE

I am running XP SP2. I have downloaded MSDE (SQL Sever 2000) to put on my
laptop for training purposes. When I try to load the setup program I get an
error message saying "The Instance Name Specified Is Invalid" and then when I
acknowledge the message the install exits. I have searched for and tried to
understand the post that seem to relate to my problem but I am just not
knowledgable enough to understand what to do. If someone would please tell me
(in baby steps) how to fix this problem so I can install MSDE then I would
really appreciate it. If you need ANY additional information please feel free
to contact me and I will respond immediately. Your time and attention is very
much appreciated.
Thank you for your help...premium001
Read into the readme file in your extracted folder.
If there is an instance of SQL Server already installed, the MSDE should be
named.
"premium001" wrote:

> I am running XP SP2. I have downloaded MSDE (SQL Sever 2000) to put on my
> laptop for training purposes. When I try to load the setup program I get an
> error message saying "The Instance Name Specified Is Invalid" and then when I
> acknowledge the message the install exits. I have searched for and tried to
> understand the post that seem to relate to my problem but I am just not
> knowledgable enough to understand what to do. If someone would please tell me
> (in baby steps) how to fix this problem so I can install MSDE then I would
> really appreciate it. If you need ANY additional information please feel free
> to contact me and I will respond immediately. Your time and attention is very
> much appreciated.
> --
> Thank you for your help...premium001
|||hi,
premium001 wrote:
> I am running XP SP2. I have downloaded MSDE (SQL Sever 2000) to put
> on my laptop for training purposes. When I try to load the setup
> program I get an error message saying "The Instance Name Specified Is
> Invalid" and then when I acknowledge the message the install exits. I
> have searched for and tried to understand the post that seem to
> relate to my problem but I am just not knowledgable enough to
> understand what to do. If someone would please tell me (in baby
> steps) how to fix this problem so I can install MSDE then I would
> really appreciate it. If you need ANY additional information please
> feel free to contact me and I will respond immediately. Your time and
> attention is very much appreciated.
as <zhaounknown> already wrote, please read the proviede ReadmeFile... it
explains you have to provide a set of parameters to the setup.exe boostrap
installer..
typically you have to provide the SAPWD="your strong password" as you are
forced to protect "sa" login ...
you can specify if you like to enable network connections
(DISABLENETWORKPROTOCOLS=0), if you like to permit standard SQL Server
authenticated connections (SECURITY MODE=SQL) as the default does not permit
them to be authenticated, or if you like to install a named instance
(INSTANCENAME="the name").. and please enable verbose logging of the
installation task providing the /L*v "c:\Msde.txt" parameter, which results
in an about 2Mb text file you can inspect for
RETURN VALUE 3
entries indicating troubles... about 10/20 lines before and/or after each
entry some (sometime cryptic) description of the problem will be logged..
so, if you like to install a named instance (named "MSDE") with enabled
networkprotocols and enabling SQL Server authenticated connections you have
to provide something similar to
C:\MSDERelaA\>setup.exe INSTANCENAME="MSDE" SECURITY MODE=SQL
DISABLENETWORKPROTOCOLS=0 SAPWD="your strong password" /L*v "c:\Msde.txt"
all on the same line from the command promt
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Invalid Instance Invalid Connection NT 4.0

When connecting to SQL Server using a Win NT 4.0 client I receive the messag
e:
[DBNETLIB] ConnectionOpen [Invalid Instance ()]Invalid Connection
Another Win NT 4.0 client works fine.
SQL MSDE 2000 release A installed on the server. Another SQL 2000 instance
is running (from another vendor) on the same machine. MDAC 2.7 sp1 refresh
checks out fine in component checker.
Any idea?By default MSDE 2000 SP3 only allows local connections, you have to go in
and enable MSDE to listen on TCP or Named Pipes if you wnat to allow remote
connectivity.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Invalid destination path when trying to create distribution database

Hello. I am attempting to add a distribution database to an instance of SQL Server on my local PC. I am using SQL 2005 Developer Edition. I am able to set the instance up as a distributor using the following command:

exec sp_adddistributor @.distributor = N'computername\instancename'

I use the following command to create the distribution database:

exec sp_adddistributiondb @.database = N'distribution', @.data_folder = N'C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Data',

@.data_file_size = 4, @.log_folder = N'C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Data',

I get the following error when executing that command:

Msg 14430, Level 16, State 1, Procedure sp_adddistributiondb, Line 214

Invalid destination path C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Data.

It's not due to permissions on that particular folder. I have tried using other folders, all with the same results. Also, I am an Administrator on the PC, so I have full permissions. I have tried running the SQL Server services as myself and Local System. Same results both times. Co-workers with apparently the same setup are able to create the distribution database without a problem.

Has anybody had this type of problem?

Thanks,

Evan

I executed the same thing above, but different path, and it worked for me. Proc sp_adddistributiondb is raising error 14430 because proc sp_MSget_file_existence cannot locate the path you specified. I'd run a profiler trace to see why this proc cannot locate your path.

'Invalid authorization specification' from IDBInitialize::Initialize (c++)

Hi

I've been trying to connect to my local SQL Server instance (SQL Server 2005) using the SQLNCLI interface from c++ without success. I consistently receive an 'Invalid authorization specification' error (SQL state 28000 and SQL error number 0) when I call IDBInitialize::Initialize to connect to the database. I was hoping someone here could shed some light on this and help me out.

The strange thing is that I get no error if I leave the user blank (L"" in vValue.bstrVal) and try to connect. Also, IDBProperties::SetProperties returns 0 when the user is blank but 40eda when the user is set. This seems to be a message from the pipeline facility but I haven't found the description of the code (0xeda).

The user in the database is configured with no password and I can successfully connect to the server and open the database using that user through Management Studio.

I've also tried using the SQLOLEDB provider with the same results.

Suspecting that I'm setting the properties wrong I include a code snippet below showing how I'm setting the properties:

for (int i = 0; i < sizeof(dbprop) / sizeof(dbprop[0]); i++)
VariantInit(&dbprop[ i ].vValue);

// Server name
dbprop[0].dwPropertyID = DBPROP_INIT_DATASOURCE;
dbprop[0].vValue.vt = VT_BSTR;
dbprop[0].vValue.bstrVal = SysAllocString(L"localhost");
dbprop[0].dwOptions = DBPROPOPTIONS_REQUIRED;
dbprop[0].colid = DB_NULLID;

// Database
dbprop[1].dwPropertyID = DBPROP_INIT_CATALOG;
dbprop[1].vValue.vt = VT_BSTR;
dbprop[1].vValue.bstrVal = SysAllocString(L"test");
dbprop[1].dwOptions = DBPROPOPTIONS_REQUIRED;
dbprop[1].colid = DB_NULLID;

// Username
dbprop[2].dwPropertyID = DBPROP_AUTH_INTEGRATED;
dbprop[2].vValue.vt = VT_BSTR;
dbprop[2].vValue.bstrVal = SysAllocString(L"jph");
dbprop[2].dwOptions = DBPROPOPTIONS_REQUIRED;
dbprop[2].colid = DB_NULLID;

Cheers,
JPProblem solved.

A little bit embarrasing, since I, somehow, misinterpreted the DBPROP_AUTH_INTEGRATED parameter. It should have been DBPROP_AUTH_USERID (of course) instead.

The username propertie now looks like this:

// Username
dbprop[2].dwPropertyID = DBPROP_AUTH_USERID;
dbprop[2].vValue.vt = VT_BSTR;
dbprop[2].vValue.bstrVal = SysAllocString(L"jph");
dbprop[2].dwOptions = DBPROPOPTIONS_REQUIRED;
dbprop[2].colid = DB_NULLID;

and works like a charm.

JP

Invalid Argument provided

Error message I get is:
"Invalid Argument provided Details: Object reference not set to an instance of an object."

I get this message every time I run the report. If I verify database before runing report, message is gone and report runs fine. Data connection is done using a VB file datasets (DLL). There are few subreports on this file which use same DLL but different datasets. If reports are removed report runs fine no error messages.

Any ideas would be much appreciated.

RobertFound the issue, one of Crystal dll was not properly registered (by install), once you re-install everything works fine.

Cheers|||Found the issue, one of Crystal dll was not properly registered (by install), once you re-install everything works fine.

Cheers
It is appreciable that you shared the solution :)