Essentially I have a job which runs in BIDS and as as a stand lone package and while it runs under the SQL Server Agent it doesn't complete properly (no error messages though).

The job steps are:

1) Delete all rows from table;

2) Use For each loop to fill up table from Excel spreasheets;

3) Clean up table.

I've tried this MS page (steps 1 & 2), didn't see any need to start changing from Server side security.

Also SQLServerCentral.com for this page, no resolution.

How can I get error logging or a fix?

I have logged in as the proxy account I'm running this under, and the job runs stand alone but complains that the Excel tables are empty?

  • I believe there is a logging mode property that you enable in your package in order to have SSIS log output. In the SQL Agent job, edit your job step where the package is specified and use the Advanced selection on the left to specify an output file (won't be especially useful for troubleshooting). – jl. Apr 21 '10 at 15:18
  • Thanks, I have enabled this but as it thinks there are no errors I'm not getting anything useful out of it. – alimack Apr 21 '10 at 15:24
  • If packaging logging doesn't do it, I'm not sure what will. – jl. Apr 21 '10 at 16:46

I did fix this eventually, thanks for the suggestions.

Basically I logged in with the proxy user account I was running and started to see errors like: "The For each file enumerator is empty"

I copied the project files across, and it turned out that I'd still left a file path (N:/) in the properties of the For Each loop box, although I'd changed the connection properties. I also had to recreate the variable mapping to get it working.

No wonder people just recreate the whole package(!)

Now fixed and working.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.