DB2OLEDB Failed to install on SQL Server 2005 Developer Edition

I have SQL Server 2005 Developer Edition installed on XP Pro sp2 and have not been able to get OLE DB Provider for DB2 Version 1.0 with Service Pack 1 to install. After getting a notice that the install has failed, I get these log files:

=== Logging started at: 2:12:35 PM Monday, August 20, 2007 Build: 7.0.3038.0 Calling process: H:\SQL2005\DB2OLEDB7\Setup.exe === The current user is NORTHGRUM\dinsest. Computer name: DICA2ESITE13005 OS Version: 5.1 Build: 2600 Service Pack: 2.0 Suite: 256 Product Type: 1
[2:12:35 PM Info] Command Line: H:\SQL2005\DB2OLEDB7\Setup.exe
[2:12:35 PM Info] Language: 1033
[2:12:59 PM Info] Raw module path: H:\SQL2005\DB2OLEDB7\Setup.exe
[2:12:59 PM Info] Universal module path: H:\SQL2005\DB2OLEDB7\Setup.exe
[2:12:59 PM Info] Current version of msi.dll is: 3.1 build: 4000 platform: 2
[2:12:59 PM Info] Raw module path: H:\SQL2005\DB2OLEDB7\Setup.exe
[2:12:59 PM Info] Universal module path: H:\SQL2005\DB2OLEDB7\Setup.exe === Logging stopped: 2:12:59 PM Monday, August 20, 2007 === === Logging started at: 2:13:00 PM Monday, August 20, 2007 Build: 7.0.3038.0 Calling process: C:\DOCUME~1\dinsest\LOCALS~1\Temp\EBZ34671.tmp\Setup.exe === The current user is NORTHGRUM\dinsest. Computer name: DICA2ESITE13005 OS Version: 5.1 Build: 2600 Service Pack: 2.0 Suite: 256 Product Type: 1
[2:13:00 PM Info] Command Line: H:\SQL2005\DB2OLEDB7\Setup.exe /Relaunch /RunningFromTemp /SetupXML C:\DOCUME~1\dinsest\LOCALS~1\Temp\EBZ34671.tmp\HISDB2_x86.xml
[2:13:00 PM Info] Language: 1033
[2:13:00 PM Info]

