[SQL-DMO]The name tdb_grabowy1 was not found in the Databases collection.

We need to copy about 25 databases whenever we get a new software
delivery. Currently, the process is to manually use the DTS database
copy wizard.

Doing some research, I created a DTS package to copy databases. But
this was not going to work since I have to hard code the database
names in the package. Back to RTFMing, I discovered the Dynamic
Properties Task. So now I setup a .bat file that calls dtsrun and via
global variables passes in the source and target database names to the
copy db DS package.

I did a simple test against a test database that I have and it worked.
But when I tried it against some "real" databases I get the following
errors. I have searched and googled but I have not found anything.
Help?

DTSRun OnError: Copy SQL Server Objects, Error = -2147199728
(80045510)
Error string: [SQL-DMO]The name 'tdb_grabowy1' was not found in the
Databases collection. If the name is a qualified name, use [] to
separate various parts of the name, and try again.
Error source: Microsoft SQL-DMO
Help file: SQLDMO80.hlp
Help context: 1131Hi

It is not clear why you need to update the data in a table if there is a
software delivery, normally I would expect scripts to make any of the
necessary changes, or if data is being imported then each database would
contain (common) code that would be able to do the import.

The error is reasonably self explaining. You are trying to use
'tdb_grabowy1' which either does not exists or you possibly don't have
permissions to use. If the database does exist try run the process just for
the one database on it's own.

If you process drops the database and then re-creates it, you could do this
task by restoring the database or copying the data and log files and then
attaching them.

John

"CxG" <chris.grabowy@.lmco.com> wrote in message
news:35c4f452.0409090837.77ca8573@.posting.google.c om...
> We need to copy about 25 databases whenever we get a new software
> delivery. Currently, the process is to manually use the DTS database
> copy wizard.
> Doing some research, I created a DTS package to copy databases. But
> this was not going to work since I have to hard code the database
> names in the package. Back to RTFMing, I discovered the Dynamic
> Properties Task. So now I setup a .bat file that calls dtsrun and via
> global variables passes in the source and target database names to the
> copy db DS package.
> I did a simple test against a test database that I have and it worked.
> But when I tried it against some "real" databases I get the following
> errors. I have searched and googled but I have not found anything.
> Help?
> DTSRun OnError: Copy SQL Server Objects, Error = -2147199728
> (80045510)
> Error string: [SQL-DMO]The name 'tdb_grabowy1' was not found in the
> Databases collection. If the name is a qualified name, use [] to
> separate various parts of the name, and try again.
> Error source: Microsoft SQL-DMO
> Help file: SQLDMO80.hlp
> Help context: 1131|||> It is not clear why you need to update the data in a table if there is a
> software delivery, normally I would expect scripts to make any of the
> necessary changes, or if data is being imported then each database would
> contain (common) code that would be able to do the import.

We are in development and when we get a new copy of the COTS products
then we make copies of the existing baseline databases to new baseline
copies. That way development, debugging, prod support can continue in
the previous baseline, until we get prod up and running on the new
baseline.

> The error is reasonably self explaining. You are trying to use
> 'tdb_grabowy1' which either does not exists or you possibly don't have
> permissions to use. If the database does exist try run the process just for
> the one database on it's own.

I am using a DTS package that copies databases. Its a simple package
that executes the Copy SQL Server Objects Task. Normally, it would be
hardcoded to copy a specific source database to a specific target
database, but I am using a Dynamic Properties Task to modify the
package attributes to allow me to specify a source/target database
name upon execution of the DTS package. tdb_grabowy is my play/test
database. I am attempting to copy it to tdb_grabowy1.

It is getting the noted error message in the middle of the execution
of the package.

[newbe] SQL number of querries / connections limits ?

