Using Execute Process Task to run Access (.mdb) ?

Question

Using Execute Process Task to run Access (.mdb) ?

Esined

SSC Enthusiast

Points: 170
More actions
March 6, 2008 at 7:57 am

#379064

Hi there,
I used to have no errors with my package, but recently my job failed due to a problem with the Execute Process Task which I use to run .mdb application.
The .mdb application DID execute, but the task ended with "The system cannot find the file specified" error message....
Anyone knows what's wrong and how can I rectify?
Thanks!!

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004363 More actions · Answer 1

Perhaps a permissions change on SQL Server or someone removed a "share" from the target drive... or, maybe the file isn't there anymore... or the machine the file is on isn't turned on. Could be any of a dozen more reasons including renaming, etc, etc.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Esined SSC Enthusiast Points: 170 More actions · Answer 2

It'll be wonderful if someone knows why -- If I set WindowStyle property to "Normal", the error will appear. However, once it's set to "Hidden", whalla!!!!

Problem solved (and one day gone spending on this)....

But why????

matzer SSCrazy Eights Points: 9727 More actions · Answer 3

I can't explain the message "The system cannot find the file specified", but if the WindowStyle property solves the problem, I guess there is a relation between this property and the system variable InteractiveMode. This is pure guessing, but if you run your package in BIDS, InteractiveMode will be true, so WindowsStyle will be allowed to be Normal, Maximized, etc. If the package is scheduled to run as a job in SQL Agent, InteractiveMode will be false, and therefor, WindowsStyle must be hidden. But again, pure guessing.

Peter

Matt Miller (4) SSC Guru Points: 124210 More actions · Answer 4

Esined (3/6/2008)
It'll be wonderful if someone knows why -- If I set WindowStyle property to "Normal", the error will appear. However, once it's set to "Hidden", whalla!!!!
Problem solved (and one day gone spending on this)....
But why????

If the job generates an error, then SOME PART of the job (trying to access yet another external file) is failing. Perhaps not the "main" part of the job that you're checking - but the error is still happening. Hidden just means you don't have to see the error.

Try posting exactly what is happening inside of the "access" step. Better yet: run the Access job interactively from the SQL server's console, using the same credentials as those used by the job. When the error happens - hit "debug" and see what command is failing.

----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

Esined SSC Enthusiast Points: 170 More actions · Answer 5

Thank you all for the feedback.

Peter might be right about the InteractiveMode.

I suppose that by setting WindowStyle to "Hidden" allows external process to return a status (ReturnCode) back to SSIS; otherwise, Execute Process Task will timeout and fail...