Xp_Cmdshell Problem

Question

Post reply

Xp_Cmdshell Problem

timster

Ten Centuries

Points: 1033
More actions
July 18, 2012 at 7:19 am

#278045

Hi
Getting the folling error when running any xp_cmdshell command
"A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)"
Everything was working fine yesterday but as of to day this isnt working any ideas?
Yes xp_cmdshell is enabled
Thanks

Viewing 6 posts - 1 through 5 (of 5 total)

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

timster Ten Centuries Points: 1033 More actions · Answer 1

Looks like it was a firewall issue system guys pused a policy through that inabled IPS

Johan Bijnens SSC Guru Points: 135369 More actions · Answer 2

Thank you for the feedback.

Knowing where to look is a good start for any assessment .

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

Lokesh Vij SSChampion Points: 10836 More actions · Answer 3

This has happened with me in the past as well. Is there a way out to get over this issue permanently?

Thanks in advance.

~ Lokesh Vij

Guidelines for quicker answers on T-SQL question[/url]
Guidelines for answers on Performance questions

Link to my Blog Post --> www.SQLPathy.com[/url]

Follow me @Twitter

Johan Bijnens SSC Guru Points: 135369 More actions · Answer 4

the described scenario is other people activated an IPS system.

There is only little you can do if they don't inform if such thing would cause issues for your db-server or whatever.

As in many cases, they just activate it and see what happens.

Having a good inventory of what you are doing to the outer world from within your db instance is a good starting point.

In many cases, just moving the dos call out of the db-instance (e.g. to sqlagent (cmdexec)) can already solve the issue.

But, as in most cases, the question is "does this functionality really needs to be run from within the db server, in-process, synchrone, in-transaction, ..." and is that the appropriate place/way to do it.