Sims error - Reason 5???

[cophighschool]

I am having some trouble with Sims (I know nobody can believe that right).

Upon logging in an error message appears "SIMS Connection failed for Login (username), reason: 5"

This seems to only effect laptops that are connecting via wireless network.

Any help available would be appreciated.

We have had some nice chats with Capita but that is about as far as it goes!

[dezt]

Are the laptops mapping the s: drive across?

We had a similar problem that was down to the worng DNS settings being applied via DHCP. Check your ip settings are correct via ipconfig /all.

Check the connect.ini file for problems.

[cophighschool]

Thanks for the reply

DNS/DHCP settings working fine, connect.ini file shows no abnormalities.

Also the laptops are mapped to the s:\ drive so i dont think its an issue with accessing the drive. Thinking it may be an issue with authentication. We have about 7 known incidents out of about 150 laptops, so it seems somewhat isolated.

[AnnDroyd]

Do you have a connect.ini in your program files which redirects to the copy on drive s?

If so, try replacing it with the drive S version so the laptop connects straight to the sql server rather than being passed from one connect.ini file to another.

[Ric_]

Do the laptops have offline files enabled?

I've noticed that laptops that are used on wireless occasionally get stuck in offline mode which makes weird things happen.

[Oops_my_bad]

Reason #5 - another good reason not to choose SIMS

[cophighschool]

Valid point about the offline files, though it doesnt seem to be the cause of this problem as the laptops login to SIMS fine over the LAN connection just not the wireless. Seemed to have solved one by running a batch file created for a previous problem that replaces a few of the .dll files, but this hasnt worked on any of the others.

Have also tried replacing the connect.ini files but to no avail.

Capitas only idea is to detach and reattach the database..

Any ideas would be helpfull, or anyone else who is having a similar problem

[splattthecat]

Is the SIMS .ini on the laptop pointing to the correct location for the setps folder.

It might be worth manually running the SIMSApplicationSetup.exe from the SIMS\Setups folder to ensure the client software versions are up to date.

[triskelion69]

Anyone got anywhere with this?

I actually followed Capita's supposed "fix", the only outcome was slightly angrier than normal Admin staff!

It is strange that it seems to work without wireless... 8O

edit: Have also tried replacing sims.ini, de/re-installing SIMS, installing SIMSAPPLICATIONSETUP and SIMSSQLAPPLICATIONSETUP, detaching/reattaching database, all to no avail.

[apeo]

Oh joy another one of those error, ive had 3 of these so far but not reason 5. Try checking the sims.ini in the windows directory as someone said and uninstall the simsinfrastructure. Reboot, delete the SIMS .NET folder and run simsinst. Reboot and see if it fixes it.

EDIT: Detach the database?? is that on the server?

[cophighschool]

After narrowing things down a bit, I have found a solution. Re-install the OS and SIMS etc then it seems to work nicely.

I can only assume that when the August Update was applied, it upset a setting perhaps in the registry on laptops with a certain config. Have used known good Sims.ini and Connect.ini files but to no avail. So currently spending half a day rebuilding a laptop is quicker than spending several days trying to work it out.

Have also tried reinstalling sims after completely removing it and running SimsApplicationsetup and neither works.

Being part of the Network support staff I decided against detaching and reattaching the database but nice to hear it doesnt work!

In the mean time if anyone finds a more subtle solution please share

[Oops_my_bad]

Re-attach the database? That's almost as priceless (if a little extreme) as the old "turn it off and on again" routine!

[DMcCoy]

Reattaching with dbattach recreates the sims and simsinit users I believe, which are used by all sims accounts on sql 2000. So it does actually do something :P

To fix this all I did was remove the erroneous lines from my connect.ini on the local machine.