Installing MSDE 2000

I'm trying to install SQL2000 Desktop for Visual Studio.Net. Fromcmd prompt
I'm running:
Setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD=password
Nothing happens then I get a popup saying: "Please go to the control panel
to install and configure system components".
How intuitive!! Does this mean MDAC upgrade or what? Anyone know what this
message implies?
TX
Don't know if it has anything to do with it but can you firstly try..
Setup.exe SAPWD="password"
--Original Message--
From: CW [mailto:CW@.discussions.microsoft.com]
Posted At: Tuesday, 18 January 2005 7:55 AM
Posted To: microsoft.public.sqlserver.msde
Conversation: Installing MSDE 2000
Subject: Installing MSDE 2000
I'm trying to install SQL2000 Desktop for Visual Studio.Net. Fromcmd
prompt I'm running:
Setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1
SAPWD=password
Nothing happens then I get a popup saying: "Please go to the control
panel to install and configure system components".
How intuitive!! Does this mean MDAC upgrade or what? Anyone know what
this message implies?
TX

Installing Local SQL2000 Personal Edition

I am trying to install a local version of SQL2000 on my XP Pro.

I am having this problem, do you know why because I cannot find the solution on the microsoft website:
Server: Msg 17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.You'd probably do better to post this kind of question in the Micrsoft SQL Server (http://www.dbforums.com/f7/) forum.

-PatP

installing 64bit SQL2000 EE on 32-bit Windows 2003 Enterprise server

Will my SQL server work like 32-bit or 64-bit if I installed 64bit SQL2000 EE on 32-bit Windows 2003 Enterprise server?
Did it install ? I don't think it should.Certainly doesn't on my PC
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Dipesh" <anonymous@.discussions.microsoft.com> wrote in message
news:8C50C76F-8EF4-4B09-BB17-4A7FABEE5B1E@.microsoft.com...
> Will my SQL server work like 32-bit or 64-bit if I installed 64bit SQL2000
EE on 32-bit Windows 2003 Enterprise server?
>
|||It installed fine. I am just concerned about if 64-bit functionality will be available to me or not. Is there a way to verify.

Installed SQL2005: now can't access SQL2000 (Local) in EM

After installing SQL2005 (with a new instance), I couldn't access my previous
(local) server through Enterprise Mnager, although I can access it through
Query Analyser.
I deleted the connection in Enterprise manager and tried to recreate it
(using either windows security or SQL Autentication): get the message 'Client
unable to establish connection. TCP Provider: No connection could be made
because the target machine actively refused it.'
Ashley,
Earlier versions of SQL Server 2005 had a tendancy to trash the SQL Server
2000 tools, perhaps this is your issue. I always put SQL 2005 into a virtual
machine and will keep it there until it RTMs, unless I can install it on a
fresh machine without SQL Server 2000 on.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Ashley Brewerton" wrote:

> After installing SQL2005 (with a new instance), I couldn't access my previous
> (local) server through Enterprise Mnager, although I can access it through
> Query Analyser.
> I deleted the connection in Enterprise manager and tried to recreate it
> (using either windows security or SQL Autentication): get the message 'Client
> unable to establish connection. TCP Provider: No connection could be made
> because the target machine actively refused it.'
|||You should re-register SQLDMO.DLL using:
regsvr32 "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqldmo.dll"
Razvan
|||Thanks Razvan: after restarting the services that worked perfectly.
Ashley
"Razvan Socol" wrote:

> You should re-register SQLDMO.DLL using:
> regsvr32 "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqldmo.dll"
> Razvan
>

Installed SQL2005: now can't access SQL2000 (Local) in EM

After installing SQL2005 (with a new instance), I couldn't access my previou
s
(local) server through Enterprise Mnager, although I can access it through
Query Analyser.
I deleted the connection in Enterprise manager and tried to recreate it
(using either windows security or SQL Autentication): get the message 'Clien
t
unable to establish connection. TCP Provider: No connection could be made
because the target machine actively refused it.'Ashley,
Earlier versions of SQL Server 2005 had a tendancy to trash the SQL Server
2000 tools, perhaps this is your issue. I always put SQL 2005 into a virtual
machine and will keep it there until it RTMs, unless I can install it on a
fresh machine without SQL Server 2000 on.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Ashley Brewerton" wrote:

