Getting the message in Access "your network access was interrupted
Some users are getting the message Your network access was interrupted. To continue close the database and then open it again. We had it happen yesterday. I did a compact and repair on the BE and rebooted the server last night and again this morning.
It is not happening to all users. HELP!
It is not happening to all users. HELP!
ASKER
not using WIFI.
Ping is good.
load is less that 6%
It is a VM so only 1 NIC
Why is it only certain users. Tha's what puzzling
Ping is good.
load is less that 6%
It is a VM so only 1 NIC
Why is it only certain users. Tha's what puzzling
Do you host more than 1 VM....?
If yes try to assign a single physical NIC to this VM
If yes try to assign a single physical NIC to this VM
ASKER
Jim Dettman suggested it might be NIC Teaming
NIC Teaming is taking 2 or more NICs and making them act as one...the crucial point is that your Vms has at least 1 dedicated NIC with passthrough so nothing interrupts its networking...
Now we are talking about ...it comes to me ....i had a similar case with a VM as BE on a weak host...when i changed the host to a beefier one and assigned the NIC gor the VM all the issues went away.
Now we are talking about ...it comes to me ....i had a similar case with a VM as BE on a weak host...when i changed the host to a beefier one and assigned the NIC gor the VM all the issues went away.
ASKER
I removed the Teaming, reboot and the problem is solved. Is this because the database server is a VM?
Is more a "balance" issue...resources carefully assigned to VMs and a dedicated NIC to avoid network issues that might interfere with cases like Access which extremely sensitive....
Normally NIC teaming shouldn't be an issue because in the end you are presenting the NICs teamed as one but cases do arise
Normally NIC teaming shouldn't be an issue because in the end you are presenting the NICs teamed as one but cases do arise
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I think its better to ask Jim to drop by and award him the points...
ASKER
I thanked him. He is consulting for me.
ok then
1. Wifi ...Access doesn't like Wifi...Access wants steady network connections no matter what
2. Network issues...check your server latency...just ping it (ping -t) and let it run for a few minutes...except maybe the 1st ping everything should measure <1ms no matter what...No =1ms or 2ms or average <1ms...but always <1ms...
3. Server load...a server with high load...e.g. VM on a weak host is always a trouble source
4. Network issues...cables/switches..
5...Wrong NIC setting...had a server with 2 NIC...because they had different IPs (we were doing a test and forgot it) people start having all sort of issues
6. Database corruption...C&R is great but sometimes silently "fails"...check for tables with missing keys or play with the sorting Lower to Higher and vice versa to reveal some obscure values...indication of corruption.