Jump to content

SIMS Connection failed for Login USERNAME reason: 0

tech_guy

By tech_guy
in MIS Systems

 Share

Recommended Posts

vikpaw

vikpaw

Posted
Posted
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

 

That kind of implies that the S: drive wasn't mapping correctly, though if that's the case, it's not usually a reason 0, that occurs.

dolly3900

dolly3900

Posted
Posted

The reason 0 is apparrently due to not connecting to the database, so an incomplete mapping or redirection would cause this error.

 

The problem (with mine) seems to be that despite the mapping being correct and being able to browse the drive, the connect.ini was not pickingup the mapped drive for some reason (probably reason 0 {sorry}).

 

When the local connect.ini was modified to look at the path rather than the drive, it sorted this problem out for me.

 

One thing I will say is that to make sure of the correct server being pointed to, I modified the Hosts file to make sure the local machine was loing at the correct IP address for the server, rather than relying on the DNS to pick it up.

 

Hope this helps someone

 

Mike

vikpaw

vikpaw

Posted
Posted
Maybe S was in conflict with something else, USB key, we've had that, or they didn't have permission to see the local connect.ini, though i don't think either of those would result in a reason 0.
Alfred_Bester

Alfred_Bester

Posted
Posted
The tech at one of our schools had this yesterday after uninstalling SQL2005 (he had upgraded to 2008 the week before). He reported that he got it working again after reinstalling SQL Server Native client.
  • 3 months later...
saihaynes

saihaynes

Posted
Posted
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

 

+1 for this resolving the issue

 

Sai

  • 1 month later...
gcurran1982

gcurran1982

Posted
Posted
+1 for this resolving the issue

 

I had the same problem with a new machine. In the end i changed the connect ini file. Instead of the server name i entered the ip address instead worked fine after that

vikpaw

vikpaw

Posted
Posted (edited)

Also, with windows 7 it does matter how the S: drive is mapped. If it's mapped as admin, you need to runas admin to see it, even though the user can browse. Or vice versa, it can be complex and is to do with the permissions within windows 7. Our drives were previously mapped by script, and some users were running sims 'as administrator' to help troubleshoot some issues, all was fine....

 

Recently, the drive mappings have been done by group policy in windows 2008, and all the users that were running as admin would get an "incorrect S:\sims\connect.ini" error yet could browse the S drive fine. If i got them to run a script that remapped the drive under their account it was fine. Now, we've taken the 'runas admin' tick off, and they are happily connecting again.

 

Weird, and took a while to troubleshoot, but i wasn't happy with the NMs workaround to just give them a manually created connect.ini with a servershare listed.

Edited by vikpaw
clarity
  • 10 months later...
saihaynes

saihaynes

Posted
Posted
Just make sure you're not planning a server migration in the near future ;)

 

No DNS issues at all thanks :), we are a mixed environment network running primarily mac some windows and some linux so DNS has to be spot on! Only started happening after the school had paid capita to upgrade to 2008 (prior to my arrival)

 

This solved the issue temporarily and after lengthy discussions with Capita support they decided to do a fresh installation...voila no further problems.

  • 6 months later...
renegade

renegade

Posted
Posted

Just in case anyone has this error in future:

 

It is normally caused by a machine pointing to an incorrect connect.ini, CAPITA normally set machines to point to S:\sims\connect.ini so if this file is correct a workstation could be looking to the local sims folder instead. Correct this error and it will log on fine.

  • 1 month later...
  • 2 months later...
Aelfwine

Aelfwine

Posted
Posted
Came in this morning to this error for all users. Quick look on SIMS server revealed that the SQL drive was full, removed some of the older backups to free up space and users could login again.
  • Thanks 1
  • 1 month later...
KDMann

KDMann

Posted
Posted

I had this problem after a day i gave up with Capita and took a approach into my own hands and fixed the issue if you go into firewall and add 4 exceptions this will solve your issue these are as followed

 

Pulsar - Sims.exe (Program)

SQLSERVERBROWSER - PORT:1434 UDP

SQLTCPPORT - PORT:1433 TCP

TCPDYNAMICPORT - PORT:4894 TCP

  • 1 year later...
Luap

Luap

Posted
Posted (edited)
Hi Guys, I have found that when this occurs, rename the folder c:\program Files\Sims to simsold and just copy the folder from another working computer. Easy as that. Have fun. Paul Edited by Luap
spelling
MrMat

MrMat

Posted
Posted
Hi Guys, I have found that when this occurs, rename the folder c:\program Files\Sims to simsold and just copy the folder from another working computer. Easy as that. Have fun. Paul

 

That's over complicating it a little bit, just copy the connect.ini file from a working computer and paste it into the SIMS.net folder ;)

  • 3 months later...
joeprice

joeprice

Posted
Posted

I've just had this issue when installing the client on a different subnet to the server. The SIMS installation writes a connect.ini with just the REDIRECT parameter in. I solved the problem by also including

ServerName=\SIMS2012

and for good measure

DatabaseName=SIMSwhatever

ServerType=SIMSSQL

  • 1 year later...
  • 5 weeks later...
RichardHarvey

RichardHarvey

Posted
Posted

Ah Sims.NET. . . My old nemesis. . .

 

One of my schools had this issue on several machines this week after a Sims update. The Sims.ini file in C:Windows was looking for the IP address of the server. On the machines that it worked, it was looking for the name of the server. Don't know why it should make a difference!

 

Just copied & pasted the Sims.ini from the a machine that working and it fixed the issue!

  • 10 months later...
tonyd

tonyd

Posted
Posted
I've another source of this issue - at some point our SIMS server decided it was not really connected to our LAN but was instead on a public network, and so it enabled it's firewall and blocked all connections attempts! Firewall now disabled while I figure out why this happened.
  • 8 years later...
rossibIT

rossibIT

Posted
Posted

Bringing up an old post but I am getting this issue when using SIMS connected. How can I solve this with no S: or connect.ini file to play with.


Regards

Ross

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...