Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Runtime Error No. 3043 (Disk or Networkerror)

89 views
Skip to first unread message

Andreas Meyer

unread,
Feb 17, 1998, 3:00:00 AM2/17/98
to

I divided my database into backend and frontend.
The linked tables in my frontend works fine. And yesterday,
even my vba-code, that opens und updates the backend
via "opentable" worked fine. Today - nothing was changed -
I got a runtime error in the vba-code while updating the
backend database. Do you have any idea?

Yours,

Andreas Meyer
me...@glamus.de

--------------------------------------------------
GLAMUS Gesellschaft fuer moderne Kommunikation mbH
Auguststr. 1 - 53229 Bonn - Tel +49.228.97617.0
Fax +49.228.97617.55 - Web http://www.glamus.de
--------------------------------------------------

Andreas Meyer

unread,
Feb 17, 1998, 3:00:00 AM2/17/98
to

Sorry, I have forgotten to write, that
I use MS-ACCESS 7.0.

Andreas Meyer wrote:

--

Havasu

unread,
Feb 24, 1998, 3:00:00 AM2/24/98
to

I have an application built exactly as yours. The backend is on an NT4.0
server. ALL CABLES have been reinstalled with tested CAT-5. All disks in
the server have been reformatted and are mirrored... this error (DISK OR
NETWORK ERROR) , requireing a RECOVERY of the back end in order to continue
normally, happens from 1 to 10 times a day!!! There are only 9 workstations
on the network... Any ideas or help would be appreciated

Randy Boback
Omnitech Migrations International
bob...@nbnet.nb.ca


Andreas Meyer <me...@glamus.de> wrote in article
<34E9A03D...@glamus.de>...

Steve Young

unread,
Feb 24, 1998, 3:00:00 AM2/24/98
to


If your primary network protocol is IPX/SPX, try changing to TCP/IP.
There's a KB article about this concerning NT 3.51 servers and Win 95
clients, but I suspect it's a problem with NT 4.0 as well.

Regards,

S.Y.

Havasu

unread,
Feb 25, 1998, 3:00:00 AM2/25/98
to

Steve Young <mer...@netins.net> wrote in article
<34F36D...@netins.net>...

>
>
> If your primary network protocol is IPX/SPX, try changing to TCP/IP.
> There's a KB article about this concerning NT 3.51 servers and Win 95
> clients, but I suspect it's a problem with NT 4.0 as well.
>
> Regards,
>
> S.Y.
>
In actual fact, my protocols were IPX and TCP/IP, however IPX has been
completely removed to no avail :-(.... The article you reffer to also
states NT 3.51, and is fixed with Service Pack 5, while we are running
NT4.0 and Service pack 3...

I am considering swapping the protocol back to Netbeui... While we had a
small (2 station) network on Netbeui, this was not an issue...

Could this be a solution?

Steve Johnston

unread,
Feb 25, 1998, 3:00:00 AM2/25/98
to Havasu

There was an extensive thread on this problem just a few days ago on
another newsgroup. Search Dejanews for "Disk Network or Human Error
Access" and you should see the entire thread. Cheap unmanaged hubs
contribute to this problem. Check out the thread, if I can be of any
help email me.
--
Steve Johnston


The Access Web ( http://home.att.net/~dashish ) Get yer questions
answered!
Access FAQ http://www.hammerdata.com/Newsgrp/ Right Here Right Now!
http://www.dejanews.com - Ask here first!
http://www.microsoft.com/kb/default.asp You paid for it - Use it!

pssssst! Here spammer spammer spammer
pyr...@ftc.gov, bbr...@ftc.gov, jche...@uspis.gov, fr...@uspis.gov

D Paul Phillips

unread,
Feb 25, 1998, 3:00:00 AM2/25/98
to
> If your primary network protocol is IPX/SPX, try changing to TCP/IP.
> There's a KB article about this concerning NT 3.51 servers and Win 95
> clients, but I suspect it's a problem with NT 4.0 as well.
>
> Regards,
>
> S.Y.
I have gotten a similar error on a database residing on a Novell 4.11
server. The problem was that I was running out of disk space alloted to
the client. Just an idea!

Steve Johnston

unread,
Feb 26, 1998, 3:00:00 AM2/26/98
to dpph...@mail.delcoelect.com

If you are not using DHCP to set your IP addresses check your machines
LMHOSTS file and your IP addresses in properties for your protocol,
(hopefully Netbeui and TCP/IP with TCP/IP being the default protocol
checked) and make sure that the IP addresses are the correct subnet and
that they match your LMHOSTS file.

You don't mention whether or not you have service packs installed on
your NT Server, Service pack 3 is required for stable performance. NT
had a serious memory corruption problem before SR-1 was released.

Tony Toews

unread,
Feb 27, 1998, 3:00:00 AM2/27/98
to

"Havasu" <bob...@stopspam.nbnet.nb.ca> wrote:

>this error (DISK OR
>NETWORK ERROR) , requireing a RECOVERY of the back end in order to continue
>normally, happens from 1 to 10 times a day!!!

I've also heard of a bad network card causing these kinda troubles.
If nothing else works try turning off each work station for a day one
by one and then, if nothing else, move the mdb off the server in case
it's network card is bad.

Tony
----
Message posted to newsgroup and emailed.
Tony Toews, Independent Computer Consultant
The Year 2000 crisis: Will my parents or your grand parents still be receiving
their pension in January, 2000? See www.granite.ab.ca/year2000 for more info.
Microsoft Access Hints, Tips & Accounting Systems at www.granite.ab.ca/accsmstr.htm

0 new messages