I have a package that is doing a copy down to some old DOS data. We still have some legacy DOS programs that need SQL data. Anyhow, I can run the package as myself, but when it tries to use a different login, it fails. I'm assuming there's some logging capabilities that I haven't figured out yet. Can someone please help? I've given the SQL Server Agent login (full control) rights to the directories where the process task runs. The same login as sysadmin rights. I'm at a loss of how to narrow this down further.

Thanks,
Dave

It still sounds like a permissions issue. Every case I've seen where "it works on my machine," it was a difference in access levels. What is the failure message?

Found this at:
http://www.kbalertz.com/kb_910228.aspx
4.1.4 Considerations for Assemblies That Contain User-Defined Types
The following limitations apply to common language runtime (CLR) assemblies that contain user-defined types. Common Language Runtime User-Defined Types Should Have Only One Serialization Each instance of a byte-ordered user-defined type object can have only one serialized representation. If the serialize or de-serialize routines recognize more than one representation of a particular object, you may see errors in the following cases: • During validation of a byte-ordered user-defined type passed through RPC, user-defined type validation performs de-serialization/re-serialization of the user-defined type and requires that the resulting bytes be exactly the same as the original. If the validation fails, you will see the error:
"System.Data.SqlClient.SqlException, Incoming TDS RPC protocol stream is incorrect. Parameter 1 ("<ParameterName>"): The supplied value is not a valid instance of data type <TypeName>. Check the source data for invalid values."