[TCP/IP Sockets]ConnectionCheckForData (CheckforData())

MS SQL 2000.
When I attempt a SELECT I get the following:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
The offending SELECT
select a.account
from table1 a
where a.doc = '123456A'
and (select count(1)
from table1 b
where a.account = b.account
and a.doc = b.doc
and a.oseq = b.oseq
and a.party = b.party) > 1
If I do the SELECT with out the sub select it works fine. Suggestions?Reworking the statement worked around the issue.
=?Utf-8?B?Sm9obiBCZWxs?= <jbellnewsposts@.hotmail.com> wrote:
>Hi Scott
>Having DDL and sample data with the expected results from that data would be
>nice. See http://www.aspfaq.com/etiquette.asp?id=5006
>"Scott Sheen" wrote:
>> MS SQL 2000.
>> When I attempt a SELECT I get the following:
>> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData
>> (CheckforData()).
>> Server: Msg 11, Level 16, State 1, Line 0
>> General network error. Check your network documentation.
>> Connection Broken
>>
>> The offending SELECT
>> select a.account
>> from table1 a
>> where a.doc = '123456A'
>> and (select count(1)
>> from table1 b
>> where a.account = b.account
>> and a.doc = b.doc
>> and a.oseq = b.oseq
>> and a.party = b.party) > 1
>If this worked it wouldreturn multiple rows of the same account number
>How about:
>SELECT a.account
>FROM table1 a
>JOIN table1 b ON a.account = b.account
> and a.doc = b.doc
> and a.oseq = b.oseq
> and a.party = b.party
>WHERE a.doc = '123456A'
>GROUP BY a.account
>HAVING COUNT(*) > 1
>
>> If I do the SELECT with out the sub select it works fine. Suggestions?
>>
>Johnsql

[ODBC SQL Server Driver]Connot generate SSPI Context Anybody ...

We get the following error: Connection Failed:
SQLState: 'HY000' SQL Server Error:
1060 [microsoft][ODBC SQL Server Driver]Connot generate
SSPI Context Anybody ...
client : windows nt4
server : windows 2000 sql server 7.x
but on windows xp it goes very well.
any ideas ?
Check the following Knowledge Base article:
Missing Windows NT LM Security Support Provider registry key
causes "Cannot Generate SSPI Context" error message when you
connect to SQL Server
http://support.microsoft.com/?id=269541
-Sue
On Fri, 2 Apr 2004 08:36:22 -0800, "amichaud"
<anonymous@.discussions.microsoft.com> wrote:

>We get the following error: Connection Failed:
>SQLState: 'HY000' SQL Server Error:
>1060 [microsoft][ODBC SQL Server Driver]Connot generate
>SSPI Context Anybody ...
>client : windows nt4
>server : windows 2000 sql server 7.x
>
>but on windows xp it goes very well.
>any ideas ?

[Microsoft][ODBC Text Driver] In the file specification '...', the Col1 option is invalid.

I'm trying to connect to a tab-delimited text file using the ODBC data access. I set it up using Administrative Tools - Data Sources (ODBC) from the start menu, and clicked the 'Guess' button under Define Format.

The schema it created looks like this:

[cims_output_data.txt]
ColNameHeader=True
Format=TabDelimited
MaxScanRows=0
CharacterSet=OEM
Col1=SIMNAME
Col2=TIMESTAMP
Col3=SIMTYPE
Col4=REGION
Col5=SECTOR
....etc.

It looks OK, but if I go back to Define in Administrative Tools and try to review it, I get a similar error message:

Ini File (or Registry) C:\Program Files\CIMS\schema.ini is corrupt.
Section: cims_output_data.txt, Key: Col1.

Has anyone seen this before? There is nothing on MSDN as far as I could find. I read on another forum that if you replace the label 'Col1' with 'Col' the problem is solved but it still reports that the schema is corrupt when I try to open it in Administrative Tools.

Bill.

Hi Bill,

Could you try specifying the types of your columns in the schema (i.e. Col1=SIMNAME string...)?

I hope this helps,

John Gordon (MSFT)

|||

John

thanks, I tried that. The funny thing is switching the "Col1" label to "Col" really does solve the problem so I am just going with this solution and ignoring the fact that the ODBC configuration editor says the schema is corrupt.

Bill.

[Microsoft][ODBC Text Driver] In the file specification '...', the Col1 option is invalid.

I'm trying to connect to a tab-delimited text file using the ODBC data access. I set it up using Administrative Tools - Data Sources (ODBC) from the start menu, and clicked the 'Guess' button under Define Format.

The schema it created looks like this:

[cims_output_data.txt]
ColNameHeader=True
Format=TabDelimited
MaxScanRows=0
CharacterSet=OEM
Col1=SIMNAME
Col2=TIMESTAMP
Col3=SIMTYPE
Col4=REGION
Col5=SECTOR
....etc.

It looks OK, but if I go back to Define in Administrative Tools and try to review it, I get a similar error message:

Ini File (or Registry) C:\Program Files\CIMS\schema.ini is corrupt.
Section: cims_output_data.txt, Key: Col1.

Has anyone seen this before? There is nothing on MSDN as far as I could find. I read on another forum that if you replace the label 'Col1' with 'Col' the problem is solved but it still reports that the schema is corrupt when I try to open it in Administrative Tools.

Bill.

Hi Bill,

Could you try specifying the types of your columns in the schema (i.e. Col1=SIMNAME string...)?

I hope this helps,

John Gordon (MSFT)

|||

John

thanks, I tried that. The funny thing is switching the "Col1" label to "Col" really does solve the problem so I am just going with this solution and ignoring the fact that the ODBC configuration editor says the schema is corrupt.

Bill.

[Microsoft][ODBC Text Driver] error