[2:13:00 PM Info] Running prehook init function
[2:13:00 PM Info] Entering PreInitHook
[2:13:00 PM Info] Detecting Sql Server 2005 (32bit)
[2:13:00 PM Info] Enumerating Sql Server 2005 instances from Software\Microsoft\Microsoft SQL Server\Instance Names\SQL
[2:13:00 PM Info] Checking SQL version and edition for: Software\Microsoft\Microsoft SQL Server\MSSQL.1\Setup
[2:13:00 PM Info] Got Version 9.2.3042.00
[2:13:00 PM Info] Got edition Developer Edition
[2:13:00 PM Info] Done enumerating Sql Server 2005 instances, original hr = 00000000
[2:13:00 PM Info] Done enumerating Sql Server 2005 instances, hr = 00000000
[2:13:00 PM Info] Done detecting Sql Server 2005, hr = 00000000
[2:13:00 PM Info] Detecting existing integration server installations
[2:13:00 PM Info] Integration server is not installed
[2:13:00 PM Info] Done detecting existing integration server installations, hr = 00000000
[2:13:00 PM Info] Leaving PreInitHook (hr = 00000000)
[2:13:00 PM Info] Prehook Init function returned: 0.
[2:13:00 PM Info] Prehook Init function returned the following mode: 0
[2:13:01 PM Info] Product code: {722CAF00-DE6E-4438-82DE-E664B8B6222B}
[2:13:01 PM Info] Product name: Microsoft OLE DB Provider for DB2
[2:13:01 PM Info] Product PIDSKU: BI6-00082
[2:13:01 PM Info] Product Code (MPC): 91197
[2:13:01 PM Info] OEMID:
[2:13:01 PM Info] Product is not already installed.
[2:13:01 PM Info] Successfully opened Msi package: H:\SQL2005\DB2OLEDB7\Msi\x86\HISDB2.msi
[2:13:01 PM Info] Raw module path: C:\DOCUME~1\dinsest\LOCALS~1\Temp\EBZ34671.tmp\Setup.exe
[2:13:01 PM Info] Universal module path: C:\DOCUME~1\dinsest\LOCALS~1\Temp\EBZ34671.tmp\Setup.exe
[2:13:10 PM Info] Initializing Component Updater ...
[2:13:10 PM Info] Initialized Component Updater
[2:13:10 PM Info] No updates were found on the SUS server to download.
[2:13:14 PM Info] Required platform components:
[2:13:20 PM Info] Initializing Component Updater ...
[2:13:20 PM Info] Initialized Component Updater
[2:13:20 PM Info] No updates were found on the SUS server to download.
[2:13:20 PM Info] Required platform components: (none)
[2:13:20 PM Info] MSI command line: ADDLOCAL=REQUIRED_FEATURE,OLE_DB_PROVIDER_FOR_DB2 INSTALLDIR="C:\Program Files\Microsoft OLE DB Provider for DB2\" PIDKEY="R2D433DHG9DQ79WW3DXQ929DY" USERNAME="Northrop Grumman Corporation" COMPANYNAME="NGGN" FILESINUSEERROR=""
[2:13:20 PM Info] MSI command line is ADDLOCAL=REQUIRED_FEATURE,OLE_DB_PROVIDER_FOR_DB2 INSTALLDIR="C:\Program Files\Microsoft OLE DB Provider for DB2\" PIDKEY="R2D433DHG9DQ79WW3DXQ929DY" USERNAME="Northrop Grumman Corporation" COMPANYNAME="NGGN" FILESINUSEERROR=""
[2:13:20 PM Info] Detailed Log information for product H:\SQL2005\DB2OLEDB7\Msi\x86\HISDB2.msi is available at DetailedLog
[2:13:20 PM Info] MSI installation returned 2 - The system cannot find the file specified.
[2:13:20 PM Error] Error 0 occurred during MSI installation.
[2:13:20 PM Error]
[2:13:20 PM Error] === Logging stopped: 2:13:25 PM Monday, August 20, 2007 ===

Detailed Log

=== Verbose logging started: 8/20/200714:13:20Build type: SHIP UNICODE 3.01.4000.2435Calling process: C:\DOCUME~1\dinsest\LOCALS~1\Temp\EBZ34671.tmp\Setup.exe ===

MSI (c) (E4C) [14:13:20:343]: Resetting cached policy values

MSI (c) (E4C) [14:13:20:343]: Machine policy value 'Debug' is 0

MSI (c) (E4C) [14:13:20:343]: ******* RunEngine:

******* Product: H:\SQL2005\DB2OLEDB7\Msi\x86\HISDB2.msi

******* Action:

******* CommandLine: **********

MSI (c) (E4C) [14:13:20:343]: Client-side and UI is none or basic: Running entire install on the server.

MSI (c) (E4C) [14:13:20:343]: Grabbed execution mutex.

MSI (c) (E4C) [14:13:20:359]: Cloaking enabled.

MSI (c) (E4C) [14:13:20:359]: Attempting to enable all disabled priveleges before calling Install on Server

MSI (c) (E4C) [14:13:20:359]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (B88) [14:13:20:374]: Grabbed execution mutex.

MSI (s) (B8:90) [14:13:20:374]: Resetting cached policy values

MSI (s) (B8:90) [14:13:20:374]: Machine policy value 'Debug' is 0

MSI (s) (B8:90) [14:13:20:374]: ******* RunEngine:

******* Product: H:\SQL2005\DB2OLEDB7\Msi\x86\HISDB2.msi

******* Action:

******* CommandLine: **********

MSI (s) (B8:90) [14:13:20:374]: Machine policy value 'DisableUserInstalls' is 0

MSI (s) (B8:90) [14:13:20:406]: MainEngineThread is returning 2

MSI (c) (E4C) [14:13:20:421]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.Counter after decrement: -1

MSI (c) (E4C) [14:13:20:421]: MainEngineThread is returning 2

=== Verbose logging stopped: 8/20/200714:13:20 ===

Does anyone have an idea as to why the installation is failing?

