MSDE SP4 install problem

I attempted to install MSDE SP4 (file SQL2000.MSDE-KB884525-SP4-x86-ENU) on a WinXP Pro SP2 machine.

Command used:

setup SAPWD="ourpw" SECURITYMODE=SQL /L*v c:\MSDELog.log

Install log shows successful install.

MSDE appears to function properly, service starts automatically after reboot, etc.

I can open and work with DB's with a freebie 3rd party GUI called DbaMGR2K, through which I have added the necessary DB user for our locally running ASP application to use the db.

However, when I try to use the DB with our locally running ASP application - connecting with ADO from a dll we wrote, I get the following:

"[DNETLIB]{ConnectionOpen (Connect()).]SQL Server does not exist or access denied"

Any help appreciated.

day10

Hi,

make sure that you connect to the same database and you are using a valid login for connecting. Perhaps you have chosen another authentication mode within the ADO code ? That could explain either the one or the other error message you are getting.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I think we have solved the issue. We used the SQL Server Network Utility to enable TCP/IP (apparently not enabled by default) and now all appears well.

I wonder if there is a way to enable TCP/IP during the install process. Is there an install flag/option?

|||

>> Is there an install flag/option?

Most likely. The flag for this when installing SP3 was "DISABLENETWORKPROTOCOLS=0". I wouldn't think that they would have removed it for SP4.

sql

MSDE incomplete install

I have SQL 2000 running on a Windows 2000 server.
A third party product attempted to install MSDE onto the same server, but
failed to complete its install.
At random it appears as though the MSDE attempts to run and complete its
install, which increases the processor upto approx 100%.
Since the MSDE is in an incomplete state, what is the best approach at
attempting to remove the failing component and leave SQL intact.
MSDE does not show up in the add/remove programs.
Regardshi,
Ray wrote:
> I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server,
> but failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete
> its install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
>
first identify the named instance name, perhaps looking in the \Program
Files\Microsoft SQL Server\ folder... as you already have a SQL Server 2000
installed (probably as default instance, check it first), you could have
something like MSSQL$InstanceName...
you can then manually clean up the failed install following
http://support.microsoft.com/defaul...b;EN-US;Q290991 ...
this procedure does not clean up Windows Installer MSDE related registry
entries, and you have to use (if you want to) MSIZap.exe, part of the
Windows Installer SDK as exposed in
http://support.microsoft.com/defaul...kb;en-us;320873
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||The reason MSDE doesn't appear in add/remove programs is that the third
party product installed it as a merge module which means as far as the
installer is concerned, it is part of the product you're installing. Try
removing the third party product with add/remove programs.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ray" <Ray@.test.com> wrote in message
news:%23g62vrfiGHA.1600@.TK2MSFTNGP04.phx.gbl...
>I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server, but
> failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete its
> install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
> Regards
>

MSDE incomplete install

I have SQL 2000 running on a Windows 2000 server.
A third party product attempted to install MSDE onto the same server, but
failed to complete its install.
At random it appears as though the MSDE attempts to run and complete its
install, which increases the processor upto approx 100%.
Since the MSDE is in an incomplete state, what is the best approach at
attempting to remove the failing component and leave SQL intact.
MSDE does not show up in the add/remove programs.
Regardshi,
Ray wrote:
> I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server,
> but failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete
> its install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
>
first identify the named instance name, perhaps looking in the \Program
Files\Microsoft SQL Server\ folder... as you already have a SQL Server 2000
installed (probably as default instance, check it first), you could have
something like MSSQL$InstanceName...
you can then manually clean up the failed install following
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 ...
this procedure does not clean up Windows Installer MSDE related registry
entries, and you have to use (if you want to) MSIZap.exe, part of the
Windows Installer SDK as exposed in
http://support.microsoft.com/default.aspx?scid=kb;en-us;320873
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||The reason MSDE doesn't appear in add/remove programs is that the third
party product installed it as a merge module which means as far as the
installer is concerned, it is part of the product you're installing. Try
removing the third party product with add/remove programs.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ray" <Ray@.test.com> wrote in message
news:%23g62vrfiGHA.1600@.TK2MSFTNGP04.phx.gbl...
>I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server, but
> failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete its
> install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
> Regards
>

MSDE Error on attempting to create new Access 2000 project

Hi folks
I've just installed MSDE on my Win 2k machine and have attempted to
create a new Access 2000 project. When I do (and using a number of
different Login ID/Password combinations), I get this:
Connection failed:
SQLState: '01000'
SQL Server Error: 123
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen
(CreateFile()).
Connection failed:
SQLState: '08001'
SQL Server Error: 123
[Microsoft][ODBC SQL Server Driver]Client unable to establish
connection
can anyone tell me what this means and what I should do. Any help much
appreciated.
thanks
Laurence
Laurence,
See: http://support.microsoft.com/default...b;en-us;233312
It looks like you do not have named pipes installed with your MSDE, but you
are using it from your client.
Russell Fields
"Laurence" <laurencetruman@.yahoo.com> wrote in message
news:c8e229b3.0406090533.5ecefd75@.posting.google.c om...
> Hi folks
> I've just installed MSDE on my Win 2k machine and have attempted to
> create a new Access 2000 project. When I do (and using a number of
> different Login ID/Password combinations), I get this:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen
> (CreateFile()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver]Client unable to establish
> connection
> can anyone tell me what this means and what I should do. Any help much
> appreciated.
> thanks
> Laurence
|||Laurence,
Actually, you might find this more helpful (since my first post was to an
old version of MSDE)
ACC2002: "Configuring SQL Server 2000 Desktop Engine" White Paper Available
in Download Center
http://support.microsoft.com/default...b;en-us;301413
Russell Fields
"Laurence" <laurencetruman@.yahoo.com> wrote in message
news:c8e229b3.0406090533.5ecefd75@.posting.google.c om...
> Hi folks
> I've just installed MSDE on my Win 2k machine and have attempted to
> create a new Access 2000 project. When I do (and using a number of
> different Login ID/Password combinations), I get this:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen
> (CreateFile()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver]Client unable to establish
> connection
> can anyone tell me what this means and what I should do. Any help much
> appreciated.
> thanks
> Laurence