[QUOTE=saihaynes;671898]+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
You've got a DNS problem then.
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.
This solved the issue temporarily and after lengthy discussions with Capita support they decided to do a fresh installation...voila no further problems.
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.
I have just had this error and it was caused by the data drive on our SIMS server being full.
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.
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
Also another option is set firewall up on your switch and disable the firewall on your server.
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
Hi, Tried that first and it never worked! :-)
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
and for good measure