TIA,

Steve

P.S. Those aren't really smileys, they're actually semicolon Ds but I can't seem to get rid of the cartoon translation, even after checking the "This post contains a code sample" checkbox.

Trial and error has provided my answer to this problem. It seems that not all executables will perform as expected when run from a USB attached drive. Copying them to the C: drive and then executing them was the only way this worked.

Hope this will help someone else. I didn't know this would be a problem.

Steve

sql

DB2 and Service Pack 2

Hi

We have recently upgraded to SP2, and some of the packages that used to run under SP1, simply don't work anymore. The thing is everytime we try to access DB2 using a SQL Task with at least 1 parameter, the task fails with the following error.

CLI0109E String data right truncation. SQLSTATE=22001 Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

The SQL Task works as long as I don't use parameters, but if I try something like this

SELECT CHAR(current timestamp) FROM sysibm.sysdummy1 where 'SAMPLE' = ?

and I try to map a String variable, that contais the value SAMPLE, to its only parameter,

User::Var1 INPUT VARCHAR 0 -1

the task fails.

Has anyone faced the same problem using IBM's OLE DB provider for DB2 after installing SP2?
I would really appreciatte any suggestions/comments on this matter.

Thanks.

While I don't know what might be causing the issue, a workaround would be to use a package variable to contain the SQL command and update the variable with a Script task before the Execute SQL task runs. In the Script task, you could update the variable and concatenate in the value of your parameter, producing a complete string that represents the parameterized SQL you want to run. This would eliminate the need for a parameterized query.

HTH,

Dave Fackler

|||Hello Dave

Yes, I suppose I could use a Script Task to build the query, and if I only had 1 sql task I would probably do it, but the truth is I've got several packages, each one having several SQL Tasks accesing DB2. Besides, in the near future, more people from my department will be using SSIS to access DB2, so sooner or later we will have to address this problem.

Due to the nature of the error, my guess is the new 'Parameter Size' field has something to do with it, but I cannot be certain.

Thanks|||Just a follow up

I've just noticed that some of my SSISs actually do work. The difference is that in these packages the SQL Tasks use the SUBSTR function to process the parameter. As far as I know SUBSTR processes a character expression and returns a VARCHAR, so I guess I'm experiencing a data-type conversion problem.

I would really appreciatte it if someone could tell me if they are able to use a SQL Task with parameters to access DB2 using IBM's OLE DB Provider for DB2 and SQL Server 2005 SP2.

Thanks in advance.|||

A number of changes were made to the SQL Task in SP2 to improve our handling of variable length parameters (mainly string types). I didn't think they affected input parameters, but if you're only seeing the problems after installing SP2, they could be related.

The last field on the parameter mapping page sets the parameter size. Since your error message is relating to string truncation, could you try setting this value to something large enough to hold your string? (1024, for example). The default value (-1) tell SSIS to guess at the correct size to use, and we may be having trouble retrieving the size from the DB2 provider.

|||Hello everybody

I had the same problem with data truncation. Then I changed the connection from OLE DB to ODBC. Now it works fine.

However you to adapt the parameter names according to the yellow table in this entry: http://www.msdner.com/dev-archive/5/19-80-57637.shtm

For string values I took the datatype "SQL_WVARCHAR".

Hope this helps...

Cheers

sql

DB properties cannot be changed with Enterprise Manager

Hello,

after the upgrade of MS SQL Server 7 to MS SQL Server 2000 on MS Windows 2000 Server and installation of MS SQL Server 2000 SP2 it is not possible to make changes to DB properties of user DBs with Enterprise Manager. MS SQL Server Instance properties and System DB properties are changeable with Enterprise Manager, but user DB properties can only be changed using Query Analyzer.

Has anybody an idea how to fix this problem?

Regards
Joe :rolleyes:Hi,

Do u trying to change by local Enterprise Manager or over Network?

Remember that are some new things in (2000) Permissions topic.

Explain more your schema.

[ ]'s|||Hi,

I tried to use the enterprise manager local and remote. Both doesn't work. I can display the user DB properties, but the ok button is grey. So I cannot use it.
What do you mean with new permissions at SQL 2000?

Regards
Joe