Re: ADO Connection Strng Error

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Rinoo Rajesh (rinoorajesh_at_yahoo.com)
Date: 03/02/04 

Date: Tue, 2 Mar 2004 22:39:56 +0530

What's the error description that accompanies these errors? If it is
something like "changed language context..." then it is a harmless message
(more akin to information being sent back and being trapped by ADO as part
of the errors collection.

Alternatively, it could be NT LM Security provider service (SSPI uses
this)...

Regards,

Rinoo Rajesh

"MG" <anonymous@discussions.microsoft.com> wrote in message
news:155D8F21-7B81-4DFA-9F9D-CD0F873551EB@microsoft.com...
> Here Goes:
>
> I have a SQL Server 7 DTS job that uses an Active X Task. That task uses
an ADO Connection string to connect to the server to run some stored
procedures. This code HAS been working for over two years. The Server is
NT4, the workstation WAS NT4. The DTS job runs fine in production on SQL
Server via SQL Agent and from the NT4 workstation as well. When I run the
DTS job manually from a Windows 2000 workstation, the same identical piece
of ADO Code errors with a Invalid Connection String Attribute error message.
I know conclusively that it is tied to something on the Windows 2000
workstation. The connection string is:
> myconstr = "Provider=SQLOLEDB.1;DATA SOURCE=CHNTBCC10;Inital
Catalog=Warehouse;Integrated Security=SSPI"
>
> Now, the place where the error occurs is at the Open myconstr part of the
code. ADO (not ADO.Net) is sending back on error record with an error number
of zero.
>
> Obviously, I have worked around this with a condition whereby when the
error count is 1 and that error number is zero, continue. The rest of the
logic works fine.
>
> Any ideas why this is happening with the windows 2000 workstation? Any
other ideas of how to handle this.

Relevant Pages