Often upgrading to a new version of Domino means that a new machine has been set up that will take the place of the previous one and one or more required setup steps have been forgotten. This checklist applies to products such as DECS, LSX LC, LS:DO and LEI.
1. The most frequent error messages encountered are "unable to create product object" or "unable to load libraries for...". However if scripts are being used and insufficient error checking has been built in the actual error message may not be seen.
2. The error "unable to create product object" comes from many causes but may be that the connector file cannot load the client libraries.
3. You may notice that the scripts will run manually, and not scheduled. This is an important clue. Running manually usually means running on the client, and connectivity may be correct there, running on schedule with Agent Manager means running on the server where the connectivity may not have been set up.
INFORMATION YOU WILL NEED:
What is the OS? Not all versions on all operating systems support all connectors. The Release Notes will till you this.
Is it 32 or 64 bit? Data access clients (DB2 and Oracle for instance) come in both version but only one might be enabled.
What is the version of Domino? It is required that the LEI version is the same as Domino version.
Is Domino installed as a 32 or 64 bit application? Not all versions support all Lotus Connectors on all platforms. Again see the Release Notes on the Lotus Documentation Web site.
Was Domino installed with the Enterprise Edition option? This is necessary to get the DECS/LSX LX connector files to use with LotusScript or LEI.
Is Domino being run as a Service, or as an Application? If Domino is started as a service you may need to confirm that Domino, and the companion products, have access to the connectivity libraries.
Have you restarted Domino after all client products have been installed? A reboot at the OS level is recommended and may be mandatory.
What companion product is being used? ( DECS, LSX LC, LS:DO and LEI for example. Domino does not itself connect directly to external databases.) If you need to contact technical support the software engineer will need to know this.
What Connector is being used?
Is the DB2 Connect client installed?
32 or 64 bit?,
Connection set up in Configuration Assistant?
Tested with Command Line Editor or other client tool?
Must be 9.5 or later.
Is the full Oracle Client installed? (The Oracle Express Client. does not provide the necessary API for our needs.)
32 or 64 bit?
Net Configuration set up for the intended database?
Tested with SQL*Plus?
Note: if OS is 64 bit Oracle will install both 32 and 64 bit versions. If Domino and the companion products are installed as 32 bit applications you will have to have the PATH pointed to the 32 bit Oracle libraries, and visa versa.
Note: Oracle Client 8 is no longer supported.
OLE DB (Microsoft SQL Server)
This is a part of the Windows operating system and does not need installation or configuration.
Which driver is the ODBC connection using? DB2, Oracle, MS SQL Server, Sybase are a few options.
Note: Lotus IBM only supports the IBM Branded Data Direct ODBC drivers.
32 or 64 bit? Note: using ODBC with 64 bit Domino will not be supported until Domino 8.5.2.
You can test any of the above connections with the small utility dctest in the Domino program directory. On Windows it is called ndctest, dctest on UNIX. Check the User's Guide for more information.
If you are using LotusScript agents they must be recompiled on the new machine so that the new connections are included in the pseudo code. To do this you only need to touch each script and save it.
You can find syinfo logs in the IBM_TECHNICAL_SUPPORT folder under the data directory that can be very helpful to you and support determining what environment the Domino server actually "sees". Search for the "environment" section. This can be very different from what you see logged in as yourself from a command line prompt.