BUG: DTS Packages Stored in the Repository Are Not Listed

ID: Q245253

The information in this article applies to:

Microsoft SQL Server version 7.0

BUG #: 56523, 56226 (SQLBUG_70)

SYMPTOMS

The SQL Server Enterprise Manager listing of Data Transformation Services (DTS) packages stored in the repository is incomplete or empty.

A package may be created and saved to the repository but when the design window is closed the package is not displayed in the repository packages list in SQL Server Enterprise Manager.

The list may display different packages on different clients, for example some clients may show all the packages while other clients show none.

CAUSE

Some packages may have been stored from a client computer with a non-default short date format specified in the Regional Settings. If the date format for a stored package is not valid on the client retrieving the package list, the package is not listed and no subsequent packages are listed. If an existing package is edited and saved by a client with a non-default short date format specified, then that package will no longer be displayed in the list and any packages that were previously displayed after the updated package will also disappear from the list.

The order of the package listing may not be the chronological order of the creation date values in the list.

WORKAROUND

All clients should be set with the same short date format in the Regional Settings dialog from Control Panel.

Where existing packages are not being displayed the following steps can be used to access those packages and set the required short format setting:

Set the short date format to the format that has been used to store the problem packages.

Refresh the list of packages, which should then show those packages.

Open any packages that have been stored using the wrong date format.

Leaving the package design windows open, change the short date format back to the required format.

Save the open packages and close the design windows.

This process stores the latest version of the package with the required date format and all packages should then be listed.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 7.0.

MORE INFORMATION

The default short date format for Windows NT with the Regional Setting of English (United States) is d/m/yy. The problem can be seen if some packages are created on a client with this default setting and other packages are created on a client where the short date format has been changed to d.m.yy.

Additional query words: visible invisible missing lost

Keywords : SSrvAdmin SSrvEntMan kbSQLServ700bug
Version : winnt:7.0
Platform : winnt
Issue type : kbbug