> After installing SQL2005 (with a new instance), I couldn't access my previ
ous
> (local) server through Enterprise Mnager, although I can access it through
> Query Analyser.
> I deleted the connection in Enterprise manager and tried to recreate it
> (using either windows security or SQL Autentication): get the message 'Cli
ent
> unable to establish connection. TCP Provider: No connection could be made
> because the target machine actively refused it.'|||You should re-register SQLDMO.DLL using:
regsvr32 "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqldmo.dll"
Razvan|||Thanks Razvan: after restarting the services that worked perfectly.
Ashley
"Razvan Socol" wrote:

> You should re-register SQLDMO.DLL using:
> regsvr32 "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqldmo.dll"
> Razvan
>sql

Installed SQL2005: now can't access SQL2000 (Local) in EM

After installing SQL2005 (with a new instance), I couldn't access my previous
(local) server through Enterprise Mnager, although I can access it through
Query Analyser.
I deleted the connection in Enterprise manager and tried to recreate it
(using either windows security or SQL Autentication): get the message 'Client
unable to establish connection. TCP Provider: No connection could be made
because the target machine actively refused it.'Ashley,
Earlier versions of SQL Server 2005 had a tendancy to trash the SQL Server
2000 tools, perhaps this is your issue. I always put SQL 2005 into a virtual
machine and will keep it there until it RTMs, unless I can install it on a
fresh machine without SQL Server 2000 on.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Ashley Brewerton" wrote:
> After installing SQL2005 (with a new instance), I couldn't access my previous
> (local) server through Enterprise Mnager, although I can access it through
> Query Analyser.
> I deleted the connection in Enterprise manager and tried to recreate it
> (using either windows security or SQL Autentication): get the message 'Client
> unable to establish connection. TCP Provider: No connection could be made
> because the target machine actively refused it.'|||You should re-register SQLDMO.DLL using:
regsvr32 "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqldmo.dll"
Razvan|||Thanks Razvan: after restarting the services that worked perfectly.
Ashley
"Razvan Socol" wrote:
> You should re-register SQLDMO.DLL using:
> regsvr32 "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqldmo.dll"
> Razvan
>

Installed SQL2000 SP4 successfully but still shows RTM as installe

After installing SP4 on server, I checked ProductLevel and Productversion and
they still showed RTM and 8.00.194.
I did see a whitepaper about this regarding SP1 and the fix was to apply the
latest SP which is SP4, so this does not apply to me.
The other option was to edit the registry key which I do not feel
comfortable doing.
Has anyone else come across this before??
Hi Kristen
Your version number is not SP1 (384) but the RTM version.
Did you run the setup from the directory that you unzipped the files to?
Have you more than one instance of SQL Server running and have you upgraded
them all?
Did you run the service pack setup from the server?
John
"Kristen" wrote:

> After installing SP4 on server, I checked ProductLevel and Productversion and
> they still showed RTM and 8.00.194.
> I did see a whitepaper about this regarding SP1 and the fix was to apply the
> latest SP which is SP4, so this does not apply to me.
> The other option was to edit the registry key which I do not feel
> comfortable doing.
> Has anyone else come across this before??

Installed SQL2000 SP4 successfully but still shows RTM as installe

After installing SP4 on server, I checked ProductLevel and Productversion and
they still showed RTM and 8.00.194.
I did see a whitepaper about this regarding SP1 and the fix was to apply the
latest SP which is SP4, so this does not apply to me.
The other option was to edit the registry key which I do not feel
comfortable doing.
Has anyone else come across this before'?Hi Kristen
Your version number is not SP1 (384) but the RTM version.
Did you run the setup from the directory that you unzipped the files to?
Have you more than one instance of SQL Server running and have you upgraded
them all?
Did you run the service pack setup from the server?
John
"Kristen" wrote:
> After installing SP4 on server, I checked ProductLevel and Productversion and
> they still showed RTM and 8.00.194.
> I did see a whitepaper about this regarding SP1 and the fix was to apply the
> latest SP which is SP4, so this does not apply to me.
> The other option was to edit the registry key which I do not feel
> comfortable doing.
> Has anyone else come across this before'?

