Sql 2005 Remote Connection

I am having a problem connecting to a remote SQL server 2005 instance.  The remote server is for a website hosting account of mine.  I can connect to the server from computers other than the problem computer just fine.  I cannot connect to the server using any software including SQL Server Management Studio Express, Visual Web Developer, or even when trying to use aspnet_regsql.exe on the problem computer.  The request to connect to the remote server never seems to leave my computer.  When talking to my hosting service, they replied that they did not receive a request to connect to their server from me.  I have shut down Windows Firewall as well as my third-party firewall with no change.  The error message that I receive is:
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: 53)
If anyone has any ideas they would be appreciated.

There are a couple of changes that need to be made to allow remote connections to the server... and these need to be made on the server. Have a look at this KB Atricle. Also one way to test is to create a simple ODBC Connection and see if you can get through. Also I see it stange that a hosting company is allowing remote connections to the database server, normally they only allow connections through some sort of web interface or one of there own client tools.

Similar Messages

  • MS SQL 2005 remote connection using sqljdbc

    Hi,
    I have production line computer with software using java code and firebird database, i also have sqljdbc.jar also in the library.
    my software is trying to connect to mssql2005 database in a remote computer and got this error message:
    java.lang.classnotfoundexception: com.microsoft.sqlserver.jdbc.SQLServerDriver.
    I have no problem when connecting to my local mssql2005 database though. but have problems when trying to make remote connection.
    May i know what could seem to be the cause of the problem, is there anything missing ? do i need to instal anything else on the production line computer? currently it does not have mssql2005 instal on the production computer do i need to instal it ? please help. thanks

    Btreksun wrote:
    Hi,
    Im using MS SQL 2005 Express edition, I dont find any sqljdbc.jar driver inside the installation,
    I dont see any other driver or driver folder in the installation path.
    Inside my instalation path C:\Program Files\Microsoft SQL Server: only shows these folders
    MSSQL$MSSQL2000
    MSSQL.1
    80
    90
    100
    "Class path" applies to java. None of the above is java.
    I dont know what to set my classpath with?You are running your java in "something". That "something" is an application. That "something" does not have the correct class path. You didn't tell us what it is so we can't help you with it.
    I even download sqljdbc.jar and put it inside C:\Program Files\Microsoft SQL Server and set the classpath but doesnt work ?I suggest you google for class path, read several articles about it and try some of the stuff that they talk about.

  • Trying to use Linked Servers in SQL 2005 to connect to RDB 7

    I'm looking for detailed info on how to set up a linked server in SQL 2005 to connect to my Oracle RDB 7 database (running on VMS). I'm able to connect via odbc using VS.Net and Sql Server 2005 Reporting Services. I'm not sure if I need to use the ODP.NET or not. I have created a generic linked server, but it requires me to use the OpenQuery function to access the data, which is not giving me the functionality I'm looking for.

    Hi doanpq,
    Please download and install OLE DB Provider for Visual FoxPro 9.0, which exposes OLE DB interfaces that you can use to access Visual FoxPro databases and tables from other programming languages and applications. Please see:
    http://www.microsoft.com/en-us/download/details.aspx?id=14839
    Then, please follow up the following article to create a linked server:
    Creating Linked Servers:
    http://technet.microsoft.com/en-us/library/ff772782(v=sql.105).aspx
    For more information, you can also take a look at the following article, especially Dave K's comment:
    http://blog.dbase.integralwebsolutions.co.za/2008/10/accessing-your-dbf-tables-via-linked.html
    Elvis Long
    TechNet Community Support

  • SQL 2005 remote login

    Hi there,
    Could you let me know me - how do you configure / disable remote logon for SQL 2005. Are <sid> and SAP<SID>DB allowed to logon remotely?
    Thank you!
    Sim

    Hi,
    if you want to disable remote login on sql server 2005 do following
    -> Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration.
    ->On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration for Services and Connections.
    ->On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Remote Connections
    if you only allowed local connection then check local connections only. apply
    regards,
    kaushal

  • Windows authentication for SQL 2005 DB connect

    Hi all,
    I'm trying to create a DB connect
    in the connection parameters when I mention a user name and password who is created as a SQL authentication then it is working fine.
    but in my connection parameters if I mention a user name password who have a Windows authentication in the SQL 2005 which we are trying to connect then it gives an error. It is not connecting .
    Can you please tell me how can we connect using a windows authentication.
    Mey

    Solution to solve the actual issue :
    For the SAP system to use standard default NT authentication
    Please refer to this link: http://help.sap.com/saphelp_nw04s/helpdata/en/9c/d736b880c34f76b507bac7751a0474/content.htm
    1.       Database login:
    SQL Server login with System Administrator privileges, that is this login should be member of the sysadmin fixed server role on the target SQL Server. If such a login does not exist, you have to create it on the target SQL Server. The SAP multi-connect mechanism allows both integrated security logins and the use of SQL Server authentication. For security reasons, we highly recommend to use integrated security (Windows authentication). If you use Windows security, leave this field empty.
    2.     &#61601;        Password / Re-enter password :
    If you have decided to use integrated security, leave these fields empty. Otherwise enter the password of the SQL Server login.
    The above pointer was used to solve the login issue but we still had issues in getting the schema visible in SAP BW. As the user ID was left blank we were not able to get the schema view for the <blank> user.
    Note to be applied to solve the Schema issue :
    note 1091929 : &#61664; Link
    so now you can enter the schema to be used in DS creaton screen.

  • 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,

    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)

    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)
    Hello,
    Make sure your SQL Server service is started.
    Make sure TCP\IP and names pipes protocol is enabled
    Make sure you have made an exception in firewall for SQL Server connection
    Make sure SQL Server browser service is enabled
    Make sure you connect with correct name hostname\instance name for named instance,MSSQLSERVER for default instance and Hotname\SQLEXPRESS for express edition.
    Please make sure you use port no when connecting to SQL server listeing on different port (hostname\instance ,portno)
    http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
    Hope this helps
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (p

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that
    the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)(Microsoft SQL Server, Error: 2)
    The system cannot find the file specified
    Cannot connect to COWBOYS.
    Here are the technical details===================================
    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
    Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
    Error Number: 2
    Severity: 20
    State: 0
    Program Location:
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
    timeout)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
    SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
       at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
    ===================================
    The system cannot find the file specified
    I have tried from so many forms. This is so frustrating. Thank for everyone/anyone who wants to help. So this is what happened: I had to uninstall my previous sqlserver 2012(which worked great) for some reason, and I uninstalled everything from that download.
    Then I installed the trial edition of sql server 2012 (64 Bit) and It wouldn't connect to the database. (Error mentioned above.) My local DB is COWBOYS. (COWBOYS is also my computer name.) After this, I have tried downloading sqlexpress and sqlserver 64bit
    many times and cannot connect to my local DB. 
    How do I connect to my Local DB? 
    Also, I think this might help: (When I run sqlserve.exe, which I was able to find in C:\Program Files\Microsoft SQL Server\110\LocalDB\Binn, I get an error: Your SQL server installation is either corrupt or has been tampered with(Error getting
    instance ID from name). Please uninstall then re-run setup to correct this problem.
    I would happily re install it, if it wasn't my 20th time.
    I don't have any remote connections, I don't use username/password, only window authentication. I work mostly on visual studio, but without able to store /retrieve data, I don't know how to survive.
    May be the solution is very simple, but I am too frustrated. 
    Some of the things I have tried:
    From a command prompt, enter one of the following commands:
    net start "SQL Server Agent (MSSQLSERVER)" OR 
    net start "SQL Server Agent(instancename)"(for instance)
    on my sql configuration, I cannot start anything because there is nothing there to start. I can post more details, if that would help. Also, some more details about the error:
    Details
    Product:
    SQL Server
    ID:
    2
    Source:
    MSSQLServer
    Version:
    10.0
    Component:
    SQLEngine
    Message:
    An error has occurred while establishing a connection to the server. When connecting to SQL Server, 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) (.Net SqlClient Data Provider)
    Explanation
    SQL Server did not respond to the client request because the server is probably not started.
    User Action
    Make sure that the server is started.
    Version:
    9.0
    Component:
    SQLEngine
    Message:
    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) (.Net SqlClient Data Provider)
    Explanation
    SQL Server did not respond to the client request because the server is probably not started.
    User Action
    Make sure that the server is started.
    Any one that can help me, I will be greatful. Thank you so much. p.s. please ask me anything if you have any questions.

    It sounds like there are a couple things going on here.  First check if you have a successful install of SQL Server, then we'll figure out the connection issues.
    Can you launch SQL Server Configuration Manager and check for SQL Server (MSSQLSERVER) if default instance or SQL Server (other name) if you've configured your instance as a named instance.  Once you find this, make sure the service is started. 
    If not started, try to start it and see if it throws an error.  If you get an error, post the error message your hitting.  If the service starts, you can then launch SSMS and try to connect.  If you have a default instance, you can use the machine
    name in the connection dialog.  Ex:  "COWBOYS" where Cowboys is the machine name.  However, if you named the SQL Server instance during install, you'll need to connect using the machine\instance format.  Ex:  COWBOYS\Romo (where Romo
    is the instance name you set during install).
    You can also look at the summary.txt file in the SQL Server setup error logs to see what happened on the most recent install.  Past install history is archived in the log folder if you need to dig those up to help troubleshoot, but the most
    recent one may help get to the bottom of it if there is an issue with setup detecting a prior instance that needs to be repaired.
    Thanks,
    Sam Lester (MSFT)
    http://blogs.msdn.com/b/samlester
    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
    "Mark as Answer" and
    "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

  • Unable to Access SQL Server 2005 Remotedly

    Not sure if this is the right forum to post this...
    After going through lot of old posts in various forums and changing lot of settings, i'm still not able to access my Server remotely.
    This is Windows 2003 Server machine with Sonicwall Firewall, i have allowed Port 1433 in both Firewall and ISA and call is getting through but i'm getting following error msg :-
    {"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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"}
    This machine is also having Sql Server 2000, and the SQL Server 2005 is installed with named instance.
    My connection string is :-
    "Data Source=192.168.0.1\MYSERVER;Initial Catalog=MyDatabase;Integrated Security=True"
    In example above, i'm showing dummy values but actual string is having the actual live IP address and correct named instance and database.
    If i use a local address like 192.168.0.1 then i'm able to connect.
    My TCP/IP Address in Sql configuration is having my Live IP Address and the port 1433.
    Any help will be highly appreciable..

    i'm still checking on this. i have changed the port now to 1434 and changed in all places.
    my connection string is also changed now, so now i'm using :- MYIP\MYSERVER,1434
    now i'm getting a different error msg
    {"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: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)"}
    this can also be due to firewall or something else is blocking it, i will rechk n post back final answer.

  • Remote Connection from SAP to MS-SQL server

    Hello Experts,
    We have been following 2 options so far and we have come across some issues
    The first Option is to call a stored procedure (this is our preferred method) which does the data transfer for us
    We have been able to test this scenario successfully from SQL Server side
    However, while calling the stored proc via native SQL from ABAP we have come across an issue which is due to SQL 2005 changes (Schema implementation and difference in the security context)
    While calling the stored procedure from the ABAP Code we have an error
                The program short dumps with runtime error DBIF_DSQL2_SQL_ERROR, exception CX_SY_NATIVE_SQL_ERROR. The database error code is 15274, and the error text is
                 "Access to the remote server     is denied because the current security context is not trusted."
    This issue is new after the SQL Server 2005.
    We are trying to resolve that.
    Secondly we have been trying the DBCON option as well as per OSS Note 323151
    We have a few things thatu2019s impacting our scenario:
    The remote servers are in a different domain
    The remote servers are located  in DIZ
    Remote server is a named instance
    Remote server has been configured with a different port than standard (1565) u2013 All Connection strings will need port in there
    The Database name starts with a numeric value
    Due a combination of factors as mentioned above the standard approach does not work
    Have any of you used this approach while connecting from SAP to MS-SQL server? Do you know of any successful methods to connect to SQL using ABAP (or not) from SAP.
    Thanks in advance,

    Yes,
    DBConnect & UDConnect.
    Works like a charm.
    We write data into a MS-SQL database via DBConnect & an ABAP program (using open sql).

  • Unable to Remote connect to a SQL 2008 server

    I just set up a virtual server with Godaddy with CF and SQL Server 2008
    The SQL server appears to be running because if I RDC into the server and connect using the Server management Studio, it works. To find the instance I have to look at network devices and I find it under MACHINENAME\SQLINSTANCE
    The problem I have is that I want to connect to this instance using server management studio on a computer with SQL2005 installed. I guess/hope that a 2005 can connect to a 2008
    I'm not 100% sure what the exact correct format is for the "Server Name" when trying to set it up. I've tried everything I can think of
    ServerName\IPNumber\Instance
    IPNumber\ServerName\Instance
    IPNumber\Instance
    Nothing seems to work, it kicks back with a big error, aying it can not connect:
    A network-related or instance-specific error occured while establishing a connection to SQL Server.
    The server was not found or was not accessible. Verify the instance name is correct and that
    SQL Server is configured to allow remote connections (provider: SQL Network Interfaces, Error: 26-
    Error Locating Server/Istance Spcified) (Microsoft SQL Server)
    The firewall on the server is off, I checked the properties of the instance and the option to allow remote connections is also checked
    Anybody have any ideas?
    Thanks
    Mark

    Solved this myself.
    I was trying to log in with the user name of the adminstrator for the server, which worked locally while on the server but when I tried to use SQL SERVER AUTHENTICATION , tapping in the user name and password, it failed in the same way, even though the password was correct. Connecting using WINDOWS AUTHENTICATION worked, so I checked the users and found that user name did not have a password set because it was the admin I guess, so it just rejected all attempts using SQL SERVER AUTHENTICATION.
    What I then did is tried the 'sa' user, and saw that it did have a password set when I viewed it in USERS... so I tried to connect remotely using that, and it worked... problem solved
    Thought I'd post that, just incase anybody else came across the problem
    After posting this I reversed a change that I had made from info found on another forum, and it stopped working! I put the change back again and it works, so it looks like a combo, here is the info that I found that helped fix the problem
    "In the SQL server configuration manager, there is an item called SQL server network configuration, under protocols, I selected the properties of the TCP/IP protocol. There is a tab “IP Addresses” there, and at the bottom of the list is an entry called IPAll. In my case the TCP port was empty. I entered the SQL standard port 1433 in there and I was able to connect."
    I had also since posting upgraded to 2008 locally, not that I believe it had anything to do with the problem
    Mark

  • Error in Connecting to MS SQL 2005 via JDBC Driver

    Here's the setup
    CF MX7 resides on a centOS wid Apache 2.0 webserver box.
    I need to established a datasource connection between the
    Coldfusion server and a MSSQL 2005 Express+SP1 database sitting on
    a remote XP wid SP2 setup.
    I've also downloaded and installed on the /lib folder of the
    CFMX7 server the corresponding JDBC drivers (versions 1.1 and 1.0)
    for the MS SQL server.
    The thing is, this problem always occurs:
    Connection verification failed for data source:
    datasourcename
    java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
    JDBC]Error establishing socket.
    The root cause was that: java.sql.SQLException:
    [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing
    socket.
    The datasource connection info is as follows:
    CF Datasource Name: datasourcename_JDBCdriver
    JDBC URL:
    jdbc:microsoft:sqlserver://192.168.0.47:1433;DatabaseName=nameofdatabase
    Driver Class: com.microsoft.sqlserver.jdbc.SQLServerDriver
    Driver Name: mssql2005
    Username: sa
    Password: userdefinedpassword
    I've already tried these settings:
    * Enabled mix mode of authentication under the SQL server
    * Affix a /MSSQLSERVER instance name on the jdbc url setting
    "jdbc:microsoft:sqlserver://192.168.0.47\MSSQLSERVER:1433;DatabaseName=nameofdatabase"
    but a different error had occured:
    The root cause was that: java.sql.SQLException:
    [Microsoft][SQLServer 2000 Driver for JDBC]The requested instance
    is either invalid or not running.
    so i remove it since its only an optional setting
    * Configured the SQL 2005 Express, under the SQL Server
    Configuration Manager, to listen to protocol TCP/IP under port 1433
    (this is the ONLY ENABLE protocol)
    I've checked using Telnet and netstat and the SQL service is
    normally listening to the said port.
    * Disabled windows firewall under XP (came with SP2)
    and even tried using other JDBC drivers such as:
    * macromedia drivers
    * jtds driver
    but to no avail.
    Is the problem still within the MS SQL 2005 Express wid
    XP+SP2 box or a connecting issue on the Cf server under the
    centOS/Apache machine?
    A little help would do wonders just about now.

    I had the same problem, but do not have express version. In
    the configuration manger, I viewed the properties of the enabled
    tcp/ip protocol. On the IP addresses tab, I found that though the
    IPs were enabled, the drop down beside active was no. I changed all
    to yes, applied it and restarted my instance. Then in the cf
    datasource I left the port blank and everything worked.

  • Visual Studio 2005 The remote connection to the device has been lost. Please verify the device connection and restart debugging.

    Basically I've been using Visual Studio 2005 for a few weeks now moving a Pocket PC project from 2003 to 2005. When I hit the Start Debugging Button every time until today the project would rebuild and deploy to my pocket PC allowing me to debug etc but now I get
    The remote connection to the device has been lost.
    Please verify the device conection and restart debugging.
    I used to get this problem in VS2003 sometimes and just like the numerous posts on different sites that I've looked at the problem eventually goes away and I'm none the wiser. One guy said that he found that if he went to bed the problem was resolved when he came back!
    My PDA running Windows 2003 2nd Edition is directly connected to my PC via a USB port. I've rebooted my PC and done a soft reset on the PDA but it didn't help. I'm using ActiveSync 4.1.
    Does anyone know how to resolve this problem?

    I still can't debug. I have just tried a hard reset and I get the same problem
    The build output is as follows
    ------ Build started: Project: BO, Configuration: Debug Any CPU ------
    BO -> C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\BO\bin\Debug\BO.dll
    ------ Build started: Project: Printing, Configuration: Debug Any CPU ------
    No way to resolve conflict between "System.Data.SqlServerCe, Version=3.0.3600.0, Culture=neutral, PublicKeyToken=3be235df1c8d2ad3, Retargetable=Yes" and "System.Data.SqlServerCe, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes". Choosing "System.Data.SqlServerCe, Version=3.0.3600.0, Culture=neutral, PublicKeyToken=3be235df1c8d2ad3, Retargetable=Yes" arbitrarily.
    Printing -> C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\Printing\bin\Debug\Printing.dll
    ------ Build started: Project: MobileSeller, Configuration: Debug Any CPU ------
    Consider app.config remapping of assembly "System.Data, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "1.0.5000.0" [] to Version "2.0.0.0" [C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\System.Data.dll] to solve conflict and get rid of warning.
    Consider app.config remapping of assembly "System.Windows.Forms, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "1.0.5000.0" [] to Version "2.0.0.0" [C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\System.Windows.Forms.dll] to solve conflict and get rid of warning.
    Consider app.config remapping of assembly "System, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "1.0.5000.0" [] to Version "2.0.0.0" [C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\System.dll] to solve conflict and get rid of warning.
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3247: Found conflicts between different versions of the same dependent assembly.
    MobileSeller -> C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\bin\Debug\MobileSeller.exe
    Done building project "MobileSeller.vbproj".
    ------ Skipped Deploy: Project: BO, Configuration: Debug Any CPU ------
    Project not selected to build for this solution configuration
    ------ Skipped Deploy: Project: Printing, Configuration: Debug Any CPU ------
    Project not selected to build for this solution configuration
    ------ Deploy started: Project: MobileSeller, Configuration: Debug Any CPU ------
    Deploying 'C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\v2.0\windowsce\wce400\armv4\NETCFV2.ppc.armv4.cab'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\BO\bin\Debug\System.Data.Common.dll'
    Deploying 'C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v2.0\wce400\ARMV4\sqlce20.ppc.wce4.armv4.CAB'
    Deploying 'C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v2.0\wce400\ARMV4\sqlce20.dev.ppc.wce4.armv4.cab'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\BO\bin\Debug\InTheHand.Data.Adoce.dll'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\BO\bin\Debug\InTheHand.Interop.dll'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\Printing\bin\Debug\PocketHTMLprint_NetCF.dll'
    Deploying 'C:\Dev\MILLAR CODE CABINET\VS2003CF\References\USICF.dll'
    Deploying 'C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce400\ARMV4\sqlce30.ppc.wce4.armv4.CAB'
    Deploying 'C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce400\ARMV4\sqlce30.repl.ppc.wce4.armv4.CAB'
    Deploying 'C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce400\ARMV4\sqlce30.dev.enu.ppc.wce4.armv4.CAB'
    Deploying 'C:\Dev\VS2005CF\References\release\Signature.dll'
    Deploying 'C:\Dev\VS2005CF\References\release\RealUpDown.dll'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\Printing\bin\Debug\Printing.dll'
    Deploying 'C:\Dev\VS2005CF\References\release\PhoneAPI.dll'
    Deploying 'C:\Dev\VS2005CF\References\release\MVnetApplication.dll'
    Deploying 'C:\Dev\VS2005CF\References\release\MobileHList.dll'
    Deploying 'C:\Dev\VS2005CF\References\release\MobileGrid.dll'
    Deploying 'C:\Dev\VS2005CF\References\release\ImageButtons.dll'
    Deploying 'C:\Dev\VS2005CF\References\release\CreditCardValidator.dll'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\BO\bin\Debug\BO.dll'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\View.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Unscheduled.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Unschedule.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\tr.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\top.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Tools.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\tl.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\SmlButUnPressed.jpg'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\SmlButSquUnPressed.jpg'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\SmlButSquPressed.jpg'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\SmlButPressed.jpg'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Select1.jpg'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\sekonda3.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\sekonda2.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\sekonda1.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\ScrewDriver.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Scheduled.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Scheduled.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Schedule.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Scan.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Save.ICO'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Remove.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\ReceiptTemplate.htm'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Problem.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\PrintDC.dll'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Print.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Prev.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\bin\Debug\PocketHTMLprint_NetCF.dll'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\pocketHTMLprint.dll'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Phone.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Page.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\NotesExist.ICO'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Notes.ICO'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Next.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\NewCust.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\MVNetLogoSmall.png'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\mtiny.jpg'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\MoneyScrew.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Money.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Magnify.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Lock.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Line.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\InvoiceTemplate.htm'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\gradus4.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\gradus3.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\gradus2.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\gradus1.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\FindVisit.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\FindCustomer.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Find.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\DropDown.jpg'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\dentsplus3.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\dentsplus2.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\dentsplus1.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\DentDevilsCar.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\DentDevils2.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\DentDevils1.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Default2.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Default1.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Cust.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Completed.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Cancelled.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\Call.ico'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\br.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\bottom.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\bl.gif'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\BigButUnPressed.jpg'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\Resources\BigButPressed.jpg'
    Deploying 'C:\Dev\millar\MobileSeller\code\2005\MobileSeller\MobileSeller\MobileSeller\bin\Debug\MobileSeller.exe'
    Deploying 'C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\v2.0\windowsce\diagnostics\System_SR_enu.cab'
    ========== Build: 3 succeeded or up-to-date, 0 failed, 0 skipped ==========
    ========== Deploy: 1 succeeded, 0 failed, 2 skipped ==========
    Visual studio indicates that
    Deployment Started
    Depolyment Succeeded
    Loading Symbols
    Ready
    and then I get the same problem ie The Remote connection to the device has been lost

  • How to enable remote connections in SQL Server 2008

    I'm trying to enable remote connections in SQL Server 2008 R2 as described in the following article.  I see the error message at the top of the article. 
    http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx
    One step in the article describes how to enable TCP/IP in Configuration Manager.  Specifically it says that
    'SQL Server NETWORK Configuration' should have TCP/IP enabled.
    The issue I've encountered is that my Configuration Manager
    is different than what appears in the article. My Configuration Manager shows the following:
    SQL Server 2005 Services
    SQL Server 2005 Network Configuration (32 bit)
           - Protocols for SQLExpress
    SQL Native Client Configuration (32 bit)
           - Client protocols
           - Aliases
    Note that I see 'SQL Server 2005 Network Configuration'
    rather than that for 2008.  When 'Protocols for SQLExpress'
    is expanded, there is a TCP/IP setting, but it's disabled and I see an
    Access Denied message if I try to enable this. 
    I also see a TCP/IP setting under Client protocols and successfully enabled this.  This uses port 1433 and I configured my firewall to accomodate this port as suggested in the article. 
    I also followed the other steps in the article, but still don't have remote access to SQL Server 2008 R2.  (I can access it from the office.)  I'm wondering if this remote access issue is because SQL Server
    2008 Network Configuration does not appear in Configuration Manager
    and if so, I'm interested in how this might be resolved.  (I'm running Windows 7 - 64 bit.)
    I'd appreciate any ideas on this.  Thanks. 

    Hello,
    Please refer to the following resource.
    http://support.microsoft.com/kb/KbView/914277
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • SQL 2005 will not connect in SQL 2012 profiler

    We have a few SQL 2005 databases that we manage. I went to do a trace on them(recently upgraded to 2012) and it gives me the error, "SQL Server Native Client 11.0 does not support connections to SQL Server 2000 and earlier versions".
    According to MSDN it does.  https://msdn.microsoft.com/en-us/library/cc280356(v=SQL.110).aspx  
    "SQL Server Native Client 11.0 supports connections to SQL Server 2005, SQL Server 2008, SQL Server 2008
    R2, SQL Server 2012, and Windows Azure SQL Database."
    Any clue why it wouldn't let me connect?

    Can you specify the following parameter in the "connect to server" dialog when you load the Profiler --> click on "options" button and go to "Additional Connection Parameters" tab and paste the following?
    DataTypeCompatibility=80
    Satish Kartan www.sqlfood.com

  • Database connection to MS SQL 2005 (URGENT Help Needed)

    Hi all,
    Does anyone know how to connect my adobe form to MS SQL 2005?
    I have this code:
    try {
         InitialContext initialContext = new InitialContext ();
         DataSource dataSource = (DataSource) initialContext.lookup ("jdbc/MyAlias");
          java.sql.Connection connection = dataSource.getConnection ();
    } catch (SQLException e) {
         // handle exception
    } catch (NamingException e) {
    // handle exception
    Other than these, what else do i need to do inorder to get my database connection up?
    And after my database connection is up, how do i test to check if my database connection is up or not?
    How do i extract the information from the database and put them onto the textfields/dropdownlists on my form?
    Thanks In Advance

    Hi Mel,
    After implementing the codes and modifying them, some of them are underlined, why is this so? =X
    Or are u willing to exchange msn so i could send u the screenshot instead?
    Thanks In Advance
    (Sorry im not that good in this)
    (I shall underline the areas which represents the red underline in my web dynpro)
         //Code for database connection.
           InitialContext ctx = new InitialContext();
           DataSource ds = (DataSource)_ctx.lookup("jdbc/JXDataSource");_
           Connection conn = ds.getConnection();
           Statement st = null;
           ResultSet rs = null;
           IPrivateDetailed_Claims_FormView.IFillDataElement dataEle = null;
           st = conn.createStatement();
         //     Execute the appropriate SQL query
           rs = st.executeQuery("SELECT NAME WHERE VENDORCODE='9000116L' ");_     
           while (rs.next())       {
         //     Code that will populate your VN based on the data obtained in the ResultSet.
           dataEle = wdContext.createFillDataElement();
           dataEle.setName(_rs.getString(1)_);
          // dataEle.setAge(rs.getInt(2));
          // dataEle.setAddress(rs.getString(3));
           //wdContext.nodeFillData.addElement(dataEle);
           //  Close the connections
           rs.close();
           st.close();
                      conn.close();
    Edited by: JingXuan Lim on Jan 25, 2008 4:59 AM
    Edited by: JingXuan Lim on Jan 25, 2008 5:00 AM

Maybe you are looking for