I can no longer connect to SQL Server 2000 using ADO after installing XP SP2.
I receive authentication error. I have even turned off all firewalls.
I also installed SQL Server Service Pack 4.
I also added the SQL Server data source(ODBC). I am using Windows
Authentication. When I test the ODBC data source it connects successfully.
I just can not access it via ADO.
The receive the error message when I try to open the connection in my program.
Conn.Open
"SQL Server does not exist or access denied."
Can anyone tell me what else I need to do?
RonRon wrote:
> I can no longer connect to SQL Server 2000 using ADO after installing
> XP SP2. I receive authentication error. I have even turned off all
> firewalls.
> I also installed SQL Server Service Pack 4.
> I also added the SQL Server data source(ODBC). I am using Windows
> Authentication. When I test the ODBC data source it connects
> successfully.
> I just can not access it via ADO.
> The receive the error message when I try to open the connection in my
> program. Conn.Open
> "SQL Server does not exist or access denied."
> Can anyone tell me what else I need to do?
> Ron
Can you tell us what your server name is and what connection string you
are passing to the ADO connection object?
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||The server name is: S002542194
Conn.Provider = "SQLOLEDB"
Conn.Properties("Data Source").Value = "S002542194"
Conn.Properties("Initial Catalog").Value = dbstring
Conn.Properties("User ID").Value = user
Conn.Properties("Password").Value = pswd
"David Gugick" wrote:
> Ron wrote:
> > I can no longer connect to SQL Server 2000 using ADO after installing
> > XP SP2. I receive authentication error. I have even turned off all
> > firewalls.
> > I also installed SQL Server Service Pack 4.
> > I also added the SQL Server data source(ODBC). I am using Windows
> > Authentication. When I test the ODBC data source it connects
> > successfully.
> > I just can not access it via ADO.
> > The receive the error message when I try to open the connection in my
> > program. Conn.Open
> > "SQL Server does not exist or access denied."
> > Can anyone tell me what else I need to do?
> > Ron
> Can you tell us what your server name is and what connection string you
> are passing to the ADO connection object?
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||FAQ: How Windows XP Service Pack 2 (SP2) Affects SQL Server and MSDE
http://www.microsoft.com/sql/techinfo/administration/2000/security/winxpsp2faq.asp
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:E8DD2341-1928-4D7E-975A-A53294AA05E8@.microsoft.com...
>I can no longer connect to SQL Server 2000 using ADO after installing XP
>SP2.
> I receive authentication error. I have even turned off all firewalls.
> I also installed SQL Server Service Pack 4.
> I also added the SQL Server data source(ODBC). I am using Windows
> Authentication. When I test the ODBC data source it connects
> successfully.
> I just can not access it via ADO.
> The receive the error message when I try to open the connection in my
> program.
> Conn.Open
> "SQL Server does not exist or access denied."
> Can anyone tell me what else I need to do?
> Ron
>
>|||These are the links I have already been to and told me to install SQL Server
SP4.
I did that and it still doesn't work.
What else can I do?
"Mike Epprecht (SQL MVP)" wrote:
> FAQ: How Windows XP Service Pack 2 (SP2) Affects SQL Server and MSDE
> http://www.microsoft.com/sql/techinfo/administration/2000/security/winxpsp2faq.asp
>
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:E8DD2341-1928-4D7E-975A-A53294AA05E8@.microsoft.com...
> >I can no longer connect to SQL Server 2000 using ADO after installing XP
> >SP2.
> > I receive authentication error. I have even turned off all firewalls.
> > I also installed SQL Server Service Pack 4.
> > I also added the SQL Server data source(ODBC). I am using Windows
> > Authentication. When I test the ODBC data source it connects
> > successfully.
> > I just can not access it via ADO.
> > The receive the error message when I try to open the connection in my
> > program.
> > Conn.Open
> > "SQL Server does not exist or access denied."
> > Can anyone tell me what else I need to do?
> > Ron
> >
> >
> >
>
>|||Ron wrote:
> The server name is: S002542194
> Conn.Provider = "SQLOLEDB"
> Conn.Properties("Data Source").Value = "S002542194"
> Conn.Properties("Initial Catalog").Value = dbstring
> Conn.Properties("User ID").Value = user
> Conn.Properties("Password").Value = pswd
Make sure there isn't an ODBC data source on the PC with the same name.
If all else fails, try and create an alias from the SQL Server Client
Network Utility using the desire protocol and see if that helps.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||David
There is no other ODBC data source on the PC with the same name.
Can you explain how to create an alias from the SQL Server Client
Network Utility using the desire protocol?
"David Gugick" wrote:
> Ron wrote:
> > The server name is: S002542194
> > Conn.Provider = "SQLOLEDB"
> > Conn.Properties("Data Source").Value = "S002542194"
> > Conn.Properties("Initial Catalog").Value = dbstring
> > Conn.Properties("User ID").Value = user
> > Conn.Properties("Password").Value = pswd
> Make sure there isn't an ODBC data source on the PC with the same name.
> If all else fails, try and create an alias from the SQL Server Client
> Network Utility using the desire protocol and see if that helps.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||Ron wrote:
> David
> There is no other ODBC data source on the PC with the same name.
> Can you explain how to create an alias from the SQL Server Client
> Network Utility using the desire protocol?
Sure. Try both named piped and tcp-ip and use the alias name in the
connection string to see if that works. If it does, it won't address the
problem, but will let you know that you can see the server from that
client.
Snipped from the Coefficient online help...
1.. Run the SQL Server Client Network Utility. You should find this
item under your Start Menu and then under the SQL Server program group.
2.. Click the Alias tab
3.. Click the Add button to add a new alias
4.. Select the Network Library you want to use with the alias. We
recommend you use TCP/IP whenever possible.
5.. Type in the name for the alias in the Server Alias entry field.
This can be any name, but it should not conflict with the real name of
any server or any other alias defined on the client.
6.. Enter the real server name in the Server Name entry field. For a
default instance of SQL Server, specify the server name as it is defined
by the server. For a named instance of SQL Server 2000+, use the
SERVER_NAME\INSTANCE_NAME format.
7.. For TCP/IP, you should elect to Dynamically Determine Port if your
SQL Server is defined on the default port (normally 1433). For a custom
port number, uncheck this option and enter the correct TCP/IP port
number.
8.. For Named Pipes, you will see the default pipe name, which is
normally the correct one. For custom pipe names, enter the correct name
in the Pipe Name entry field.
9.. Press OK twice to exit the Client Network Utility
10.. When you register the server in Coefficient, use the alias name
instead of the real server name.
David Gugick
Quest Software
www.imceda.com
www.quest.com
willajo wrote:
