How do you track done an error that is not defined..

We have SQL Server & Integrations Services 2005.
OK.. I have been doing a few successful SSIS packages this way. I put out a flat file to a directory folder the Server has access to.

Just built a new one. I ran if from BIDS it works fine. I moved the package to the IS on the Server & created a job agent to run it. It blew up with this very helpful error..

Run SSIS Package through Job Agent..
The job failed.  The Job was invoked by User UNIONLEADER\wstephens.  The last step to run was step 1 (testprocess).

So I tried running the package stand-alone. it give the error ..

Error: SSIS Error Code DTS_E_ProductLevelToLow. The product level is insufficient to component 'Flat File Destination"

So I took a similar package that runs fine in the job agent. I ran the package stand-alone.. I get similar errors about product level is insufficient..  I run the normal job.. works fine.

I take the package to the bids program do minor changes upload works fine.. I take the package and rename it, and do major changes to remove all but the flat file move, but leave where it is moving it to, and all file connections alone.. Set it up to run in the job agent. I get the original error of the job agent.. "Job failed"

At this point I do not know what to try, or why I get this. A co-worker thinks an upgrade may be leaving the old packages working fine, but now not allowing us the same priviledge we had on any new packages we build.. If so this will be a major melt down, and why are they taking away functionality from their old Servers???
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Anthony PerkinsCommented:
It sounds like the startup account for the SQL Server Agent service is set to a Local System account or does not have the required permissions.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Alpha AuCommented:
i've encounter similar error message yesterday,

does your sql server installed with Integration Service??

please refer to this:
moosetrackerAuthor Commented:
is that what this error that says nothing more then "It Failed" means? It is not even getting in to run the first step out of the package?..

The Integration service is set up and is currently running several jobs of SSIS packages daily and has been doing so for about a year now..

I created a test package about a week back that didn't push out a flat file to a path folder, but was used to test something else. That was successful. I don't think I am doing anything different in my setup..

But it gives me one more idea to try tommorrow. I will simply create a new job in the job agent to run the one program that has similar features yet runs successfully..  I only did that with the package after I renamed it, and wittled out all the code except for the push of the data out to a folder outside the database..  I am curious to see if the unmodified package will work under a new job setup or not..

Thanks, I will let you know tommorrow.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Alpha AuCommented:
for your information, the error message i encountered yesterday is :
The task cannot run on this edition of Integration Services. It requires a higher level edition

not sure is that the one you encounter.
Reza RadConsultant, TrainerCommented:
What is your protection Level?
try with SaveSensitiveWithPassword, and set a password, and in the job set password to run the package.
this is good picture tutorial about how do deploy your package with SaveSensitiveWithPassword protectionlevel and run it as sql server job:
moosetrackerAuthor Commented:
OK.. I am closing this up and awarding all three of you some of the points..

I am not going to add this to the Knowledge Base as the whole thing was very, very dumb on my part..

I have done multi Job Agent setups but I guess the majority have been with combining multiple SSIS packages into the Job Agent.  I knew on an error for those to open the History tab up, look for the package with the error and then read the error..

For some reason the single package in the Job thru me.. I was only looking at the head process in the history and not opening up and reading the specific package detail..  The generic "Package Failed" was because I was at the main level !!!

Once I could read the error, it became a simple issue of the fact the proxy only gave the directory I was trying to wright to, read priviledges..

Duh! Duh! and Double Duh!!! How long did I waste my time with this?  Way.. Way.. too long..
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.