Hello,
I am trying to import test file into a SQL Server 2000 database. If I
run the dts package manually I do not receive any errors. However when
I try and attempt to run the same package with dtsrun I receive the
following error.
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled
correctly and that you are connected to the server on which the file
resides
The path of the file is set correctly in the ODBC connection. Any
insight or assistance would be imprecated.
ThanksOn Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> Hello,
> I am trying to import test file into a SQL Server 2000 database. If I
> run the dts package manually I do not receive any errors. However when
> I try and attempt to run the same package with dtsrun I receive the
> following error.
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled
> correctly and that you are connected to the server on which the file
> resides
> The path of the file is set correctly in the ODBC connection. Any
> insight or assistance would be imprecated.
> Thanks
Hi
Are you running DTSRun from a command prompt?
Why are you using a DSN?
Have you tried creating the package using the Import Wizard?
John|||On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
> > Hello,
> > I am trying to import test file into a SQL Server 2000 database. If I
> > run the dts package manually I do not receive any errors. However when
> > I try and attempt to run the same package with dtsrun I receive the
> > following error.
> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > valid path. Make sure that the path name is spelled
> > correctly and that you are connected to the server on which the file
> > resides
> > The path of the file is set correctly in the ODBC connection. Any
> > insight or assistance would be imprecated.
> > Thanks
> Hi
> Are you running DTSRun from a command prompt?
> Why are you using a DSN?
> Have you tried creating the package using the Import Wizard?
> John
I am trying to run the schedule the package from using .xp_cmdshell
and DTSRun , The package will run if execute it from Enterprise Manager|||On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
> > On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > Hello,
> > > I am trying to import test file into a SQL Server 2000 database. If I
> > > run the dts package manually I do not receive any errors. However when
> > > I try and attempt to run the same package with dtsrun I receive the
> > > following error.
> > > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > valid path. Make sure that the path name is spelled
> > > correctly and that you are connected to the server on which the file
> > > resides
> > > The path of the file is set correctly in the ODBC connection. Any
> > > insight or assistance would be imprecated.
> > > Thanks
> > Hi
> > Are you running DTSRun from a command prompt?
> > Why are you using a DSN?
> > Have you tried creating the package using the Import Wizard?
> > John
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> - Show quoted text -
Hi
If you manually run the command from a command prompt does it work?
If xp_cmdshell is running from a job, then make sure service accounts
have access to the directory/file.
John|||On Jun 11, 1:30 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
> > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > > Hello,
> > > > I am trying to import test file into a SQL Server 2000 database. If I
> > > > run the dts package manually I do not receive any errors. However when
> > > > I try and attempt to run the same package with dtsrun I receive the
> > > > following error.
> > > > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > > valid path. Make sure that the path name is spelled
> > > > correctly and that you are connected to the server on which the file
> > > > resides
> > > > The path of the file is set correctly in the ODBC connection. Any
> > > > insight or assistance would be imprecated.
> > > > Thanks
> > > Hi
> > > Are you running DTSRun from a command prompt?
> > > Why are you using a DSN?
> > > Have you tried creating the package using the Import Wizard?
> > > John
> > I am trying to run the schedule the package from using .xp_cmdshell
> > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> > - Show quoted text -
> Hi
> If you manually run the command from a command prompt does it work?
> If xp_cmdshell is running from a job, then make sure service accounts
> have access to the directory/file.
> John
Thanks, If I manually run the command from the command prompt it does
work, however if I try and run using xp_cmdshell I receive the error.
Both SQLAgent and MSSQL services have access to the directory/file|||When you are running it from EM, the package will use your logon to
determine the right and security to access a file but this will not be the
case when running it from a service (xp_cmdshell, DTS_Run or any other
service like SQL-Agent).
Also, if you are not using a UNC pathway but a drive letter (such as C:\);
many of these drive letters will be unknown to system accounts and other
accounts other than your own login. If you have used a driver letter, you
should replace with its full UNC name.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
<mtatlow@.gmail.com> wrote in message
news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>>
>> > Hello,
>> > I am trying to import test file into a SQL Server 2000 database. If I
>> > run the dts package manually I do not receive any errors. However when
>> > I try and attempt to run the same package with dtsrun I receive the
>> > following error.
>> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
>> > valid path. Make sure that the path name is spelled
>> > correctly and that you are connected to the server on which the file
>> > resides
>> > The path of the file is set correctly in the ODBC connection. Any
>> > insight or assistance would be imprecated.
>> > Thanks
>> Hi
>> Are you running DTSRun from a command prompt?
>> Why are you using a DSN?
>> Have you tried creating the package using the Import Wizard?
>> John
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager
>|||On Jun 11, 9:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 11, 1:30 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
> > On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > > On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > > > Hello,
> > > > > I am trying to import test file into a SQL Server 2000 database. If I
> > > > > run the dts package manually I do not receive any errors. However when
> > > > > I try and attempt to run the same package with dtsrun I receive the
> > > > > following error.
> > > > > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > > > valid path. Make sure that the path name is spelled
> > > > > correctly and that you are connected to the server on which the file
> > > > > resides
> > > > > The path of the file is set correctly in the ODBC connection. Any
> > > > > insight or assistance would be imprecated.
> > > > > Thanks
> > > > Hi
> > > > Are you running DTSRun from a command prompt?
> > > > Why are you using a DSN?
> > > > Have you tried creating the package using the Import Wizard?
> > > > John
> > > I am trying to run the schedule the package from using .xp_cmdshell
> > > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> > > - Show quoted text -
> > Hi
> > If you manually run the command from a command prompt does it work?
> > If xp_cmdshell is running from a job, then make sure service accounts
> > have access to the directory/file.
> > John
> Thanks, If I manually run the command from the command prompt it does
> work, however if I try and run using xp_cmdshell I receive the error.
> Both SQLAgent and MSSQL services have access to the directory/file- Hide quoted text -
> - Show quoted text -
Hi
You don't say what the service accounts are. The LOCALSYSTEM will not
have access to network resources, so it would have to be a domain
account. Try logging in as this account and run the package from the
command prompt.
John|||I am using a domain account that has access to the file. I am using
the [ODBC Text Driver] which does not allow you to use a UNC in the
pathway.
On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
blanks, no spam please)> wrote:
> When you are running it from EM, the package will use your logon to
> determine the right and security to access a file but this will not be the
> case when running it from a service (xp_cmdshell, DTS_Run or any other
> service like SQL-Agent).
> Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> many of these drive letters will be unknown to system accounts and other
> accounts other than your own login. If you have used a driver letter, you
> should replace with its full UNC name.
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
> <mtat...@.gmail.com> wrote in message
> news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> >> > Hello,
> >> > I am trying to import test file into a SQL Server 2000 database. If I
> >> > run the dts package manually I do not receive any errors. However when
> >> > I try and attempt to run the same package with dtsrun I receive the
> >> > following error.
> >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> >> > valid path. Make sure that the path name is spelled
> >> > correctly and that you are connected to the server on which the file
> >> > resides
> >> > The path of the file is set correctly in the ODBC connection. Any
> >> > insight or assistance would be imprecated.
> >> > Thanks
> >> Hi
> >> Are you running DTSRun from a command prompt?
> >> Why are you using a DSN?
> >> Have you tried creating the package using the Import Wizard?
> >> John
> > I am trying to run the schedule the package from using .xp_cmdshell
> > and DTSRun , The package will run if execute it from Enterprise Manager|||On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> I am using a domain account that has access to the file. I am using
> the [ODBC Text Driver] which does not allow you to use a UNC in the
> pathway.
> On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> blanks, no spam please)> wrote:
>
> > When you are running it from EM, the package will use your logon to
> > determine the right and security to access a file but this will not be the
> > case when running it from a service (xp_cmdshell, DTS_Run or any other
> > service like SQL-Agent).
> > Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> > many of these drive letters will be unknown to system accounts and other
> > accounts other than your own login. If you have used a driver letter, you
> > should replace with its full UNC name.
> > --
> > Sylvain Lafontaine, ing.
> > MVP - Technologies Virtual-PC
> > E-mail: sylvain aei ca (fill the blanks, no spam please)
> > <mtat...@.gmail.com> wrote in message
> >news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > >> > Hello,
> > >> > I am trying to import test file into a SQL Server 2000 database. If I
> > >> > run the dts package manually I do not receive any errors. However when
> > >> > I try and attempt to run the same package with dtsrun I receive the
> > >> > following error.
> > >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > >> > valid path. Make sure that the path name is spelled
> > >> > correctly and that you are connected to the server on which the file
> > >> > resides
> > >> > The path of the file is set correctly in the ODBC connection. Any
> > >> > insight or assistance would be imprecated.
> > >> > Thanks
> > >> Hi
> > >> Are you running DTSRun from a command prompt?
> > >> Why are you using a DSN?
> > >> Have you tried creating the package using the Import Wizard?
> > >> John
> > > I am trying to run the schedule the package from using .xp_cmdshell
> > > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> - Show quoted text -
Hi
So logging in as this account, you can run the job/package
sucessfully? Have you used the /L command to log output to a file?
John|||On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
> > I am using a domain account that has access to the file. I am using
> > the [ODBC Text Driver] which does not allow you to use a UNC in the
> > pathway.
> > On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> > blanks, no spam please)> wrote:
> > > When you are running it from EM, the package will use your logon to
> > > determine the right and security to access a file but this will not be the
> > > case when running it from a service (xp_cmdshell, DTS_Run or any other
> > > service like SQL-Agent).
> > > Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> > > many of these drive letters will be unknown to system accounts and other
> > > accounts other than your own login. If you have used a driver letter, you
> > > should replace with its full UNC name.
> > > --
> > > Sylvain Lafontaine, ing.
> > > MVP - Technologies Virtual-PC
> > > E-mail: sylvain aei ca (fill the blanks, no spam please)
> > > <mtat...@.gmail.com> wrote in message
> > >news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > >> > Hello,
> > > >> > I am trying to import test file into a SQL Server 2000 database. If I
> > > >> > run the dts package manually I do not receive any errors. However when
> > > >> > I try and attempt to run the same package with dtsrun I receive the
> > > >> > following error.
> > > >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > >> > valid path. Make sure that the path name is spelled
> > > >> > correctly and that you are connected to the server on which the file
> > > >> > resides
> > > >> > The path of the file is set correctly in the ODBC connection. Any
> > > >> > insight or assistance would be imprecated.
> > > >> > Thanks
> > > >> Hi
> > > >> Are you running DTSRun from a command prompt?
> > > >> Why are you using a DSN?
> > > >> Have you tried creating the package using the Import Wizard?
> > > >> John
> > > > I am trying to run the schedule the package from using .xp_cmdshell
> > > > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> > - Show quoted text -
> Hi
> So logging in as this account, you can run the job/package
> sucessfully? Have you used the /L command to log output to a file?
> John
This is the output that I get when I use xp_cmdshell
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSDataPumpTask_1
DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259
(80004005)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
Error Detail Records:
Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
DTSRun: Package execution complete.
NULL
this is the output when I run from the cmd prompt
The execution of the following DTS Package succeeded:
Package Name: test
Package Description: (null)
Package ID: {28220C92-CA63-4664-B356-2155FC002749}
Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
Executed On: SERVERNAME
Executed By: username
Execution Started: 6/12/2007 9:31:01 AM
Execution Completed: 6/12/2007 9:31:01 AM
Total Execution Time: 0.64 seconds
Package Steps execution information:
Step 'DTSStep_DTSDataPumpTask_1' succeeded
Step Execution Started: 6/12/2007 9:31:01 AM
Step Execution Completed: 6/12/2007 9:31:01 AM
Total Step Execution Time: 0.593 seconds
Progress count in Step: 1672
****************************************************************************************************|||On Jun 12, 2:37 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
> > On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > I am using a domain account that has access to the file. I am using
> > > the [ODBC Text Driver] which does not allow you to use a UNC in the
> > > pathway.
> > > On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> > > blanks, no spam please)> wrote:
> > > > When you are running it from EM, the package will use your logon to
> > > > determine the right and security to access a file but this will not= be the
> > > > case when running it from a service (xp_cmdshell, DTS_Run or any ot=her
> > > > service like SQL-Agent).
> > > > Also, if you are not using a UNC pathway but a drive letter (such a=s C:\);
> > > > many of these drive letters will be unknown to system accounts and =other
> > > > accounts other than your own login. If you have used a driver lett=er, you
> > > > should replace with its full UNC name.
> > > > --
> > > > Sylvain Lafontaine, ing.
> > > > MVP - Technologies Virtual-PC
> > > > E-mail: sylvain aei ca (fill the blanks, no spam please)
> > > > <mtat...@.gmail.com> wrote in message
> > > >news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > > > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > > >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrot=e:
> > > > >> > Hello,
> > > > >> > I am trying to import test file into a SQL Server 2000 databas=e=2E If I
> > > > >> > run the dts package manually I do not receive any errors. Howe=ver when
> > > > >> > I try and attempt to run the same package with dtsrun I receiv=e the
> > > > >> > following error.
> > > > >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is no=t a
> > > > >> > valid path. Make sure that the path name is spelled
> > > > >> > correctly and that you are connected to the server on which th=e file
> > > > >> > resides
> > > > >> > The path of the file is set correctly in the ODBC connection. =Any
> > > > >> > insight or assistance would be imprecated.
> > > > >> > Thanks
> > > > >> Hi
> > > > >> Are you running DTSRun from a command prompt?
> > > > >> Why are you using a DSN?
> > > > >> Have you tried creating the package using the Import Wizard?
> > > > >> John
> > > > > I am trying to run the schedule the package from using .xp_cmdsh=ell
> > > > > and DTSRun , The package will run if execute it from Enterprise M=anager- Hide quoted text -
> > > - Show quoted text -
> > Hi
> > So logging in as this account, you can run the job/package
> > sucessfully? Have you used the /L command to log output to a file?
> > John
> This is the output that I get when I use xp_cmdshell
> DTSRun: Loading...
> DTSRun: Executing...
> DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error =3D -2147467259
> (80004005)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> Error Detail Records:
> Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
> DTSRun: Package execution complete.
> NULL
> this is the output when I run from the cmd prompt
> The execution of the following DTS Package succeeded:
> Package Name: test
> Package Description: (null)
> Package ID: {28220C92-CA63-4664-B356-2155FC002749}
> Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
> Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
> Executed On: SERVERNAME
> Executed By: username
> Execution Started: 6/12/2007 9:31:01 AM
> Execution Completed: 6/12/2007 9:31:01 AM
> Total Execution Time: 0.64 seconds
> Package Steps execution information:
> Step 'DTSStep_DTSDataPumpTask_1' succeeded
> Step Execution Started: 6/12/2007 9:31:01 AM
> Step Execution Completed: 6/12/2007 9:31:01 AM
> Total Step Execution Time: 0.593 seconds
> Progress count in Step: 1672
> *************************************************************************=**=AD*************************- Hide quoted text -
> - Show quoted text -
Although you are not using ASP this article gives reasons for this
error number http://support.microsoft.com/kb/306518 especially
http://support.microsoft.com/kb/306269
John

