Errors received when logging into TOXICALL®, or selecting the network database through TOXICALL®, such as those below, are usually caused by either the inability of TOXICALL® to locate the network database, or database corruption.
•‘Error: -2147467259 couldn’t find file (path of file) Error Location Provider Microsoft Jet OLEDB.3.5.1; Persist Security info=false. Datasource=(path of file) Modual: modcommon, Function, CASOpenADOconnection,’
•Network database cannot be found
•Toxinet.mdb is not a valid database.
Note: The datasource could list Toxinet.mdb, Toxiloc.mdb or another .mdb file. For Toxinet and Toxiloc, follow the instructions below. For other files, call Toxicall Technical Support.
The first thing to check is that TOXICALL® can locate the file:
•Check your Configuration window to verify the network database location. Click the Lookup button next to the Network Database Location field.
•If you are running SQL Server, verify all fields with a machine that is working. If no machines are working contact your IT department and let them know you are unable to access the SQL server. If your SQL lines are the same as a working machine, see the next step.
•If you are running Access, click the next Lookup button. Verify that you are in the same directory that was specified in the Configuration window for this machine’s Toxinet.mdb. Toxinet.mdb should be visible in this directory. Double click it to select it again, click Save or OK in the next window and Save in the main Configuration window. Try to open TOXICALL® again. If you can’t get to the Toxinet.mdb mapped path through TOXICALL®, check the path with a working machine. If the non-working machine has a different path, modify it to match the working machine. If it has the same path defined, try to access it through My Computer. If you are not able to access it this way, there may be a problem with your network connection. You can try to reboot your system to see if it comes back, or you may have another problem which will require your IT department to fix. If all your workstations are having trouble accessing the network database this way, you may have a larger network problem. Contact your IT department.
•If this problem is happening on all machines and they have the correct path to the network database and it can be located through the Configuration window, you may have a corrupt network database.