Jump to content

Recommended Posts

Posted

Staff can't logon, and the error message says "Reason: 0".

 

Has anybody come across this before? A County engineer says we need to re-install it all all client machines, but that's not practicle as we have 200+ machines with it on!

 

Please help!

Posted
Restart the SIMS Server - should solve the problem.

 

Tom

 

We've tried that, and it hasn't done a thing! :(

 

The odd thing is my Boss can log in with his credentials (Admin) and so can some one in GA.

Posted

Check sims.net version number - latest is 7.114 - had problems upgrading to this with some stuck on 7.112.

Had to run simsapplicationsetup on some to install.

Posted
Have you just applied a patch/upgrade/changed anything or has the problem suddenly started occurring on it's own?

 

Just happened on it's own!

Posted

Isn't reason 0 something to do with the user not having permission to install software?

 

have you tried it logged on as admin to the machine?

Posted
Isn't reason 0 something to do with the user not having permission to install software?

 

have you tried it logged on as admin?

 

Yep, done it logged as admin - and it does the same thing!

Posted
Check sims.net version number - latest is 7.114 - had problems upgrading to this with some stuck on 7.112.

Had to run simsapplicationsetup on some to install.

 

Were on 7.112

Posted
Reason zero is down to not being able to connect to the server, ie. check firewall settings and check connect.ini files.

 

But I can logon with admin on my machine and it works fine - then as a teacher (that's had the same problem elsewhere in the school) and it doesn't work!

Posted

Try on one of those machines

 

Logon as administrator

Start | Run

s:\setups\simsperm.bat everyone

Runs sims (does it work?)

Logoff, logon as staff

Does sims work

Posted

Well so far, a fix in MS SQL Server Management Studio were you have to enforce password policy per user.

 

Worked on one so far, going to see if it works on all with the issue!

Posted

We had this exact same problem recently. We had to detach the database and then re-attach it before everything would work again.

 

Here is what our county helpdesk sent us to resolve this issue:

 

Open dbAttach

 

Backup the "SIMS" database, close the error message and click on backup at the right.

 

Close and re-open dbAttach.

 

Detach the "SIMS" database.

 

Close dbattach.

 

Cut and paste the "SIMS.MDF" and "SIMS.LDF" files to another location.

 

Run dbAttach.

 

Browse to this new location for the "SIMS" file, type "SIMS" as your database and re-attach.

 

Try loggig into "SIMS .net" on the server.

 

---------------------

 

Also they sent me this Capita Doc:

 

KB72254 - SIMS Connection failed for Login USERNAME reason: 0 - When logging into SIMS .net

________________________________________

Created 07/08/2007

Last Updated 07/01/2009

 

________________________________________

Affected Products SIMS .net Setup & Permissions

SIMS .net Installation & Upgrade

________________________________________

Notes When logging into SIMS .net

SIMS Connection failed for Login USERNAME reason: 0

This will only occur if you are on August 2007 or later version of SIMS .net

________________________________________

Advice 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

 

----------------------------------------

 

Hope this is helpful!

Posted
Staff can't logon, and the error message says "Reason: 0".

 

Has anybody come across this before? A County engineer says we need to re-install it all all client machines, but that's not practicle as we have 200+ machines with it on!

 

Please help!

 

Exactly the problem we had earlier this week.

 

Resolved when traced to the fact I:o had turned the Firewall on on the SIMS server.

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



×
×
  • Create New...