[Microsoft][ODBC Text Driver] error

Hello,
I am trying to import test file into a SQL Server 2000 database. If I
run the dts package manually I do not receive any errors. However when
I try and attempt to run the same package with dtsrun I receive the
following error.
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled
correctly and that you are connected to the server on which the file
resides
The path of the file is set correctly in the ODBC connection. Any
insight or assistance would be imprecated.
Thanks
On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> Hello,
> I am trying to import test file into a SQL Server 2000 database. If I
> run the dts package manually I do not receive any errors. However when
> I try and attempt to run the same package with dtsrun I receive the
> following error.
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled
> correctly and that you are connected to the server on which the file
> resides
> The path of the file is set correctly in the ODBC connection. Any
> insight or assistance would be imprecated.
> Thanks
Hi
Are you running DTSRun from a command prompt?
Why are you using a DSN?
Have you tried creating the package using the Import Wizard?
John
|||On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
>
>
>
> Hi
> Are you running DTSRun from a command prompt?
> Why are you using a DSN?
> Have you tried creating the package using the Import Wizard?
> John
I am trying to run the schedule the package from using .xp_cmdshell
and DTSRun , The package will run if execute it from Enterprise Manager
|||On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> - Show quoted text -
Hi
If you manually run the command from a command prompt does it work?
If xp_cmdshell is running from a job, then make sure service accounts
have access to the directory/file.
John
|||When you are running it from EM, the package will use your logon to
determine the right and security to access a file but this will not be the
case when running it from a service (xp_cmdshell, DTS_Run or any other
service like SQL-Agent).
Also, if you are not using a UNC pathway but a drive letter (such as C:\);
many of these drive letters will be unknown to system accounts and other
accounts other than your own login. If you have used a driver letter, you
should replace with its full UNC name.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
<mtatlow@.gmail.com> wrote in message
news:1181582401.465253.261890@.w5g2000hsg.googlegro ups.com...
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager
>
|||I am using a domain account that has access to the file. I am using
the [ODBC Text Driver] which does not allow you to use a UNC in the
pathway.
On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
blanks, no spam please)> wrote:[vbcol=seagreen]
> When you are running it from EM, the package will use your logon to
> determine the right and security to access a file but this will not be the
> case when running it from a service (xp_cmdshell, DTS_Run or any other
> service like SQL-Agent).
> Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> many of these drive letters will be unknown to system accounts and other
> accounts other than your own login. If you have used a driver letter, you
> should replace with its full UNC name.
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
> <mtat...@.gmail.com> wrote in message
> news:1181582401.465253.261890@.w5g2000hsg.googlegro ups.com...
>
>
>
>
>
>
|||On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> I am using a domain account that has access to the file. I am using
> the [ODBC Text Driver] which does not allow you to use a UNC in the
> pathway.
> On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> blanks, no spam please)> wrote:
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
Hi
So logging in as this account, you can run the job/package
sucessfully? Have you used the /L command to log output to a file?
John
|||On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
> Hi
> So logging in as this account, you can run the job/package
> sucessfully? Have you used the /L command to log output to a file?
> John
This is the output that I get when I use xp_cmdshell
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSDataPumpTask_1
DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259
(80004005)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
Error Detail Records:
Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
DTSRun: Package execution complete.
NULL
this is the output when I run from the cmd prompt
The execution of the following DTS Package succeeded:
Package Name: test
Package Description: (null)
Package ID: {28220C92-CA63-4664-B356-2155FC002749}
Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
Executed On: SERVERNAME
Executed By: username
Execution Started: 6/12/2007 9:31:01 AM
Execution Completed: 6/12/2007 9:31:01 AM
Total Execution Time: 0.64 seconds
Package Steps execution information:
Step 'DTSStep_DTSDataPumpTask_1' succeeded
Step Execution Started: 6/12/2007 9:31:01 AM
Step Execution Completed: 6/12/2007 9:31:01 AM
Total Step Execution Time: 0.593 seconds
Progress count in Step: 1672
************************************************** **************************************************
|||On Jun 12, 2:37 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> This is the output that I get when I use xp_cmdshell
> DTSRun: Loading...
> DTSRun: Executing...
> DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259
> (80004005)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> Error Detail Records:
> Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
> DTSRun: Package execution complete.
> NULL
> this is the output when I run from the cmd prompt
> The execution of the following DTS Package succeeded:
> Package Name: test
> Package Description: (null)
> Package ID: {28220C92-CA63-4664-B356-2155FC002749}
> Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
> Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
> Executed On: SERVERNAME
> Executed By: username
> Execution Started: 6/12/2007 9:31:01 AM
> Execution Completed: 6/12/2007 9:31:01 AM
> Total Execution Time: 0.64 seconds
> Package Steps execution information:
> Step 'DTSStep_DTSDataPumpTask_1' succeeded
> Step Execution Started: 6/12/2007 9:31:01 AM
> Step Execution Completed: 6/12/2007 9:31:01 AM
> Total Step Execution Time: 0.593 seconds
> Progress count in Step: 1672
> ************************************************** *************************X************************ *- Hide quoted text -
> - Show quoted text -
Although you are not using ASP this article gives reasons for this
error number http://support.microsoft.com/kb/306518 especially
http://support.microsoft.com/kb/306269
John

