[sims] SIMS Connection failed for Login USERNAME reason: 0

[tech_guy]

Hi,

 

A number of users have come in this morning and are getting the "SIMS Connection failed for Login USERNAME reason: 0" error message when logging into SIMS .net.

 

Other users are able to login successfully on the same workstations.

 

We've had a look at Capita's KB72254 article but none of the seven fixes seem applicable to us.

 

Any suggestions?

[Mcshammer_dj]

check that sql is runing and that the tcp is available as a protocol.

 

check the connect.ini

[Ric_]

I had this recently. Re-installing SIMS on the client fixed the problem.

 

Mine were fresh installs and I put it down to a couple of them borking the settings.

[tech_guy]

Thank's it's a weird one though - it's not the clients as I and others are able to successfully log in to Sims.Net on machines that the affected users can't?!

[Ric_]

Thank's it's a weird one though - it's not the clients as I and others are able to successfully log in to Sims.Net on machines that the affected users can't?!

 

But can you log into SIMS whilst the machine is logged in as an affected user?

 

I seem to remember that I could log in but others could not on our machines. A quick re-install fixed the problem and I didn't lose any sleep over it

[Mcshammer_dj]

check user rights to the drives. Can the users see the sims.ini in the windows folder and can they see the connect.ini in the Program files\sims\sims .net folder.

 

If this is a redirect can they see the redirected connect.ini

[tech_guy]

Yeah, no problems with perms or getting to the correct connect.ini.

 

It's weird why it's only a handful of people affected and not workstation specific.

[EduTech]

Yh i have come accross this before, as ric_ say's it's got to the point where its onluy a handful of clients/users, restarted the machine, re-connected to the mapped drive (if you hadone)

 

But in the end, just a re-inst of sims fixed the problem!

 

James.

[tech_guy]

Just trying a re-install on a client now.

[Mcshammer_dj]

don't see how this is aclient issue if it works for some people.

 

This may be a profile issue as I know that sims will write data to the my documents folder and will check this area to create the files.

 

Have you tried login to network with a user that is failing and then try sims with a known working users??

[tech_guy]

Same problem even after a reinstall.

 

[tech_guy]

don't see how this is aclient issue if it works for some people.

 

This may be a profile issue as I know that sims will write data to the my documents folder and will check this area to create the files.

 

Have you tried login to network with a user that is failing and then try sims with a known working users??

 

Yes, I agree that it seems to be a server issue not a client issue.

 

Yes, we've logged on as a user that can't login in to SIMS.NET, then successfully logged in to SIMS.NET as a user who doesn't have the problem.

[tech_guy]

In the SQL logs it is showing users with the issue as having either a state 5 or a state 8 problem - confusing as we know their usernames and passwords are correct!?

[atfnet]

Hi tech_guy,

 

Had this problem last week every time I reset a password or changed permissions in system manager. As a temporary fix dismount and remount the database.

 

Capita have a password reset patch but it corrupted our database and I had to restore from a backup.

I am awaiting a new patch.

 

Hope this helps

 

Andy

[Mcshammer_dj]

Hi tech_guy,

 

Had this problem last week every time I reset a password or changed permissions in system manager. As a temporary fix dismount and remount the database.

 

Capita have a password reset patch but it corrupted our database and I had to restore from a backup.

I am awaiting a new patch.

 

Hope this helps

 

Andy

 

SO you are finding that if you make a change in system manager it cause all users to fail? or certain users to fail?

[atfnet]

Hi,

 

The problem is with all users, and some depending on the wether. Capita have now suggested i re apply the patch using the sysman account.

 

Andy

[itboss]

Hi tech_guy,

 

Had this problem last week every time I reset a password or changed permissions in system manager. As a temporary fix dismount and remount the database.

 

Capita have a password reset patch but it corrupted our database and I had to restore from a backup.

I am awaiting a new patch.

 

Hope this helps

 

Andy

 

 

when I got this problem ( Connection Failed Reason 0) after some investigation and experimentation the following worked

 

1. If logging on remotely using a script to map the drives so you get a S:\sims drive mapped >> change the names of the servers to their internal IP addresses in the logon script

 

2. on the local machine go to the sims installation in c:\program files or where-ever

 

>> DELETE the Connect.ini file ( make sure you are on the LOCAL Machine NOT server !) Then try to run SIMS or Pulsar.exe - it will give 'can't find connect.ini' error

 

>> BROWSE to the Connect.ini file on S: Drive Sims folder

 

>> connection became established

[amvc]

Had this too, cured by changing the local connect.ini to point directly to the server instead of to the servers connect.ini.

 

So, changed from

 

[sIMSConnection]

Redirect=S:\sims

 

to

 

[sIMSConnection]

Servername=mis-sr-sims

DatabaseName=SIMS_220807

 

 

Jon

[creese]

Had this too, cured by changing the local connect.ini to point directly to the server instead of to the servers connect.ini.

 

So, changed from

 

[sIMSConnection]

Redirect=S:\sims

 

to

 

[sIMSConnection]

Servername=mis-sr-sims

DatabaseName=SIMS_220807

 

 

Jon

 

We never use redirect but had massive problem, which now seem to have settled down. Fingers crossed and touching anything wooden.

[mac_shinobi]

Not sure if this is still relevant but in the sims setup directory somewhere is there a simsperm.bat file ?

 

If so run that and that should correct the permissions for sims

[ndavies]

Moved SIMS from an old server to a brand new one today..sims runs fine on this server but same issue Reason 0 on workstations. Tried all of the KB suggestions...plus the ones on here, anybody got any more advice...

 

Cheers

[matt40k]

Firewall on the server? Is TCP\IP enabled? Edited August 10, 2009 by matt40k

[dhicks]

sims runs fine on this server but same issue Reason 0 on workstations.

 

Remember that each SIMS client needs to connect to your SQL server, so you have to let whatever port SQL Server uses through your firewall and ensure that SQL Server knows multiple clients will be connecting (and you have to buy SQL Server CALs for the appropriate number of clients). Same goes for the SIMS document server - it runs on port 8080 by default (I think), so make sure that can get through your firewall too.

 

--

David Hicks

[ndavies]

Grrr...it was a mapped drive thing...set the new one up as S when the old one was G....changed the S to G (like Chain Letters) and it's fine...I did re-run simsinst with S instead but it didn't like it...

[dolly3900]

Had this several times and this seens to do it for me.

 

Connect.ini

[sIMSConnection]

Redirect=S:\sims

 

changed to

[sIMSConnection]

Redirect=\\[server Name]\[sims Share]\sims

 

Like a charm.

Mike