Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
srinivaskv Respected Contributor.
Respected Contributor.
1625 views

is there any max number of drivers that get mapped in login

How to increase the number of drives that can be mapped in the Login scripts? Beyond 7 drives oes login from Windows gives error.
Labels (1)
0 Likes
11 Replies
Knowledge Partner
Knowledge Partner

Re: is there any max number of drivers that get mapped in login

On 11/08/18 10:34, srinivaskv wrote:

> How to increase the number of drives that can be mapped in the Login
> scripts? Beyond 7 drives oes login from Windows gives error.


It was my understanding that Windows (later versions at least) could
handle drive letters A through Z so 7 drives seems a little low and
suggests a problem somewhere.

Which version of Windows are you using?
Which version of the Novell/Micro Focus client are you using?
How are you mapping drives in the login script?

HTH.
--
Simon
Micro Focus Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------
0 Likes
Knowledge Partner
Knowledge Partner

Re: is there any max number of drivers that get mapped in login

In article <srinivaskv.8lu0yo@no-mx.forums.microfocus.com>, Srinivaskv
wrote:
> How to increase the number of drives that can be mapped in the Login
> scripts? Beyond 7 drives oes login from Windows gives error.


I've used up all 26 drive letters before (even without floppy drives
attached), and have clients who currently use more than a dozen. So
something is off and answering Simon's questions are a good start to
figuring this out.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Knowledge Partner
Knowledge Partner

Re: is there any max number of drivers that get mapped in login

Srinivaskv,
> Beyond 7 drives oes login from Windows gives error.


What error?

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
https://www.novell.com/products/enhancement-request.html

0 Likes
srinivaskv Respected Contributor.
Respected Contributor.

Re: is there any max number of drivers that get mapped in lo

Hi Simon and all,

This is the mapping I have in the login script
map s1:=\\lfa2\vol1\
map s2:=vol2:\
map s3:=vol3:\
map s4:=\\lfa2\vol4\
map s5:=\\lfa2\vol5\
map s6:=\\lfa2\vol6
map s7:=Vol2:\Srinivas
map s8:="\\lfa1\vol2\SupplierPlanning\Supplier Material Issue & Receipt"

I get this error when I login:
LOGIN-LGNWNT32-430: The following drive mapping operation could not be completed.
[S8:="\\lfa1\vol2\SupplierPlanning\Supplier Material Issue & Receipt"]
The error code was 9002.

After your questions, I went back and looked at the map command: Then If I try the following it succeeds.

map Z:=\\lfa2\vol1\
map Y:=vol2:\
map X:=vol3:\
map W:=\\lfa2\vol4\
map V:=\\lfa2\vol5\
map U:=\\lfa2\vol6
map T:=Vol2:\Srinivas
map S:="\\lfa1\vol2\SupplierPlanning\Supplier Material Issue & Receipt"

The s1.. version of map commands were in use for a long time before me.
The windows oes client version: oes 2 sp4 ir7
windows version : windows 10
0 Likes
Knowledge Partner
Knowledge Partner

Re: is there any max number of drivers that get mapped in login

On 14/08/18 05:16, srinivaskv wrote:

> This is the mapping I have in the login script
> map s1:=\\lfa2\vol1\
> map s2:=vol2:\
> map s3:=vol3:\
> map s4:=\\lfa2\vol4\
> map s5:=\\lfa2\vol5\
> map s6:=\\lfa2\vol6
> map s7:=Vol2:\Srinivas
> map s8:="\\lfa1\vol2\SupplierPlanning\Supplier Material Issue &
> Receipt"
>
> I get this error when I login:
> LOGIN-LGNWNT32-430: The following drive mapping operation could not be
> completed.
> [S8:="\\lfa1\vol2\SupplierPlanning\Supplier Material Issue &
> Receipt"]
> The error code was 9002.
>
> After your questions, I went back and looked at the map command: Then If
> I try the following it succeeds.
>
> map Z:=\\lfa2\vol1\
> map Y:=vol2:\
> map X:=vol3:\
> map W:=\\lfa2\vol4\
> map V:=\\lfa2\vol5\
> map U:=\\lfa2\vol6
> map T:=Vol2:\Srinivas
> map S:="\\lfa1\vol2\SupplierPlanning\Supplier Material Issue &
> Receipt"
>
> The s1.. version of map commands were in use for a long time before me.
> The windows oes client version: oes 2 sp4 ir7
> windows version : windows 10


My suspicion is it's your specific "map S:..." command that's failing
and throwing the error rather than hitting a limitation of number of
drives that can be mapped.

What happens if you comment out that specific map command and add
something like "map S:=\\lfa2\vol1" (yes it's a repeat of an earlier map
but that shouldn't stop it being mapped again, this time to S:) as a
test to see if S: can be mapped?

If the test S: map works that definitely confirms an issue with your
original "map S:..." command - two obvious things spring to mind, one
being the use of spaces and/or ampersand character (&), and the other is
that there appears to be double spaces between Material and Issue. Is
the latter correct is that a typo in your script?

HTH.
--
Simon
Micro Focus Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------
srinivaskv Respected Contributor.
Respected Contributor.

Re: is there any max number of drivers that get mapped in lo

Hi Simon,

If I change from s1, s2 , etc versions of map to S:, T: version (from search drive method to using Drive letter method), then it is working ok.
So It could be problem with using search drive notation. It may not be problem with folder names (At first I had problem with using folder names containing & and space, but that got solved by using quotes)
0 Likes
Knowledge Partner
Knowledge Partner

Re: is there any max number of drivers that get mapped in login

On 14/08/18 11:44, srinivaskv wrote:

> If I change from s1, s2 , etc versions of map to S:, T: version
> (from search drive method to using Drive letter method), then it is
> working ok.
> So It could be problem with using search drive notation. It may not be
> problem with folder names (At first I had problem with using folder
> names containing & and space, but that got solved by using quotes)


Sorry, I mixed up the s1, s2, etc. versions with drive letters in my reply.

Given that you're getting an error when using search drives (which maps
a drive letter then adds to the search path) I'm wondering whether it's
not a drive letter issue but that you're hitting the maximum length of
the PATH environment variable which is/was* 2047 characters?

You can test this theory by mapping S: (so not search drive) before your
"map s8:..." command - does it map as S:? i.e. if the "map s8:..." were
then to work you'd get R: mapped and added to PATH.

HTH.

*depends on which build of Windows 10 you're using
--
Simon
Micro Focus Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: is there any max number of drivers that get mapped in lo

Maybe you're just hitting the maximum length of the path variable. Should be easy to check by simply looking at it or extending the path before logging in to check whether the error strikes earlier in the script.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: is there any max number of drivers that get mapped in login

srinivaskv <srinivaskv@no-mx.forums.microfocus.com> wrote:

> If I change from s1, s2 , etc versions of map to S:, T: version
> (from search drive method to using Drive letter method), then it is
> working ok.


Potentially hitting some issue with the PATH variable is also a good
possibility, too. While Windows itself long ago increased the maximum
PATH variable data length, I do believe that the eDirectory login
script parser has a shorter limit. Or maybe that was when trying to
"SET" or "DOS SET" the PATH variable directly; I can't find a
reference to any known issue at the moment.

But the first thing that stands out is that the current MAP statement
syntax is "replace this item in the PATH with this search drive
mapping" (e.g. "MAP S1:" to overwrite first item in PATH, "MAP S2:" to
overwrite second item in PATH, etc.)