[Microsoft][ODBC SQL Server Driver]Timeout expired"

Could anyone help?
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
Thanks in advance
Please post your connection string.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> Could anyone help?
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> Thanks in advance
|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
"Dan Guzman" wrote:

> Please post your connection string.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
>
>
|||The 'invalid connection string attribute' informational error is due to the
extraneous 'OPEN=ODBC' specification. Try removing it:
DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
I don't know what API you are using but the default command timeout is 30
seconds. In the case of ADO, you can specify a longer interval with the
CommandTimeout command object property. Specify 0 for unlimitted. You
might also consider query/index tuning to speed up the query and also check
for blocking.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...[vbcol=seagreen]
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> "Dan Guzman" wrote:
|||It hs been always working with that string. Anyway, I'm going to try to see
if it works.
Thanks
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>
|||It didn't connect when I remove 'OPEN=ODBC'
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>
|||Try changing the order of the parameters. Normally, the DSN will have a designated DATABASE parameter, although this can be overridden. But how could it be if it hasn't loaded from the DSN yet.
Try 'OPEN=ODBC;DSN=AFM_CALLISTO;DATABASE=AFM_CALLISTO'
Another possibility is that a recent MDAC release or patch has been applied to the client. This has a nasty habit of messing with ODBC. You might want to use the ODBC Administrator and recheck the DSN attributes. When you're done, use the TEST CONNECTION capability to validate the attributes.
Sincerely,
Anthony Thomas

