We are experiencing a problem trying to enable our JDBC adapter (6.0.2.) instances using MS SQL Server 2000.
(Note: these errors only occur on our development server. We can create and enable a successful connection on a our Test Integration server and on our laptops)

The errors are:

Error encountered
[ART.118.5042] Adapter Runtime (Connection): Unable to enable connection resource xpi.xrefServices.connection:connectToDB.
[ART.118.5036] Adapter Runtime (Connection): Unable to configure connection manager.
com/wm/dd/jdbcspy/SpyLoggerForDataSource

The adapter is JDBC 6.0.2.

Here are the Connection properties:

Connection Type: JDBC Adapter Connection
Package Name: JDE_XRef

Connection Properties

Transaction Type: NO_TRANSACTION
DataSource Class: com.microsoft.jdbcx.sqlserver.SQLServerDataSource
serverName: AUG-SQL70
user: wmxrefuser
password ******
databaseName: wmxref
portNumber: 1433
networkProtocol: just blanks
Other Properties: ServerName=AUG-SQL70\AUGSSQL12;selectMethod=cursor

Connection Management Properties

Enable Connection Pooling true
Minimum Pool Size 1
Maximum Pool Size 10
Pool Increment Size 1
Block Timeout (msec) 1000
Expire Timeout (msec) 1000

NOTE: we have the MS SQL 2000 errors in the Integration Service lib\jars folder and we see them in the CLASSPATH.

Here’s the “About” information for our Integration Server:

Server Environment
Java Version 1.3.1_09 (47.0)
Java Vendor Sun Microsystems Inc.
Java Home C:\jdk1.3.1_09\jre
Java Classpath C:\jdk1.3.1_09\jre\lib\rt.jar
C:\jdk1.3.1_09\jre\lib\i18n.jar
C:\webMethods6\IntegrationServer\lib\proxy.jar
C:\webMethods6\IntegrationServer\lib\system\mIcons.zip

Server Classpath C:\webMethods6\IntegrationServer\updates\IS_6-0-1_SP2.jar
C:\webMethods6\IntegrationServer\lib\classes\
C:\webMethods6\IntegrationServer\lib\server.jar
C:\webMethods6\IntegrationServer\lib\client.jar
C:\webMethods6\IntegrationServer\lib\mail.jar
C:\webMethods6\common\lib\client60.jar
C:\webMethods6\common\lib\apiutil60.jar
C:\webMethods6\IntegrationServer\lib\jars\classes12.zip
C:\webMethods6\IntegrationServer\lib\jars\jt400.jar
C:\webMethods6\IntegrationServer\lib\jars\log4j-full.jar
C:\webMethods6\IntegrationServer\lib\jars\mfapi602.jar
C:\webMethods6\IntegrationServer\lib\jars\msbase.jar
C:\webMethods6\IntegrationServer\lib\jars\mssqlserver.jar
C:\webMethods6\IntegrationServer\lib\jars\msutil.jar
C:\webMethods6\IntegrationServer\lib\jars\sl53_cj32.jar
C:\webMethods6\IntegrationServer\packages\imdk\code\classes\
C:\webMethods6\IntegrationServer\packages\WmART\code\jars\static\wmartbundle.jar
C:\webMethods6\IntegrationServer\packages\WmEDIINT\code\jars\static\ediint.jar
C:\webMethods6\IntegrationServer\packages\WmFlatFile\code\jars\static\ffcore.jar
C:\webMethods6\IntegrationServer\packages\WmFlatFile\code\jars\static\tspace.jar
C:\webMethods6\IntegrationServer\packages\WmIPRoot\code\jars\static\WmIPRoot.jar
C:\webMethods6\IntegrationServer\packages\WmItemSync\code\jars\static\WmItemSync.jar
C:\webMethods6\IntegrationServer\packages\WmItemSyncWF\code\jars\static\WmItemSyncWF.jar
C:\webMethods6\IntegrationServer\packages\WmJDBCAdapter\code\jars\static\javaxsql.zip
C:\webMethods6\IntegrationServer\packages\WmPKI\code\classes\
C:\webMethods6\IntegrationServer\packages\WmPRT\code\jars\static\wmprt.jar
C:\webMethods6\IntegrationServer\packages\WmRNIF11TRP\code\jars\static\WmRNIF11TRP.jar
C:\webMethods6\IntegrationServer\packages\WmRNIF20TRP\code\jars\static\WmRNIF20TRP.jar
C:\webMethods6\IntegrationServer\package

Hi. We got the fix for this problem from webMethods support.

We were getting the above error because of the parm
“watt.adapter.JDBC.JDBCLogFile” in the server.cnf file.

This problem seems specific to the Microsoft jdbc drivers because they seem to be using the merant jdbcspy classes for logging purposes but do not include those classes in the jar files they provide.

We removed the parm, restarted the server and we were able to enable our adapters.

Wayne

I have exactly the same problem, however I don´t have the “watt.adapter.JDBC.JDBCLogFile” key in the server.cnf file.

Does anyone know another fix for this problem?

Regards
Mikael Håkansson

Okay - Found the problem!

I was missing the msutil.jar file that should be in the IS_DIR\lib\jars directory. Just copy it from the installation of “SQL Server 2000 Driver for JDBC”.

Thanks
Mikael

Hi,

The issue i have is on the same lines as yours So i am posting it here(Guess you wont mind).

I was trying configure a new JDBC connection (to JDE test environment )and i have got the following errors.

ART.118.5042] Adapter Runtime (Connection): Unable to enable connection resource Test_Connection.
[ART.118.5063] Adapter Runtime (Connection): Unable to start connection Test_Connection: after 1 attempt(s) null

I have already a JDBC connection set up from the same IS server( to the JDE development environment )so i guess i have all the fixes,service packs and drivers in place and i think the issue is with connection properties(server name,database name,user,pass,port and the libraries).

Any Comments.

Thanks,
Ram

my issue has been resolved.
i got one of the Connection properties/parameters wrong.

Thanks,
ram

what is parameters wrong?
I have same problem…