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 #Table MSysConf does not exist or cannot be accessed "Msysconf" errors arise when the Microsoft Jet Engine attempts to retrieve tables from a non-existent msysconf table. This is a "misfeature" of the Microsoft product. Furthermore, "msysconf" errors are seldom fatal. As a result, they may often be ignored when observed in logs or traces. The true error condition will be found further along in your log or trace.Be advised. "Msysconf" errors cannot be ignored, if they are logged directly to your client. If "Msysconf" errors appear on your screen, perform the following actions:I. Edit the OpenLink Session Rules BookA) Use a text editor to open the oplrqb.ini file which you find in the /bin sub-directory of your server's OpenLink installation.B) Locate the [Mapping Rules] section.C) Place the following line at the top of the Mapping Rules:*:*:Admin:msdos:*:msaccess:* = reject Admin user account is not registered D) Save your changes and exit the file.E) Restart or reinitialize your OpenLink Request Broker.II. Disable Jet Engine LogonsA) Run regedit from a DOS prompt.B) Expand the Edit menu and select Find.C) Search the following directory structure for a JetTryAuth and/or TryJetAuth:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ C) Set JetTryAuth=0 and/or TryJetAuth=0.D) Exit the registry and test. Evidence Session Rules Book Request Broker Log ODBC Client Trace