SQL Server and .NET 1.1 failed sa login

Question

SQL Server and .NET 1.1 failed sa login

Summer90

SSC-Dedicated

Points: 32891
More actions
January 19, 2004 at 9:20 am

#64719

We have an existing SQL Server 2000 SP3a/Win2k SP3 that had .Net 1.1 installed on it. After that every half hour messages appear in the event log saying Login failed for user 'sa'. Any help would be appreciated.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 1

Start Profiler (Event : Security Audit - Audit Login Failed) to trace which application is tring to access your server with 'sa' login.

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 2

Great idea but doesn't get me anywhere. Audit Login FailedLogin failed for user 'sa'.Microsoft(R) Windows (R) 2000 Operating Systemsa1032652004-01-19 14:00:00.650

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 3

Do you run clustered SQL Server or non-clustered SQL Server? Any schedule jobs fail?

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 4

This is non clustered. Nothing else is failing. This started RIGHT after they installed .NET 1.1 on this server. That is why I think it has something to do with the install but I cannot prove it.

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 5

Can you post the result of "select loginname from syslogins" here?

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 6

OK: sa BUILTIN\Administrators DUBLINNT\SQLITA1 dbadm02 WALTIR1 5 row(s) affected

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 7

Have any linked servers configured to access this server? Any scheduled Window tasks? (Control panel --> Scheduled Tasks)

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 8

No scheduled tasks, no linked servers, no DTS packages, no jobs using 'sa'

rimort SSC Rookie Points: 27 More actions · Answer 9

I ran into a similar issue once .NET was installed on one of our web servers. My issue was in the web.config file as that is where the credentials are declared. The sa password was causing the XML to be read improperly. This became evident once I noticed that other accounts/passwords would allow the app to function. The root cause was a special character % in the password of the sa account. I hope this helps.

joachim.verhagen Hall of Fame Points: 3560 More actions · Answer 10

I also have a Windows 2000 server with .Net 1.1 recently installed, but that had no effects on SQL Server. There are no strange login attempts. As far as I know .Net has no special relationship with Sqlserver.

What was the hostname of the sa login? I did not see it in your profiler output.

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 11

It just says Windows, no specifics like a servername or application name.