Does anybody know what this is?

[jsql12]

Hi all,

I always see an entry in the error log like this:

using 'xplog70.dll' version '2000.80.760' to execute extended stored procedure 'xp_cmdshell'

Does anybody know what it is? what's the purpose?

Thank you!

 

[ESquared]

Look up xp_cmdshell in SQL Server Books Online. Helloooo.

[COLOR=#aa88aa black]Cum catapultae proscriptae erunt tum soli proscript catapultas habebunt.[/color]

 

[jsql12]

Hi Esquared,

I know what it does. What I'm more interested in is what would cause this entry in the error log.
spidXX using 'xplog70.dll' version '2000.80.760' to execute extended stored procedure 'xp_cmdshell'

Thanks!

 

[LNBruno]

Sounds like you're actually looking at the the event viewer?

Is there an Event number (like 1755) associated with what you're seeing? If so, Event 1755s are informational messages.

It may be simply letting you know that SQL Server launched an extended stored procedure called 'XP_CMDSHELL'



< M!ke >
I am not a hamster and life is not a wheel.

 

[jsql12]

LNBruno the message is from sql server error log and it is not associated with any number. What is worrying me is that the source of this message is a spid. So I'm wondering if somebody is trying to do something he/she is not supposed to be doing.

Thanks!

 

[LNBruno]

Can you identify using the spid?

SELECT 
   SYSTEM_USER AS 'Login Name'
   , USER AS 'User Name'
WHERE @@SPID = nn

< M!ke >
I am not a hamster and life is not a wheel.

 

[SQLSister]

you would get a spid for an application doing this task as tell. Many DTS packages use active x components. While it is running, you will see the spid for DTS if you run sp_who2. It would probably also put this message into the log.

"NOTHING is more important in a database than integrity." ESquared

 

[jsql12]

that query doesn't return anything. I already did the following:

select loginame from sysprocesses
where spid = xx
--xx is the spid that is apparently using the dll
and it didn't return anything. So for some reason it wasn't logged in the sysprocesses table.

Thank you for the effort guys.