Hi all, We installed RS on a non default website on our IIS server. When targeting the Reports page from the server itself (http://site:8015/Reports) we can see the welcome page. However if we try to access that same page from another machine we get a generic IE message: IE cannot open the specified page check your internet connection etc. Because the error is so generic I have no idea as to what can be the cause: IIS or RS config ? I suspect IIS because no RS error is raised but then I don't see what I could've missed on that level... Any ideas of what could be the cause of this ? thanks a lot
Notes: - the DB and the RS instance are on the same server - other sites hosted on the same server are accessible from the client machine - Anonymous access is enabled on the site level, and on the Reports / ReportServer level. I tried unsetting it but it didn't change anything for the remote client. - I tried changing the account RS is running under: it used to be LocalSystem, I now set it to NT AuthorityNetworkService but no difference.
Environment: SQL Express Advanced & Windows Server 2003
I would like to be able to change the configuration of a remote machine`s SQL client config. Can anyone provide me with the registry location of where it stores the protocol and libraries? Can`t always depend on having someone at remote to run the SQL client app.
Hello all,I know that this is a long shot, but I have a problem which someonereading this group *may* just be able to shed some light on.We have a new internal personnel planner/attendance system in place. Ituses a web interface to allow members of staff to select their sitelocation for any week, request leave and record absences.The server-side scripting is composed of VB/ASP and Javascript whichultimately queries & writes to an MS SQL Server 2000 database via anODBC connection between webserver (IIS6.0).Here is the problem and I *know* that it sounds unlikely/impossible butwe carried out exhaustive tests.-> I open a web browser on my local PC (XP Pro SP2)-> Login to the web-based planning system-> Update information-> Submit ChangesAt this point I get a script error:---error message---Microsoft OLE DB Provider for ODBC Drivers error '80040e14'[Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntaxnear ')'./staff/wfp/Whereabouts/writeAbsence_v2_5.asp, line 108-------------------Which is fair enough as it probably points to a problem with the SQLstatement being passed by the .asp page.***BUT*** I _only_ get this message when I access the page via a browserfrom certain PCs!I have tried 3 browsers: MSIE6, Firefox1.5, Opera8.5.I have obviously ensured that it isn't any kind of browser caching issue.I have no issues using scripted-based web pages in general from the PCin question.I have checked the regional settings to ensure that I am using astandard character set.I *can* submit database changes via web browsers from most other PCs onour network, without incurring the error message.Even when I get the error message, the values are written to the db andthe information is updated.The other PCs from which I am experiencing the same difficulty areservers running Win2000 & Win2003 respectively.Is there any kind of OS/User Profile setting which would mean thatscripts running on a remote webserver would fall over when trying toperform an SQL write?Could it be some kind of character encoding issue, which means that theparameters that are received by the .asp script and then written via theSQL statement are mangled in any way?I can't see that there is any kind of local setting that would influencewhether remote scripts would or would not cause an error such as this.If anyone has any ideas, has encountered anything similar or can shedlight on a system-specific setting or feature that may cause this,please post your thoughts.Yours GratefullyGuy
I am a VB6 programmer and I'm really new to SQL Express, I have always used ACCESS because it was so easy to deploy. I've now written a VB6 program which uses SQL Express and I want to know how to deploy it. Basically my PC will host the SQL database as it has SQL Express loaded onto it. I now want to install my EXE onto other Client's PC and have them read/write to the database on my machine.
Besides the EXE program, what software do I need to load onto the Client's PC so they can access my SQLExpress database...? (eg: Net Framework, SQLExpress, etc).
Also, if my machine is called ABC123, in my connectionstring do I just put in
ABC123sqlexpress as the datasource..?. Will this be enough for the other PCs to connect to mine ?
I currently develop/maintain VB 05' apps for PDA's and desktops. I've got a scanner app that scans labels to build/transmit orders via an HTTP byte stream. I'm currently building an inventory app that resides at the remote client (windows not web) and can eventually connect to my SQL Server @ corp. At this point SQL 2005 endpoints work on the internal network but fail to resolve remotely. I've read about connecting to a SQL Server via HTTP with ip specs embedded in the connect string but havnt been able to find an example. Outside of creating a VPN for connectivity, can anyone recommend connection ideas for my scenario? Is it true that endpoints are only recommended for intranet consumption?
We have installed a SQL 2000 server on a windows xp-pro machine and succesfully installed DotNetNuke. Now is the problem that there is no way we can manage to get a client connected. We have tried everything, changing tcp port, setting permissions, changing registry according to document 307197 in the microsoft database and nothing helps. The only thing we can see is that in the serverlog we get a message stating that "SuperSocket Info : Bind failed on TCP port 1433". Can anyone help?Regards Ulla & Tom
I'm brand new to SQL server and all that and am having a little bit of hassles getting up and running.
I have a server 2003 computer running on my lan that I installed SQL server 205 express onto. I have attatched a database that I got with a C# book..
When I go into visual studio 2005 on the client to try and connect to te server vs cannot see the server at all.. the only server that displays is the client computer(which isn't a server??) I know there is a valid connection between the two computers because I login to the server using remote access..
Also, I have enabled TCP in the SQL server configuration program..
I wonder is there any beginnger guides on how to get the whole show up and running??
If I look under SQL native client configuration | Client protocols, I have no entries and no ability to look at the properties of SQL Native client Configuration. Something is missing which I think is related to an error when connecting to my local server.
sqlcmd -E -S .devmain, 1064
I get error :
Encryption not support sqlcmd: Error: microsoft SQL native Client : Client unable to establish connection
An error has occurred while establish 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..
In comparison to other machines here at work, it appears my remote connections are configured. But I have no Client Protocols under sql native client configuration, how can I get them in there?
Upgraded Enterprise Mgr. from SQL7 to SQL 20000. When trying to connect to SQl 2000 server using Enterprise mgr using TCP/IP am getting Invalid attribute/option identifier any suggestions???
Could someone please tell me what I need to do to be able to connect a user, who is on a Novell Network to a SQL Server using tcp/ip. Do I need to make the user a member of the NT Domain or have a local user account on the NT box, where the SQL Server is installed.
I have a Visual C# WinForms app which I am accessing a SQL Server 2005 database with. On the Server, I have allowed remote connections (TCP and named pipes) and enable SQL Browser as per instructions on MSDN. The app works fine on the development machine.
Server name is <machine name>SQLEXPRESS, connecting with Windows Authentication. Server log states that it is listening on [ 'any' <ipv4> 3153]. Server named pipe provider is ready to accept connection on [ \.pipeMSSQL$SQLEXPRESSsqlquery ].
On the client (local network), when trying to open the database I get this error still:
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)
Also on the client, I can go into the ODBC Data Source Administation, and connect to the SQL Server Database that way successfully.
What further steps can I take to allow the client to access the SQL Server?
I m a new member to this forum. Im a hardware engineer who rectify aome software related issues. Now our employees having problem with connecting their XP prof based clients to 2003 server from SQL query analyzer. I tried refresh sql server manager in server and tried restarting the server machine many times. sometimes it the client machine connects and disconnects immediately. i aslo tried changing the poll interval , but no use.
waiting for a speedy solutin... i know this is as easy query.
When you connect to SQL Server using SQLConnection, how to set client machine name(or IP address) so that you can monitor the process on Server side using Enterprise Manager?
I have a Visual C# WinForms app which I am accessing a SQL Server 2005 database with. On the Server, I have allowed remote connections (TCP and named pipes) and enable SQL Browser as per instructions on MSDN. The app works fine on the development machine.
Server name is <machine name>SQLEXPRESS, connecting with Windows Authentication. Server log states that it is listening on [ 'any' <ipv4> 3153]. Server named pipe provider is ready to accept connection on [ \.pipeMSSQL$SQLEXPRESSsqlquery ].
On the client (local network), when trying to open the database I get this error still:
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)
Also on the client, I can go into the ODBC Data Source Administation, and connect to the SQL Server Database that way successfully.
What further steps can I take to allow the client to access the SQL Server?
I have a Visual C# WinForms app which I am accessing a SQL Server 2005 database with.
On the Server, I have allowed remote connections (TCP and named pipes) and enable SQL Browser as per instructions on MSDN. The app works fine on the development machine.
Server name is SQLEXPRESS, connecting with Windows Authentication. Server log states that it is listening on [ 'any' 3153]. Server named pipe provider is ready to accept connection on [ \.pipeMSSQL$SQLEXPRESSsqlquery ].
On the client (local network), when trying to open the database I get this error still:
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)
Also on the client, I can go into the ODBC Data Source Administation, and connect to the SQL Server Database that way successfully.
What further steps can I take to allow the client to access the SQL Server?
i am using sql2005 on win2k3(sbs) platform(domain concept).my client is winxp.when i am tring to connect from client pc i am getting following error message.
connection failed sql state 01000 sql server error 233 microsoft odbc sql server driver(dbnetlib) connection open (connect) connection failed sql state 08001 sql server error 17 microsoft odbc sql server driver(dbnetlib)sql server does not exist or access denied
I have written a VB component to execute a SSIS package stored in SQL server.
I am using the Microsoft.sqlserver.dts.dtsclient, dtsconnection/dtscommand
and executereader and everything works perfect on the local machine. This is descibed in a msdn site .
But my customer have a remote SQL server and want no extra BI clients/SQL server clients etc on the client machine, only an ordinary windows client and network connection to the SQL server.
My question is: Can you still use dtsclient or do you have to do in some other way?
I am trying to link tables from an access 2003 frontend to sql server 2005 backend.
I am doing this in a vmware test environment. I am using vmware server and running sbs 2003 and xp sp2 client. Both virtaul machine can talk to each other(using local host connection).
I have tried to create a dsn to the sql server but i cannot connect. I can ping the sbs server through the command interface but the error i get when i try to connect is :
Connection failed: Sql state: hyt00 sqlserver error: 0 microsoft odbc sql server driver timeout expired.
spent a day trying various combinations - still no joy.
Here is my problem: I have SQLEXPRESS running with Windows Authentication on a "server" PC named "ASUS1", and I need to connect from a "client" PC named "Presario1", user "Mauro", connected through a peer network (I use a cross-over cable); both PCs belongs to the same workgroup named "RMT-WORK", and they can see each others shared folders without problems.
I have installed the connectivity components + Management Studio Express on Presario1, and enabled named pipes and TCP/IP protocols; then I've got SQL Browser running. I have also added the Login "Guest" on ASUS1SQLEXPRESS.
When I start Management Studio Express on Presario1 and browse for servers I can select "ASUS1" as database engine but when I try to connect I receive "Error 40: could not open a connection to SQL Server" (same result using SQLCMD); I have tried to add on ASUS1SQLEXPRESS a user "Presario1Mauro" with "CREATE LOGIN [Presario1Mauro] FROM WINDOWS" but I receive a "Windows user not found" error...
i have a small problem to connect SQL Native ODBC Client to a mirrored Database. The connection goes without any problem when I connect to a primary Database, but when i give this connect string to an ODBC Client ""Server=Partner_A; Failover Partner=Partner_B; Database=XXX; Network=dbmssocn"", then i get an connect fail. There are no firewalls and other things on the network. I am also able to connect to a mirror database during failover, but I'm not able to set both servers on the ODBC Connection.
We are unable to connect with Client SQL database server using VPN connection, even we are able connect with their intranet site.
We tried to connect using IP address, but no success. After that tried to ping that server with server name and IP address using command prompt, but got request time out error.
Help Me In This : My Client Applicaion Can't Connect To Sql Server 2005 Express
Story :
I have Application Coded by C# To Connect To Sql Express Data Base , And I have Form In This Application To Configure The Connection String .
This Application Is Tested Local Ok (MY Server Name :- .SqlExpress ) When i User This Application In Client In Same Network And Try To Connect To The Data Base In Server (My Server Name :- ServerNameSqlExpress ) This Error Appeared "Server Does Not Exist Or Access Denied"
Note : I Configure My Server Configuration And Enabled The Tcp/ip .
Questions : How Can I Connect To Data Base From Client To Server Through NetWork Connection Using ServerNameInstance ?
How Can I Connect To Data Base From Client To Server Through NetWork Connection Using IpInstance ?
How Can I Connect To Data Base From Client To Server Through InterNe ?
All This Questions Using Sql Server 2005 Express .
Someone please help me before I loose all of my hair :mad: !!!
I have two machines, a Windows Server 2003 machine running an SQL Server Standard Edition database instance and client tools (Enterprize Manager etc.), and a workstation PC running Windows XP SP2 which has just the SQL Server client tools (not an actual DB instance).
I'm trying to use the Enterprize Manager client tool on my WinXP machine to remotely connect to the server instance on the server PC (via 'New SQL Server Registration' option). Everytime I do this I get the following error message:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server Connection.
Now I've tried using different usernames and passwords. I have login details for my SQL Server set to use Windows Login rather then SQL Server login, so I tried remotely connecting with the username and password for the server PC, tried 'sa' with server password, even tried setting up a new user on the server and logging in from the client with that, no luck. I've opened up correct ports 1433 on both PCs, even disabled the windows firewalls algother. Both server and client have SP3a installed, WinServer2003 has SP1 and XP SP2.
So I'm at a loss to how to remotely connect to my SQL Server. FYI I know the server itself is working fine because I can connect to it using Enterprize Manager/Query Analyser on the local machine. Any ideas? Many thanks for your help!
Anyone support a config where you have an unix/linux (AIX here) ODBCclient connection to SQL Server database? I am looking for a simple,supportable configuration that does not require me to learn perl orinstal a bunch of crap gnu shareware on enterprise class machines.Please help!
Hey. I've a windows vista machine which can't connect to SQL 2005 box. Other machines which are lower than vista work fine. Also, vista box can connect to other SQL 2005 instances but can't connect to only one instance. But, I can connect to the instance fine from my XP box. Also, it's not a permissions issue. This user is an SA and can connect form some other machine. SQL 2005 box is at 2047 version right now. And, the user is able to connect to some other boxes which are also at 2047. Please help. Thank you
Hi all,myDB is located atX:Program FilesMicrosoft SQL ServerMSSQLDatamyDB.mdfand my code is located at : C:Inetpubwwwrootapplicationfolderhow do I code my server.mapPath?
Btw, can I get VS 2005 to detect the server path when using server solution.Thanks sub Page_Loaddim dbconn,sql,dbcomm,dbreaddbconn = New OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;data source=" & Server.MapPath("X:Program FilesMicrosoft SQL ServerMSSQLDatamyDB.mdf"))dbconn.Open()sql = "SELECT * FROM myTable"dbcomm=New OleDbCommand(sql,dbconn)dbread=dbcomm.ExecuteReader()myDB.DataSource = dbreadmyDB.DataBind()dbread.Close()dbconn.Close()end sub