"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
It didn't connect when I remove 'OPEN=ODBC'
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
>
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
>
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
>
> --
> Hope this helps.
>
> Dan Guzman
> SQL Server MVP
>
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>
>|||In my ADO test, ODBC ignored the ODBC attribute in the connection string,
returned an informational message and successfully connected. Without the
attribute, the connection was successful without the message. What API are
you using? Perhaps the ODBC attribute is required by a high-level API that
you are using. I'd expect the API to remove the attribute before passing it
to ODBC, though.
In any case, I suggest you follow the suggestions in my earlier response to
resolve the timeout problem.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>
|||Can I remove the MDAC?
"AnthonyThomas" wrote:

> Try changing the order of the parameters. Normally, the DSN will have a designated DATABASE parameter, although this can be overridden. But how could it be if it hasn't loaded from the DSN yet.
> Try 'OPEN=ODBC;DSN=AFM_CALLISTO;DATABASE=AFM_CALLISTO'
> Another possibility is that a recent MDAC release or patch has been applied to the client. This has a nasty habit of messing with ODBC. You might want to use the ODBC Administrator and recheck the DSN attributes. When you're done, use the TEST CONNEC
TION capability to validate the attributes.[vbcol=seagreen]
> Sincerely,
>
> Anthony Thomas
>
> --
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>
> "Dan Guzman" wrote:

[Microsoft][ODBC SQL Server Driver]Timeout expired"

