Sims Reason 0

[FN-GM]

Hi,

 

I have just built a new image on some machines. I have installed sims but when i try to login i get error message reason 0. (sorry cant recall the full error message)

 

The connect.ini is all fine and this is on an account using full domain admin rights. The machine is fully patched up with MS updates. I have also tried removing sims and starting a fresh. The same windows account and sims account work fine on another machine its just these causing the problem.

 

Does anyone have any ideas please? I have logged a call but thought i might as well give it a shot on here.

 

Thanks

 

Z

[Messa]

As mad as it sounds last i saw this it was related to either there being no default printer set or printers in the printers and faxes folder that don't exist anymore.

 

Give that a try?

 

HTH

[FN-GM]

As mad as it sounds last i saw this it was related to either there being no default printer set or printers in the printers and faxes folder that don't exist anymore.

 

Give that a try?

 

HTH

 

Hmmm you know what it is very possible that none of the printers are set to default. I will check tomorrow....

[michael2k6]

I am not a SIMS person, but Login reason 0 in SQL is a login failure, bad loginID, password, or SQL might be set to only use windows authentication not SQL, or there might be a SQL login with a weak password, and 'enforce password policy' checked, and now the windows password gp has been turned on or strengthened?

 

I don't know whether SIMS uses Windows Authentication or SQL, or how it connects, etc, etc, but if the printers don't work, try checking out the logins.

 

It might even be that it can't see the SQL server.

Please don't waste too much time on my suggestions though i have no basis to offer advice on this one!

[FN-GM]

I am not a SIMS person, but Login reason 0 in SQL is a login failure, bad loginID, password, or SQL might be set to only use windows authentication not SQL, or there might be a SQL login with a weak password, and 'enforce password policy' checked, and now the windows password gp has been turned on or strengthened?

 

I don't know whether SIMS uses Windows Authentication or SQL, or how it connects, etc, etc, but if the printers don't work, try checking out the logins.

 

It might even be that it can't see the SQL server.

Please don't waste too much time on my suggestions though i have no basis to offer advice on this one!

 

Thanks for the suggestions but its nothing to do with the server as all other clients work fine and so does the sims account on other machines.

 

The problem is actually with the client.

[FN-GM]

Can you log into SIMS from another workstation?

 

If not, have you enabled TCP/IP in the SQL Server settings (if you install full SQL or use the SQL Express installer from Microsoft the default is for that to be disabled) and if the server has a firewall enabled then you'll need to either add the SQL Server service executable to the exception list or manually add the ports.

 

Also, if you can log in on other workstations, and it only seems like one or two user accounts wont work, try to detach then reattach the database; that usually sorts a bunch of stuff out.

 

not being rude but if you look up there all your questions are answered.

 

1. its not a server fault.

2. the users are fine on another machine

 

It is a problem with the client machine.

 

Thanks anyway

[Messa]

FNGM - Have you ruled out the printer issue yet?

[FN-GM]

FNGM - Have you ruled out the printer issue yet?

 

Just checked this wasn't the issue.

 

Thanks anyway

[Jamo]

I have had that issue before and reason 0 is when it cannot connect to the server for whatever reason. It happened to us as our server was creaking and v old, so when loads of people were logging on some just gave reason 0 errors. Since we have had a new server it has stopped.

 

I believe we also had it when SIMS tried to update and managed to lock the database then the update failed and the database wasn't unlocked.

 

Only thing I can think is check mapped drives and recreate the connect.ini

 

Sorry I cant be more specific I don't have much to do with the inners of SIMS as county support it our end.

[bossman]

@FN-GM:

 

Have you ran the simsperm.bat on the client from the server?

you probably have knowing you but just thought that it may be client id problem.

[scebe427]

not being rude but if you look up there all your questions are answered.

 

1. its not a server fault.

2. the users are fine on another machine

 

It is a problem with the client machine.

 

Thanks anyway

 

Missed that last post of yours. if you install management studio on the client can you access the server that way?

[kentt]

Hi,

 

I have just built a new image on some machines. I have installed sims but when i try to login i get error message reason 0. (sorry cant recall the full error message)

 

The connect.ini is all fine and this is on an account using full domain admin rights. The machine is fully patched up with MS updates. I have also tried removing sims and starting a fresh. The same windows account and sims account work fine on another machine its just these causing the problem.

 

Does anyone have any ideas please? I have logged a call but thought i might as well give it a shot on here.

 

Thanks

 

Z

 

 

I have had odd faults in the past with the locally stored Sims *.XML file becoming corrupt. But this only generally affects an individual sims users on that client, but it would not harm to rename the “C:\Documents and Settings\%username%\Mydocuments\My SIMS Documents\%Username% folder as Sims will generate another one.

 

"He says, clutching at straws"

[FN-GM]

@FN-GM:

 

Have you ran the simsperm.bat on the client from the server?

you probably have knowing you but just thought that it may be client id problem.

 

We dont normally use it. We change the permissions on the sims folder and does the trick. I did try it an still no luck

 

Missed that last post of yours. if you install management studio on the client can you access the server that way?

 

Management Studio?

 

I have had odd faults in the past with the locally stored Sims *.XML file becoming corrupt. But this only generally affects an individual sims users on that client, but it would not harm to rename the “C:\Documents and Settings\%username%\Mydocuments\My SIMS Documents\%Username% folder as Sims will generate another one.

 

"He says, clutching at straws"

 

Tried binning the profile, still not working

[scebe427]

We dont normally use it. We change the permissions on the sims folder and does the trick. I did try it an still no luck

 

 

 

