dbTalk Databases Forums  

Scheduled DTS package fails only when run as a scheduled job

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Scheduled DTS package fails only when run as a scheduled job in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Tyler
 
Posts: n/a

Default Scheduled DTS package fails only when run as a scheduled job - 09-15-2005 , 01:31 PM






I have DTS packages that import data from SQL Anywhere and MS Access. The
ones that import from SQL Anywhere run fine (that was last month's battle).
Only the jobs importing from MS Access are failing with the following message:

Executed as user: FED\service. ...n OnStart: DTSStep_DTSExecuteSQLTask_1
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: Copy Data
from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step DTSRun
OnError: Copy Data from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step, Error =
-2147467259 (80004005) Error string: [Microsoft][ODBC Microsoft Access
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 Microsoft Access Driver] '(unknown)' is not a valid path.
Make sure that the path name is spelled correctly and that you are connect...
Process Exit Code 1. The step failed.



I have read this article: http://support.microsoft.com/?id=269074
Here are the answers to the questions (by section)

Where is the DTS Package Running?
On the server. It was also developed there (using Remote Desktop).

Who Owns the Job That Runs the DTS Package?
FED\SERVICE which is a member of the SYSADMIN group.

How is the DTS Package Launched?
By the Job Scheduler in Enterprise Manager.

Mapped Drives
The package is using a mapped drive. However, I can see the mapped drive
when I open Windows Explorer from the server on which the package runs & the
package still fails.

Relative Path
Same as previous answer.

COM Components in ActiveX Scripts
Not used.

Package Security
None used.

Thanks in advance.
--
Tyler

Reply With Quote
  #2  
Old   
David J. Cartwright
 
Posts: n/a

Default Re: Scheduled DTS package fails only when run as a scheduled job - 09-15-2005 , 01:38 PM






Not sure but the mapped drive may be your problem, the package is being run
in the context of the account for sql server agent, which would not have an
iteractive session, therefore drive would not be mapped ?, can you use UNC
instead.

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote

Quote:
I have DTS packages that import data from SQL Anywhere and MS Access. The
ones that import from SQL Anywhere run fine (that was last month's
battle).
Only the jobs importing from MS Access are failing with the following
message:

Executed as user: FED\service. ...n OnStart: DTSStep_DTSExecuteSQLTask_1
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: Copy Data
from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step DTSRun
OnError: Copy Data from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step, Error =
-2147467259 (80004005) Error string: [Microsoft][ODBC Microsoft
Access
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 Microsoft Access Driver] '(unknown)' is not a valid path.
Make sure that the path name is spelled correctly and that you are
connect...
Process Exit Code 1. The step failed.



I have read this article: http://support.microsoft.com/?id=269074
Here are the answers to the questions (by section)

Where is the DTS Package Running?
On the server. It was also developed there (using Remote Desktop).

Who Owns the Job That Runs the DTS Package?
FED\SERVICE which is a member of the SYSADMIN group.

How is the DTS Package Launched?
By the Job Scheduler in Enterprise Manager.

Mapped Drives
The package is using a mapped drive. However, I can see the mapped drive
when I open Windows Explorer from the server on which the package runs &
the
package still fails.

Relative Path
Same as previous answer.

COM Components in ActiveX Scripts
Not used.

Package Security
None used.

Thanks in advance.
--
Tyler



Reply With Quote
  #3  
Old   
Tyler
 
Posts: n/a

Default Re: Scheduled DTS package fails only when run as a scheduled job - 09-15-2005 , 02:11 PM



I'm not sure if I'm using mapped drives or a UNC.

The DTS package has 2 steps & was created using the Import Wizard.
Step 1 truncates a table on the SQL server. this works when the package is
run manually or by the scheduler.
Step 2 copies a table from a MS Access to SQL Server.
Connection 1 Properties:
Data Source: Microsoft Access
File name: Q:\REHold2005.mdb
Username: Admin
Password: <blank>

I changed the File Name to: \\Backoffice\REShare\REHold2005.mdb

The package succeeds when run manually & fails when run by the job scheduler.

--
Tyler


"David J. Cartwright" wrote:

Quote:
Not sure but the mapped drive may be your problem, the package is being run
in the context of the account for sql server agent, which would not have an
iteractive session, therefore drive would not be mapped ?, can you use UNC
instead.

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote in message
news:E2485A5F-CC58-4DF7-B18A-8DE6354F5A79 (AT) microsoft (DOT) com...
I have DTS packages that import data from SQL Anywhere and MS Access. The
ones that import from SQL Anywhere run fine (that was last month's
battle).
Only the jobs importing from MS Access are failing with the following
message:

Executed as user: FED\service. ...n OnStart: DTSStep_DTSExecuteSQLTask_1
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: Copy Data
from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step DTSRun
OnError: Copy Data from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step, Error =
-2147467259 (80004005) Error string: [Microsoft][ODBC Microsoft
Access
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 Microsoft Access Driver] '(unknown)' is not a valid path.
Make sure that the path name is spelled correctly and that you are
connect...
Process Exit Code 1. The step failed.



I have read this article: http://support.microsoft.com/?id=269074
Here are the answers to the questions (by section)

Where is the DTS Package Running?
On the server. It was also developed there (using Remote Desktop).

Who Owns the Job That Runs the DTS Package?
FED\SERVICE which is a member of the SYSADMIN group.

How is the DTS Package Launched?
By the Job Scheduler in Enterprise Manager.

Mapped Drives
The package is using a mapped drive. However, I can see the mapped drive
when I open Windows Explorer from the server on which the package runs &
the
package still fails.

Relative Path
Same as previous answer.

COM Components in ActiveX Scripts
Not used.

Package Security
None used.

Thanks in advance.
--
Tyler




Reply With Quote
  #4  
Old   
David J. Cartwright
 
Posts: n/a

Default Re: Scheduled DTS package fails only when run as a scheduled job - 09-15-2005 , 02:14 PM



does FED\SERVICE have access to \\Backoffice\REShare\REHold2005.mdb (The
Share and File ???)

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote

Quote:
I'm not sure if I'm using mapped drives or a UNC.

The DTS package has 2 steps & was created using the Import Wizard.
Step 1 truncates a table on the SQL server. this works when the package is
run manually or by the scheduler.
Step 2 copies a table from a MS Access to SQL Server.
Connection 1 Properties:
Data Source: Microsoft Access
File name: Q:\REHold2005.mdb
Username: Admin
Password: <blank

I changed the File Name to: \\Backoffice\REShare\REHold2005.mdb

The package succeeds when run manually & fails when run by the job
scheduler.

--
Tyler


"David J. Cartwright" wrote:

Not sure but the mapped drive may be your problem, the package is being
run
in the context of the account for sql server agent, which would not have
an
iteractive session, therefore drive would not be mapped ?, can you use
UNC
instead.

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote in message
news:E2485A5F-CC58-4DF7-B18A-8DE6354F5A79 (AT) microsoft (DOT) com...
I have DTS packages that import data from SQL Anywhere and MS Access.
The
ones that import from SQL Anywhere run fine (that was last month's
battle).
Only the jobs importing from MS Access are failing with the following
message:

Executed as user: FED\service. ...n OnStart:
DTSStep_DTSExecuteSQLTask_1
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: Copy
Data
from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step DTSRun
OnError: Copy Data from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step, Error =
-2147467259 (80004005) Error string: [Microsoft][ODBC Microsoft
Access
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 Microsoft Access Driver] '(unknown)' is not a valid
path.
Make sure that the path name is spelled correctly and that you are
connect...
Process Exit Code 1. The step failed.



I have read this article: http://support.microsoft.com/?id=269074
Here are the answers to the questions (by section)

Where is the DTS Package Running?
On the server. It was also developed there (using Remote Desktop).

Who Owns the Job That Runs the DTS Package?
FED\SERVICE which is a member of the SYSADMIN group.

How is the DTS Package Launched?
By the Job Scheduler in Enterprise Manager.

Mapped Drives
The package is using a mapped drive. However, I can see the mapped
drive
when I open Windows Explorer from the server on which the package runs
&
the
package still fails.

Relative Path
Same as previous answer.

COM Components in ActiveX Scripts
Not used.

Package Security
None used.

Thanks in advance.
--
Tyler






Reply With Quote
  #5  
Old   
AlexT
 
Posts: n/a

Default Re: Scheduled DTS package fails only when run as a scheduled job - 09-16-2005 , 01:20 AM



FWIW I have a very similar problem, except that I am importing from an
ODBC data source.

The reported error messag eis

Error string: [Microsoft][ODBC Driver Manager] Data source name not
found and no default driver specified Error source: Microsoft OLE
DB Provider fo... Process Exit Code 7. The step failed.

I guess that the problem lies in then context of the account for sql
server agent, but I'm not too sure WHAT to check...

Any help welcome

--alexT


Reply With Quote
  #6  
Old   
Tyler
 
Posts: n/a

Default Re: Scheduled DTS package fails only when run as a scheduled job - 09-16-2005 , 09:21 AM



I think so because FED/SERVICE is in the Sysadmin group.
How can I tell for sure?
--
Tyler


"David J. Cartwright" wrote:

Quote:
does FED\SERVICE have access to \\Backoffice\REShare\REHold2005.mdb (The
Share and File ???)

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote in message
news:0BC906E9-BD01-4AD7-9747-96C799563929 (AT) microsoft (DOT) com...
I'm not sure if I'm using mapped drives or a UNC.

The DTS package has 2 steps & was created using the Import Wizard.
Step 1 truncates a table on the SQL server. this works when the package is
run manually or by the scheduler.
Step 2 copies a table from a MS Access to SQL Server.
Connection 1 Properties:
Data Source: Microsoft Access
File name: Q:\REHold2005.mdb
Username: Admin
Password: <blank

I changed the File Name to: \\Backoffice\REShare\REHold2005.mdb

The package succeeds when run manually & fails when run by the job
scheduler.

--
Tyler


"David J. Cartwright" wrote:

Not sure but the mapped drive may be your problem, the package is being
run
in the context of the account for sql server agent, which would not have
an
iteractive session, therefore drive would not be mapped ?, can you use
UNC
instead.

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote in message
news:E2485A5F-CC58-4DF7-B18A-8DE6354F5A79 (AT) microsoft (DOT) com...
I have DTS packages that import data from SQL Anywhere and MS Access.
The
ones that import from SQL Anywhere run fine (that was last month's
battle).
Only the jobs importing from MS Access are failing with the following
message:

Executed as user: FED\service. ...n OnStart:
DTSStep_DTSExecuteSQLTask_1
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: Copy
Data
from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step DTSRun
OnError: Copy Data from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step, Error =
-2147467259 (80004005) Error string: [Microsoft][ODBC Microsoft
Access
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 Microsoft Access Driver] '(unknown)' is not a valid
path.
Make sure that the path name is spelled correctly and that you are
connect...
Process Exit Code 1. The step failed.



I have read this article: http://support.microsoft.com/?id=269074
Here are the answers to the questions (by section)

Where is the DTS Package Running?
On the server. It was also developed there (using Remote Desktop).

Who Owns the Job That Runs the DTS Package?
FED\SERVICE which is a member of the SYSADMIN group.

How is the DTS Package Launched?
By the Job Scheduler in Enterprise Manager.

Mapped Drives
The package is using a mapped drive. However, I can see the mapped
drive
when I open Windows Explorer from the server on which the package runs
&
the
package still fails.

Relative Path
Same as previous answer.

COM Components in ActiveX Scripts
Not used.

Package Security
None used.

Thanks in advance.
--
Tyler







Reply With Quote
  #7  
Old   
David J. Cartwright
 
Posts: n/a

Default Re: Scheduled DTS package fails only when run as a scheduled job - 09-16-2005 , 09:50 AM



check permisssion on the share and files, log onto computer as FED\SERVICE
then try to access files

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote

Quote:
I think so because FED/SERVICE is in the Sysadmin group.
How can I tell for sure?
--
Tyler


"David J. Cartwright" wrote:

does FED\SERVICE have access to \\Backoffice\REShare\REHold2005.mdb (The
Share and File ???)

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote in message
news:0BC906E9-BD01-4AD7-9747-96C799563929 (AT) microsoft (DOT) com...
I'm not sure if I'm using mapped drives or a UNC.

The DTS package has 2 steps & was created using the Import Wizard.
Step 1 truncates a table on the SQL server. this works when the package
is
run manually or by the scheduler.
Step 2 copies a table from a MS Access to SQL Server.
Connection 1 Properties:
Data Source: Microsoft Access
File name: Q:\REHold2005.mdb
Username: Admin
Password: <blank

I changed the File Name to: \\Backoffice\REShare\REHold2005.mdb

The package succeeds when run manually & fails when run by the job
scheduler.

--
Tyler


"David J. Cartwright" wrote:

Not sure but the mapped drive may be your problem, the package is
being
run
in the context of the account for sql server agent, which would not
have
an
iteractive session, therefore drive would not be mapped ?, can you use
UNC
instead.

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote in message
news:E2485A5F-CC58-4DF7-B18A-8DE6354F5A79 (AT) microsoft (DOT) com...
I have DTS packages that import data from SQL Anywhere and MS Access.
The
ones that import from SQL Anywhere run fine (that was last month's
battle).
Only the jobs importing from MS Access are failing with the
following
message:

Executed as user: FED\service. ...n OnStart:
DTSStep_DTSExecuteSQLTask_1
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart:
Copy
Data
from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step
DTSRun
OnError: Copy Data from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step,
Error =
-2147467259 (80004005) Error string: [Microsoft][ODBC
Microsoft
Access
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 Microsoft Access Driver] '(unknown)' is not a valid
path.
Make sure that the path name is spelled correctly and that you are
connect...
Process Exit Code 1. The step failed.



I have read this article: http://support.microsoft.com/?id=269074
Here are the answers to the questions (by section)

Where is the DTS Package Running?
On the server. It was also developed there (using Remote Desktop).

Who Owns the Job That Runs the DTS Package?
FED\SERVICE which is a member of the SYSADMIN group.

How is the DTS Package Launched?
By the Job Scheduler in Enterprise Manager.

Mapped Drives
The package is using a mapped drive. However, I can see the mapped
drive
when I open Windows Explorer from the server on which the package
runs
&
the
package still fails.

Relative Path
Same as previous answer.

COM Components in ActiveX Scripts
Not used.

Package Security
None used.

Thanks in advance.
--
Tyler









Reply With Quote
  #8  
Old   
Tyler
 
Posts: n/a

Default Re: Scheduled DTS package fails only when run as a scheduled job - 11-29-2005 , 02:34 PM



To revive this thread (because the scheduled job still fails), when I logon
as FED\SERVICE I can access the files.

--
Tyler


"David J. Cartwright" wrote:

Quote:
check permisssion on the share and files, log onto computer as FED\SERVICE
then try to access files

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote in message
news:FF31F691-6498-47BA-A27A-97523EE58AA8 (AT) microsoft (DOT) com...
I think so because FED/SERVICE is in the Sysadmin group.
How can I tell for sure?
--
Tyler


"David J. Cartwright" wrote:

does FED\SERVICE have access to \\Backoffice\REShare\REHold2005.mdb (The
Share and File ???)

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote in message
news:0BC906E9-BD01-4AD7-9747-96C799563929 (AT) microsoft (DOT) com...
I'm not sure if I'm using mapped drives or a UNC.

The DTS package has 2 steps & was created using the Import Wizard.
Step 1 truncates a table on the SQL server. this works when the package
is
run manually or by the scheduler.
Step 2 copies a table from a MS Access to SQL Server.
Connection 1 Properties:
Data Source: Microsoft Access
File name: Q:\REHold2005.mdb
Username: Admin
Password: <blank

I changed the File Name to: \\Backoffice\REShare\REHold2005.mdb

The package succeeds when run manually & fails when run by the job
scheduler.

--
Tyler


"David J. Cartwright" wrote:

Not sure but the mapped drive may be your problem, the package is
being
run
in the context of the account for sql server agent, which would not
have
an
iteractive session, therefore drive would not be mapped ?, can you use
UNC
instead.

"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote in message
news:E2485A5F-CC58-4DF7-B18A-8DE6354F5A79 (AT) microsoft (DOT) com...
I have DTS packages that import data from SQL Anywhere and MS Access.
The
ones that import from SQL Anywhere run fine (that was last month's
battle).
Only the jobs importing from MS Access are failing with the
following
message:

Executed as user: FED\service. ...n OnStart:
DTSStep_DTSExecuteSQLTask_1
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart:
Copy
Data
from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step
DTSRun
OnError: Copy Data from JJ_ConsWPayRestrDetail to
[ThankYouAcknowledgements].[dbo].[JJ_ConsWPayRestrDetail] Step,
Error =
-2147467259 (80004005) Error string: [Microsoft][ODBC
Microsoft
Access
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 Microsoft Access Driver] '(unknown)' is not a valid
path.
Make sure that the path name is spelled correctly and that you are
connect...
Process Exit Code 1. The step failed.



I have read this article: http://support.microsoft.com/?id=269074
Here are the answers to the questions (by section)

Where is the DTS Package Running?
On the server. It was also developed there (using Remote Desktop).

Who Owns the Job That Runs the DTS Package?
FED\SERVICE which is a member of the SYSADMIN group.

How is the DTS Package Launched?
By the Job Scheduler in Enterprise Manager.

Mapped Drives
The package is using a mapped drive. However, I can see the mapped
drive
when I open Windows Explorer from the server on which the package
runs
&
the
package still fails.

Relative Path
Same as previous answer.

COM Components in ActiveX Scripts
Not used.

Package Security
None used.

Thanks in advance.
--
Tyler










Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.