Hi all!
Can you tell me if there are any default or manually set limits of
subsequent querries / connections per user or database? I couldnt find
any in Enterprise Manager, but my Perl / ASP aplications seems to behave
as if it were some.
Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
2000 - 3000 per hour). After doing a couple of thosands it sudenly stops
- querry is sent but no result returns. If I limit the numer of being
sent per minute - the program seems to work propotionally longer, but
finally 'hangs' in the very same well.
Moreover, ASP IIS based cooperating aplication seems to reach the same
limit - after some time querries (actually doing SELECTS on data
previously INSERTED by Perl script) are processed longer than ASP
timeout allows, well the actually hangs, Profiler shows some crazy
processing times. If I reduce the number of queries per transaction -
namely changing a subquerry to join construction - it works ok. It all
makes me think I hit some limits.
I've searched the WEB archives (my MS coleeges' knowledge as well )
but couldn't find much - does any body knows sth about it?
pk
There is no hard limit on the number of connections you can have to a SQL
Server. But every connection takes up about 40KB of server memory, so there
are definitely practical limitations. Make sure that all your code drops the
connections to the server that are no longer needed.
Jacco Schalkwijk
SQL Server MVP
"Piotr Kowalski" <wywaltopkwlski@.oitotez2.pl> wrote in message
news:ctl2ea$oa9$1@.atlantis.news.tpi.pl...
> Hi all!
> Can you tell me if there are any default or manually set limits of
> subsequent querries / connections per user or database? I couldnt find any
> in Enterprise Manager, but my Perl / ASP aplications seems to behave as if
> it were some.
> Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
> 2000 - 3000 per hour). After doing a couple of thosands it sudenly stops -
> querry is sent but no result returns. If I limit the numer of being sent
> per minute - the program seems to work propotionally longer, but finally
> 'hangs' in the very same well.
> Moreover, ASP IIS based cooperating aplication seems to reach the same
> limit - after some time querries (actually doing SELECTS on data
> previously INSERTED by Perl script) are processed longer than ASP timeout
> allows, well the actually hangs, Profiler shows some crazy processing
> times. If I reduce the number of queries per transaction - namely changing
> a subquerry to join construction - it works ok. It all makes me think I
> hit some limits.
> I've searched the WEB archives (my MS coleeges' knowledge as well ) but
> couldn't find much - does any body knows sth about it?
> pk
|||Jacco Schalkwijk wrote:
> There is no hard limit on the number of connections you can have to a SQL
> Server. But every connection takes up about 40KB of server memory, so there
> are definitely practical limitations. Make sure that all your code drops the
> connections to the server that are no longer needed.
>
yeah, I've considered that.
Sybase DBI library unfortunately uses new connection every query, but
neither client's nor server's network stack reports other TCP
connections than being actually used (some 3 connection in every moment)
so older ones are properly disconnected. Maybe some "residues" still
remains on the SQL box, on the aplication layer, which aren't counted by
netstat but still reserve some resources (RAM). Enterprise manager shows
only as many proceses as really exists (3).
What about query limit? Or other limits that could come in question in
this case?
hk

[newbe] SQL number of querries / connections limits ?

Hi all!
Can you tell me if there are any default or manually set limits of
subsequent querries / connections per user or database? I couldnt find
any in Enterprise Manager, but my Perl / ASP aplications seems to behave
as if it were some.
Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
2000 - 3000 per hour). After doing a couple of thosands it sudenly stops
- querry is sent but no result returns. If I limit the numer of being
sent per minute - the program seems to work propotionally longer, but
finally 'hangs' in the very same well.
Moreover, ASP IIS based cooperating aplication seems to reach the same
limit - after some time querries (actually doing SELECTS on data
previously INSERTED by Perl script) are processed longer than ASP
timeout allows, well the actually hangs, Profiler shows some crazy
processing times. If I reduce the number of queries per transaction -
namely changing a subquerry to join construction - it works ok. It all
makes me think I hit some limits.
I've searched the WEB archives (my MS coleeges' knowledge as well :))
but couldn't find much - does any body knows sth about it?
pkThere is no hard limit on the number of connections you can have to a SQL
Server. But every connection takes up about 40KB of server memory, so there
are definitely practical limitations. Make sure that all your code drops the
connections to the server that are no longer needed.
--
Jacco Schalkwijk
SQL Server MVP
"Piotr Kowalski" <wywaltopkwlski@.oitotez2.pl> wrote in message
news:ctl2ea$oa9$1@.atlantis.news.tpi.pl...
> Hi all!
> Can you tell me if there are any default or manually set limits of
> subsequent querries / connections per user or database? I couldnt find any
> in Enterprise Manager, but my Perl / ASP aplications seems to behave as if
> it were some.
> Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
> 2000 - 3000 per hour). After doing a couple of thosands it sudenly stops -
> querry is sent but no result returns. If I limit the numer of being sent
> per minute - the program seems to work propotionally longer, but finally
> 'hangs' in the very same well.
> Moreover, ASP IIS based cooperating aplication seems to reach the same
> limit - after some time querries (actually doing SELECTS on data
> previously INSERTED by Perl script) are processed longer than ASP timeout
> allows, well the actually hangs, Profiler shows some crazy processing
> times. If I reduce the number of queries per transaction - namely changing
> a subquerry to join construction - it works ok. It all makes me think I
> hit some limits.
> I've searched the WEB archives (my MS coleeges' knowledge as well :)) but
> couldn't find much - does any body knows sth about it?
> pk|||Jacco Schalkwijk wrote:
> There is no hard limit on the number of connections you can have to a SQL
> Server. But every connection takes up about 40KB of server memory, so there
> are definitely practical limitations. Make sure that all your code drops the
> connections to the server that are no longer needed.
>
yeah, I've considered that.
Sybase DBI library unfortunately uses new connection every query, but
neither client's nor server's network stack reports other TCP
connections than being actually used (some 3 connection in every moment)
so older ones are properly disconnected. Maybe some "residues" still
remains on the SQL box, on the aplication layer, which aren't counted by
netstat but still reserve some resources (RAM). Enterprise manager shows
only as many proceses as really exists (3).
What about query limit? Or other limits that could come in question in
this case?
hk