Management Studio?

 

 

 

Tried binning the profile, still not working

 

Google

[enjay]

Check the drive mapping (typically S:) is in place - missing that will cause Reason 0 errors.

[alextreadwell]

check c:\Program Files\SIMS\SIMS .net\connect.ini is pointing to the right place it should redirect to you sims shared folder on your networ ie s:\sims

[FN-GM]

Check the drive mapping (typically S:) is in place - missing that will cause Reason 0 errors.

Its mapped

 

check c:\Program Files\SIMS\SIMS .net\connect.ini is pointing to the right place it should redirect to you sims shared folder on your networ ie s:\sims

 

Yep the file is fine

[glennda]

Hiya,

 

did you sort this? we had a sims reason 0 error before because the firewall was on, on the local machine. this was about a year ago tho so cannot remember the exact details but it was something todo with the firewall just not sure exactly what!

[siuko]

My Reason 0 problem was all server side and randomly affected certain staff accounts.

 

You are 100% certain it is the workstation at fault?

[FN-GM]

Hi,

 

I needed up formatting the box and started again. Now works fine.

[01hanstu]

Hi, If you have not sorted it yet my solution that works is to go to C:\progam files\SIMS .net\SIMS and rename SIMS to SIMSold and run simsinst.exe from S:\ and it works we have had an isse wth our new server and this error and this is how we cured it

 

Thanks

Stuart

[User3204]

There was a point I was getting this error which turned out to be an error in DNS.

 

We had a machine that was mapping the server as its IP address fine, but when we ran the SIMS pulsar it was using a connect.ini that made reference to the servername. It was only when I tried pinging this name from that machine did we discover that for some stupid reason it was using an old version of the DNS, as it couldn't contact the proper DNS server. The IP that was recorded in the false DNS was responding but it wasn't the right machine.

 

This workstation had needed a static IP and hadn't been updated with the new DNS servers, so had remembered them somehow when it could no longer find the old DNS servers.

[adamf]

This has just started happening at my school, only with staff that started this academic year. It happens randomly, for example it occured last week Thursday, by Friday the problem had mysteriously fixed itself and then again today, this morning it was fine, after lunch all of a sudden it's back.

 

We use SIMS in a terminal services environment - 2 servers acting as clients. I'm not really in a position to re-build them.

 

I also check the usual, connect.ini etc.. but when I discovered that I could log on in the same terminal session that a new member of staff couldn't that ruled that out. I don't think it's corrupt .xml becuase again it comes and goes as it pleases, nor DNS becuase wouldn't that affect all trying to logon to that client?

 

Any other suggestions?

[stratisphere]

We had this a short while back. Simply put, some member of staff messed up connect.ini (by not asking us when the select connect.ini file dialog came up).

 

Capita say this could mean anything... here's the supportnet article off support.capitaes.co.uk:

 

PLEASE NOTE : FIX 1 IS ONLY RELEVANT IF THE USER'S PASSWORD HAS BEEN RESET

 

Fix 1

This may be due to the 'Enforce Password Policy' settings within SQL 2005

 

To change this, log into SQL Server Management Studio and expand the Security tree and then the Logins tree.

Find the user that is getting the error, right click on their name and select properties.

In the Login Properties window, remove the tick from the 'Enforce Password Policy' tick box and then click OK. Close SQL Server Management Studio.

 

Fix 2

The machine may be pointing to a incorrect networked Connect.ini file and therefore cannot see any SQL Server or Database. Delete the Connect.ini from e.g. C:\Program files\SIMS\SIMS .net and then run SIMS .net and select the correct Connect.ini from e.g. S:\SIMS or alternatively create a local connect.ini and enter the correct SQL Server and Database name. Also check that the connect.ini in the S:\SIMS folder is pointing to the correct server\instance and the database

 

Fix 3

The error can also be an indication that the upgrade has been run, but has been unsuccessful.

 

Please check that the version of SIMSSQLApplicationsetup.exe in the setups folder is 1.574.12.0 (for August 2008 release). Then run this to upgrade to version of DBupgrade

 

Run Dbupgrade.exe manually from e.g. D:\Program files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn (This should be version 2.20.3.0). The list of upgrade files will be shown or there may be a message about a User already logged in. If Users are detected, a Force All will need to be run to exit the Users out of SIMS to allow the upgrade to commence (requiring the SA logon credentials). This Force All option will appear automatically if Users are detected as being logged in.

 

Once this has completed run SIMSApplicationsetup.exe on the machine that is generating the error

 

Fix 4

If the error still occurs and you installed SQL Server 2005, but did not use our installer then please follow KB71936

 

 

Fix 5

 

Check there is sufficient space on the partition where SQL is installed. Also check the system partition has sufficient space as temporary files can be created during the backup.

 

Check the size of the SQL Log file eg SIMS.LDF. If excessively large use SHRINKDBLOG.BAT to shrink the log file.

 

 

Fix 6

 

Please ensure that SQL connections are allowed through the Firewall.

 

For information on how to do this, see the Microsoft article relating to How to: Configure a Windows Firewall for Database Engine Access

 

Fix 7

Please also ensure that TCP/IP and Named Pipes are enabled.

To Enable TCP/IP and Named Pipes, please see KB79978

 

Fix 8

 

Please try stoping and starting the SQL Server

Edited September 14, 2009 by stratisphere
cleanup

[deKay]

Just to add another reason to the list (which we found last week):

 

The user's Application Data and/or My Documents are redirected to a server share, which has quota management and the quota has been hit. Clear some space, and it all works again.