error to executing job on Sql Server Enterprise Manager

[Maurizio Amoroso]

.... DTSRun: Executing... DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_2 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnError:
DTSStep_DTSDataPumpTask_2, Error = -2147467259 (80004005) Error
string: [Microsoft][ODBC Visual FoxPro Driver]Cannot open file
e:\private.dbc. Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0 Error Detail
Records: Error: -2147467259 (80004005); Provider Error: 171
(AB) Error string: [Microsoft][ODBC Visual FoxPro Driver]Cannot
open file e:\private.dbc. Error source: Microsoft OLE DB
Provider for ODBC Drivers Help file: Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnError: DTS... Process Exit Code
4. The step failed.

anyone know becaouse if i execute this job whit the Schedule package
dont work but i execute manually it's work ?

pls help me ...

[Harold Helmich]

Initial guess would be that the account that is used for running SQL
Agent can not see e:\private.dbc... Double check what user account is
being used to run SQL Server service versus SQL Agent service and double
check permissions on the directory. Also, test what user accounts can
run the DTS package from Ent Man. It may be that the system or service
account can not run the scheduled job because service account does not
have access where as your account does via Ent Man.

Maurizio Amoroso wrote:

... DTSRun: Executing... DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_2 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnError:
DTSStep_DTSDataPumpTask_2, Error = -2147467259 (80004005) Error
string: [Microsoft][ODBC Visual FoxPro Driver]Cannot open file
e:\private.dbc. Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0 Error Detail
Records: Error: -2147467259 (80004005); Provider Error: 171
(AB) Error string: [Microsoft][ODBC Visual FoxPro Driver]Cannot
open file e:\private.dbc. Error source: Microsoft OLE DB
Provider for ODBC Drivers Help file: Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnError: DTS... Process Exit Code
4. The step failed.

anyone know becaouse if i execute this job whit the Schedule package
dont work but i execute manually it's work ?

pls help me ...

[Simon Hayes]

"Maurizio Amoroso" <ma**************@mlink.it> wrote in message
news:93**************************@posting.google.c om...

... DTSRun: Executing... DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_2 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnError:
DTSStep_DTSDataPumpTask_2, Error = -2147467259 (80004005) Error
string: [Microsoft][ODBC Visual FoxPro Driver]Cannot open file
e:\private.dbc. Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0 Error Detail
Records: Error: -2147467259 (80004005); Provider Error: 171
(AB) Error string: [Microsoft][ODBC Visual FoxPro Driver]Cannot
open file e:\private.dbc. Error source: Microsoft OLE DB
Provider for ODBC Drivers Help file: Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnError: DTS... Process Exit Code
4. The step failed.

anyone know becaouse if i execute this job whit the Schedule package
dont work but i execute manually it's work ?

pls help me ...

Check out this KB article:

http://support.microsoft.com/default...&Product=sql2k

The account running the job probably doesn't have access to E:\ (NTFS
permissions, unknown drive mapping), and the article explains quite well how
to work out what context the job is running in.

Simon