FIX: The Host Integration Server 2004 Transaction Integrator Designer does not update a type library's GUIDs when you migrate an existing type library from an earlier version of Host Integration Server

When you migrate an existing Microsoft Host Integration Server 2004 Transaction Integrator type library from an earlier version of Host Integration Server, the type library is correctly saved. However, when the type library is saved, the Transaction Integrator Designer does not update the Typelib GUID, the Interface GUID, and the CLSID GUID that are associated with the type library. This problem occurs when you change the existing type library, and then you save the type library by using the same file name as the existing type library.

Note The same problem occurs if you drag an existing Transaction Integrator type library into Microsoft Visual Studio .NET 2003 without opening an existing Transaction Integrator project first.

This problem does not occur if you save the modified type library by using a new file name for the type library. In this scenario, the type library GUIDs are updated correctly when the type library is saved.

Service pack information

To resolve this problem, obtain the latest service pack for Host Integration Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Host Integration Server 2004 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name	File version	File size	Date	Time	Platform
Ibmcobol.xml	Not Applicable	42,943	31-Jan-2005	18:16	Not Applicable
Microsoft.hostintegration.tidesigner.app.dll	6.0.2058.0	368,640	06-Dec-2006	01:45	x86
Microsoft.hostintegration.tidesigner.ctrl.dll	6.0.2058.0	90,112	06-Dec-2006	01:45	x86
Microsoft.hostintegration.tidesigner.pkg.dll	6.0.2058.0	200,704	06-Dec-2006	01:45	x86
Microsoft.hostintegration.tidesigner.wizards.dll	6.0.2058.0	462,848	06-Dec-2006	01:45	x86

To work around this problem, follow these steps so that the Transaction Integrator type library GUIDs are updated correctly when you save a modified type library with the same file name:

1.	Open Visual Studio .NET 2003.
2.	Open an existing Transaction Integrator project, or create a new Transaction Integrator project.
3.	In Solution Explorer, right-click the Transaction Integrator project name, click Add, and then click Add Existing Item.
4.	Locate the Transaction Integrator type library that you want to modify, and then click Open.
5.	Change the type library properties. For example, change the Version property value.
6.	Click File, click Save <Type Library Name> As, and then type the same file name as the existing type library. This action overwrites the existing type library file by using the new updates.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: