home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC63960 Status: Closed

32 BIT .NET PROVIDER NOT GETTING INSTALLED ON 64 BIT WINDOWS.

product:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problem description:
When installing 32 bit IBM data server client on a 64 bit 
Windows, .NET Provider does not get registered. 
 
The client installation finishes successfully, but VSAI  fails 
to install with the following error. 
1: ERROR:To install IBM Database Add-Ins for Visual Studio, you 
must have one of the following providers installed: 
IBM Data Server Provider for .NET
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users installing V9.7 32 bit IBM ADD-INS for Visual Studioon * 
* 64 bit Windows.                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* IBM Data server client installation finishes                 * 
* successfully,but IBM add-ins for Visual studio(VSAI)  fails  * 
* to installwith the following error.1: ERROR:To install IBM   * 
* Database Add-Ins for Visual Studio,you must have one of the  * 
* following providers installed:IBM Data Server Provider for   * 
* .NET                                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FP2.                                         * 
****************************************************************
Local Fix:
Workaround is to manually register the driver using db2nmpcfg or 
use "db2swtch.exe -IDS common"  command.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in V9.7 FP2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
30.06.2010
30.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList