Hi,

I am monitoring through a log file when a user loses connection to the SQL Server and if it recovers. At the same time there is an error log system that logs all other general errors.

I have noticed that yesterday, almost at the same time, twice, two users lost connection to the SQL Server and to the VM drive (where various meta files and the executable reside). I think that SQL Server connection was restored because the log showed that after attempt to recover, no more failure. But the application crashed based on the fact that it (the application) could not read the Shared drive (on the VM).

Should I just discount this as a glitch with the network where the station completely lost connection to the network?

Of course, I am thinking how can I recover - or attempt again - to have the application try connecting to the network, in order to restore the connection to the Share. The only way I possibly see it is by giving the application time (establishing a loop) whenever it tried to read a file or access a file on the Share. But there are SO many places where this is done, I can't think that it would be practical.

Any suggestions? It was suggested already to write the error to the local drive but I don't want to go this route. Because then I will completely lose the knowledge of possible issues.

TIA

UPDATE. I am thinking of setting a loop to read any file on the SHARE, at the very top of the application. Then, if the program cannot read this "dummy" file, it can show a message to the user and close "gracefully." And the same at the end of the application, when the file on the Share is accessed. This way, also, to check if there is a connection. And if not, close gracefully.
What do you think?