Jet Oledb connection problem in C# Win Application

Question

0.00/5 (No votes)

See more:

Hi,

I am developing a win .net application which runs continuously in server machine. Application will get connected with access(mdb) databases resided in several client machines using Jet 4.0 OLEDB provider.

Each connected database was already in use by some other application installed locally.

My app successfully communicates with all the databases when client machines are constantly alive.

But if one of my client machine goes down(say system or network) and rebooted, application cannot reconnect to that specific database, though it is accessible via network.

Even i tried to restart my application programmatically to re-establish the connection. But, It also fails.

Application just throws

"Disk or Network error"

or

"Unspecified Error"

or

"Cannot start your application. The workgroup information file is missing or opened exclusively by another user."

Anyone?

Posted 4-Aug-10 1:56am

dvkates

Add a Solution

Comments

Dylan Morley 4-Aug-10 8:16am

wow - inverse client server programming!

R. Giskard Reventlov 4-Aug-10 8:39am

Why are you using a) Access and b) lots of Access? Why don't you use Sql Server or MySql or similar?

dvkates 4-Aug-10 9:12am

@dylan
I have no authority to inverse the setup. It is already there.

@digital man
I am allowed to use the existing database only

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

E.F. Nijboer · Answer 1 · 2010-08-04T04:40:00

Besides the fact that I also agree that access only has disaster database guarantee, maybe the following links can provide you with a solution to your problem.

http://support.microsoft.com/?scid=kb%3Ben-us%3B300699&x=14&y=14[^]

http://support.microsoft.com/kb/823913[^]

By the way...
- the user isn't simply using the access db at that moment?
- is there a left over lock file (.ldb) in the same folder as the access file?

Good luck!