Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ConnectionWrite(WriteFile()) Error

Status
Not open for further replies.

hsitz

Programmer
Dec 14, 2000
396
0
0
US
I have an Access .adp that's getting intermittent errors when getting data from SQL Server. The initial error will be:

[DBNMPNTW] ConnectionWrite(WriteFile()).object failed

followed by a:

"The operation on the Connection falure object failed."

I have yet to figure out any rhyme or reason to why this would appear. It seems to afflict one user especially. I can have this user switch to an administrative password (db is using WinNT security) and the errors will stop. But it doesn't seem tied to permissions, since the same action that brings up the error can be done after restarting the app and trying again, even without switching logins.

It's possible that it may be triggered initially by user-inactivity, say 15 minutes of doing nothing, but this isn't always the case.

I haven't been able to dig up much on this error in my search so far, other than that a connection is getting dropped for some reason.

Has anybody seen this before? Know the cause and/or the fix?

Thanks,

Herb Sitz
 
It sure sound like a network problem. If the problem is inflicting only one machine, then change the network card and try it, or even the cable/switch/hub.

________________________________________________________________________________
If you do not like change, get out of the IT business...
 
Thanks. Yes, it also seems to me like it's something with the network rather than with the application itself.

But it does occur on all the users computers. I guess the switch or hub could be suspect, but for the fact that the problems definitely disappear when a user logs out and relogs in with an administrative user account.

So I don't see how it could be tied to network hardware. Or could it?

Also, it doesn't seem to be anything with permissions, because a user can restart the application after an error and perform the very same action that gave rise to the error. But the fact that it doesn't happen at all on administrative accounts seems like an important piece of the puzzle.

I'm still stumped.

-- Herb
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top