Problem after SQL Migration

[Jawloms]

Since doing the MSDE to SQL Express migration, my error log is reporting the below when someone tries to log in, even though SIMS appears to work correctly;

 

Event Type: Failure Audit

Event Source: MSSQL$SIMS2005

Event Category: (4)

Event ID: 18456

Date: 24/10/2007

Time: 08:50:45

User: N/A

Computer: ADMIN

Description:

Login failed for user 'sims'. [CLIENT: xx.xx.xx.xx]

Data:

0000: 18 48 00 00 0e 00 00 00 .H......

0008: 0f 00 00 00 41 00 44 00 ....A.D.

0010: 4d 00 49 00 4e 00 5c 00 M.I.N.\.

0018: 53 00 49 00 4d 00 53 00 S.I.M.S.

0020: 32 00 30 00 30 00 35 00 2.0.0.5.

0028: 00 00 07 00 00 00 6d 00 ......m.

0030: 61 00 73 00 74 00 65 00 a.s.t.e.

0038: 72 00 00 00 r...

 

Event Type: Warning

Event Source: SQLBrowser

Event Category: None

Event ID: 3

Date: 24/10/2007

Time: 09:10:40

User: N/A

Computer: ADMIN

Description:

The configuration of the AdminConnection\TCP protocol in the SQL instance SIMS2005 is not valid.

 

 

 

I've obviously removed the IP address from this error. Any idea what's going on? Is it related to the fact that SIMS now takes about 90 seconds to open whereas prior to the migration it was about 30?

 

Any help greatfully received.

 

Thanks

 

Stuart

[tech_guy]

Apparently the 'Audit Failure' is a 'feature' of using SQL 2005 - on Capita SupportNet KB72846 there is some information stating that these log entries are 'not a cause for concern'.....

 

Roll on the bug fix, eh Capita?

 

My app log is chocka with these now :-(

[Adam_C]

Do any of you guys schedule reports? If so have you now got problems?

 

I have found that this error prevents the schedule from working. (presumably AutoReport.exe attempts to log in to the SQL Server as user 'sims').

[Jawloms]

We don't use scheduled reports.

 

Any thoughts on the speed issue? Thanks for pointing that KB out to me.

 

Stuart

[tech_guy]

We haven't noticed a decrease in speed but then again Sims.Net has always been a bit of an OAP for us..... ;-)

[PhilNeal]

If SIMS is running slow then there is probably another cause. For example 300 full page reports will print in less then a minute and that involves grabbing data from attendance, assessment and gluing text together.