Could anyone help?
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
Thanks in advancePlease post your connection string.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> Could anyone help?
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> Thanks in advance|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
"Dan Guzman" wrote:
> Please post your connection string.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> > Could anyone help?
> >
> > "Connection failed:
> > SQLState: '01S00'
> > SQL Server Error: 0
> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> > Connection failed:
> > SQLState: 'S1T00'
> > SQL server Error: 0
> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> >
> > Thanks in advance
>
>|||The 'invalid connection string attribute' informational error is due to the
extraneous 'OPEN=ODBC' specification. Try removing it:
DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
I don't know what API you are using but the default command timeout is 30
seconds. In the case of ADO, you can specify a longer interval with the
CommandTimeout command object property. Specify 0 for unlimitted. You
might also consider query/index tuning to speed up the query and also check
for blocking.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> "Dan Guzman" wrote:
>> Please post your connection string.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
>> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
>> > Could anyone help?
>> >
>> > "Connection failed:
>> > SQLState: '01S00'
>> > SQL Server Error: 0
>> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
>> > Connection failed:
>> > SQLState: 'S1T00'
>> > SQL server Error: 0
>> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
>> >
>> > Thanks in advance
>>|||It hs been always working with that string. Anyway, I'm going to try to see
if it works.
Thanks
"Dan Guzman" wrote:
> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> > Here is the connection string:
> >
> > OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> >
> > "Dan Guzman" wrote:
> >
> >> Please post your connection string.
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> >> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> >> > Could anyone help?
> >> >
> >> > "Connection failed:
> >> > SQLState: '01S00'
> >> > SQL Server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> >> > Connection failed:
> >> > SQLState: 'S1T00'
> >> > SQL server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> >> >
> >> > Thanks in advance
> >>
> >>
> >>
>
>|||It didn't connect when I remove 'OPEN=ODBC'
"Dan Guzman" wrote:
> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> > Here is the connection string:
> >
> > OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> >
> > "Dan Guzman" wrote:
> >
> >> Please post your connection string.
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> >> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> >> > Could anyone help?
> >> >
> >> > "Connection failed:
> >> > SQLState: '01S00'
> >> > SQL Server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> >> > Connection failed:
> >> > SQLState: 'S1T00'
> >> > SQL server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> >> >
> >> > Thanks in advance
> >>
> >>
> >>
>
>|||In my ADO test, ODBC ignored the ODBC attribute in the connection string,
returned an informational message and successfully connected. Without the
attribute, the connection was successful without the message. What API are
you using? Perhaps the ODBC attribute is required by a high-level API that
you are using. I'd expect the API to remove the attribute before passing it
to ODBC, though.
In any case, I suggest you follow the suggestions in my earlier response to
resolve the timeout problem.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>|||Can I remove the MDAC?
"AnthonyThomas" wrote:
> Try changing the order of the parameters. Normally, the DSN will have a designated DATABASE parameter, although this can be overridden. But how could it be if it hasn't loaded from the DSN yet.
> Try 'OPEN=ODBC;DSN=AFM_CALLISTO;DATABASE=AFM_CALLISTO'
> Another possibility is that a recent MDAC release or patch has been applied to the client. This has a nasty habit of messing with ODBC. You might want to use the ODBC Administrator and recheck the DSN attributes. When you're done, use the TEST CONNECTION capability to validate the attributes.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>
> "Dan Guzman" wrote:
> > The 'invalid connection string attribute' informational error is due to the
> > extraneous 'OPEN=ODBC' specification. Try removing it:
> >
> > DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> >
> > I don't know what API you are using but the default command timeout is 30
> > seconds. In the case of ADO, you can specify a longer interval with the
> > CommandTimeout command object property. Specify 0 for unlimitted. You
> > might also consider query/index tuning to speed up the query and also check
> > for blocking.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> > news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> > > Here is the connection string:
> > >
> > > OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> > >
> > > "Dan Guzman" wrote:
> > >
> > >> Please post your connection string.
> > >>
> > >> --
> > >> Hope this helps.
> > >>
> > >> Dan Guzman
> > >> SQL Server MVP
> > >>
> > >> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> > >> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> > >> > Could anyone help?
> > >> >
> > >> > "Connection failed:
> > >> > SQLState: '01S00'
> > >> > SQL Server Error: 0
> > >> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> > >> > Connection failed:
> > >> > SQLState: 'S1T00'
> > >> > SQL server Error: 0
> > >> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> > >> >
> > >> > Thanks in advance
> > >>
> > >>
> > >>
> >
> >
> >

[Microsoft][ODBC SQL Server Driver]Timeout expired"

Could anyone help?
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribu
te
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
Thanks in advancePlease post your connection string.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> Could anyone help?
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attri
bute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> Thanks in advance|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_
CALLISTO;
"Dan Guzman" wrote:

> Please post your connection string.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
>
>|||The 'invalid connection string attribute' informational error is due to the
extraneous 'OPEN=ODBC' specification. Try removing it:
DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
I don't know what API you are using but the default command timeout is 30
seconds. In the case of ADO, you can specify a longer interval with the
CommandTimeout command object property. Specify 0 for unlimitted. You
might also consider query/index tuning to speed up the query and also check
for blocking.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...[vbcol=seagreen]
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_
CALLISTO;
> "Dan Guzman" wrote:
>|||It hs been always working with that string. Anyway, I'm going to try to see
if it works.
Thanks
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to th
e
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also chec
k
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>|||It didn't connect when I remove 'OPEN=ODBC'
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to th
e
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also chec
k
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>|||Try changing the order of the parameters. Normally, the DSN will have a des
ignated DATABASE parameter, although this can be overridden. But how could
it be if it hasn't loaded from the DSN yet.
Try 'OPEN=ODBC;DSN=AFM_CALLISTO;DATABASE=AFM
_CALLISTO'
Another possibility is that a recent MDAC release or patch has been applied
to the client. This has a nasty habit of messing with ODBC. You might want
to use the ODBC Administrator and recheck the DSN attributes. When you're
done, use the TEST CONNECTION capability to validate the attributes.
Sincerely,
Anthony Thomas
--
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
It didn't connect when I remove 'OPEN=ODBC'
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to
the
> extraneous 'OPEN=ODBC' specification. Try removing it:
>
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
>
> I don't know what API you are using but the default command timeout is 3
0
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also ch
eck
> for blocking.
>
> --
> Hope this helps.
>
> Dan Guzman
> SQL Server MVP
>
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in messag
e
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>
>|||In my ADO test, ODBC ignored the ODBC attribute in the connection string,
returned an informational message and successfully connected. Without the
attribute, the connection was successful without the message. What API are
you using? Perhaps the ODBC attribute is required by a high-level API that
you are using. I'd expect the API to remove the attribute before passing it
to ODBC, though.
In any case, I suggest you follow the suggestions in my earlier response to
resolve the timeout problem.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>|||Can I remove the MDAC?
"AnthonyThomas" wrote:

