Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Script files failed to load.

Script files failed to load.

Script files failed to load.

I have numerous DTS files that contain script files on a 32-bit server with no problems when running. However, after deploying these packages to a 64-bit server I have began recieving an error on all script files that state:
Error: 0x5 at "script name"" The Script files failed to load.

Has anyone had this problem???


RE: Script files failed to load.

I don't know if this helps, but....

REF: http://technet.microsoft.com/en-us/library/aa274595(SQL.80).aspx

SQL Server 2000 (64-bit)
Differences Between 64-bit and 32-bit Releases (64-bit)

<skipped parts not about DTS>
Data Transformation Services (DTS) components for 64-bit servers are not available in this release. Note the resulting functionality changes:

A DTS package can be saved on the 64-bit server, and a DTS package can be run against a SQL Server 2000 (64-bit) dataset, but the package must run from a 32-bit machine that is set up with SQL Server 2000 tools.

The Copy Database Wizard will not be able to run on a 64-bit server or target a 64-bit server. Data migration from SQL Server 2000 to SQL Server 2000 (64-bit) is supported. Attaching a 32-bit database to a 64-bit instance is possible by using either the detach/attach or the backup/restore technique. You can move databases back and forth between 32-bit and 64-bit versions of SQL Server.

If you are using Meta Data Services (MDS) to store a DTS package, you must manage and store the DTS package on a 32-bit server.

Transformable push subscriptions are not supported. Pull subscriptions from a 32-bit installation of SQL Server 2000 should work with a 64-bit Publisher or Distributor.


Posting advice: FAQ481-4875: What should I know before I post?

RE: Script files failed to load.

After several hours of trial and error and Googling i was able to resolve this issue by simply removing all breakpoints in the scripts. breakpoints are not allowed when running packages in the 64-bit environment.

I literally had to open all script tasks on all packages remove the breakpoints, save the script and then rebuild the solution.

Upon completing this, the packages ran fine....


(If it won't work, Make it... if it breaks in needed fix'in anyways.)

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close