Lloyd thank you for answering.

Can you please be more specific. I have built other packages (insert from excel to tables and that stuff) and they all work when scheduled through SQL 2005. This specific package was built (creator) from another person of the domain group. I have changed this in the properties of the package however. My problem is, that no matter what i do, and no matter what option i set to data (encrypt sensitive with user key, dont save anything, etc) or regardless if on my data sources are sa, or windows authentication, the packages do execute from visual studio and commandline, but not through sql server agent. With the same package creator (VS 2005), and with the same owner (sql 2005) of the package, other packages run, but this one does not.

I reckon it is a user right thing as you say, but the owner of the package is a sys admin just like the sqlserver agent.

I have run out of ideas... can you read the message that i have posted and try to figure it out? Why is so difficult to schedule a package? ^#$$#% Microsoft!!!

So please help me a bit more if you can, and tell me what exactly you suggest...

I would be gratefull if you could provide me some more info...

Kind Regards,

Dionisis