November 2, 2004 at 8:03 am
Hi,
We have successfully migrated DTS Packages from SQL 7.0 (Win NT 4.0) To Sql 2000. (Win 2003).
We encountered problems in some of the DTS Packages i.e., if the source table or query had more than 21 columns we are not able to transfer data from sqlserver 2000 to the .dat,.csv,.txt(Destination) files. But the same package is working fine in previous version(sqlserver 7.0).we are using Transform Data Task to export data from sqlserver to .dat file
an error is reported in Application log stating that "faulting application mmc.exe version 5.2.3790.0,faulting module msvcrt.dll version 7.0.3790.0,faulting address 0x00034d30"
When we click Transformation tab it prompts
Some of your transformation refer to column that do not exist in your source or destination
Remove invalid Transformations
Change source/destination
Remove all transformations and redo auto-mapping
since no fields are present in the destination columns we are not able to do any thing.
Hoping that everyone gets the scene
excepting suggestions/solutions with anticipation
Thanks in advance
Marimuthu A
November 3, 2004 at 2:40 am
Hi, Not sure if this is the same thing but ...
There was an issue with the DTSUI.dll file in one of the SQL Server 2000 Service Packs - 3a I think - where if the data in a datapump to file (an dpossible more) was over so many characters in total the package would fail when run via the GUI. From my dim memory again as it was DTSUI.dll that was dodgy I think the package worked fine when run from a job (sorry a bit vague it was like 18months ago or so that I hit this issue).
What release of SQL Server 2000 are you having this problem on. If you are running 8.00.760 it could be this, install HF 818.
Regards,
Stu
November 3, 2004 at 4:59 am
Version Details:
Microsoft SQL Server 2000 - 8.00.760 Standard Edition on Windows NT 5.2 (Build 3790: )
December 6, 2004 at 4:15 pm
Marimuthu,
Were you able to resolve this issue by applying a hotfix? If so, which one?
Thanks,
Steve
January 11, 2005 at 10:23 am
FYI, we resolved this issue by applying the "SQL Server 2000 (32-bit) Security Patch MS03-031" patch to the server:
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply