Folks-

We've received a couple of reports that when a system was upgraded to OI 4.1.2 with the upgrade posted yesterday that the users listed in the database manager disappear. The users can still log in, but the user information cannot be seen. Likewise, they cannot be listed from a LIST_USERS command from the system monitor.

Can anyone confirm or deny this? We cannot duplicate in-house.

Thanks-

Mike

Mike,

We do not have this problem on our end, however, we usually only create one user for each application. We have no trouble using LIST_USERS either.

[email protected]

SRP Computer Solutions, Inc.

This would affect multiple users only, but thanks anyway.

We have upgraded to 4.12 from the one posted on the board yesterday.

I looked at our user list and I see our users still listed there. Also, I ran List_Users and it seems okay to me.

Hope this helps,

Ray

Thanks Ray.

Have you created a new user, set up an expiration date, and then run list users? It should show more information…

Mike

Mike,

Upgraded from 4.0.3 to latest 4.1.2. All users show in User Management.

Defined a new user, with an Expiration Date. Also that user shows fine in User Management.

Ran the List_Users command in the System Editor. All users show, also the new one. After each user name the user level shows (0, 1, or 2). But the Expiration Date for the new user doesn't show. In its place there's just a "1".

- Oystein -

Oystein-

A list_Users should return the following:

SYSPROG, 2, ,

FOO, 0, 1,

BAR, 0, 2, 11/21/2002

Foo has a password that never expires

Bar has a password that expires 11 NOV 2002.

Are you sure that the new user has an expiration date?

Oystein,

If the new user shows in LIST_USERS like this:

NEW, 1, 2, 11/27/2002

then that user has a password that will expire on 11/27/2002.

However, if the new user shows in LIST_USERS like this:

NEW, 1, 1,

then that user is set such that their password will never expire.

Are you sure that the radio button was on the bottom option "Password expires on:" when you clicked the OK button? It's possible to pick a date from the calender (via the drop-down arrow), but still have the radio button set on the default of "Password never expires" and in that case the user will not have an expiration date set for them. The radio button must be selected on the bottom option for an expiration date to be set. I made it easier to be sure you're really setting an expiration date by having the calendar automatically pop up if the bottom radio button is selected, but that can be defeated if the calendar is brought up by clicking on the arrow to the right of the date (while not changing the radio button selection to the left of the calendar).

Jim

Mike,

I might have made mistakes.

One mistake I made was to select an expiration date without ticking Password expires on. But I think Password expires on should be ticked automatically once the user changes the expiration date. We're used to that from other programs. (I can give you examples if you like.)

Another mistake I made was to press the Update button after I had defined a new user. Then you can see the expiration date reverting to today's date. Pressing the Update button might be illogical when defining a new user, but I think it should be allowed. Or the Update button should be greyed out.

Once I got beyond these mistakes things brightened up. Here's a list of my users at a certain point:

REGIMUS 2

SYSPROG 2

BRUKAR1 0

BRUKAR2 0

BRUKAR3 0

TEST4 2

TEST_USER 0 1

TEST_USER2 0 2

TEST_ADM 1 2 11/30/2002

TEST_ADM2 1 2 11/30/2002

But then really odd things started happening:

REGIMUS 2 ??1× ¨2×

SYSPROG 2

BRUKAR1 0

BRUKAR2 0

BRUKAR3 0

TEST4 2

TEST_USER 0 01/01/1968

TEST_USER2 0 01/02/1968

TEST_ADM 1 01/02/1968

TEST_ADM2 1 01/02/1968

TEST_USER3 0 2

But I don't know what I did to cause it, except I defined yet another user.

- Oystein -

Jim,

I read your posting too late. But you can see I found out by myself that mistake with the expiration radio choice not being ticked.

- Oystein -

Oystein,

]]But I think Password expires on should be ticked automatically once ]]the user changes the expiration date. We're used to that from other ]]programs. (I can give you examples if you like.)

No need to give me examples - as soon as I answered your post I realized that this is the way it should work also, and I just finished making the code changes to make it so. The next time we have a new release, that feature will be in it.

I'm not quite sure what's going on with the other issues you posted, or exactly what should happen if update is pressed on a new user with an expiration date set. I'll have to talk to Mike about this.

Thanks for your feedback!

Jim

To continue the list of mistakes I made: The version of OI I did my tests in was the latest beta version of 4.1.2 and not the "final" 4.1.2 that was posted on Works November 6th and later withdrawn.

- Oystein -

View this thread on the Works forum...