Ifmember login errors windows 2003

Posted on 2010-11-23
Medium Priority
Last Modified: 2012-05-10
We have users that just started getting a random error when mapping drives. We have login scripts that use ifmember statements to check membership and to assign resources. It works fine except for certain users get an error 122. This is in a Windows 2003 AD environment and on XP clients.

Here is a sample of the login script:

%logonserver%\netlogon\ifmember "group"
if not errorlevel 1 goto End
net use k: \\server\share /persisten:no

I can't figure out why this error is just happening on certain users and not system wide. I have tried replacing the ifmember program with an updated version and that did not work. The helpmsg states that error 122

The data area passes to a system call is too small.

Any help would be appreciated with this. I have looked all over the net and many have the issues but no fix has been found.

Question by:PVHS
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
LVL 66

Expert Comment

ID: 34198123

On teh ones that dont work, are they in too many groups by any chance? Any correlation between the users that do and do NOT work in regards to this? Remember, to account for nested groups as well....

Author Comment

ID: 34198329
Actually this user is in a TON of groups. Does that actually cause issues? She is a Director so has access to a ton of stuff.

LVL 85

Expert Comment

ID: 34199088
Yes, it is definitely an issue for some versions of ifmember.exe if the user is a member of a lot of groups. The problem is described here:
Ifmember causes Error 122

The version in the W2k(!) SP4 is supposedly fixed. The download is here:
Windows 2000 Service Pack 4 Network Install for IT Professionals

You can open the download in WinZip or 7Zip or WhateverZip, extract ifmember.ex_ (in the i386 folder), then expand ifmember.ex_ to ifmember.exe (which should finally leave you with an exe file of 5.392 bytes).
Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI


Author Comment

ID: 34199214
I tried that earlier and no luck. I found if I remove the ifmember check everything works fine but that is a work around. This particular user belongs to ~180 different groups which could include nested as well.

LVL 85

Expert Comment

ID: 34199284
Which ifmember.exe versions exactly have you tried so far (source, size in bytes and date)?

There are two other downloads available; I've used a version that didn't stall with large group memberships, but I don't remember which one finally worked.

Windows Server 2003 Resource Kit Tools

Windows 2000 Resource Kit Tools for administrative tasks

Author Comment

ID: 34199469
size: 6kb

Tried from 2k resource kit:
size: 10kb

Downloaded from 2k3 resource kit
size: 6kb

None of these worked for this user. It acts like it wants to work the initial run but doesn't do anything. Then after that I will get the 122 error.

I am stumped. Hopefully this goes away when we move to client side preferences and mapping drives through GPOs with 2008.
LVL 85

Expert Comment

ID: 34199590
Well, then you haven't tried the one from the W2k Service Pack 4 I described above.
Date is 06/19/2003, so later than the one from the W2k3 ResKit.

Author Comment

ID: 34199991
I have tried that one and yes it gets rid of the error but still doesn't map the drives. If I use that one it stops all users from mapping drives. It gives no errors now just get an hourglass and then nothing.

The file used was from:
size: 3kb
LVL 85

Accepted Solution

oBdA earned 2000 total points
ID: 34200114
Do NOT just rename the extracted ifmember.ex_ to ifmember.exe. As I said, ifmember.ex_ needs to be expanded, either with a zip program that supports this (7zip does), or using the command line:
expand -r ifmember.ex_

Author Comment

ID: 34200874
Ok you are the king. Thank you for being patient with me. After a lot of massaging, updating and expanding the correct ifmember (w2k SP4) all is working now. Thank you very much for your help.


Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Compliance and data security require steps be taken to prevent unauthorized users from copying data.  Here's one method to prevent data theft via USB drives (and writable optical media).
Let's recap what we learned from yesterday's Skyport Systems webinar.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.
Suggested Courses
Course of the Month13 days, 10 hours left to enroll

800 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question