Rockwell Automation Emonitor with a Gupta Multi-User Database - Manual (Page 44)

I NSTALLING E MONITOR S OFTWARE WITH A G UPTA SQLB ASE M ULTI -U SER D ATABASE
40
• •
•
•
•
„
Make sure that you have only one copy of SQL.INI on your computer.
„
Make sure that the SQL.INI file has not been renamed or deleted.
„
If you log in to your computer, make sure that you used the correct login name and
password.
Why can’t I connect to the database?
If you cannot connect to databases after installing, ensure that your databases have been
added to the server configuration and that they are enabled. See Adding a new database on
page 34 for more information. See Setting up the server on page 8 for more information
(for a Multi-User installation).
If you still can't connect to the database, check the SQL.INI file to make sure the line that
says DBDIR=C:\Program Files\SQLBase901 actually points to the installed location of
the SQLBase database.
Why can’t it find the ERROR.SQL file?
If you get an error like this, check your path by typing PATH at an MS-DOS prompt. If
your path does not contain the SQLBase program directory, Emonitor cannot find the
needed database files. Also, check to make sure error.sql is in the SQLBase directory and
has not been renamed.
My other SQLBase programs cannot find the SQL.INI file.
The Emonitor installation program renames any SQL.INI, MESSAGE.SQL, or
ERROR.SQL file that it finds in your path. If other SQLBase programs are affected by
this, you must rename these other files before attempting to run the other program that
uses SQLBase.
Do I add DBNTSRV to the Windows Firewall exceptions?
If you do not reboot after installing the SQLBase and Emonitor software, a message
appears when you start Emonitor, asking if you want to add DBNTSRV to the Windows
Firewall exceptions. In order for Emonitor to communicate with the database, you must
allow DBNTSRV to be added to the exceptions list.