Installed SQL2000 SP4 successfully but still shows RTM as installe

After installing SP4 on server, I checked ProductLevel and Productversion an
d
they still showed RTM and 8.00.194.
I did see a whitepaper about this regarding SP1 and the fix was to apply the
latest SP which is SP4, so this does not apply to me.
The other option was to edit the registry key which I do not feel
comfortable doing.
Has anyone else come across this before'?Hi Kristen
Your version number is not SP1 (384) but the RTM version.
Did you run the setup from the directory that you unzipped the files to?
Have you more than one instance of SQL Server running and have you upgraded
them all?
Did you run the service pack setup from the server?
John
"Kristen" wrote:

> After installing SP4 on server, I checked ProductLevel and Productversion
and
> they still showed RTM and 8.00.194.
> I did see a whitepaper about this regarding SP1 and the fix was to apply t
he
> latest SP which is SP4, so this does not apply to me.
> The other option was to edit the registry key which I do not feel
> comfortable doing.
> Has anyone else come across this before'?

Installation problem with SQL2000 on WinXP

Hello all!

I'm trying to install: Microsoft SQL Server 2000, Developer Edition

On my Laptop :

Windows XP Professional
Intel(R) Pentium(R) 4, Mobile CPU 1.80Ghz
352 Mb of RAM
40Gb Harddrive

Problem:
When I start the setup(setup.exe) I get the following msg:

Exexution cannot continue as the language dependent resource file c:\Windows\Temp\SqlSetup\Bin\Resources\1033\sqlsui .RLL

When I press ok I get the msg:

LoadLirary failed on sqlsui.dll

I've used the search function but haven't found anyone with the same problem, other than this one :
http://dbforums.com/arch/71/2002/10/521355

But in that case its Win2000 not XP.

If anyone could help I would be very happy

Best Wishes,
Farekhttp://dbforums.com/arch/71/2002/10/532051

Installation Problem

I am trying to install MS SQL2000 onto a remote WinServ2003 from an XP. Since XP is client, it greys out option to install on a remote server. Help and directions to resolve install would be appreciated, TKS
>
> I am trying to install MS SQL2000 onto a remote WinServ2003 from an XP.
> Since XP is client, it greys out option to install on a remote server.
> Help and directions to resolve install would be appreciated, TKS
>
This is by design.
Windows NT 4.0 workstation, Windows 2000 professional and Windows XP home
and professional editions do not support a remote server install.
You need a server edition installation to do a remote install.
Hope this helps,
Eric Crdenas
SQL Server senior support professional

Installation Problem

I am trying to install MS SQL2000 onto a remote WinServ2003 from an XP. Since XP is client, it greys out option to install on a remote server. Help and directions to resolve install would be appreciated, TKS>
> I am trying to install MS SQL2000 onto a remote WinServ2003 from an XP.
> Since XP is client, it greys out option to install on a remote server.
> Help and directions to resolve install would be appreciated, TKS
>
--
This is by design.
Windows NT 4.0 workstation, Windows 2000 professional and Windows XP home
and professional editions do not support a remote server install.
You need a server edition installation to do a remote install.
Hope this helps,
--
Eric Cárdenas
SQL Server senior support professional

Installation Problem

I am trying to install MS SQL2000 onto a remote WinServ2003 from an XP. Sinc
e XP is client, it greys out option to install on a remote server. Help and
directions to resolve install would be appreciated, TKS>
> I am trying to install MS SQL2000 onto a remote WinServ2003 from an XP.
> Since XP is client, it greys out option to install on a remote server.
> Help and directions to resolve install would be appreciated, TKS
>
--
This is by design.
Windows NT 4.0 workstation, Windows 2000 professional and Windows XP home
and professional editions do not support a remote server install.
You need a server edition installation to do a remote install.
Hope this helps,
Eric Crdenas
SQL Server senior support professional