> Try changing the order of the parameters. Normally, the DSN will have a d
esignated DATABASE parameter, although this can be overridden. But how coul
d it be if it hasn't loaded from the DSN yet.
> Try 'OPEN=ODBC;DSN=AFM_CALLISTO;DATABASE=AFM
_CALLISTO'
> Another possibility is that a recent MDAC release or patch has been applied to the
client. This has a nasty habit of messing with ODBC. You might want to use the OD
BC Administrator and recheck the DSN attributes. When you're done, use the TEST CON
NEC
TION capability to validate the attributes.[vbcol=seagreen]
> Sincerely,
>
> Anthony Thomas
>
> --
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in messag
e news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>
> "Dan Guzman" wrote:
>

[Microsoft][ODBC SQL Server Driver]Timeout expired

I keep getting the above error when i run a sql from my web page. The query runs fine in enterprise manager. What is worng . Please help.

sql="SELECT top 1 * FROM V_ISSUE WHERE ISSUE_ID=" & issueid & " order by issue_id"

if Session("rs").State = 1 then Session("rs").Close
Session("rs").Open sql,Session("MyConn")Please Try this Code

sql="SELECT top 1 * FROM V_ISSUE WHERE ISSUE_ID=" & issueid & " order by issue_id"

Session("rs").Open sql,Session("MyConn")

Session("rs").close
Set Session("rs")=Nothing

[Microsoft][ODBC SQL Server Driver]Timeout expired

Hi:
I am getting this error when the .asp page tries to connect to the DB server.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent sessions
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.
Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.

[Microsoft][ODBC SQL Server Driver]Timeout expired

Hi all !!
I get the error: "[Microsoft][ODBC SQL Server Driver]Timeout expired
"
when I run a delete statement for a table to delete records which run
into 100s. The SQL is 2000 enterprise edition SP4 on a win 2000 server.
Can the timeout be changed so that the command can go through'
Thanks in advance,
VishalTimeout in this case is a client setting. How you set it depends on what
client you are using. If you are using Query Analyzer, you can go
Tools->Options->Connections, and modify the query time-out there.
Linchi
"bajaj.vishal@.gmail.com" wrote:

> Hi all !!
> I get the error: "[Microsoft][ODBC SQL Server Driver]Timeout expir
ed"
> when I run a delete statement for a table to delete records which run
> into 100s. The SQL is 2000 enterprise edition SP4 on a win 2000 server.
>
> Can the timeout be changed so that the command can go through'
> Thanks in advance,
> Vishal
>

[Microsoft][ODBC SQL Server Driver]Timeout expired

Hi all !!
I get the error: "[Microsoft][ODBC SQL Server Driver]Timeout expired"
when I run a delete statement for a table to delete records which run
into 100s. The SQL is 2000 enterprise edition SP4 on a win 2000 server.
Can the timeout be changed so that the command can go through'
Thanks in advance,
VishalTimeout in this case is a client setting. How you set it depends on what
client you are using. If you are using Query Analyzer, you can go
Tools->Options->Connections, and modify the query time-out there.
Linchi
"bajaj.vishal@.gmail.com" wrote:
> Hi all !!
> I get the error: "[Microsoft][ODBC SQL Server Driver]Timeout expired"
> when I run a delete statement for a table to delete records which run
> into 100s. The SQL is 2000 enterprise edition SP4 on a win 2000 server.
>
> Can the timeout be changed so that the command can go through'
> Thanks in advance,
> Vishal
>

[Microsoft][ODBC SQL Server Driver]Timeout expired

Hi,
[Microsoft][ODBC SQL Server Driver]Timeout expired
I am getting the above error all the time:
In are old verison of the App it is not working.
The query is updating are table that has varchar(8000) columns and text(16)
columns.
Is there anything I can do to make this run faster. If you run the whole
query in SQL Analyzer it runs in milliseconds, but through the ASP pages that
are updating a record it Timeouts. And it is only happening to this one
table, we have other similar tables that have text and large varchars, that
run in are ASP pages just fine.
Thanks,
MattHi
Whist it is running, run sp_who2
Check for blocked processes
Looks like you have processes blocking each other so eventually the query
times out.
Regards
--
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/
"Jaffa" <Jaffa@.discussions.microsoft.com> wrote in message
news:EE8F55E6-C237-4262-920D-B0E889DE29CD@.microsoft.com...
> Hi,
> [Microsoft][ODBC SQL Server Driver]Timeout expired
>
> I am getting the above error all the time:
> In are old verison of the App it is not working.
> The query is updating are table that has varchar(8000) columns and
text(16)
> columns.
> Is there anything I can do to make this run faster. If you run the whole
> query in SQL Analyzer it runs in milliseconds, but through the ASP pages
that
> are updating a record it Timeouts. And it is only happening to this one
> table, we have other similar tables that have text and large varchars,
that
> run in are ASP pages just fine.
> Thanks,
> Matt
>|||Can you post the DDL for the table and exactly how you are updating the row?
--
Andrew J. Kelly SQL MVP
"Jaffa" <Jaffa@.discussions.microsoft.com> wrote in message
news:EE8F55E6-C237-4262-920D-B0E889DE29CD@.microsoft.com...
> Hi,
> [Microsoft][ODBC SQL Server Driver]Timeout expired
>
> I am getting the above error all the time:
> In are old verison of the App it is not working.
> The query is updating are table that has varchar(8000) columns and
> text(16)
> columns.
> Is there anything I can do to make this run faster. If you run the whole
> query in SQL Analyzer it runs in milliseconds, but through the ASP pages
> that
> are updating a record it Timeouts. And it is only happening to this one
> table, we have other similar tables that have text and large varchars,
> that
> run in are ASP pages just fine.
> Thanks,
> Matt
>

[Microsoft][ODBC SQL Server Driver]Timeout expired

Hi,
Our web applications are using COM objects to call sps in
SQL server. We are getting a lot of timeout errors. If
you know why this happens and any fixes pls let me know.
The error looks like following:
[Microsoft][ODBC SQL Server Driver]Timeout expiredhi
I also face to that prob.At last i found the solution for the "timeout
expired" problem. what we
have to do is, we have to edit two windows files calld
,"c:\winnt\system32\drives\ect\hosts.txt"
and "c:\winnt\system32\drives\ect\Lhosts.txt"
we should enter sql server IP and name like this
169.192.2.100 sqlserverName
in both files
Thanks,
indika
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

