System.Data.OleDb.OleDbException: Unspecified error

S

Sarah

I have a function residing in a module that is doing some file copy and
database query operations. This function is called from a regular form under
a System.Windows.Forms.Timer control. The problem is that sometimes it gives
an error - even when it is doing the same exact operations. It may fail on
the 20th tick event or the 100th. The file and data has no changes - so, it
is doing the same operations repeatedly. I'm wondering if anyone can look at
the error below and tell me where to start because I know that there is no
problem with the code to copy the files or to read/write to the database.
The error comes up during different points of the code execution in the
function - pretty random.



Error Message:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.Data.OleDb.OleDbException: Unspecified error

at System.Data.OleDb.OleDbConnection.ProcessResults(Int32 hr)

at System.Data.OleDb.OleDbConnection.InitializeProvider()

at System.Data.OleDb.OleDbConnection.Open()

at DominosUI_VBProject.mdlDatabaseConnection.StartDBConnection() in
F:\Source Code\mdlDatabaseConnection.vb:line 26

at DominosUI_VBProject.mdlSoftwareEventLog.fxLogDebugEvent(String
CprtEventDescription) in F:\Source Code\mdlSoftwareEventLog.vb:line 28

at DominosUI_VBProject.mdlAutoPrintPos1.AutoPrintPos1() in F:\Source
Code\mdlAutoPrintPos1.vb:line 264

at DominosUI_VBProject.MainForm.timerAutomaticPrinting_Tick(Object sender,
EventArgs e) in F:\Source Code\MainForm.vb:line 1474

at System.Windows.Forms.Timer.OnTick(EventArgs e)

at System.Windows.Forms.Timer.DebuggableCallback(IntPtr hWnd, Int32 msg,
IntPtr idEvent, IntPtr dwTime)



************** Loaded Assemblies **************

mscorlib

Assembly Version: 1.0.3300.0

Win32 Version: 1.0.3705.288

CodeBase: file:///c:/windows/microsoft.net/framework/v1.0.3705/mscorlib.dll

----------------------------------------

DominosUI_VBProject

Assembly Version: 1.0.1810.5631

Win32 Version: 1.0.1810.5631

CodeBase: file:///F:/Source Code/bin/DominosUI_VBProject.exe

----------------------------------------

System.Windows.Forms

Assembly Version: 1.0.3300.0

Win32 Version: 1.0.3705.288

CodeBase:
file:///c:/windows/assembly/gac/system.windows.forms/1.0.3300.0__b77a5c56193
4e089/system.windows.forms.dll

----------------------------------------

System

Assembly Version: 1.0.3300.0

Win32 Version: 1.0.3705.288

CodeBase:
file:///c:/windows/assembly/gac/system/1.0.3300.0__b77a5c561934e089/system.d
ll

----------------------------------------

System.Drawing

Assembly Version: 1.0.3300.0

Win32 Version: 1.0.3705.288

CodeBase:
file:///c:/windows/assembly/gac/system.drawing/1.0.3300.0__b03f5f7f11d50a3a/
system.drawing.dll

----------------------------------------

Microsoft.VisualBasic

Assembly Version: 7.0.3300.0

Win32 Version: 7.00.9502

CodeBase:
file:///c:/windows/assembly/gac/microsoft.visualbasic/7.0.3300.0__b03f5f7f11
d50a3a/microsoft.visualbasic.dll

----------------------------------------

System.Data

Assembly Version: 1.0.3300.0

Win32 Version: 1.0.3705.288

CodeBase:
file:///c:/windows/assembly/gac/system.data/1.0.3300.0__b77a5c561934e089/sys
tem.data.dll

----------------------------------------

System.EnterpriseServices

Assembly Version: 1.0.3300.0

Win32 Version: 1.0.3705.288

CodeBase:
file:///c:/windows/assembly/gac/system.enterpriseservices/1.0.3300.0__b03f5f
7f11d50a3a/system.enterpriseservices.dll

----------------------------------------

Accessibility

Assembly Version: 1.0.3300.0

Win32 Version: 1.0.3705.0

CodeBase:
file:///c:/windows/assembly/gac/accessibility/1.0.3300.0__b03f5f7f11d50a3a/a
ccessibility.dll

----------------------------------------

************** JIT Debugging **************

To enable just in time (JIT) debugging, the config file for this

application or machine (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 machine

rather than being handled by this dialog.
 
S

scorpion53061

Sarah,

Try stepping through the program to see what line exactly is throwing
the exception and then post that section of code here.
 
S

Sarah

Try stepping through the program to see what line exactly is throwing
the exception and then post that section of code here.
Click to expand...

There are a lot of lines of code and the problem is that it does not happen
every time. Sometimes it executes the tick every 5secs successfully for
hours. So, I can't step through!

It is executing the same code again and again - i.e. all running through the
very same steps. It is connecting to an Access .mdb database file and only
fails once in a while. Same problem on multiple systems. CPU resource and
memory usage very low. Anything else to try?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Closing a App 4
Deployment Question 4
Exception when working with app.config with windows .net 1
exe issues 1
"Index was outside the bounds of the array" error out of nowhere 1
What is a solution for below problem. 3
CDO exception with Web.Mail 4
unhandeled execption in PrintPreview 1

Top