Xp_cmdshell - Problem Creating Txt File For Working For Remote Computer
Jan 20, 2004
I am having problem creating/copying "txt" file in a remote machine by using the "exec master..xp_cmdshell" command in query analyzer. For example, we are getting errors for the following command:
I am having problem creating/copying "txt" file in a remote machine by using the "exec master..xp_cmdshell" command in query analyzer. For example, we are getting errors for the following command:
hi every one. i am a new user of asp.net 2.0 using C# code and i am facing a problem in accessing a SQL Server2005 database file in the remote computer. i have connected two pc with peer to peer connection and trying to add a databse using the "Add connection" option from the visual studio 2005. in the add connection dialog box it is showing me the remote server and it was supposed to show all the database in that SQL Server when i select one. but when i am choosing the server name it was not showing me anything. by the way i have configuered the surface area for "both TCP/IP and named pipes" and both the pc's server browser is turned on. is it the right way to access a database file from a remote pc or not?? please send me a good solution to do this things and try to explain the codes with example. waiting for response....plz send me the solution.. as soon as possible
This is returning the following error code. I even tried placing the command in a seperate command file and calling that with no success. If I run this from the command line the error file generation does work.
The Bulk Insert actually creates a empty error.txt file (0kb) and never preforms the insert, I can not find any examples of anyone using the -ERRORFILE switch on BULK INSERT. Prolly some default security setting to allow file creation/modification I am missing. Anyone help me out? Thanks.
I have a procedure which prepares a csv file on demand using xp_cmdshell to invoke bcp.
It works fine in sql server. In fact, I have setup a proxy account to run as the domain administrator so it should even work for limited sql server accounts.
When IIS 6.0 attempts to run the procedure, however, I get "xp_cmdshell failed to execute because current security context is not sysadmin and proxy acount is not setup correctly."
For some reason, IIS 6.0 is not able to assume proxy privileges.
Recently, the machine hosting IIS was promoted to a domain controller. Is this causing a problem? My suspicion is that the proxy account has to be a LOCAL user, and since DC's do not have local users, the proxy privileges are useless.
When I was trying to execute an SSIS package from DTExec using xp_cmdShell, it is giving an error message saying "unrecognized command,...". This error I am getting only in my Staging Environment. But at the same time, it is working fine with Development and Production servers.
I suspect the issue should be with config or access issues. So if anyone of you faced the same problem or if anyone have any solution, please share with me.
I created SP and enabled db_datareader and db_datawriter for roles for BUILTINUsers on database level.
I can call that SP from my application if I am accessing DB from my app running on the same machine. If I run app on other machine SP throw exception related to lack of permission.
I fixed that by enabling db_owner roles for BUILTINUsers. But it is not good fix from security point of view.
My question is: is there any other way to allow regular user to run that SP by not giving him db_owner privileges?
Also I have to mention that my SP procedure has some dynamic SQL code.
I'm attempting to connect to an SQL Server Express database from a remote PC, but it isn't connecting. I have a user account created in the database, and I'm using the SQL authentication with that user account. I have success with this if I'm on the server that the database is on, but not remotely. Both are on the same network, even plugged into the same hub. There doesn't appear to be any network problems.
I'm just moving over one of our databases from SQL2000 to 2005. Everything is working fine, and all web sites are working, however I just can't seem to get xp_cmdshell to function on the 2005 server.
I have enabled xp_cmdshell, and when I run a stored procedure, which writes the contents of one column to a text file, it says "invalid object name". This table is definitely there, and is actually updated earlier on in the same SP, so permissions for that are fine.
This is the line causing the problem (if I take it out, the rest of the SP works no problems):
--write the text file EXEC master.sys.xp_cmdshell 'bcp "SELECT newslettertext FROM mydatabase.dbo.newsletters" queryout D:ewslettertext extbody.txt -U -P -c'
Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'mydatabase.dbo.newsletters'.
SQLState = 37000, NativeError = 8180 Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared. NULL
Could it be to do with permissions on the master.sys.xp_cmdshell? If so, wouldn't it give me a "permission denied" error?
Please bare with me as I do not have much knowledge in this area with MSSQL.
I have installed MSSQL 2000 Developer and I have setup a database which I am able to connect to and work fine with from the actual server MSSQL is installed on.
The problem comes in when i try to connect to that same database from a different remote server. It will not connect to the DB from this remote server but I know all the connection information is correct so its something on the MSSQL DB server causing this and not on this remote server.
Someone I know has had this problem and has fixed it but they wont tell me how. All I know is they said something about manually opening the ports on the MSSQL server and he also said when you set it to dynamicly determine the port that MSSQL is listening on it errored out. however if you set it staticly to 1433 it worked fine.
Ive also installed SP4 in attempt to fix this but no luck with that either. And I can also get the same exact remote server to connect to completely different DB server without issues.
If anyone can please help walk me through this I would be greatly appreciate and I am also willing to pay some money if it will make my life easier.
I am about designing an access project file that connect to a SQL Server database : it could be either on the local computer or a remote workstation, this depending on where the front end is running.
Bypassing the default log on dialog box i have set my own form that users should use to connect on adp. Then using baseconnection string i connect the adp to sql server database.
My concern is how can i check from vba if the instance of SQL Server where my back end database is located is running in order to make users knowing that due sql server service status off their connection tentative will fail.
inform u i can check same from console management however i would to automate same controle from my adp and avoid that users have to operate such task...
we have sql 2005 standard edition. i was trying ( unsuccessfully ) to configure RAS on server 2003 to allow the server to authentificate vpn requests. i don't know how but the next day people started complaining about their mapped network drives being disconnected, and now no one can connect to the database via the network, eventhough they still have access to the server, and the network drives were remapped.
Not sure if this is the right place for my question but here goes anyway.
I have an instance of SQL Server 2005 installed on my DEV PC. A colleague of mine wants to access my server from his machine which connected to the same network.
I logged on to SSMS and added him as a new login.
Will he be able to connect to it now or do I have to do more than just that?
is there any way to execute a SSIS package at the SQL Server programatically from a remote computer? (I use .net 2)
I don't need variables or return values, I only want to start the package. I know that it is easier to do that job with a webservice etc on the SQL Server but I cannot use such.
A method to call a package from a stored procedure would also help me a lot
Hello, i'v installed a pogram that uses SQLEXpress and reporting sevices on a clients computer. I can acces the reports wih http://localhost/reports$SQLEXpress from that computer, but i can't reach them from other computers in the netwok by typing http://servername/reports$SQLEXpress i am asked to imput a pasword for user "servername/guest" (which i do not know and dont think there is one) and then get the following:
You are not authorized to view this page
You do not have permission to view this directory or page using the credentials you supplied.
Please try the following:
Click the Refresh button to try again with different credentials. If you believe you should be able to view this directory or page, please contact the Web site administrator by using the e-mail address or phone number listed on the preactor home page. HTTP 401.3 - Access denied by ACL on resource Internet Information Services What should i do to solve this problem?
I have 2 xp machines one has the SQL EXPRESS Server with all the goodies on it and the other I just install the client stuff. I am using VB 6 to program with using the ADO. It works great on the server machine. The software pulls up great. I can't seem to get it to work on the client machine. I get "Login failed for user 'TIGGERLGuest'. I found the places to set the TCPIP setings on the server SQL Express to allow this even turned on the browser but nothing same error. I am using the same login on both machines and am pointed to the same workgroup. I used window authentication when I set them up. Not sure why it insists on using Guest.
This is a copy of the connection string I am using
I am unable to connect to a remote server on Computer A from Computer B, but when I reverse it I am able to connect to a remote server on computer B from computer A. I have SQL Server 2005 Developer Edition on both computers. I am using the using the SQL Management Studio to connect. Both Computers have these settings
Using Surface Area Configuration both have local and remote connections checked. Both computers using tcp/ip only checked.
Using Configuration Manager both the sql server and the sql browser are running. Both computers have tcp/ip protocols enabled.
Under the server properties on both computers, under the Security Tab, I have SQL Server and Windows Authentication Mode checked. Under the Connections tab I have Allow remote connections on this server checked.
I believe I have the Security for both the server and databases done properly giving them both proper Logins and User Roles with the proper permission.
Also went to my window firewall settings and under the Exceptions tab, I added both the sql server.exe and sql browser.exe programs on both computers on my remote network.
But when I connect on Computer B, I get an error message stating:
TITLE: Connect to Server ------------------------------
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
------------------------------ BUTTONS:
OK ----------------------------
I tried pinging server a and then server b and they both pinged.
Could someone please tell me what could be wrong on my remote computers.
plz help me... when establishing a connection to the server. when connecting to server 2005, this failure may be caused by the fact that under the default setting SQL Server does not allow remote connections.(provider: Named pipes provider, error:40 - could not open a connection to sqlserver)
I am about updating some fields with local date and time using blw API Quote Private Declare Sub GetLocalTime Lib "kernel32" (lpSystemTime As SYSTEMTIME)
Public Function LocalDateTime()
Dim MyTime As SYSTEMTIME
GetLocalTime MyTime
Debug.Print "The Local Date is:" & MyTime.wMonth & "-" & MyTime.wDay & "-" & MyTime.wYear Debug.Print "The Local Time is:" & MyTime.wHour & ":" & MyTime.wMinute & ":" & MyTime.wSecond
End Function Unquote This works fine however due to it's not really easy for an administrator to keep checking every times wheter local date and time are correctly updated for each front end users computer i would that to reconsider my function and making it to read local date and time from remote SQL Server. my concern is to help administrator to save time as he should only need to ensure that Server is running with correct time...
I just got a Virtual Dedicated Server and installed SQL Server Express 2005 on it and while I was installing choose Mix Mode authentication and setup a sa password.....
I want to connect to that database remotely from my machine using VS 2005 or Management Studio....both are encountering the same problems.....
On the Virtual Dedicated machine if I install management studio I run has no problem....it asks me for the server name : somethingSQLEXPRESS then username and password and works fine...
The same thing I try to do remotely is not happy with ....I tried to give the IP address of the server same thing no luck.....
Can somebody tell me what I'm doing wrong and where....
Hi all. I am a bit new to SQL but I have studied much info, BOL, various best practices and so on. The problem is - I cannot find any tutorial which could tell me step by step how to set SQL server on a PC and connect to it from another computer (they all are on a domain). So I decided that I am doing something wrong...
I have done the following (all is done on virtual PCs): 1.I have installed a virtual PC with windows 2003, which acts as a domain controller.
2.I installed Win2003 on a second PC and added it to the domain. Installed MS SQL Server 2005 and SP2 on it. Server uses Windows auth. and all the services are running from a dedicated domain account which I added on the first PC.
I added a domain account (let's call it USER_X) to the SQL server Security/Logins
Everything is OK locally, I can connect to the server using USER_X from the same PC.
3.I installed Win2003 on a second PC and added it to the domain. Installed MS SQL Server 2005 client componenst, SSMS and SP2 on it. Logged on as USER_X. And tried to connect to the PC number 2. And failed. SSMS gives an error (1396) Named pipes error "Could not open a connection to SQL server". But the server appears on the list if I click Server name->Browse for more->Network servers. Why I cannot connect to it if I see it? Tried to enable Windows and SQL auth, created a pure SQL user USER_Y, checked locally - ok, can connect. But cannot connect as USER_Y from the third PC.
Finally 4.I installed Win2003 on a fourth PC (did not add it to the domain). Installed MS SQL Server 2005 and SP2 on it. Server uses Windows and SQL auth. Enabled Windows and SQL auth, again created a pure SQL user USER_Y, checked locally - ok, can connect. And checked connection from the third PC - I can connect fine as SQL USER_Y to the SQL server on a PC which is not on the domain but cannot connect as SQL USER_Y to the SQL server on a PC which is on the domain!
What am I doing wrong? How to connect from a PC on a domain to another SQL server on the same domain? It is just a basic config which (I think) SQL admins have gone through many times but I am stuck.
Help, please! I hope to hear from someone who has installed SQL server on a domain and successfully created remote connections.
When I try to access a SQL Server report on the localhost that I have deployed, I get a message that "under default settings SQL Server does not allow remote connections." After doing a little bit of searching, I went to the SQL Server Surface Area Connection and changed the server instance to allow for local and remote connections of both TCP/IP and named pipes. I stopped and restarted the service. Even after doing this I still get the same error.
If the Surface Area Configuration can't help out in this situation, what else would need to be modified?
I want to set up remote backup device on "serverCentral" for 50 MSDE SQL2k servers so that they could use one backup to create(restore) any new customer databases. This way, I could keep one resource with many coming updating on procs and triggers...
I could create remote backup device with serverCentralackupackupdeviceName...
The problem is the remote device is "access denied" when I issued a "restore headeronly from backupDeviceName" sql query.
Neither I could issue xp_cmdshell 'dir serverCentralackup' --"Access Denied" from server49 Though I could dir serverCentralackup*.* from server49 command prompt. It looks security permission is OK otherwise I could not dir from command line. thanks for the help David
[XXXXX] Connecting to remote server XXXXX failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet.
I am treating one of the XP Home system as 'Server' and installed SQL Express 2005 SP1. Enabled remote connections access.
I have total 4 XP Home systems, out of which one i am treating as Server, from the rest 3 computers, 2 are successfully connected to the Server and able to access SQL Express without any problems. But the 3rd system is unable to communicate with the Server. I disabled all firewalls in this 3rd system but still unable to connect to the server. I am able to ping the server, browse for shared folders on the server. Except SQL Express remote connection, everything else in the network is accessible from this 3rd computer.
Can anyone help me on how to troubleshoot this 3rd computer sql express connection problem to the server.
I don't have any error message to provide here. It just says, unable to connect to sql server, verify username/password etc.
Is there any limitation on SQL Express remote connections ?
All of the books I have about Visual Basic 2005 Database Programming, gives examples of connecting to a database on a localhost computer. But what about the connection to a database on a sql server 2005 on a computer wich can only be reached via the internet ? Is that possible without using ASP.NET ?
My problem:
I have a desktop with a sqlserver 2005 database . This desktop is connected with the internet . The IP address is a dynamic IP address.
On my laptop is a ADO.NET 2.0 program that needs to be connected with the database on my desktop.
What kind of address do I have to specify in my connectionstring in order to get connected to the database on my desktop , which can only be reached via the internet ?
I'm I wright to suppose that in the case of a static IP address, all I have to do is put the IP address in the connectionstring in order to get connected with my desktop via the internet? Are there some changings to be made in the settings of the SQL SERVER 2005 on my desktop ? What about the security ?
On the other hand , because the address of my desktop is a dynamic IP address, how do I solve this problem.?
I've heard about a program DynDns that can solve the problem of the dynamic address. Can i use this program together with my ADO.NET program to solve the problem , and how do I specify in this case the address to the database on my desktop in the connectionstring?
Is there someone who has experience with that program and the problem I described here ?
I am using XP_CMDSHELL to run 2 Windows commands (from a SQL 2005 SP2 server) that access files on a remote server (called webserver). The two commands are:
1. cscript.exe \webserverwwwrootEur_SaveProductImages.vbs 2. dir \webserverwwwroot Up until very recently this worked fine. Now I am getting Access Is Denied errors:
For #1: Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. CScript Error: Loading script "\webserverwwwrootEur_SaveProductImages.vbs" failed (Access is denied. ).
For #2: Access is denied.
This happens if the above commands are run through a job, or directly with Query Analyzer as SA.
I understand that XP_CMDSHELL commands are run in the security context of the SQL Server startup account. The SQL Server startup account is called SQLServer and this account exists on both webserver and the database server. On both servers the username & password are identical and the user is in the local Administrators group. The two servers are in a workgroup.
Things I have tried (with no effect):
1. Restarted the servers 2. Deleted and recreated the SQLServer login on both servers 3. Changed the startup account for SQL Server through the SQL Server Configuration Manager to another account and back to SQLServer.
The most revealing tests are these:
1. If I log into the database server myself using the SQLServer account I can run the above commands in a Command Prompt with no problem
2. I installed SQL 2005 Express SP2 on webserver using the same startup account (SQLServer). If I run the same XP_CMDSHELL commands as above but accessing files on the database server, the commands work! So, an XP_CMDSHELL command run under SQL Express using the local SQLServer account to access a remote server works, but an XP_CMDSHELL command run under SQL Server using a local SQLServer account (that is supposedly identical to the same named account on the other server) does not work !!?!?!?
It is almost as if XP_CMDSHELL commands run under SQL Server are NOT using the SQLServer startup account, but using some other weaker account. How can I tell if this is true?
How can I get this back working (as it was a week ago). The only thing I can think that happened on the servers to cause this is the installation of Windows Updates.
We connect to the remote database servers through the network from loca by using Query Analyzer. Previously we were able to execute the xp_cmdshell command from local Query Analyzer to fetch the remote databases data. But now we are unable to execute the xp_cmdshell command on remote databases from local Query Analyzer We do not know what happened but i think due to network updates this command is not able to execute...
For ex: Previously i was able to execute master..xp_cmdshell 'net start' from local Query Analyzer.But now not able to execute
Now my question is, is there any other way(Directly or indirectly) to execute the xp_cmdshell command on remote databases from local?
Note : we are able to execute this command on remote Query Analyzer but not from local QA
I am trying to set up a ODBC connection to a remote database using the ODBC data source administrator. I am getting an error message complaining of an invalid instance(). The database I am trying to connect to does have a default instance and a named instance. Do I need to specify the instance name somewhere in the connection settings? I tried specifying the server name as <Remote computer IP Address>/<Instance Name> but this didn't work. Any ideas?
