Profile Error 17055

I applied a service pack to a third party application and
as of now I keep receiving the following in the sql
server log and application log every 1 minute or so.
How can I use the profiler on this to find out what's
happening?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 17055
Date: 12/28/2003
Time: 11:54:26 AM
User: N/A
Computer: SERVERP01
Description:
18456 :
Login failed for user 'TRACK'.
Data:
0000: 18 48 00 00 0e 00 00 00 .H.....
0008: 0f 00 00 00 4a 00 52 00 ...J.R.
0010: 41 00 59 00 44 00 55 00 A.Y.D.U.
0018: 42 00 49 00 53 00 51 00 B.I.S.Q.
0020: 4c 00 50 00 30 00 31 00 L.P.0.1.
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...
Thanks,
ShonetYou can use profiler to log connection attempts...Someone is trying to log
in using the login TRACK, which is a failed attempt... Watching this in
profiler will get you the name of the workstation, and name of the program
they are using... then you can track them down..
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shonet" <anonymous@.discussions.microsoft.com> wrote in message
news:02bc01c3cd17$897e17f0$a601280a@.phx.gbl...
> I applied a service pack to a third party application and
> as of now I keep receiving the following in the sql
> server log and application log every 1 minute or so.
> How can I use the profiler on this to find out what's
> happening?
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (4)
> Event ID: 17055
> Date: 12/28/2003
> Time: 11:54:26 AM
> User: N/A
> Computer: SERVERP01
> Description:
> 18456 :
> Login failed for user 'TRACK'.
> Data:
> 0000: 18 48 00 00 0e 00 00 00 .H.....
> 0008: 0f 00 00 00 4a 00 52 00 ...J.R.
> 0010: 41 00 59 00 44 00 55 00 A.Y.D.U.
> 0018: 42 00 49 00 53 00 51 00 B.I.S.Q.
> 0020: 4c 00 50 00 30 00 31 00 L.P.0.1.
> 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...
>
> Thanks,
> Shonet|||I managed to work this one out, but I'm please to see
what I came up with is was the same as your solution.
Excellent.
Thanks!!
Shonet
>--Original Message--
>You can use profiler to log connection
attempts...Someone is trying to log
>in using the login TRACK, which is a failed attempt...
Watching this in
>profiler will get you the name of the workstation, and
name of the program
>they are using... then you can track them down..
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Computer Education Services Corporation (CESC),
Charlotte, NC
>www.computeredservices.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>
>"Shonet" <anonymous@.discussions.microsoft.com> wrote in
message
>news:02bc01c3cd17$897e17f0$a601280a@.phx.gbl...
>> I applied a service pack to a third party application
and
>> as of now I keep receiving the following in the sql
>> server log and application log every 1 minute or so.
>> How can I use the profiler on this to find out what's
>> happening?
>> Event Type: Information
>> Event Source: MSSQLSERVER
>> Event Category: (4)
>> Event ID: 17055
>> Date: 12/28/2003
>> Time: 11:54:26 AM
>> User: N/A
>> Computer: SERVERP01
>> Description:
>> 18456 :
>> Login failed for user 'TRACK'.
>> Data:
>> 0000: 18 48 00 00 0e 00 00 00 .H.....
>> 0008: 0f 00 00 00 4a 00 52 00 ...J.R.
>> 0010: 41 00 59 00 44 00 55 00 A.Y.D.U.
>> 0018: 42 00 49 00 53 00 51 00 B.I.S.Q.
>> 0020: 4c 00 50 00 30 00 31 00 L.P.0.1.
>> 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...
>>
>> Thanks,
>> Shonet
>
>.
>

Process Blocking Problem

We are running SQL Server 7.0 Service Pack #4, running on Windows 2000 Server.
We have a problem with process blocking. At some points the T-SQL statement runs restricting all our users from accessing the DB.
The statement is:

SET FMTONLY ON
exec sp_execute 1
SET FMTONLY OFF

Only when it finishes running, then users are allowed to access the db again.
It is triggered automatically. Does any know what condition on the server is causing this statements to run and what can be done to prevent it. Thanks so much for your help.Look at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql7/html/sqlquerproc.asp

It explains what sp_execute does.
Do you have a lot of dynamic sql or embedded sql rather than SPs?|||Also look at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlmag2k/html/adoapp.asp|||What I found out from the Microsoft website that sp_execute is a command that runs a prepared statement using the sp_prepare command.
So what happened is I've watched the SQL for the condition to repeat but it did not. However what I've noticed that our of nowhere at time sp_prepare runs without any parameters, causing the CPU utilization go up to high 90%.
What is causing this sp_prepate to run, as it done automatically.
Thanks for your help.