Error: ""The transaction has exceeded the allotted time"

I receive this error "The transaction has exceeded the allotted time" in a pop-up sometimes when I use DTS. This happens in an alleatory way, when I run a package, when I try to open a package or save it, and normally happens when the machine is very busy with another process. I'm running SQL Server 2000 with SP2, and Windows 2000 Advanced Server with SP2.

Thank you very much in advance,

XavierWas any one able to find an answer to this? I'm getting the exact same error. Thanks.

Originally posted by xfolch
I receive this error "The transaction has exceeded the allotted time" in a pop-up sometimes when I use DTS. This happens in an alleatory way, when I run a package, when I try to open a package or save it, and normally happens when the machine is very busy with another process. I'm running SQL Server 2000 with SP2, and Windows 2000 Advanced Server with SP2.

Thank you very much in advance,

Xavier|||I solve it saving the packages as Local Packages instead of Meta Data Services Package: it never happens again|||So what is the difference between the two: "Local Packages" and "Meta Data Services Packages".

Thanks.

Originally posted by xfolch
I solve it saving the packages as Local Packages instead of Meta Data Services Package: it never happens again|||It works the same, but it's store in a different format:

When you save a Data Transformation Services (DTS) package, you save all DTS connections, DTS tasks, DTS transformations, and workflow steps and preserve the graphical layout of these objects on the DTS Designer design sheet.

You can save a package to:

Microsoft SQL Server.
With this default save option, you can store a package as a SQL Server msdb table, allowing you to: store packages on any instances of SQL Server on your network; keep a convenient inventory of saved packages in SQL Server Enterprise Manager; and create, delete, and branch multiple package versions during the package development process.

SQL Server 2000 Meta Data Services.
With this save option, you can maintain historical information about the data manipulated by the package. However, Meta Data Services and the repository database must be installed and operational on your server. You can track the columns and tables that are used by the package as a source or destination. You also can use the data lineage feature to track which version of a package created a particular row. You can use these types of information for decision-support applications.