Thanks but this is the process that i used when i set up the linked server user mapping in the first place; the problem is that if i now test...

Thanks for the response.

No the login account on the local server is mapped to a login account with a different name on the remote server.

That's great, thanks very much for your help. I had looked online but my google searches must have been too vague to point me to the relevent BOL article.

Thats great, thanks very much for your help.

Thanks for your reply, i simply ran an sp_who2 and the system processes that i mentioned has 'sa' in the login column. I assume this is output by default for...

Thanks very much, i did indeed have the "include execution plan" option selected and it was this which was creating the extra output message.

Thanks for the response, i'll check out the article that you have suggested.

great, thanks for the advice. i'll give it a try and let you know how i get on.

Thanks for the advice; i'll give it a try and let you know how i get on.

Thanks for your reply, could you please provide a little more detail. Where should i apply the string formatting method and how do i apply embedded VB code?

Just to complete the picture here; we performed a full server reboot out of hours and the SQL Server Agent Jobs that contain SSIS package steps are now executing without...

The job runs successfully using the DTEXEC utility; so it's just if i try to run the job through the SQL server agent; does this confirm your suspicions that the...

I'll give it a try with DTEXEC and let you know the outcome.

There have been no hotfixes applied in the weeks leading up to the first occurance of this problem.

Thanks...

I set up a TSQL step to simply create an empty table before running the SSIS step as you suggested and the first step executed without a problem (the new...

Thanks for the response.

I have tried both methods and neither is working; although if i store the SSIS package on the server and execute it via SSIS withiin management studio...