2007-08-31 09:32:09.79 Logon Error: 18456, Severity: 14, State: 5.
2007-08-31 09:32:09.79 Logon Login failed for user 'sims'. [CLIENT: 10.2.110.97]
2007-08-31 09:32:55.10 Logon Error: 18456, Severity: 14, State: 5.
2007-08-31 09:32:55.10 Logon Login failed for user 'sims'. [CLIENT: 10.2.110.97]
2007-08-31 09:32:55.25 Logon Error: 18456, Severity: 14, State: 5.
2007-08-31 09:32:55.25 Logon Login failed for user 'sims'. [CLIENT: 10.2.110.97]
There’s no user called sims in the AD but there is a group called sims which has all the sims users in it. I understand that a state 5 error means invalid user ID but apart from Sims running slow it works.
Jobos, this is a suggestion from one of our technical people.
It might be worth asking the customer if their connect.in is set to Trusted/Auto. My guess is that it is and is therefore trying to connect as an AD user and not a SIMS SQL user. They could try changing the connect .ini to Trusted (ConnectionType=Trusted), this will give them to the option to use a AD account or SIMS account. Or they could remove their ConnectionType from their connect.ini.
I get exactly the same error. Along with it my workstations now refuse to automatically update themselves when any user tries to log into SIMS, give an error and then fail the login. I logged a call with Capita via my support unit and their great advice was to run SIMSApplicationSetups.exe on each w/s to update it manually. This updates the w/s ok but now I have to now go round the entire school & logon to every single w/s & laptop to run the update. They didn't even bother to answer my question of why I was getting the SQL errors (so they continue to fill up my logs).
I'm sure there's a link between the two but don't know enough about SQL. And what happens when the next update arrives? Manual installs all round again??
Domino - my problem with auto updates was indeed to do with the sims.ini file pointing to the wrong location (I migrated to a new server during the August update, more fool me). Auto updates is now working ok so many, many thanks for your help. I wonder why Capita couldn't come up with such a simple solution...
Jobos, Server management is on CD 2. We had missed that too but found it eventually.
Our SQL server is on Mixed mode as that is what our instructions told us to do and that is what the previous version is on.