SQL server remote configuration
Hi,
We are trying to install just the BIDS in a user machine to be able to develop reports remotely. I have a couple of questions.
1. In my current scenario, SQL server 2008 R2 is already setup with the reporting services in say, Machine1. Can it be reconfigured so that
a user in Machine2, trying to develop a report, access report server DB in Machine1?
2. Can this be done in such a way that, first we want to point BIDS to a sample database (like Adventureworks etc.) in Machine1, before trying
to develop reports with the actual database?
Could anyone help with the detailed steps involved.
I have done development of reports with an SQL server installation and configuration in the same machine sometime before, but not remote.
I looked for manuals, there is help available, but for this scenario, I want to confirm with the steps involved.Any input in this regard would be extremely helpful.
Thanks,
SK
Hi valueinfo,
As per my understanding, you have a machine named machine1 with Reporting Services in SQL Server 2008 R2 installed. When the users create reports using BIDS, you want to allow them to use the database installed on machine1 remotely. If that is the
case, we need to allow remote connections to this server, then add new login to the database. For detail information, please refer to the following steps:
In SQL Server Management Studio, right-click the instance and open properties dialog box.
Click Connections, in Remote server connections section, check Allow remote connections to this server check box.
To configure database access, expand the Security folder, right-click Logins, and then click New Login.
In the Login – New dialog box, specify SQL Server Authentication mode.
Type a logon name and password, and then confirm the password.
In the left pane, click Database Access.
In the right pane, select the Permit check box for the databases you are granting access to, and then click OK.
If we want to use Windows Authentication, we need to be members of the local Administrators or users group.
Reference:
How to enable remote connections in SQL Server
How to add a SQL Server Login
If there is any misunderstanding , please feel free to let me know.
Best Regards,
Wendy Fu
Similar Messages
-
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. -
Hi,
I have taken farm back and restore it in new UAT environment, while access to the main site getting the below error:
Error
An unexpected error has occurred.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 866476f3-23dd-4e1e-97af-bffc62cc2d57
Date and Time: 7/15/2014 11:26:35 AM
When i checked in log i got below error
System.Data.SqlClient.SqlException: 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) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj) at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecu...
Thanks in advance
Said Al BalushiHi Wendy,
i have checked all below points, every thing is fine but still i am getting the same error.
Check SQL services are runing
Check remote conenctions are enabled
Check SQL Browser service is runing
Check TCP/IP protocal enabled at SQL server
Check out windows firewall setting
Thanks,
Said
-
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: SQL Network Interfaces, error: 26- Error:Locating Server\instance Specified)
How Can i solve this?1. Make sure SQL Server Service is running
2. If a named instance, make sure SQL Server browser service is running
3. Make sure SQL Server is configured to allow remote connections
4. Examine the SQL Server error log for messages confirming that SQL is listening on the expected network interfaces and ports
5. Test server connectivity with PING from the client machine
6. Test port connectivity using TELNET or PowerShell to the server and port (from step 4) from the client machine. For example
a. TELNET <server-name> 1433
b. PowerShell: 1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect("YourServerName",$_)) "server listening on TCP port $_" }
7. Check firewall settings if step 5 or 6 connectivity test fails
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence -
Network protocols are not showing in sql server network configuration manager
Hi,
We are running 64 bit SQL server 2012 SP1 version. Everything was working fine but suddenly SQL server network configuration showing blank.
So please suggest how do I get it back.Hello,
Could you please try to repair the installation?
http://technet.microsoft.com/en-us/library/cc646006(v=sql.110).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Can't find SQL Server 2012 Configuration Manager
In my Win8 I can't find SQL Server Configuration Manager.
I need to connect to an SQL Database using a specific port.
Does anyone know how to do that?
Thanks a lot!!Hi Lina,
Did you install multiple SQL Server instances on your local server? We can not configure SQL Server 2012 instance under SQL Server 2008 R2 Configuration Manager.
If you had installed SQL Server Configuration Manager with SQL Server 2012, you can try to run "sqlservermanager11.msc". If this is not opening then you might not install SQL Server 2012 Configuration Manager.
Regards,
Fanny Liu
If you have any feedback on our support, please click
here.
Fanny Liu
TechNet Community Support -
SQL Server memory Configuration - SCOM 2012 R2
Hi,
The following article http://technet.microsoft.com/en-us/library/gg682077#BKMK_SupConfigSQLDBconfig states the following about SQL Server memory configuration for SCCM:
When you use a database server that is co-located with the site server, limit the memory for SQL Server to 50 to 80 percent of the available addressable system memory.
When you use a dedicated SQL Server, limit the memory for SQL Server to 80 to 90 percent of the available addressable system memory.
The question is:
Is there any advice (from technet articles) about SQL Server memory configuration for SCOM 2012 R2?
Thanks in advance!Hi There,
Read the 5th point below
General SQL Server recommendations for System Center 2012 R2
This information describes general recommendations for SQL Server regardless of what System Center component you are deploying.
You will need a minimum of four computers to deploy all System Center components. Aside from performance reasons, not all system components can coexist on the same computer. For more information, see Component
Coexistence for System Center 2012 R2.
For testing purposes only, one SQL Database Engine Services instance may be used for all components, but is not recommended in a production setting due to performance concerns.
Reporting Services instances cannot be shared between System Center components.
SQL_* collations are being deprecated for their Windows equivalents.
Limit the memory of each SQL Server instance such that the Total Memory setting allows a minimum of 1 GB (2GB preferred) of free memory after all services are running.
System Center components requiring the most disk resources are Service Manager, Operations Manager and Configuration Manager.
Disks used should be formatted to a 64K allocation unit size.
Disks used should be configured to allow 20% free space after all calculations for monitoring. Set growth upper limits to not exceed this space limit.
Pre-sizing is preferred - use auto-grow if needed as it uses more resources.
Set Pre-size to 8GB/2GB as a minimum. 20-30% of the database file size is a rule of thumb.
Set Auto-grow to 500/100 as a minimum.
Refer: http://technet.microsoft.com/en-in/library/dn281933.aspx
Gautam.75801 -
Hardware Requirements for a SCCM 2012 CAS with SQL Server Remote
The hardware requirements for a CAS server with SQL Server Enterprise locally installed are:
16 cores (Intel Xeon L5520 or comparable CPU)
64 GB of RAM
1.5 TB of disk space for the operating system, Configuration Manager, SQL Server, and all database files.
Does anyone know what the hardware requirements are if SQL Server Enterprise is remote from the CAS server? It's not listed. -ShaneEven though I am going to be strung up for even saying this, I do agree there is a use for a CAS outside of 100,000 users. If you do indeed have distinct admins managing their own images and apps in remote
locations then I see the benefit of a CAS. A remote ConfigMgr console connecting to a primary site would perform poorly. Admin A at the primary site would not experience any issues but Admin B would be in for a lot of work and waiting. Any
time Admin B needed to add an app or image it would have to be copied up to the remote primary site and then distributed back down. This is not the best scenario.
There are scenarios in company merger situations (and others I am sure) where the management of both locations has not been consolidated down to one location yet and is not going to be done as part of the deployment or upgrade. If you had a 2007 environment
it is going to be very hard to convince the admin at the remote location that this upgrade is going to be a good thing for him/her. There is an option for the remote admin to RDP into a server in the primary site but the image and apps still need
to be distributed down to the remote location. During testing this can be very time consuming.
I do agree that adding a CAS adds additional complexity but in some cases such as the one I described it is the right decision.
Thank you for the reply. And i totally agree that in some cases a design like that is a necessary evil (but not by our personal wants).
We had that design with 2007 (implemented before my time), and as you predicted EU admins complained about difficulty using the console RDP-ed into a box close to the primary site. The bandwidth to and from different regions is out of scope for me so I do what
I can with what I have. We too will be moving forward with a CAS hierarchy.
Administratively the other IT depts in other regions operate on their own. I dont handle any of the EU computers on a day to day basis whatsoever, etc. We're not merging but our IT shops operate with near independence. -
Services of 2nd instance disappearded from SQL Server 2012 Configuration Manager but still running
We recently configured multiple SQL Server 2012 R1 (two-node) clusters. Some with two instances. However, we discovered later that the Configuration Manager only lists the services of the 1st instance (the default MSSQLSERVER instance). The other named instance
is still running and can be failed over from one node to the other using Cluster Failover Manager but the services are not showing up in Configuration Manager in any of the two nodes.
Any thoughts as to why we see this odd behavior and how to fix it? We have done two instances before in SQL Server 2008 R2 but never saw this behavior.
Thanks,
OmerPlease see my answer above about the SQLCM version. We use the highest.
As I said before that this happens only when we have two instances running in a SQL2012 cluster. We configured 7 SQL 2012 clusters. three of them have two instances but only the services of one instance are displayed in CM. Services of the default instance
are listed in two of these clusters while services of the named instance are listed in the 3rd one.
One thing to note about these configurations is that the installer could not bring the services at the end of installation online because it did not have permission to create the computer objects in AD during setup thus we had to follow a known workaround
that involves having the domain admin fix these permissions and then we were able to add the SQL Agent Service to the cluster and bring the services online after modifying the ConfigurationState key value of each instance in the registry.
The installer account is setup as a local admin and we asked the domain admin to give it "Read All properties" and "create computer objects" in AD but for some reason it does not seem to have the ability to create these computer objects during installation
and the objects are to be pre-created and their permissions reset afterward.
I am giving this information and I am not sure if it has anything to do with the fact that SQLCM is listing the services of one instance and not the other. -
SQL Server Remote Allow Connections
Hi All
I am trying to connect to a remote server which has SQL Server Express on it.
I am unable to connect to the SQL Server. I have Management Studio Express installed on my local machine... when I goto File > Connect Object Explorer then it asks me for the Server Name: What do i type here if a remote one i.e. an IP address followed
by the port? If yes then how do i find the correct IP address for the SQL Server Express on the remote server and what is the correct syntax for it?
Many ThanksIs it a named instance ?
If No, try just the servername while login thru SSMS
If Yes, try Servername/instancename
Here is the way to find the instance name
http://stackoverflow.com/questions/16088151/how-to-find-server-name-of-sql-server-management-studio
Satheesh
My Blog |
How to ask questions in technical forum -
How to Configure Remote Connections To SQL Server 2008 R2 Express
Post written June 10, 2010 and pertains to:
SQL Server 2008 R2 Express on both my server and local machines: SQLX_SRV,
SQLX_LOC
SQL Server 2008 R2 Management Studio on both my server and local machines:
MS_SRV, MS_LOC
Windows Server 2008 R2 Enterprise installed on a Hyper-V VPS: WS
SQL Server Configuration Manager on both my server and local machines:
CMGR_SRV, CMGR_LOC
Server Manager: SMGR
I am connecting to my hosting server via Remote Desktop Connection: RDC
I installed SQLX_SRV and MS_SRV on my hosting server and SQLX_LOC and MS_LOC on my local development machine. I am able to use MS_LOC to connect to SQLX_LOC and to use MS_SRV to connect to SQLX_SRV. However I am not able to use MS_LOC to connect
with SQLX_SRV. Here's what I have done so far:
SMGR -> Configuration -> Windows Firewall to turn off the Windows Firewall for Domain, Private and Public profiles. Obviously I'll change this later, but until I can connect I want to remove as many variables as possible.
CMGR_SRV -> SQL Server Services to confirm that both SQL Server (SQLEXPRESS) and SQL Server Browser services were running.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS to ENABLE the Shared Memory, Named Pipes, and TCP/IP protocols and DISABLE the deprecated VIA protocol.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS -> double click TCP/IP to open the TCP/IP properties dialogue. On the Protocol tab Enabled: Yes, Keep Alive: 30000, changed Listen All to No. I've tried it both
ways, but I've got six IP addresses on my server and I wanted to configure SQLEXPRESS to listen to only the first and primary IP. On the IP Addresses tab went to IPALL and cleared the TCP Dynamic Ports field and entered 1433 in the TCP Port field.
For my first and primary IP Address I made sure that Enabled was Yes, I cleared the TCP Dynamic Ports field, and entered 1433 in the TCP Port field. For all other IP Addresses Enabled was set to No and I cleared both the TCP Dynamic Ports and TCP Port
fields.
CMGR_SRV -> SQL Server Services -> SQL Server (SQLEXPRESS) right click and Restart. This of course stopped and restarted my instance of SQLX_SRV enabling the TCP/IP configuration in the previous step to take effect.
On my server, SQLX_SRV is the only instance of SQL Server running and so it's easy to hard wire it to the default port 1433.
The instance name for both SQLX_SRV and SQLX_LOC is the default "SQLEXPRESS". My server machine name is "SERVER1" on the EnglishBrains.com domain. So the proper local name (local within the context of my remote server as connected via RDC) for
my instance of SQLX_SRV would be:
SERVER1\SQLEXPRESS
Note the use of a backslash NOT a forward slash.
Of course to connect remotely from my development machine, which is not on the same domain as my hosting server, I would need to specify the domain as well, so the SQL Server name becomes:
SERVER1.EnglishBrains.com\SQLEXPRESS
I must also use SQL Server Authentication. Before I can use such a remote connection, however, there are still several configuration steps required. So on my server (connected via RDC) I used MS_SRV to connect to SQLX_SRV using SERVER1\SQLEXPRESS
for the server name and Windows Authentication. Once connected I performed the following steps:
MS_SRV -> right click the connected parent SERVER1\SQLEXPRESS instance node at the top -> Properties -> Security -> Server authentication: select "SQL Server and Windows Authentication mode". This will enable connections using either type
of authentication.
Next, leaving the Server Properties dialogue open, Connections -> check "Allow remote connections to this server" box.
Click OK to save these changes and close the Server Properties dialogue.
MS_SRV -> Security -> right click Logins and select "New Login...", the Login - New dialogue opens.
On the General page Enter a name for your new login
Select SQL Server Authorization
Enter and confirm a password
Uncheck Enforce password expiration
Select the default Database and Language
On the ServerRoles page Public will be checked, also check SysAdmin. This is probably not a good idea and I'll uncheck this as soon as I can connect to the SQLX_SRV.
On the User Mapping page select the databases you want your new Login to access and enter the Default Schema of "dbo".
At the bottom of the User Mapping page you'll see the Database Roles table. Public will be selected by default. Also select db_Owner. Again this is probably not a good idea, and I'll refine this once I can connect.
On the Status page confirm that "Grant" is checked under "Permission to connect to database engine" and "Enable" is checked under "Login".
Click OK to save all changes and close the Login - New dialogue.
With these steps completed you should now be able to use MS_SRV to connect to SQLX_SRV using SQL Server Authentication by supplying the name and password for your new Login. I tried this and it worked fine. Next I tried to use this same login
remotely, that is I went to my local development machine and used MS_LOC to try and connect to SQLX_SRV by using
SERVER1.EnglishBrains.com\SQLEXPRESS
and opting for SQL Server Authentication and supplying the name and password of my new login.
THIS DID NOT WORK?? Instead I get the following error message:
Cannot connect to SERVER1.EnglishBrains.com\SQLEXPRESS.
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:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1
If you follow the suggested help link, you are told:
The SQL Server client cannot connect to the server. This error could be caused by one of the following reasons:
A specified SQL Server instance name is not valid.
The TCP, or named pipes protocols are not enabled.
The firewall on the server has refused the connection.
The SQL Server Browser service (sqlbrowser) is not started.
WRONG on all 4 counts! The instance name IS valid. Both TCP/IP and Named Pipes protocols are enabled. The firewall has been shut down, so it is not relevant. Finally the SQL Server Browser IS started.
The next thing I tried was to circumvent discovery by the SQL Browser service by using the following syntax to specify the IP address and port directly when specifying the SQL Server name.
tcp:68.71.134.186,1433
Using this in the Server Name field I was able to use MS_SRV to successfully connect to SQLX_SRV (using SQL Server Authentication of course) with or without the SQL Browser service running.
However when I tried to connect from MS_LOC to SQLX_SRV using this same login (WITH SQL Browser service running just for good measure) it does not work?? I get the following error message:
Cannot connect to tcp:68.71.134.186,1433.
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:
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.) (Microsoft SQL Server, Error: 10060)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
If you follow the help link you are told:
"The SQL Server client cannot connect to the server. This error could occur because either the firewall on the server has refused the connection or the server is not configured to accept remote connections."
However, the firewall has been shut down and the server HAS been configured to accept remote connections!
I confirmed that i could indeed Ping to 68.71.134.186 and running NetStat -a |find /i "listening" on the server shows that the server is indeed listening at 68.71.134.186 Port 1433 -- which is why I was able to connect to SQLX_SRV using MS_SRV with
tcp:68.71.134.186,1433 .
IN SUMMARY: Even though I can connect to my SQLEXPRESS instance multiple ways from the server itself, I cannot connect remotely from my development machine!
If anyone can help me figure out why I would be very, very grateful!My two cents to help you out on c# code example to configure the remote sql server express.
Hope it helps. It works, but you have to be extra carefull to read it all and setup the server configuration and netsh commands; also the port fowarding on the router.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Data.SqlClient;
namespace sqlremoteconnection
class Program
static void Main(string[] args)
// this is the local sql server connection
// 192.168.1.101\SQLEXPRESS
// now, the configuration for remote access:
// activate SQL SERVER BROWSER - set it to start "automatic"; then START UP
// SQL Server Configuration Manager
// --> SQL SERVER BROWSER -> properties -> Service -> Start Mode -> automatic -> apply
// --> Log On -> Start -> Ok
// netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = all profile = CURRENT
// netsh firewall set portopening protocol = UDP port = 1434 name = SQLPort mode = ENABLE scope = all profile = CURRENT
// netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = any profile = PUBLIC
// netsh advfirewall firewall add rule name = SQLPort dir = in protocol = udp action = allow localport = 1434 remoteip = any profile = PUBLIC
// VERY IMPORTANT FOR REMOTE ACCESS: you have to add the rules on port fowarding
// on the router!!!
// TCP: 1433
// UDP: 1434
// or just a personal port like TCP 31433/UDP 31434
// read carefully the netsh commands above
// server name: 123.132.24.177\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,1433 <<-- regular port
// server name: anyurl.myftp.org\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,31433 <<-- WOW different PORT here!!!
SqlConnection myConnection = new SqlConnection(
"user id=sa;" +
"password=password_goes_here!;" +
"server=anyurl.myftp.org\\SQLEXPRESS,31433;" +
//"Trusted_Connection=no;" +
"database=database_name_here; " +
"connection timeout=30");
try
myConnection.Open();
catch (Exception e)
Console.WriteLine(e.ToString());
try
SqlDataReader myReader = null;
SqlCommand myCommand = new SqlCommand("select * from mytable", myConnection);
myReader = myCommand.ExecuteReader();
while (myReader.Read())
Console.WriteLine(myReader["tab01_name"].ToString());
Console.WriteLine(myReader["tab01_age"].ToString());
catch (Exception e)
Console.WriteLine(e.ToString());
try
myConnection.Close();
catch (Exception e)
Console.WriteLine(e.ToString());
Adelino Araujo -
SQL Server Express 2008 no longer accepting remote connections
Last night our SQL Server Express 2008 (running on Windows 2003 server) stopped accepting remote connections.
1. We restarted the SQL Server -- no resolution.
2. We rebooted the host Windows 2003 server - no resolution.
3. telnet localhost 1433: says Could not open connection to the host on port 1433... connection failed.
4. netstat -an indicates that the server is not listening on port 1433
5. SQL Server Network Configuration -> Protocols for SQLEXPRESS2008A -> (properties) -> TCP-IP (enabled), Listen All (yes)
6. SQL Native Client 10.0 Configuration -> Client Protocols -> (properties) TCP-IP (enabled), Default port (1433)
Fragment from the server error log:
2014-03-26 08:50:41.09 Server A self-generated certificate was successfully loaded for encryption.
2014-03-26 08:50:41.11 Server Server is listening on [ 'any' <ipv4> 1026].
2014-03-26 08:50:41.11 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS2008A ].
2014-03-26 08:50:41.11 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS2008A\sql\query ].
2014-03-26 08:50:41.11 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the
trace flag 7806. This is an informational message only. No user action is required.
2014-03-26 08:50:41.11 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-03-26 08:50:41.11 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-03-26 08:50:41.29 spid10s Clearing tempdb database.
2014-03-26 08:50:41.89 spid10s Starting up database 'tempdb'.
2014-03-26 08:50:42.09 spid13s The Service Broker protocol transport is disabled or not configured.
2014-03-26 08:50:42.09 spid13s The Database Mirroring protocol transport is disabled or not configured.
2014-03-26 08:50:42.14 spid13s Service Broker manager has started.
2014-03-26 08:50:42.14 spid7s Recovery is complete. This is an informational message only. No user action is required.
2014-03-26 08:50:53.48 spid51 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2014-03-26 08:50:53.48 spid51 Using 'xpstar.dll' version '2007.100.1600' to execute extended stored procedure 'xp_enumerrorlogs'. This is an informational message only; no user action is required.
2014-03-26 08:51:35.68 spid54 Starting up database 'Web TimeSheet2'.
2014-03-26 08:51:38.47 spid54 Recovery is writing a checkpoint in database 'Web TimeSheet2' (6). This is an informational message only. No user action is required.
Note: the lines referring to xpstar.dll is new after this porblem. Previous logs do not have this,Any help will be appreciated.Hi,
>>Server is listening on [ 'any' <ipv4> 1026].
Your sql server is not listening on default port 1433 but on 1026.When you connect to instance like hostname\instancename you should specify post no also.
like hostname\instancename ,1026
Can you try this.Makes sure TCP/IP and named pipes protocol is enabled
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
Could not connect to SQL Server 2012 Remotely
Hello,
I have a situation as follows:
The Server
SQL Server 2012 Standard Edition installed on Windows Server 2012 Standard Edition
Active Directory is installed on the same server as well
Remote Access Role added and configured to connect VPN
DNS Role added
Windows Firewall is disabled
The Server is connected to the internet
SQL Server Service & SQL Browser both are running under domain accounts
SQL Server allows remote connections
The Router
The router that connects the server to the Internet is configured to:
Enable VPN Tunnels Protocols (PPTP, L2TP and IPSec)
Forwarding > Virtual Servers (all requests on TCP and UDP on all ports to the server local IP)
The Client
PC running Windows 7 SP1 with SQL Server 2012 Express
Joined AD on the server
Connected to the internet
VPN Connected to the Server
Can Remote Desktop the Server
Can ping the server host name
Can nslookup the server host name
The Problem
If Both the Server and the Client are connected in the same Local Area Network, Client can connect to the SQL Serve
Once the Client is placed in different location connected to the Interent, VPN connected as described above, I could not connect to the Server using:
Windows Authentication Domain Users or
SQL Server users
and the error message is:
Cannot connect to SERVER\SQLINSTANCE.
ADDITIONAL INFORMATION:
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:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
Any thoughts
Thanks in advance
Hello Hilary,
I have been working on a small replication test.
On the Publisher, things went smooth and the Snapshot Agent was able to work and produce a snapshot written in a shared folder located on the Publisher
On the Subscriber, as I am testing from SQL Server Express, I had run the following command:
replmerg.exe -Publisher [SERVER\SQLInstance] -PublisherDB [dbRepl] -PublisherSecurityMode 0 -PublisherLogin rplMergeAgent -PublisherPassword p@ssw0rd -Publication [TEST Publication] -Distributor [SERVER\SQLInstance] -DistributorSecurityMode 0 -DistributorLogin
rplMergeAgent -DistributorPassword p@ssw0rd -Subscriber [SUBSCRIBER\SQLInstance] -SubscriberSecurityMode 0 -SubscriberLogin rplMergeAgent -SubscriberPassword p@ssw0rd -SubscriberDB [dbRepl] -SubscriptionType 1 -OutputVerboseLevel 2 -Output C:\TEMP\mergeagent.log
Where
SERVER
Publisher and Distributor
dbRepl
Database to replicate
Merge Agent
rplMergeAgent
Subscriber
SUBSCRIBER
dbRepl
Subscriber Database
Merge Agent
rplMergeAgent
Password
p@ssw0rd
rplMergeAgent
SQL Login defined in both Publisher and Subscriber with same password
Granted the following at Publisher:
Login to Publication Database (dbRepl)
Login to Distribution Database (distribution)
Member of PAL
Granted the following at Subscriber:
db_owner fixed database role in Subscription database (dbRepl)
I couldn't grant rplMergeAgent Read Permission on SnapshotFolder as it is only a SQL Login.
When I ran the above command line, I received the following error:
Message: The schema script 'Person_2.sch' could not be propagated to the subscriber.
I am pasting below the whole log file written by the above command:
2014-04-11 15:38:07.205 Microsoft SQL Server Merge Agent 11.0.2218.0
2014-04-11 15:38:07.342 Copyright (c) 2008 Microsoft Corporation
2014-04-11 15:38:07.389
2014-04-11 15:38:07.406 The timestamps prepended to the output lines are expressed in terms of UTC time.
2014-04-11 15:38:07.433 User-specified agent parameter values:
-Publisher SERVER\SQLInstance
-PublisherDB dbRepl
-PublisherSecurityMode 0
-PublisherLogin rplMergeAgent
-PublisherPassword **********
-Publication TEST Publication
-Distributor SERVER\SQLInstance
-DistributorSecurityMode 0
-DistributorLogin rplMergeAgent
-DistributorPassword **********
-Subscriber SUBSCRIBER\SQLInstance
-SubscriberSecurityMode 0
-SubscriberLogin rplMergeAgent
-SubscriberPassword **********
-SubscriberDB dbRepl
-SubscriptionType 1
-OutputVerboseLevel 2
-Output C:\TEMP\mergeagent.log
2014-04-11 15:38:07.497 Percent Complete: 0
2014-04-11 15:38:07.517 Connecting to Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:38:07.518 Connecting to OLE DB Subscriber at datasource: 'SUBSCRIBER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:07.608 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:07.613 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:07.617 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select
collationproperty(@collation, N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) &
0x1 = 0x1 then 0 else 1 end as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
2014-04-11 15:38:07.637 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {?=call sp_helpsubscription_properties (N'SERVER\SQLInstance', N'dbRepl', N'TEST Publication')}
2014-04-11 15:38:07.681 Distributor security mode: 0, login name: rplMergeAgent, password: ********.
2014-04-11 15:38:07.682 Percent Complete: 0
2014-04-11 15:38:07.683 Connecting to Distributor 'SERVER\SQLInstance'
2014-04-11 15:38:07.684 Connecting to OLE DB Distributor at datasource: 'SERVER\SQLInstance', location: '', catalog: '', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:25.062 OLE DB Distributor: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name:
user name: guest
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:28.887 OLE DB Distributor 'SERVER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:29.842 OLE DB Distributor 'SERVER\SQLInstance': {call sp_helpdistpublisher (N'SERVER\SQLInstance') }
2014-04-11 15:38:32.198 OLE DB Distributor 'SERVER\SQLInstance': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'SERVER\SQLInstance')
2014-04-11 15:38:33.199 OLE DB Distributor 'SERVER\SQLInstance': {call sp_MShelp_merge_agentid (0,N'dbRepl',N'TEST Publication',null,N'dbRepl',100,N'SUBSCRIBER\SQLInstance')}
2014-04-11 15:38:34.451 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:34.560 OLE DB Distributor 'SERVER\SQLInstance': {call sp_MShelp_profile (23, 4, N'')}
2014-04-11 15:38:36.189 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:36.499 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_get_redirected_publisher(N'SERVER\SQLInstance',N'dbRepl',0)}
2014-04-11 15:38:37.396 Percent Complete: 0
2014-04-11 15:38:37.396 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:37.399 Initializing
2014-04-11 15:38:37.401 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:37.403 Connecting to OLE DB Publisher at datasource: 'SERVER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:38.427 Percent Complete: 0
2014-04-11 15:38:38.428 Validating publisher
2014-04-11 15:38:38.429 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:39.455 Percent Complete: 0
2014-04-11 15:38:39.456 Connecting to Publisher 'SERVER\SQLInstance'
2014-04-11 15:38:39.457 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:46.548 OLE DB Publisher: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:50.282 OLE DB Publisher 'SERVER\SQLInstance': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
2014-04-11 15:38:57.393 OLE DB Publisher 'SERVER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:59.236 Connecting to OLE DB Publisher at datasource: 'SERVER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:39:07.271 OLE DB Publisher: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:39:45.229 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:45.234 Percent Complete: 0
2014-04-11 15:39:45.235 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:45.236 Retrieving publication information
2014-04-11 15:39:45.238 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:46.287 Percent Complete: 0
2014-04-11 15:39:46.288 Retrieving subscription information.
2014-04-11 15:39:46.290 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:00.472 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:00.478 Percent Complete: 0
2014-04-11 15:40:00.479 Applying the snapshot to the Subscriber
2014-04-11 15:40:00.480 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:02.535 OLE DB Distributor 'SERVER\SQLInstance': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'SERVER\SQLInstance')
2014-04-11 15:40:03.559 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_mergesubentry_indistdb (0,N'SERVER\SQLInstance',N'dbRepl',N'TEST Publication',N'SUBSCRIBER\SQLInstance',N'dbRepl',1,1,0,N'',?,90)}
2014-04-11 15:40:04.600 Connecting to OLE DB Subscriber at datasource: 'SUBSCRIBER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:40:04.609 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:40:04.611 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:40:07.454 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSacquiresnapshotdeliverysessionlock
2014-04-11 15:40:07.526 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MStrypurgingoldsnapshotdeliveryprogress
2014-04-11 15:40:07.530 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSissnapshotitemapplied @snapshot_session_token = N'\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST PUBLICATION\20140411082109\', @snapshot_progress_token = N'\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST
PUBLICATION\20140411082109\Person_2.sch'
2014-04-11 15:40:24.659 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSreleasesnapshotdeliverysessionlock
2014-04-11 15:40:24.663 The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:24.665 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:24.690 Percent Complete: 18
2014-04-11 15:40:24.692 The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:24.693 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:27.541 Percent Complete: 0
2014-04-11 15:40:27.542 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:28.563 Percent Complete: 0
2014-04-11 15:40:28.565 Category:AGENT
Source: SUBSCRIBER\SQLInstance
Number: 0
Message: The process could not read file '\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST PUBLICATION\20140411082109\Person_2.sch' due to OS error 1326.
2014-04-11 15:40:28.566 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.568 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.569 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.570 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.571 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.573 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.575 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.577 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.578 Disconnecting from OLE DB Distributor 'SERVER\SQLInstance'
2014-04-11 15:40:28.579 Disconnecting from OLE DB Distributor 'SERVER\SQLInstance'
I can say it is about how can the rplMergeAgent read the Shared folder.
What do you think? -
SQL Server Agent gives- Remote procedure call failed (0x800706be)
I can't access SQL Server 2008 R2 remotely on Windows 2008
1. TCP/IP Enabled for SQL Server Network Configuration Protocols, SQL Native Client 10.0 configuration clients, and SQL Native Client 10.0 configuration clients(32 bit)
2. Firewall disabled to make sure its not interferring with things.
I noticed the SQL Server Agent is Stopped. Not sure if this is the issue. When I try and turn this from disabled to Automatic or Manual, I get this error:
Remote procedure call failed (0x800706be)
It shouldn't be this difficult.
Thank you for your help in advance!Any luck?
The following thread is on the same topic with solutions:
http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/75933d1c-f142-459e-b7dc-d43ad4f8f93f/
Kalman Toth SQL SERVER 2012 & BI TRAINING
New Book:
Beginner Database Design & SQL Programming Using Microsoft SQL Server 2012 -
Can't connect to remote SQL Server 2014 Standard with VS 2012
Hi all,
I am trying to create a development environment using SQL Server 2014 (not Express). The SQL server instance is on a Windows 8.1 Pro machine in a non-domain environment. I have Visual Studio 2012 installed on the same machine which can connect
to the SQL server instance without problems. I have another machine with VS 2012 that cannot connect. SQL server is configured for mixed authentication. The SSDT on the remote machine can see the SQL server networked instance, but will not
connect with SQL authentication.
I have rounded up all the usual suspects;
- The SQL server service is running
- Remote connections are enabled on SQL server and the relevant firewall ports are open.
- TCP/IP and named pipes are enabled
- Remote connections are enabled in Management Studio
- SQL Server Browser service in enabled and running
What am I missing? I have been out of developer mode for a few years and all of the tools have changed, but I seem to be missing something obvious.
Many thanks in advance,
Tim
Tim in DublinHello,
Have you configured the Windows Firewall on the Visual Studio computer too? Is there any other security software on those
2 computers?
Can you ping between both computers by computer name? If not, try connecting using the IP address. For example:
10.0.0.10,1433
1433 is the default SQL Server port number.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Maybe you are looking for
-
I have a friend who uses an iPod to iMessage me and about two nights ago, my messages to him from my iPhone were no longer listed as delivered and then I started getting the message "Contact is unavailable. This person cannot be reached by iMessage a
-
Read troubleshooting info below............and Question above
-
HT1726 Charging iPod with mains charger or dock
When Charging an iPod Classic using a mains charger or an iPod dock (on a CD midi-system), do you simply remove the iPod when it's finished or is there a safe ejecting procedure like there is when charging from your computer? I am being cautious as m
-
Apache/Tomcat plugin mod_jk.so vs. mod_wls_20.so
Hi, Someone says to me why apache/tomcat mod_jk.so is so advanced regarding to mod_wls_20.so for load balancing function? With a Apache server with mod_jk.so I can to balance N server with Tomcat ( or JBoss ) : with mod_wls_20.so no. The bea plungid
-
Dear Sapers, How to find table name from field name to write functional spec.Pl elaborate it for normal & zdevelopment.Points will be rewarded for useful answer. Thanks in advance.