Some users' profile cannot access a said path...

[Arun Mathew_2]

We have an HP L-1000 server running HP-UX v11.00. We use MFG/PRO as our ERP system running on Progress RDBMS. Recently, we migrated to ver. 9 of MFG/PRO and to ver. 8.3d ov Progress.

This has caused a unique problem. When the user's profiles were changed to access the PATH of the new versions of Progress and MFG/PRO, most users were able to log on to the system and later in to MFG/PRO too, but some (abt. 40%) of the users were not able to log onto the MFG/PRO system. It gave an error of a perticular program not being seen in the said PATH(s). However, on investigation we found that the same program was accessible from other profiles that were working with the same PATH configuration.

Now, as a work-arround, we changed the uid of all the users to the uid of the user that was working and also the home directory permissions to that of the working user id, and found that all users were able to log on to UNIX with their own user ID and also to MFG/PRO without any problems. However, the default user id that appears on the MFG/PRO log in would show that of the working user ID.

PLEASE HELP as we are now facing a problem in the second location where we are going live on Ver. 9 of MFG/PRO.

[Darrell Allen]

Hi Arun,

Here's a couple of things to think about.

My test shows that MFG/PRO sees all the users with the same numeric uid as the first one found in /etc/profile. I presume that's the working user you refer to. That's also pretty much now UNIX works. For example, ls -l will show the owner as the first loginid from /etc/passwd even if another loginid with the same uid created the file.

Did you verify all home directories and .profiles were owned by the correct loginid? Does the program file not seen by all users actually have the appropriate owner, group, and permissions to allow everyone to access it?

I suspect your issue is strictly a UNIX problem. We are running MGF/PRO 9.0 sp2 and Progress 8.3b without any issue of this kind.

Darrell

[Jim Turner]

Hi Arun,

Make sure all of your app dirs are mode 755. A dir must have read and run set for a user (whether owner, group, or world) in order for said user to cd to or *through* that dir.

All the best,
Jim

[Roger Baptiste]

Arun,

This seems to be a Unix permission/ownership
related issue. Make sure the profile/startup
files of the problem users are correctly
configured. If it is PATH issue, make
sure the PATH is pointing to all the
required directories.

A simple but careful comparision of a working user configuration and a non-working one would
point out the problem. This does not
seem to be an application problem.

-raj