Are they attempting to access SSAS directly? You will need to grant them access to SSAS as well. Connect to SSAS via Management Studio, right-click server, select properties, select security...

This article might help -

http://www.sqlis.com/58.aspx

Have you attempted to create a new credential and execute the job under this account? Refer to "Credential Properties (General Page)" in BOL.

This might help -

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=478437&SiteID=1

Have you verified the MsDtsSrvr.exe executable? i.e. Is it still in "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.exe"? Can you launch from the command line and connect via management studio?

If your working in a distributed environment i.e. running MSX, a single SSIS package running against multiple TSX (targets) is much easier to maintain.

David - sent you an e-mail w/ example.

This is just a generic exception thrown by SSSIS. Your best bet is to debug the package from VS/BID - I would recommend adding a data viewer in on the...

Your on the right track w/ using VS as opposed to the wizard. Create a string variables for your connection strings. You can then pass these in the /SET parameter...

Can you verify the scope of your variable? i.e. ensure its on the package

Check out this article on SQLIS.com -

http://www.sqlis.com/311.aspx

Create a new SSIS project and package. Create string variables for the server name and database name. Create a new connection manager, point it to a server, database. Then right-click...

Just FYI, replied to your e-mail with an example package attached. Hope it helps.

I'm assuming your running W2K with the /3GB switch? If your running W2K3 you can remove this from the boot.ini file altoghether and it will use PAE. In either case I...

Check out http://www.sqlis.com - they often have some good examples/tutorials.