Sims.net adding new personnel officer [solved]

[sakwoya]

Hi all

 

I am having a struggle with sims.net - here's what's happening...

 

New member of staff to be added as a Sims.net user with membership of the Personnel Assistant group.

 

Yesterday Bursar added the staff member using the Focus > System Manager > Add Existing People as users of the System, she thinks she also added the new user to the group 'Personnel Assistants'.

 

New user unable to logon - gets 'incorrect username/password' popup.

 

Today I checked the settings and the new user is visible, no group was assigned so I have reassigned her to the Personnel Assistants group (this may be a red herring though)

 

Can anybody suggest why the user is getting 'incorrect username/password'?

 

Graeme

 

------------------------------------------------------------

Edited March 9, 2010 by sakwoya

[Tyiell]

Asside for the possibility of her being a bit of a password idiot, it might be worth checking that there isn't another member of staff with the same or similar name (particularly one who has left and doesn't show up unless you search Staff - All rather than Staff - Current).

 

I believe when you add a new member of staff Sims likes to pop up and helpfully say "that new person your putting in, John Smith, looks like this person, Johnathon Smith. Is it the same contact?" One moments inattention, and the bursar clicks "yes" and it re-enables the old member of staff instead of creating the new.

 

This has caused trouble for us in the past - several members of staff have been found to have duplicate records and so have two usernames and passwords. This is escpecially common for us since our HR department are a bit rubbish at reading messages from Sims - they just click "yes" to everything

 

Hope that helps!

[vikpaw]

start with checking username is correct, they should be unique right...?

then reset password and log in yourself with those credentials.

 

i've had this problem where they think they need to click the 'change password' box, this doesn't need to be done on first log on and causes an infarction.

 

to resolve i had to completely remove user and then add them in again. once this caused me to wait a day as system just wasn't having it, i think this time it was an existing user who just thought they'd try and click the change password box. never worked for me personally so i tell people not to touch it. especially new users.

 

other issue can be start dates, when adding users and group memberships i often backdate the membership if possible. as it can have an effect - or appears to.

 

but the main thing i would say is to remove user, and re-add to the list of users. then apply group permission again for testing.

[sakwoya]

but the main thing i would say is to remove user, and re-add to the list of users. then apply group permission again for testing.

 

Hi all

 

The above worked - changing dates, resetting passwords failed. Just recreated the user, added to group and -tada! New user.

 

Second problem - new user logs in, logs out, logs in again but gets an 'incorrect G:sims\connect.ini file' warning - edited the connect.ini from

[sIMSConnection]

ServerName=server\SIMS2005

 

to

 

[sIMSConnection]

ServerName=172.16.1.11\SIMS2005

 

Logon works - why is that?

 

Graeme

[Tyiell]

 

Second problem - new user logs in, logs out, logs in again but gets an 'incorrect G:sims\connect.ini file' warning - edited the connect.ini from

[sIMSConnection]

ServerName=server\SIMS2005

 

to

 

[sIMSConnection]

ServerName=172.16.1.11\SIMS2005

 

Logon works - why is that?

 

 

Hmm. Never seen that before, our always works with the server name. Maybe a dns problem?? Can they browse to the G:\ when this happens?

[vikpaw]

is this everywhere?

check dns, it could be up the creek.

check the user's mapped drive, is it correct? does it save to their profile or is an old / incorrectly mapped drive on a different pc causing a hiccup.

The local connect.ini should redirect to the mapped drive.

If you are editing the connect.ini on the mapped drive which is the global one for all to use, all users would experience this problem.

[sakwoya]

Hi

 

Mapping is correct and local connect.ini is:

[sIMSConnection]

Redirect=G:\SIMS

 

Browsing to the G: drive is possible

 

DNS and Hosts file are correct.

 

I seem to remember this happening before on another workstation and I got around it by setting a timeout in the connect.ini file - I've added that in to see what happens (also taken the IP address out of the connect.ini file and replaced with the server name).

 

The fault is intermittent (as before) and I think the timeout takes place because the 'server' is simply too busy (it's a peer to peer network and the 'server' also was running FMS and a SIMS workstation when the failure took place

 

Graeme

[vikpaw]

FYI

My connect.ini:

 

 
[sIMSConnection]
ServerName=SQLserver1\MIS
DatabaseName=SIMS2008
CommandTimeout=10000
[Reports]
MaxNumberOfTableJoins=1

[sakwoya]

Hi

 

So far (touching wood) no repeat of the login error so I'm assuming that the timeout correction has done the trick

 

Thanks

 

Graeme