Unable to invoke the Data Link Properties dialog box from the modules:
Extract - File Processing - Define Items
One of the errors, below, may be encountered
The connection string might be blanked out and must be re-entered
Possible error #1:
!! ERROR IN D:\PROGRAM FILES\COGNOS\CER4\BIN\LEXWTP ON 2005/06/01 AT 08:31 FOR USER GOS ADMINISTRATOR !!
Error Code: 9.7426.0.7970.85126.96.36.199
?WI OBJECT ERROR: Object "ado" not found
ado_error_message (0=?eado_errors wself)/0
Possible error #2:
Connection String Error
IBM Cognos Finance is version independent. When using ADO, the application doesn't ask for a specific version. If it asked for ADO 2.80, the registry key HKCR\ADODB.xxx.2.80 would be used and would work. The coding calls for the current version (which is supposed to be the preferred method), which looks at HKCR\ADODB.xxx\CurVer, to determine the current version. Since the value of that key doesn't match, it doesn't work.
Windows 2003 Server SP1
Resolving the problem
#1. Downgrade the MDAC installed on your application server.
#2. Modify the registry.
1. Locate your original Windows 2003 Server CD.
2. Browse to the %systemroot%\$NtServicePackUninstall$ directory.
3. Locate the file called 'mdac.inf'.
4. Right click on the file and select Install. You will be prompted for the Windows 2003 CD.
5. Answer Yes to all the Overwrite Newer File prompts.
Important Note: The %systemroot%\$NtServicePackUninstall$ directory is by default a hidden folder. In Windows Explorer, ensure that you have enabled the Show hidden files and folders option in the View tab in Folder Options. If you have and it is still missing, that means someone has removed it. Contact Microsoft for assistance with restoring the directory or assistance with unpacking the file required in step #3 above from one server machine to another before proceeding to steps #3, #4 and #5.
1. Run REGEDIT (or any other available registry editor)
2. Open HKEY_CLASSES_ROOT
3. Scroll down to the set of keys whose names begin "ADODB"
4. These keys come in pairs - one with a version number and one without.
(where "xxx" is one of Command, Connection, Error, ErrorLookup, Parameter, Record, RecordSet, and Stream).
5. For each pair, the key without the version number will contain a "CurVer" sub-key whose default value should be the name of the other key:
HKCR\ADODB.xxx\CurVer would have a default value of ADODB.xxx.###
6. In the Windows 2003 SP1/MDAC 2.8 SP2 install, the keyname with the version is 2.80 but the CurVer value is 2.8 (which doesn't match).
Update the CurVer default value for each pair.
For example, you'll have:
(in total 8 pairs)
Correct each HKCR\ADODB.xxx\CurVer from ADODB.xxx.2.8 to ADODB.xxx.2.80. So:
Key (Default) value
(in total 8 entries)