Found this....
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 Fix 1
The error is an indication that the upgrade has been run, but has been unsuccessful.
Please check the version of SIMSSQLApplicationsetup.exe in the setups folder is 1.558.12 (for August 2007 release) or 1.0560 (for September 2007 release) then run this to upgrade to version of DBupgrade which should be 2.11.10.24603
Then run Dbupgrade.exe manually from e.g. C:\Program files\Microsoft SQL Server\MSSQL$SIMS\Binn
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.
Fix 2
If fix 1 does not resolve the issue please run SIMSApplicationsetup.exe from the setups folder
Fix 3
If the error still occurs and you installed SQL 2005, but not via one of our installers then please follow KB71936
Fix 4
This error can also be caused by a corrupt user in the users table. If all other users can login to the system OK please re-create the user that is getting reason 0
Yeh saw that but I get as far as running DBupgrade and then when I try and login to that it comes up with.
"login failed for user Simsinit. The user is not associated with a trusted SQL server connection.
I'm guessing its the same error.
Did you see this one!
KB73455 - The login failed for user sims_USER database SIMS When Running DBUpgrade
--------------------------------------------------------------------------------
Created 26/09/2007
Last Updated 06/11/2007
--------------------------------------------------------------------------------
Affected Products SIMS .net Installation & Upgrade
--------------------------------------------------------------------------------
Notes When running SOLUS to do a patch or a release you may see the error:
"Upgrade Failed, script that caused this error 3.61.387 to 3.61.388"
The login failed for user sims_USER database SIMS.
--------------------------------------------------------------------------------
Additional Notes We have had reports of this error but so far we have only been able to replicate this once and it is currently under investigation however we do have the following workarounds to try.
After each of the fixes please run dbupgrade manually
--------------------------------------------------------------------------------
Advice Fix 1
This error can occur if the upgrade is not run on the SIMS Server. Please ensure that DBUpgrade.exe is run on the SQL Server.
Fix 2
Please run SIMSSQLApplicationSetup.exe from the Setups folder to ensure that the BINN folder on the Microsoft SQL Server is up to date and re-run the upgrade
Fix 3
If when running the upgrade originally a backup was taken please re-run DBupgrade using the no backup parameter as per KB65058
Fix 4
Please change the attribute of the SQL Batch files in the i.e D:\Simsroot\SIMS\Setups folder by right clicking the file > Selecting Properties > Untick the read-only box > Click Apply > Click OK
Fix 5
Please try running the upgrade as SA. The SA user is the SQL Administrator user and the password for this account will have been specified during the installation of SQL Server.
Fix 6
Please make the SIMS user an authenticated user to the Windows Administrator account and run SOLUS/DBupgrade as the trusted user. Details on how to make the user trusted can be found in KB72751
Fix 7
If still failing then please try running the following script through Microsoft SQL Management Studio
exec sims.db_p_install
This may be totally off the mark but our server ran out of space recently and was down to 500mb this became a real problem as when staff logged onto sims I could see the disk space going down. Once the disk space got down to less than 20meg we would get that error, when staff tried to log on to sims.
Now this is such a simple solution I bet you have checked or that you know you have enough free space, but hey just incase.
As all SIMS users are now held OUTSIDE of the SIMS database can you be sure that they have all migrated over correctly, I know when our LEA SIMS support came in to do our upgrade (as i would not take responsability for it going belly up) there was problems with user migration which resulted in Reason 0 errors followed by Reason 2 errors.
Yeh the error was from me not using the right authentication method when I installed SQL 2005 and doing the migration. (I used the default method and apparently you have to choose mixed mode).
I have no idea how to fix that now so I guess its a complete re-install and restore this morning :/
This on the same server? or did you migrate to another server? Dunno if this has anything to do with it but when we did it, it reset all the passwords so you can only go in as sysman i believe.
try the default sims username and password when we did the migration on a test machine it hashed all the passwords and this ws the only wway we could get in.
Whats the default one? I only know my passwordOriginally Posted by Uraken
EDIT: Nevermind, I finally managed to do the sql migration properly and all the old user names and passwords worked as they should.
No more Error: 0's yey!
Where are they stored :?:Originally Posted by ICTNUT
Thanks,
Jim
I think it's in the master db. That is apparently the reason why a standard SQL database backup is now no good for restoring your sims installation onto a different server.
I'm assuming they've done this to allow for the login-via-windows-credentials feature that came along not so many updates ago. </guesswork>
We have also backed up and restored the master database- and can actually see the usernames in sql studio.
We are still getting the "Reason 0" error though !
:?: :?: :?:
I am having the same problem, any advise on how to get round/sort it is appricated. here is what I have done to date
(This is on a new sims server on a brand-new domain)
Installed the Server (2008)
Installed SQL 2005
Installed SQL 2005 SP2
Copied our simsroot folder from a backup (DPM)
Restored our copy of sims.mdf and sims.ldf from our dpm server (to a file then copied to the server)
shared the simsroot folder as simsoot / mapped to S:
Ran s:\sims\setups\simssqlapplicationsetup.exe , put the files in the right sql db
Ran dbattach (which worked)
ran simsinst and installed sims workstation and document storage server
altered s:\sims\connect.ini to point to the right server.
ran sims and pointed it to s:\sims\connect.ini
tried to logon to sims and get
SIMS Connection failed for login ITAdmin , reason: 0
ARGHHHHHHH
Just one thing for people to note.. do not have any users with ' in the logon name.. it causes the db not to attach (2formats later and i am here)
Thanks for any pointers
Brett
You could try detaching and then re-attaching the database - I have found that this works in this situation.
broyles (3rd March 2009)
There are currently 1 users browsing this thread. (0 members and 1 guests)