Network share time out; software crashes
-
Over the last few weeks my HR Director has has Abra Suite crash on him. Today while looking at another issue I also checked on this. He had been using it, went to lunch and had not used it since.
The application appeared to be running. But when you tried to update a employee record it crashed.
For what ever reason I checked the network shares, which seemed to be okay (via MY Computer). But I also decided to check via CMD:\Net Use.
This CMD screen shows the M: is mapped and 'OK' but before I used My Computer and doubled clicked on it, it showed Disconnected (as \fiscalserver2.. shows).
Once the status was OK - the application was able to connected again.
What would cause it to disconnect and how can I prevent that?
-
@g.jacobse said:
Over the last few weeks my HR Director has has Abra Suite crash on him. Today while looking at another issue I also checked on this. He had been using it, went to lunch and had not used it since.
The application appeared to be running. But when you tried to update a employee record it crashed.
For what ever reason I checked the network shares, which seemed to be okay (via MY Computer). But I also decided to check via CMD:\Net Use.
This CMD screen shows the M: is mapped and 'OK' but before I used My Computer and doubled clicked on it, it showed Disconnected (as \fiscalserver2.. shows).
Once the status was OK - the application was able to connected again.
What would cause it to disconnect and how can I prevent that?
A timeout of some sort or a permissions change? Try running the command "net use /persistent:yes".
-
@thanksaj
To my knowledge it is not a permission change. This seems to be a time out issue. The drive is mapped, set to reconnect on login and using the correct credentials (for the person).The software will crash about 4 or 5 times a day. And my guess is that each time it's 'dropping' the connection.
-
What is sharing the share?
-
What is happening is the mapped drive is sitting idle for 15 min and then disconnecting to free up resources. DB applications such as yours get these errors because this connection is not persistent as g.jacobse has eluded to with the /persistent:yes command. This will keep the drive mapped but does not stop the idle timeout from occuring which will continue your error.
Do this on the machines in question: (also can be deployed via Group policy script)
Open CMD then right click and run as administrator
net config server /autodisconnect:-1
This will set the autodisconnect to never disconnect and you should not see this error any more.
Give it a try and report back your findings.
