Differences

This shows you the differences between two versions of the page.

--- sa26-00 [2018/07/14 01:56] – [Narrowing Down the Likely Causes of Connection Failure] Justin Willey
+++ sa26-00 [2018/07/17 08:23] (current) – [Database connection error] sean
@@ Line 55: / Line 55: @@
 <li class="level1"><div class="li"> Can other users that share the same iqx.ini file (on a network share or mapped drive) connect? If so then 3 &amp; 7 are not the problem.<button type="button" class="button button1" onclick="document.getElementById('3').style.color='lightgrey'; document.getElementById('7').style.color='lightgrey'">Yes</button></div>
 </li>
-<li class="level1"><div class="li">Does the problem affect all users in one office (who have connected in the past) while other offices can connect alright. If so, then 5 is almost certainly the problem, unless there have been changes made to all the computers iqx.ini files (or a shared iqx.ini).<button type="button" class="button button1" onclick="document.getElementById('1').style.color='lightgrey'; document.getElementById('2').style.color='lightgrey'; document.getElementById('3').style.color='lightgrey'; document.getElementById('4').style.color='lightgrey'; document.getElementById('5').style.color='#4CAF50'; document.getElementById('6').style.color='lightgrey'; document.getElementById('7').style.color='gray';">Yes</button></div>
+<li class="level1"><div class="li">Does the problem affect all users in one office (who have connected in the past) while other offices can connect alright. If so, then 5 is almost certainly the problem, unless there have been changes made to all the computers' iqx.ini files (or a shared iqx.ini).<button type="button" class="button button1" onclick="document.getElementById('1').style.color='lightgrey'; document.getElementById('2').style.color='lightgrey'; document.getElementById('3').style.color='lightgrey'; document.getElementById('4').style.color='lightgrey'; document.getElementById('5').style.color='#4CAF50'; document.getElementById('6').style.color='lightgrey'; document.getElementById('7').style.color='gray';">Yes</button></div>
 </li>
 <li class="level1"><div class="li"><button type="button" class="button button1" onclick="document.getElementById('1').style.color='#4CAF50'; document.getElementById('2').style.color='#4CAF50'; document.getElementById('3').style.color='#4CAF50'; document.getElementById('4').style.color='#4CAF50'; document.getElementById('5').style.color='#4CAF50'; document.getElementById('6').style.color='#4CAF50'; document.getElementById('7').style.color='#4CAF50';">Reset Choices</button></div>
@@ Line 110: / Line 110: @@
 {{ ::databaseconnectionerror.jpg |}}
 This message indicates that while connection settings have been identified for the requested database, a successful connection could not be established. To get more information, press the <key>Details</key> button. This results in a detailed and somewhat technical error log, which can be copied to the Windows clipboard. The following sections give guidance for the possible different error messages:
-<accordion>
+\\
 <panel title="Data source name not found and no default driver specified">
 {{ :nodefaultdriverspecified.jpg? |}}This is a rather misleading error message from the Microsoft ODBC driver manager that indicates that the ODBC driver requested is not installed. The driver version required is specified in the connection string in iqx.ini. In the example above the setting in the ini file was:<code>[Databases]
@@ Line 140: / Line 140: @@
 ===Database server not found, but no other indication===
 {{ :databaseservernotfoundwithoutotherindication.jpg |}}
-This indicates that IQX can get no response from the given network address nor by trying to find the database engine by name. Either the address is wrong, or the database server is not running, or there is a network problem (which could include a firewall blocking traffic). If other users **can** connect, then check that the iqx.ini setting are the same and that a firewall is not blocking traffic.\\
+This indicates that IQX can get no response from the given network address nor by trying to find the database engine by name. Either the address is wrong, or the database server is not running, or there is a network problem (which could include a firewall blocking traffic). If it is a firewall issue on a central/hosted server then it is likely that no one at all will be able to connect.  If it is a firewall or antivirus issue on the local pc then you may find that some others can connect when one user can't.  It is best to check the other things first before investigating a port blocking issue.  If there is an IT department or hosted IT company that manages the client's IT then any network or server changes should be carried out by them. \\
-This is an example of either Reason 4, 5 or 7 in the [[##narrowing_down_the_likely_causes_of_connection_failure|list]] above. </callout>
+This is an example of either Reason 4, 5 or 7 in the [[##narrowing_down_the_likely_causes_of_connection_failure|list]] above.
+<callout type="primary">
+</callout>
 </panel>
 <panel title="Specified database not found">
 {{ ::specifieddatabasenotfound.jpg |}}
-This error indicates that IQX has been able to connect to the database server specified in the iqx.ini file, but it has not found a database of the name specified in the dbn= setting. The most likely cause is that the database name in iqx.ini is wrong, there is a possibility that an administrator has temporary stopped the individual database while leaving the database engine running on the server. In the cas of a live database this latter reason is highly unlikely, but is possible for a training or test database.\\ \\ The required action in most cases is to correct the dbn= setting in iqx.ini. \\ \\ This is an example of Reason 7 in the [[##narrowing_down_the_likely_causes_of_connection_failure|list]] above.
+This error indicates that IQX has been able to connect to the database server specified in the iqx.ini file, but it has not found a database of the name specified in the dbn= setting. The most likely cause is that the database name in iqx.ini is wrong, there is a possibility that an administrator has temporary stopped the individual database while leaving the database engine running on the server. In the case of a live database this latter reason is highly unlikely, but is possible for a training or test database.\\ \\ The required action in most cases is to correct the dbn= setting in iqx.ini. \\ \\ This is an example of Reason 7 in the [[##narrowing_down_the_likely_causes_of_connection_failure|list]] above.
 </panel>
-</accordion>
 The guidance above assumes that iqx.ini rather than the ODBC administrator is being used to manage database connection details. For help with the ODBC administrator, refer to [[DeguggingBDEConnectionFailures#issues_with_the_odbc_dsn_or_the_network|Issues With the ODBC DSN]] in the BDE troubleshoot guide.