[newbe] SQL number of querries / connections limits ?

Hi all!
Can you tell me if there are any default or manually set limits of
subsequent querries / connections per user or database? I couldnt find
any in Enterprise Manager, but my PERL / ASP aplications seems to behave
as if it were some.
Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
2000 - 3000 per hour). After doing a couple of thosands it sudenly stops
- querry is sent but no result returns. If I limit the numer of being
sent per minute - the program seems to work propotionally longer, but
finally 'hangs' in the very same well.
Moreover, ASP IIS based cooperating aplication seems to reach the same
limit - after some time querries (actually doing SELECTS on data
previously INSERTED by PERL script) are processed longer than ASP
timeout allows, well the actually hangs, Profiler shows some crazy
processing times. If I reduce the number of queries per transaction -
namely changing a subquerry to join construction - it works ok. It all
makes me think I hit some limits.
I've searched the WEB archives (my MS coleeges' knowledge as well )
but couldn't find much - does any body knows sth about it?
pkThere is no hard limit on the number of connections you can have to a SQL
Server. But every connection takes up about 40KB of server memory, so there
are definitely practical limitations. Make sure that all your code drops the
connections to the server that are no longer needed.
Jacco Schalkwijk
SQL Server MVP
"Piotr Kowalski" <wywaltopkwlski@.oitotez2.pl> wrote in message
news:ctl2ea$oa9$1@.atlantis.news.tpi.pl...
> Hi all!
> Can you tell me if there are any default or manually set limits of
> subsequent querries / connections per user or database? I couldnt find any
> in Enterprise Manager, but my PERL / ASP aplications seems to behave as if
> it were some.
> PERL script (DBI + Sybase DBD) is doing some quite massive inserts (a
> 2000 - 3000 per hour). After doing a couple of thosands it sudenly stops -
> querry is sent but no result returns. If I limit the numer of being sent
> per minute - the program seems to work propotionally longer, but finally
> 'hangs' in the very same well.
> Moreover, ASP IIS based cooperating aplication seems to reach the same
> limit - after some time querries (actually doing SELECTS on data
> previously INSERTED by PERL script) are processed longer than ASP timeout
> allows, well the actually hangs, Profiler shows some crazy processing
> times. If I reduce the number of queries per transaction - namely changing
> a subquerry to join construction - it works ok. It all makes me think I
> hit some limits.
> I've searched the WEB archives (my MS coleeges' knowledge as well ) but
> couldn't find much - does any body knows sth about it?
> pk|||Jacco Schalkwijk wrote:
> There is no hard limit on the number of connections you can have to a SQL
> Server. But every connection takes up about 40KB of server memory, so ther
e
> are definitely practical limitations. Make sure that all your code drops t
he
> connections to the server that are no longer needed.
>
yeah, I've considered that.
Sybase DBI library unfortunately uses new connection every query, but
neither client's nor server's network stack reports other TCP
connections than being actually used (some 3 connection in every moment)
so older ones are properly disconnected. Maybe some "residues" still
remains on the SQL box, on the aplication layer, which aren't counted by
netstat but still reserve some resources (RAM). Enterprise manager shows
only as many proceses as really exists (3).
What about query limit? Or other limits that could come in question in
this case?
hk

[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