As opposed to "please insert this into the beginning of the PATH"
("MAP INS S1:") or "please insert this at the end of the path" ("MAP
INS S16:").

Which makes me wonder whether the error you got once you hit "MAP S8:"
wasn't simply because whatever was in the seventh position of the
existing PATH variable (the one replaced by the previous MAP
statement) was critical enough to cause failure when Windows tried to
handle the next MAP statement.

I would say "usually" you want network paths to be at the end of the
PATH contents, so that all local paths are searched first before
resorting to searching the network for things that will exist locally.
If that's the case, simply repeating "MAP INS S16:" for all of the MAP
statements might create the search drives in the most desired manner.

There could still be some other condition we're not expecting, such as
something that is unique with the PATH variable data that is already
set. (Since both MAP S1: or MAP INS S1: still have to parse and
understand what's in the PATH regardless.) So if MAP INS doesn't
already resolve it, maybe also confirm what's in the path before
starting the MAP statements.

Alan Adams
Client for Open Enterprise Server
Micro Focus
alan.adams@microfocus.com
0 Likes
srinivaskv Respected Contributor.
Respected Contributor.

Re: is there any max number of drivers that get mapped in lo

Hi All,

Thanks for all your suggestions.
1. I tried MAP INS S16: for all drives. I get the same error 9002 for the last drive (8th) mapping.
2. I reversed the order of mapping. Now also same error 9002 for the last drive in the list (8th).
3. I removed whole lot of paths from the PATH variable. and tried the above. Same error
4. I do mapping using drive letters: S:, T:, etc , no error.
5. I removed the path string with & and space and tried mapping (MAP INS) the simple path 8 times. Error at the eighth place.

There is some problem at the 8 mapping ... Anyhow, at present I realized this user does not require search drives at all. So I have changed his mapping to drive letters.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: is there any max number of drivers that get mapped in login

srinivaskv <srinivaskv@no-mx.forums.microfocus.com> wrote:

> There is some problem at the 8 mapping ... Anyhow, at present I realized
> this user does not require search drives at all. So I have changed his
> mapping to drive letters.


For the problem to follow "whatever is eighth in my "MAP Sx:" attempts
(whether INS or not), and "it's not to do with the current contents of
the PATH variable", and "it's not because we're colliding with
something else using the S: drive letter, because I can map it
successfully as a non-search drive"... this doesn't bring any kind of
further logical suspicion to me.

I think the next step would be concurrent Process Monitor and LAN
trace to see if either one could reveal a clue as to what's being
encountered on this machine when trying to map the eighth search
drive.

But yes, you would probably only want to spend time on that if the
user actually needed search drives in the first place. 🙂

"Search drives" are a bit of a legacy concept, much as "PATH
environment variable" also less important for Windows itself than in
the past. Certainly there are still situations where they are an
appropriate solution, and/or they are part of how an environment is
designed such that they're non-optional in a particular context.

But it's certainly also not unexpected or unusual that you could deem
them as unnecessary for this user on their current applications and
Windows platform.

Thanks for sharing what your follow-up findings were.

Alan Adams
Client for Open Enterprise Server
Micro Focus
alan.adams@microfocus.com
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.