Date: Mon, 18 Oct 2010 07:33:49 -0400
Reply-To: Arthur Tabachneck <art297@NETSCAPE.NET>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Arthur Tabachneck <art297@NETSCAPE.NET>
Subject: Re: Mapped Drive Problems
Craig,
I don't know if what worked for me will provide an equally good solution
for you, but it may be worth a try. We confronted a similar problem when
we first went to a server version of SAS and discovered that not
everyones' computers were mapped the same way.
Our solution was to include some dot net calls, in a batch file, that were
run whenever the user booted up. For example:
net use g: /delete
net use h: /delete
net use i: /delete
net use s: /delete
net use k: /delete
net use m: /delete
net use g: \\fileshare.intranet.ibc.ca\vicc\vol1
net use h: \\fileshare.intranet.ibc.ca\vicc\vol2
net use i: \\fileshare.intranet.ibc.ca\vicc
net use s: \\winsrvp03\sastemp\vinlink
net use k: \\winsrvp03\sastemp
net use m: \\intranet.ibc.ca\dfsroot
HTH,
Art
--------
On Sun, 17 Oct 2010 22:45:31 -0500, Craig Johnson <cjohns38@GMAIL.COM>
wrote:
>Correction - if I actually try and use a libname to datafiles on the drive
>it works (\\server\whatever\_) rather than S:\whatever\. However, if you
>try and open a program from the file menu it doesn't work because the
drive
>doesn't even show up.
>
>On Sun, Oct 17, 2010 at 10:38 PM, Craig Johnson <cjohns38@gmail.com>
wrote:
>
>> Yep, it's visible and usable under windows explorer. It's not visible
under
>> 'Computer' in SAS so you can't libname to it. It's like SAS doesn't
consider
>> it real.
>>
>>
>> On Sun, Oct 17, 2010 at 10:34 PM, Joe Matise <snoopy369@gmail.com>
wrote:
>>
>>> Is it visible in windows explorer? If so then it ought to be visible
in
>>> SAS, I'd think, unless something isn't set up right.
>>>
>>> If it is visible in windows, can you LIBNAME to it? Either by the
mapped
>>> drive, or the UNC path to it (Assuming you have it set up as a UNC
directory
>>> tree, or whatever filesystem you're using)?
>>>
>>> -Joe
>>>
>>>
>>> On Sun, Oct 17, 2010 at 10:21 PM, Craig Johnson
<cjohns38@gmail.com>wrote:
>>>
>>>> All of our SAS programs and a large chunk of SAS data files are
stored on
>>>> the shared drive so when they don't show up on the persons SAS
explorder
>>>> window it's a pretty big problem. It requires the person to
transfer the
>>>> data sets to their PC and rewrite code.
>>>>
>>>> I've been struggling with this for quite a while and have no idea why
SAS
>>>> isn't reading the mapped drive. Every other PC we'ved installed SAS
on has
>>>> picked the mapped drive up.
>>>>
>>>> This PC is running Windows 7, SAS 9.2 32 bit (we tried the 64 bit with
>>>> similar results so not sure what is going on.
>>>>
>>>> Hopefully someone has some input because this is pretty frustrating.
>>>>
>>>>
>>>> On Sun, Oct 17, 2010 at 10:16 PM, Joe Matise
<snoopy369@gmail.com>wrote:
>>>>
>>>>> What do you mean not showing up, and what does this have to do with
>>>>> SAS? (Also, what kind of computer/OS?)
>>>>>
>>>>> -Joe
>>>>>
>>>>>
>>>>> On Sun, Oct 17, 2010 at 10:09 PM, Craig Johnson
<cjohns38@gmail.com>wrote:
>>>>>
>>>>>> We have a mapped drive that we use and it's not showing up on a
>>>>>> computer.
>>>>>> I've uninstalled sas and reinstalled and it's not showing up. Any
>>>>>> suggestions on what might be causing this or how to fix it?
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
| 
