Error Messages (T) A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #The <database> database agent is not configured for jet "Not configured for jet" errors are generated by the OpenLink Session Rulebook. They occur when Microsoft Access is the ODBC client application. If you receive "not configured for jet" errors, take the following action: Use a text editor to open the oplrqb.ini file which you find in the /bin/ sub-directory of your OpenLink server components installation. Locate the [Domain Aliases] section of the Rulebook. Determine how your client's "Domain" or "ServerType" value is aliased. For instance: Oracle 8 = ora8 Locate the [Mapping Rules] section of the Rules Book. Find the rule associated with your alias and jet. For example: ora8:*:*:*:*:jet:* = reject The Oracle 8 Database Agent is not configured for jet Replace "reject The Database Agent is not configured for jet." with "accept generic_<alias>_jet". For example: ora8:*:*:*:*:*:* = accept generic_ora8_jet Ensure that there is a [generic_<alias>_jet] section, which includes CommandLine = +jetfix. This setting turns on several compatibility features, specific to Microsoft Jet-based client applications including Microsoft Access. For example: [generic_ora8_jet] Program = ora803_mv.exe Environment = ORACLE8 ReUse = always CommandLine = +jetfix . . Ensure that there is an associated [Environment <DATABASEX>] section. This section corresponds to the value passed to Environment in the [generic_<alias>_jet] section. Furthermore, ensure that the environment variables in [Environment DATABASEX] are set correctly. For example: [Environment ORACLE8] Path = \BIN;C:\WINNT\System32 ;ODBC_CATALOGS = Y ; Uncomment after loading odbccat7.sql ;MULTIPLEX_LDA = 5 ; Allow 5 OpenLink clients on a single lda . . . Restart or reinitialize your Request Broker to register your changes. Test. Evidence Session Rulebook Request Broker Log