xp_cmdshell

Question

xp_cmdshell

river1

SSC-Insane

Points: 24309
More actions
July 12, 2010 at 10:03 am

#226718

Hi,
I execute a command (xp_cmdshell) , but i always receive this error:
Login failed for user 'teste'.
But the user is sysadmin and the password is correct.... and the functionality is already active in the surface area)
Here is the command that i execute:
Declare @osql varchar(8000)
Set @osql='EXEC master.dbo.xp_cmdshell '+''''+'osql -Uteste -Pteste -Q"DBCC Checkdb (''''securdb'''')" -o"C:\teste1.txt"'''''''
EXEC (@osql)
Can someone help?
Thank you

Viewing 8 posts - 1 through 7 (of 7 total)

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

James_B SSCrazy Points: 2163 More actions · Answer 1

The xp_cmdshell is calling a command line program called OSQL which is connecting to the default instance on the local computer with the username teste and password teste.

If you are already connected to the default instance on the server you may as well just run DBCC Checkdb ('securdb') in mangagement studio with results to file option selected.

magasvs SSCertifiable Points: 7660 More actions · Answer 2

Try to add -S (Servername) option to OSQL command.

Jeff Moden SSC Guru Points: 1004356 More actions · Answer 3

river1 (7/12/2010)
Hi,
I execute a command (xp_cmdshell) , but i always receive this error:
Login failed for user 'teste'.
But the user is sysadmin and the password is correct.... and the functionality is already active in the surface area)
Here is the command that i execute:
Declare @osql varchar(8000)
Set @osql='EXEC master.dbo.xp_cmdshell '+''''+'osql -Uteste -Pteste -Q"DBCC Checkdb (''''securdb'''')" -o"C:\teste1.txt"'''''''
EXEC (@osql)
Can someone help?
Thank you

Agghh... don't ever hardcode user security information in SQL Server. Use a trusted connection instead of declaring the -U and -P parameters and, as has already been suggested, add the -Sputserverinstancenamehere parameter. I'm not at a machine where I can look up how to declare a trusted connection so you'll need to lookup in Books Online but IIRC, it's -T or -E... can't remember which one.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

SQLRNNR SSC Guru Points: 281334 More actions · Answer 4

Jeff Moden (7/13/2010)
river1 (7/12/2010)
Hi,
I execute a command (xp_cmdshell) , but i always receive this error:
Login failed for user 'teste'.
But the user is sysadmin and the password is correct.... and the functionality is already active in the surface area)
Here is the command that i execute:
Declare @osql varchar(8000)
Set @osql='EXEC master.dbo.xp_cmdshell '+''''+'osql -Uteste -Pteste -Q"DBCC Checkdb (''''securdb'''')" -o"C:\teste1.txt"'''''''
EXEC (@osql)
Can someone help?
Thank you
Agghh... don't ever hardcode user security information in SQL Server. Use a trusted connection instead of declaring the -U and -P parameters and, as has already been suggested, add the -Sputserverinstancenamehere parameter. I'm not at a machine where I can look up how to declare a trusted connection so you'll need to lookup in Books Online but IIRC, it's -T or -E... can't remember which one.

-E is the switch to use.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

MMartin1 One Orange Chip Points: 27795 More actions · Answer 5

It appear you have your string inlcude the EXEC portion already. When you run EXEC (@osql) it seems to come down to

Exec Exec XP_CMDshell .....

ELiminating this may not not fix your issue but may give a slightly different error message.

Or maybe I don't know the workings of the EXEC function well enough.

Best

Mark

----------------------------------------------------

nekonecny Right there with Babe Points: 720 More actions · Answer 6

nekonecny

Right there with Babe

Points: 720

July 22, 2010 at 8:53 am

#1196908

Try

sp_configure 'xp_cmdshell',1;

reconfigure

SQLBuddy123 One Orange Chip Points: 28294 More actions · Answer 7

Check whether the SQL Server account has access to C:\teste1.txt.

Thank You,

Best regards,

SQLBuddy