version-controlclearcasecleartool

Checkout issue from Windows ClearCase client

A user cannot checkout from windows client ClearCase ( see picture)

And yet, the same user can checkout from a unix client.

Error message

Why?

Thanks for your answer @VonC

Please find my below findings

Here the primary group of the vob is 

/usr/atria/bin/cleartool desc vob:/vobs/MCT

versioned object base "/vobs/MCT"
  created 2010-03-03T16:42:52+02:00 by Admin.WTD (wtadmin.wtusers@frmrssucc004)
  "MSS Access"
  master replica: xh_mct_athens@/vobs/MCT
  replica name: xh_mct_athens
  VOB family feature level: 5
  modification by remote privileged user: allowed
  atomic checkin: disabled

  VOB ownership:
    owner *********servername***/ca_xhvadm
    group eelinnis.emea.nsn-net.net/ccusers_xhaul_athens

  ACLs enabled: No
  Attributes:
  FeatureLevel = 5
  Hyperlinks:
    AdminVOB -> vob:/vobs/MPTADMIN

And user id output is 

id karageor
uid=61333334(karageor) gid=8003(ccusers_xhaul_athens) 
groups=7000(hostingusers_cic_athens),8003(ccusers_xhaul_athens)

and on the windows the primary group is set as

Primary Group on Windows

Is the unix group ccusers_xhaul_athens has to be set as windows primary group on system variable

Kindly confirm

Solution

  • The main factor which explain a permission issue in a ClearCase interop (Windows ClearCase client - Linux ClearCase server) is the CLEARCASE_PRIMARY_GROUP environment variable.

    That variable (CLEARCASE_PRIMARY_GROUP) needs to:

    Make sure on Windows the user is not launching the client with another account (Administrator, or System account), and the CLEARCASE_PRIMARY_GROUP is set.
    (and the number of group is not too high)

    You can use the creds utility to see your credentials.

    See more at "ClearCase won't allow Check-In" and use the credmap utility to verify the group assignments between Windows and Unix.

    Type set CL in a CMD shell in Windows to see the actual full value of the CLEARCASE_PRIMAY_GROUP environment variable (??_EE_CLEARCASE_USERS_XHAUL_ATHENS)

    You need to see if that group maps to the Linux one.

    Check also the protection associated to your view. See fix_prot on Windows here.