question

CHENGLUNWU-2436 avatar image
0 Votes"
CHENGLUNWU-2436 asked JeffreyWilliams-3310 commented

SQL Server Agent Failed to execute job

Every SQL Server experts~I have a problem

I want to use SQL Server Agent to excute job&schedule in SSMS,But appeared a mistake:

Executed as user: NT Service\SQLSERVERAGENT. The process could not be created for step 1 of job 0xF6FCB18EFC96C348BB90BE7CED29B30D (reason: The system cannot find the file specified). The step failed.

My job is to read the package on my file,and my SQL Server is connect to vpn and then connect to SQL ,not use Local SQL.

Similar problems on the Internet can't solve it. have any suggestions or way?~thanks!

sql-server-general
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I think you need to give us more details. What type of job step is this? Can you show us the definition of the job step?

I don't understand what VPN has to do with this. Agent runs on the same machine as SQL Server. Or is the file which the job is trying to access on a remote machine with a VPN connection?

0 Votes 0 ·

The Type I use SQL SERVER Integration Service Package,and Executive identity is SQL Server Agent Service
Acount

and my package is on local,so path like this:
C:\Users\Infofab-S508\source\repos\Integration Services Project1\Integration Services
Project1\SAPERP_EXTRACTION_SQLSTG_20210604.dtsx.


If I set job&schedule in my local SQL SERVER Agent can success,but use there SQL Server Agent is failed.



.

0 Votes 0 ·

You appear to be trying to execute the project/package from within the VS path. That is not the appropriate way to deploy SSIS packages. You need to deploy the package to an Integration Services Catalog - preferably one that has been set up on your remote SQL instance.

Once it has been deployed you can then schedule it using SQL Server Agent on the remote system.

0 Votes 0 ·
HafeezUddin-8965 avatar image
0 Votes"
HafeezUddin-8965 answered

May be it is permission issue.
Login to the SQL Server using SQL Agent account and see if you run the package manually.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ErlandSommarskog avatar image
0 Votes"
ErlandSommarskog answered Cathyji-msft edited

and my package is on local,so path like this:

C:\Users\Infofab-S508\source\repos\Integration Services Project1\Integration Services
Project1\SAPERP_EXTRACTION_SQLSTG_20210604.dtsx.

By "local", you mean your local machine?

That is not going to work out. C:\ for SQL Server Agent is C:\ on the SQL Server machine. Agent has no knowledge about your local disk.

You need to copy your package to the SQL Server machine.
· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for reply,local is mean my machine,so package is on my C disk.
So If I connect to other people SQL Server in SSMS,then SQL Server Agent can't read my package and set up
job?

0 Votes 0 ·

Correct. SQL Server, including Agent, lives on its own machine, with its own C: drive.

0 Votes 0 ·

OK~thanks ,I research it for many days

0 Votes 0 ·
Show more comments