SSIS Not pulling data correctly

[clumnah]

Ok I wrote a SSIS package that will pull down data from my AS/400 and populate a SQL Server table with the data.

1)The data is being pulled from my China configured AS/400. It is configured to handle DBCS
2)The SQL Server tables are configured to handle DBCS by using the nvarchar datatype.
3)When I run this package on my machine against the production server, it works perfectly.
4)When I run this package on my test SQL Server against the production server,it works perfectly.
5)When I run this package on my production SQL Server it brings down all the records, but does not bring down all the fields. Most of the character fields are left blank.(not all)

Production Server
Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Test Server
Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
My Machine
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

As you can see my machine is the only machine where the version differs. The test and production machines both match versions but test works and production does not.
I do not understand why this is doing this. Can anyone shed any light on this problem? Thank you.

 

[SQLBill]

Are you sure the packages are the same? Can you delete the production one, copy the test one to production and change any connection strings, etc that would be different? This indicates to me that the package isn't correct:

but does not bring down all the fields. Most of the character fields are left blank.(not all)


-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875

 

[clumnah]

The pacakge is exactly the same. I am not running a copy of the package. I am putting the package onto my production server. Running it there and watching it not work properly. I am going on my machine and the test machine and navigating to the folder where the package sits on the production box. Running it from my machine or the production machine, i watch it work perfectly. The more I think about this, i believe it is something environmental. I just dont know what to look for.

 

[SQLBill]

Try permissions. How are you running it on the Production server? How are you running it from your desktop? From the production box it may be running as the same permissions as the SQL Server Agent service. That login may not have permission to the data/file. From your desktop, you may be running it as yourself and may have permissions to the data/file.

Another thing, there can be different versions of a DTS package. You might be running one version from the server and another from your desktop.

I don't use SSIS a whole lot, so those are just suggestions that I can think of.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875

 

[clumnah]

I know it is not permissions. It is always running under my user ID. If it was permissions, then I would be rejected from writing to the file all together. This is not the case. I am writing the file on each box. The production box is just writing incomplete data. It seems that character data is not able to be written on the production box.