It's a known issue which relates to how auto-recover operates with a mapped network drive. You will find it discussed in detail in
This Thread together with some solutions/work-arounds. The best workaround would seem to be the one mentioned in the last few posts.
PDR