Jobos Posted September 3, 2007 Posted September 3, 2007 The office has reported that since they moved to SQL2005 Sims has been running slow. On checking event log I find this: Event Type: Failure Audit Event Source: MSSQL$SQL2005 Event Category: (4) Event ID: 18456 Date: 31/08/2007 Time: 09:32:09 User: N/A Computer: Server1 Description: Login failed for user 'sims'. [CLIENT: 10.2.110.97] Then I check the SQL log : 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.
PhilNeal Posted September 3, 2007 Posted September 3, 2007 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.
Jobos Posted September 3, 2007 Author Posted September 3, 2007 Thanks for the reply. After reading the August Sims release notes I can see where you’re coming from but I have checked the connect.ini files and there is no mention of a ConnectionType string
PhilNeal Posted September 3, 2007 Posted September 3, 2007 Sorry I think you will need to lodge a call with your support unit. You can email me if they can't help and I'll put you in touch with our techical team.
timzim Posted September 3, 2007 Posted September 3, 2007 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 Posted September 5, 2007 Posted September 5, 2007 Have you checked the sims.ini file in the WINDOWS directory on your machines? In there is has a line called "updatepath" - this must point to the sims setups directory
TechMonkey Posted September 5, 2007 Posted September 5, 2007 We are having this problem as well with the added complication of new sims users not being logged on till another user has logged on before them. Tried adding the trusted user string into the local connect.ini to get the choice between windows or sql auth and I still got the logon failure in the event viewer. As far as we are aware though our updating is fine.
timzim Posted September 5, 2007 Posted September 5, 2007 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...
Domino Posted September 5, 2007 Posted September 5, 2007 we did the same thing, no worries, tripped me up - and we eventually puzzled it out ourselves. Other thing to check is that under the C:\program files\sims\sims.net there is a local connect.ini you need to make sure this points at the new server too.
Domino Posted September 5, 2007 Posted September 5, 2007 also Has everyone checked that the SQL server is not trying to use windows authentication...? or Mixed? Sims may not be, but maybe SQL is...
Jobos Posted September 5, 2007 Author Posted September 5, 2007 I was thinking along those lines myself but I don’t have SQL server management studio installed which I believe would fix it. See http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx This morning I reported the issue to our LEA. They were unaware of the problems and after checking their test server found the same errors in their logs.
TechMonkey Posted September 5, 2007 Posted September 5, 2007 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.
Jobos Posted September 5, 2007 Author Posted September 5, 2007 Can the studio be installed without messing up the Sims install? I don’t fancy any sleepless nights
timzim Posted September 5, 2007 Posted September 5, 2007 Yes, but be careful what you do with it once installed as SIMS is a peculiar beast. If you don't have full SQL 2005 you can download Management Studio Express Edn from MS website for free.
Jobos Posted September 11, 2007 Author Posted September 11, 2007 Our LEA has received the following from Capita: Advice These are Audit entries only and are not a cause for concern. As of the August release, changes were made to the database security - but some areas of the application code in SIMS applications are backward-compatible. Such code may well try to connect to a database using the old security method - in which case, this audit entry will get written into the Event Log.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now