Ask them to stick the package in a job, setup a step log for the SSIS package, run the package (and fail) and ship you the file.
There's a ton more information in that file than you can get from the job errors or whatever is popping on screen, and you're going to need that to help them troubleshoot this 'over the phone' as it were. You might be looping extra files that have similar naming patterns that weren't supposed to be picked up. It might be an invalid value.
The only version differences I could see would be a difference between SP1 and 2, but I can't see date conversion being a serious issue between them, but it certainly couldn't hurt to check. You need the full error list though. Start with the log file, work from there. You may not be seeing the entire error chain *(since the job results truncate the error list) and the real error is elsewhere.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA