Consistent Error Popping up

For users or potential users.
Post Reply
Nate
Posts: 164
Joined: Wed Jun 27, 2007 1:36 pm
Location: Kansas City, MO

Consistent Error Popping up

Post by Nate » Thu Jan 14, 2010 6:24 am

We have 4 office computers networked together, running xp professional. One acts as the server computer. DSL modem bridged to linksys router BEFSX4. We have no problems accessing the internet from any computers. The only problem we have is periodic error message popping up when using open dental. This issue has been going on for quite a while but seems to be getting more frequent, maybe because we are using the program more to review charting information. The issue seems random but always occurs when we are clicking on something in OD. For example to change modules or to enter notes. Usually only one computer is accessing OD at the time the probelm is occuring. The problem will occur on any of the client computers but does not occur on the server computer. It seems like it is trying to connect to the data base or something and having issues. Usually if we wait 30 seconds or so it will have the error message below pop up. We click continue then it will refresh to the modual or chart area we had clicked on. I copied the error message and the details of the error message and posted below. PLEASE ANY HELP WOULD BE APPRECIATED. It is really slowing us down.

Thanks,
Dr. Klein

We get the following error message.

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Error connecting: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

We usually click continue and get through it but it takes a while. The details are listed below.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
MySql.Data.MySqlClient.MySqlException: error connecting: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
at MySql.Data.MySqlClient.MySqlPool.GetConnection()
at MySql.Data.MySqlClient.MySqlConnection.Open()
at System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at OpenDentBusiness.DataConnection.GetTable(String command)
at OpenDentBusiness.Appointments.GetPeriodApptsTable(DateTime dateStart, DateTime dateEnd, Int32 aptNum, Boolean isPlanned)
at OpenDentBusiness.Appointments.RefreshPeriod(DateTime dateStart, DateTime dateEnd)
at OpenDentBusiness.DataCore.GetDsByMethod(MethodNameDS methodName, Object[] parameters)
at OpenDentBusiness.Gen.GetDS(MethodNameDS methodName, Object[] parameters)
at OpenDental.AppointmentL.RefreshPeriod(DateTime dateStart, DateTime dateEnd)
at OpenDental.ContrAppt.RefreshPeriod()
at OpenDental.ContrAppt.ModuleSelected(Int32 patNum)
at OpenDental.FormOpenDental.SetModuleSelected()
at OpenDental.FormOpenDental.myOutlookBar_ButtonClicked(Object sender, ButtonClicked_EventArgs e)
at OpenDental.OutlookBar.OnButtonClicked(OutlookButton myButton, Boolean myCancel)
at OpenDental.OutlookBar.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
OpenDental
Assembly Version: 6.5.24.0
Win32 Version: 6.5.24.0
CodeBase: file:///C:/Program%20Files/Open%20Dental/OpenDental.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
CodeBase
Assembly Version: 6.4.0.0
Win32 Version: 6.4.0.0
CodeBase: file:///C:/Program%20Files/Open%20Dental/CodeBase.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
OpenDentBusiness
Assembly Version: 6.5.24.0
Win32 Version: 6.5.24.0
CodeBase: file:///C:/Program%20Files/Open%20Dental/OpenDentBusiness.DLL
----------------------------------------
SparksToothChart
Assembly Version: 4.7.1.0
Win32 Version: 4.7.1.0
CodeBase: file:///C:/Program%20Files/Open%20Dental/SparksToothChart.DLL
----------------------------------------
xImageDeviceManager
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/Open%20Dental/xImageDeviceManager.DLL
----------------------------------------
SigPlusNET
Assembly Version: 1.0.2245.36238
Win32 Version:
CodeBase: file:///C:/Program%20Files/Open%20Dental/SigPlusNET.DLL
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
CDT
Assembly Version: 6.5.1.0
Win32 Version: 6.5.1.0
CodeBase: file:///C:/Program%20Files/Open%20Dental/CDT.DLL
----------------------------------------
MySql.Data
Assembly Version: 1.0.9.0
Win32 Version: 1.0.9.0
CodeBase: file:///C:/Program%20Files/Open%20Dental/MySql.Data.DLL
----------------------------------------
Oracle.DataAccess
Assembly Version: 10.2.0.100
Win32 Version: 10.2.0.100
CodeBase: file:///C:/Program%20Files/Open%20Dental/Oracle.DataAccess.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
Tao.OpenGl
Assembly Version: 2.1.0.4
Win32 Version: 2.1.0.4
CodeBase: file:///C:/Program%20Files/Open%20Dental/Tao.OpenGl.DLL
----------------------------------------
Tao.Platform.Windows
Assembly Version: 1.0.0.4
Win32 Version: 1.0.0.4
CodeBase: file:///C:/Program%20Files/Open%20Dental/Tao.Platform.Windows.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

User avatar
jordansparks
Site Admin
Posts: 5744
Joined: Sun Jun 17, 2007 3:59 pm
Location: Salem, Oregon
Contact:

Re: Consistent Error Popping up

Post by jordansparks » Thu Jan 14, 2010 1:40 pm

Are they connected to each other wirelessly?
Jordan Sparks, DMD
http://www.opendental.com

User avatar
jordansparks
Site Admin
Posts: 5744
Joined: Sun Jun 17, 2007 3:59 pm
Location: Salem, Oregon
Contact:

Re: Consistent Error Popping up

Post by jordansparks » Sun Jan 17, 2010 8:17 am

I think it might be this:
http://www.opendental.com/manual/mysqls ... ables.html

If so, let me know so we can further define the problem and figure out exactly which server variable is responsible.
Jordan Sparks, DMD
http://www.opendental.com

Nate
Posts: 164
Joined: Wed Jun 27, 2007 1:36 pm
Location: Kansas City, MO

Re: Consistent Error Popping up

Post by Nate » Mon Jan 18, 2010 11:19 am

No we do not use wireless network.

Checked the MySQL 5.0 and only 4 lines in the my.ini file and they read the same

Called OpenDental help and they suggested going to 'setup', 'show features', and selecting 'multiple office locations'.
That also did not fix the problem.

Any other ideas?

User avatar
jordansparks
Site Admin
Posts: 5744
Joined: Sun Jun 17, 2007 3:59 pm
Location: Salem, Oregon
Contact:

Re: Consistent Error Popping up

Post by jordansparks » Mon Jan 18, 2010 1:54 pm

How about other programs that might be interfering? A few that come to mind involve firewalls, such as Zone Alarm, McAffee, and Norton. Frequently, with these kinds of firewalls, you have to uninstall the program completely because just turning off the firewall does not work.

The other possibility is hardware. Change out your router. If that doesn't work, then remove one computer from the network for one day. Then remove a different computer for one day, etc. The reason for doing it like this is that a network card on one of the computers could be bad and could be sending out garbage that confuses the rest of the network. So to eliminate your server network card as the culprit, you may just want to put in a different network card instead of trying to move your database to a different computer.
Jordan Sparks, DMD
http://www.opendental.com

Post Reply