[Microsoft][ODBC SQL Server Driver]Timeout expired

Hi,
[Microsoft][ODBC SQL Server Driver]Timeout expired
I am getting the above error all the time:
In are old verison of the App it is not working.
The query is updating are table that has varchar(8000) columns and text(16)
columns.
Is there anything I can do to make this run faster. If you run the whole
query in SQL Analyzer it runs in milliseconds, but through the ASP pages that
are updating a record it Timeouts. And it is only happening to this one
table, we have other similar tables that have text and large varchars, that
run in are ASP pages just fine.
Thanks,
Matt
Hi
Whist it is running, run sp_who2
Check for blocked processes
Looks like you have processes blocking each other so eventually the query
times out.
Regards
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/
"Jaffa" <Jaffa@.discussions.microsoft.com> wrote in message
news:EE8F55E6-C237-4262-920D-B0E889DE29CD@.microsoft.com...
> Hi,
> [Microsoft][ODBC SQL Server Driver]Timeout expired
>
> I am getting the above error all the time:
> In are old verison of the App it is not working.
> The query is updating are table that has varchar(8000) columns and
text(16)
> columns.
> Is there anything I can do to make this run faster. If you run the whole
> query in SQL Analyzer it runs in milliseconds, but through the ASP pages
that
> are updating a record it Timeouts. And it is only happening to this one
> table, we have other similar tables that have text and large varchars,
that
> run in are ASP pages just fine.
> Thanks,
> Matt
>
|||Can you post the DDL for the table and exactly how you are updating the row?
Andrew J. Kelly SQL MVP
"Jaffa" <Jaffa@.discussions.microsoft.com> wrote in message
news:EE8F55E6-C237-4262-920D-B0E889DE29CD@.microsoft.com...
> Hi,
> [Microsoft][ODBC SQL Server Driver]Timeout expired
>
> I am getting the above error all the time:
> In are old verison of the App it is not working.
> The query is updating are table that has varchar(8000) columns and
> text(16)
> columns.
> Is there anything I can do to make this run faster. If you run the whole
> query in SQL Analyzer it runs in milliseconds, but through the ASP pages
> that
> are updating a record it Timeouts. And it is only happening to this one
> table, we have other similar tables that have text and large varchars,
> that
> run in are ASP pages just fine.
> Thanks,
> Matt
>

[Microsoft][ODBC SQL Server Driver]Timeout expired

Hi:
I am getting this error when the .asp page tries to connect to the DB server
.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent session
s
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.

[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt?

Our program report the error like this:

[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt.

How does this error happen?

How can I fix it?

We use the SqlServer 2005.

Thanks

This occurs when you issue a new query before you've finished consuming the results from your previous query. Most often people are trying to issue subqueries when a JOIN statement in the original would suffice. Otherwise, you can use a different connection to make the subquery or look into MARS (multiple active result sets) for SQL Server 2005.

I don't think this is SSIS-related and should be moved to a different forum.
|||

I have never used ODBC SQL server driver from within SSIS ; I always use either SQL server ole db or .NET provider SQL client data provider.

have you tried one of these yet?

|||

the operation occours this error is just a [update] sentence.

Does this error can be caused by mutil-thread or other reasons?

Thanks a lot

|||I used vc++ and ADO.|||vc++ and ado , then this is probably not SSIS related, you should look in another forum or newsgroup.

[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt.

Our program report the error like this:

[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt.

I used VC++ and ADO.

How does this error happen?

How can I fix it?

Does this can be caused by mutil-thread?

We use the SqlServer 2005.

Thanks

This is caused by you have a opening result set open against the same connection. For example, you execute a SqlCommand to select all rows from a table, while the result set is not drained, you try to execute another SqlCommand using the same connection, you will hit this error message.

To solve this, you have two choices:

a. Make sure you read the rest data from the pending result set before you send the next SqlCommand.

b. Use MARS (Multiple Active ResultSet) connection setting to enable multiple active result set in a connection. See http://msdn2.microsoft.com/en-us/library/ms345109.aspx

for more details.

Thanks!

Ping

|||

Refer to MARS, http://msdn2.microsoft.com/en-us/library/ms345109.aspx.

It is seems that the SQL SERVER 2005 has already fixed it, isn't it?

Thanks

|||

If I'm reading your error message correctly, the issue is that you're using a pre-SQL 2005 driver. Although the SQL 2005 Server understand MARS, you'll need to use the SQL 2005 driver in order for your application to be able to use it.

You'll need to connect using the "SQL Server Native Client" driver instead of the "SQL Server" driver.

Hope this helps!

~Warren

[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt.

Our program report the error like this:

[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt.

I used VC++ and ADO.

How does this error happen?

How can I fix it?

Does this can be caused by mutil-thread?

We use the SqlServer 2005.

Thanks

This is caused by you have a opening result set open against the same connection. For example, you execute a SqlCommand to select all rows from a table, while the result set is not drained, you try to execute another SqlCommand using the same connection, you will hit this error message.

To solve this, you have two choices:

a. Make sure you read the rest data from the pending result set before you send the next SqlCommand.

b. Use MARS (Multiple Active ResultSet) connection setting to enable multiple active result set in a connection. See http://msdn2.microsoft.com/en-us/library/ms345109.aspx

for more details.

Thanks!

Ping

|||

Refer to MARS, http://msdn2.microsoft.com/en-us/library/ms345109.aspx.

It is seems that the SQL SERVER 2005 has already fixed it, isn't it?

Thanks

|||

If I'm reading your error message correctly, the issue is that you're using a pre-SQL 2005 driver. Although the SQL 2005 Server understand MARS, you'll need to use the SQL 2005 driver in order for your application to be able to use it.

You'll need to connect using the "SQL Server Native Client" driver instead of the "SQL Server" driver.

Hope this helps!

~Warren