We have seen this issue also. We have resorted to doing downloads to the local directory and having our 3rd party task processor move the files to their ultimate destinations rather than having the script directly write to remote locations.
I think if we can find or use a "refresh mapped connections" command of some sort within windows, we could have the script execute that command at the beginning of the script. I'm very interested to see if anyone knows of such a command and how we would implement it in BWS. Thank you, Mitch Lawrence Lead Applications Analyst Technical Support - NPR/Automation CHRISTUS Information Management *: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Send a "thank you <http://intranet.christushealth.org/spiritBuck/Default.asp> " to someone! ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen R. Smesny Sent: Wednesday, December 05, 2007 9:22 AM To: [email protected] Subject: [Talk] UNC vs mapped drives All of my scripts on my scripting server interact with other files on other servers. I have several mapped drives set up pointing to the appropriate folders. However, I run into problems as the mapped drives are very unreliable. They will disconnect and cause the the script to crash. The only other option I can think of is simply using the UNC path instead of a mapped drive. But I have been unsuccessfuly with this in the past. Will Boston Workstation recognize and interact properly using the UNC paths? If not, any recommendations on how to keep my mapped drives up? I have reconnect at login set to Y, but the machine is never logged off, so there is no logging in to reconnect the drive. Is there a VB command that I can run in the beginning of each script to make sure the drive is connected, All suggestions are appreciated. Thanks in advance, Stephen Smesny ********************************************************************** The information contained in this electronic communication, and any electronic attachment(s), is CONFIDENTIAL and is intended only for the named recipient(s) above. If the reader of this message is not the intended recipient(s), you are hereby notified that any release of information or distribution of this communication is prohibited by law. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender via reply email and delete this communication. ********************************************************************** This message was scanned with MIMESweeper.
<<image001.png>>
