Hi
I am very new to SqlServer. I want to my java application, using JDBC,
to connect to the SQLServer on port 1433 (Running on Windows NT). How
do I configure it? I am using 2000 version of SQL Server.
Thank you
So I have Availability groups configured as well as the Availability Group Listener, what If I want to change the port that the listener is listening on, do I need to reboot the server or is it dynamic across the board ?
View 5 Replies View RelatedIn our(my company) current design we want to switch from failover clustering to Always On as high availibility solution.
I am currently testing the availiblity Group Listener function and have two questions regarding this.
First of all, is it possible to connect to a a listener by just using its "name" instead of "name,port", it is for our users very inconvenient to start using ports. If this is possible, where can I find information on how to configure this?
Second, is it possible to use the Availiblity Group Listener as loadbalancer or in combination with a loadbalancer to split the users over two or more nodes?*note we don't use azure.
I have changed SQL Server from default port to another port number. All appears fine. If SQL Server is restarted it is all fine, however, when the server is restarted SQL Server fails to start. If you then log into the server and manually start the services they start just fine. So, it appears that something blocks the port or uses the port upon server startup for a few seconds. The AV folks say that they are not blocking ports and that it AV service actually starts 15 seconds after the SQL start failure.So, the question becomes is how can I track down what is blocking or using that port?
This is Win2012/SQL2014 CU3
Server failed to listen on xxxxx::xxxxxxxxxx <ipv6> xxxxx. Error: 0x2741. To proceed, notify your system administrator.
Server failed to listen on fe80::5efe:10.255.196.25%18 <ipv6> 14001. Error: 0x2741. To proceed, notify your system administrator.
TDSSNIClient initialization failed with error 0x2741, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The requested address is not valid in its context.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
for some reason i dont get any errors, but i believe that my server isnot running on port 1433. the tcpip protocol is selected in thenetwork configuration utility as well as name piper. the portselected is 1433. but when i telnet to 1433 i get the same errors as iwould if i telnet to a non existant port. i also tried nbstat with noluck. what else can i do? thanks
View 2 Replies View RelatedI have had an underwhelming amount of success hunting down the sourceof this error and am hoping that someone here may have some insight.Error logged in the event log:Source: MSSQLSERVERCategory: (2)EVENT ID: 17887Description: IO Completion Listener (0x754) Worker 0x00FEC0E8 appearsto be non-yielding on Node 1. Approx CPU Used: kernel 0 ms, user 0 ms,Interval: 15187.Immediately followed by 100% CPU utilization. The server remains ping-able and I can telnet to the SQL port, but it is otherwise effectivelyunresponsive (queries timeout, RDP times out, etc.). This is alsologged in the SQL error log:2008-03-19 15:52:37.80 Server Using 'dbghelp.dll' version '4.0.5'2008-03-19 15:52:46.80 Server **Dump thread - spid = 0, PSS =0x00000000, EC = 0x000000002008-03-19 15:52:46.80 Server ***Stack Dump being sent to D:Microsoft SQL ServerMSSQL.3MSSQLLOGSQLDump0004.txt2008-03-19 15:52:46.80 Server *************************************************** *****************************2008-03-19 15:52:46.80 Server *2008-03-19 15:52:46.80 Server * BEGIN STACK DUMP:2008-03-19 15:52:46.80 Server * 03/19/08 15:52:46 spid 02008-03-19 15:52:46.80 Server *2008-03-19 15:52:46.80 Server * Non-yielding IOCP Listener2008-03-19 15:52:46.80 Server *2008-03-19 15:52:46.80 Server *************************************************** *****************************2008-03-19 15:52:46.80 Server *-------------------------------------------------------------------------------2008-03-19 15:52:46.80 Server * Short Stack Dump2008-03-19 15:58:13.09 Server Stack Signature for the dump is0x000000062008-03-19 16:03:40.94 Server IO Completion Listener (0x730)Worker 0x00A060E8 appears to be non-yielding on Node 0. Approx CPUUsed: kernel 0 ms, user 0 ms, Interval: 15187.2008-03-19 16:06:10.47 Server Timeout waiting for external dumpprocess 6016.2008-03-19 16:06:10.47 Server IO Completion Listener (0x754)Worker 0x00FEC0E8 appears to be non-yielding on Node 1. Approx CPUUsed: kernel 0 ms, user 0 ms, Interval: 15187.2008-03-19 16:17:34.51 Server IO Completion Listener (0x754)Worker 0x00FEC0E8 appears to be non-yielding on Node 1. Approx CPUUsed: kernel 0 ms, user 0 ms, Interval: 15187.The server is Windows 2003 SP2 (32bit), dual dual-core AMD opteronprocessors, 8GB RAM, RAID 10. /3GB and /PAE are enabled in boot.ini."Lock pages in memory" has been granted to the account SQL runs as.SQL Server is 2005 Standard Edition SP1 (32bit). "Use AWE to allocatememory" is enabled. Min and max memory are set to 5GB.If there is any other info you think may be helpful introubleshooting, please let me know. Any insight you've had into thisor similar problem would be appreciated. Thanks in advance.
View 1 Replies View RelatedI am new to Service Broker and Query Notification. I've used Books Online and the other help files to successfully create a class to subscribe and listen for mods to a table on a SqlServer 2005 (SP1 applied) server. My prototype worked exactly as expected.
However, when I put my code into production, the listener was calling my NotifyEvent() callback repeatedly, and without any changes being made to the table! Of course, I'd tested with a simple two column table and implemented with a more complex multi-column one. After some experimentation I discovered that the problem occured when the SELECT statement refrenced a "blob" column.
That is, the CREATE TABLE command included a column:
[Data] [varbinary] (max) NULL
and the SELECT statement looked like:
private const string _select = "SELECT [Role_s], [User_s], [DataType], [Project_s], [DataName], [tag], [Data_s], [ScopeType], [ScopeOwner], [Data1], [Data2], [Data3], [Data4], [IsProject], [Data] FROM [ovs].[OVS_AppData_tbl] WHERE DataType='SchedTask'";
SqlServer called my NotifyEvent() continuously. If I removed the [Data] column from the select, then the code worked as I had tested. I also tried this on another table (fewer columns) that also had a [Data] defined similarly, and again the continuous notifications came. I've got a workaround because I also calculate a hash on the [Data] column, and I can "watch" the hash instead of the underlying [Data].
Oh, when I ask SSMS to script the table with the [Data] column it gives me:
[Data] [image] NULL
This may (or may) be relevant (vs. varbinary).
why my listener has two dns entries? Shouldn't it only have the active node's address? I have the cluster RegisterAllProvidersIP set to 0. We have two synchronous local sql 2012 servers on windows 2012 r2 and one remote (different subnet) asynchronous node. Is it safe to manually delete the dns record that's pointing to our remote listener? Why did it add both of them?
View 7 Replies View RelatedHi,
I have Oracle 9i. Oracle listener is aborting by itself after every few minutes giving TNSLSNR.exe failed. While listener is running I can do all the activity on the database.
Please let me know if there is any solution.
Thanks in Advance.
Pushpam
How can one enabledisable Availability Group listener? I know AG listener can be deleted and added but didnt find anything to disable or enable that.
View 1 Replies View Related I've started working at an organization that has a sql 2005 cluster with a named instances on it, lets call it Instance1. What they done is to create a dns alias for servername that is the same as the instance name, so when you connect to the sql server you connect "Instance1Instance1".
We want to move to SQL 2014 cluster with AlwaysOn Availability Groups doing the HA/DR, the question is if I create a listener name called "Listener1" is there a way to using DNS or anything else to point "Instance1Instance1" to "Listener1"
Is it possible to password protect the listener for SQL Server - similar to Oracle?
View 2 Replies View RelatedI have setup two node SQL 2012 Always ON cluster with file share witness. I have configured two networks, one for heartbeat and second for public.My question is do I need a third network/ subnet for AG Listener? Which network does the SQL user databases in the AG group use to replicate between the replica servers?When I do the SQL backups, do I need to backup primary and secondary replicas or just backup the databases in the secondary replica?
View 4 Replies View RelatedI have an issue when connecting with application Intent=readonly when using Listener name. I can connect to the read only secondary with application Intent=readonly if I use the server name. It gives a host does not exist error when using listener. This happens only if I am using the application Intent keyword. I can connect for normal readwrite operation using listener name.
View 3 Replies View RelatedIn our environment applications are using a DNS name which points to the physical server ip address. Now we are planning to move to 2014. We are planning to have servers in different subnets so we will be having two ip adresses for listener. How we can point the DNS to the listener ips? If failover happens can the DNS point to the exact ip address of the listener where it's primary node?
View 1 Replies View RelatedI have set up a couple of servers in a SQL 2012 AlwaysOn Availability Group (non FCI). I have also configured a Listener which enables SQL clients to connect to the server currently servicing the database, as expected.
I would also like non SQL clients to be able to connect to the server currently hosting the database so that they can run scripts sitting in a share. I don't have a shared disk so just have a directory share on each server with the same scripts in each directory.
I am able to ping and RDP to the listener IP address/name and end up on the correct server but am unable to connect to the share ListenerNameShare. Is that actually supported? If it is, any thoughts on what I need to do to get it going. If it isn't what other options do I have?
I am trying to setup an AG on a cluster, I was able to define where I want my replica, but I need to setup the ip for the listener of that one
When I am adding the Ip at the listener I am getting the following message:
The Windows Server Failover Clustering (WSFC) resource control API returned error code 5057. The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
The attempt to create the network name and IP address for the listener failed. The WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. (Microsoft SQL Server, Error: 41009)
Browsing around I found this guide: [URL] ......
And I make sure that the cluster has permissions to "Read all properties", "Create Computer Objects", even to "Create all child" permissions
I also added those permissions to the account that starts sql at that cluster and I am logged as that and I am still getting the error....
After manual AG fail-over from primary to secondary the application is not able to connect the listener name for atleast for 5 - 10 mins
The telnet fails during this time from app server, the listener ip is on muti-subnet.
At the same when i try to connect it from SSMS from a remote machine it works fine.
We have a server A and a server B setup with SQL2014 High Availability - working fine.
I need to add an additional listener to our new DR site (SQLNODECOLO).
What is the best way to do this without impacting production?
Can I just go to server A and add the new listener server here (SQLNODECOLO):
1) RS Start in Window Severvices
2) RS Start in Configration
1) and 2) Is Same?
I think that It looks like same Operation.
When I fail an availability group between subnets, I am finding that the DNS entry in DNS is staying. So what happens is the Availablity Group listener has 2 records in DNS, one for each IP. This causes the App to timeout at times, since DNS will return either of the two IP's.
View 9 Replies View RelatedHow to find when (date/time) a database was last removed from AlwaysOn Listener?
Is there any query (DMV) to find the details easily?
I have MasterDataServices installed on a server and the database is in an AlwaysOn Availability Group.The MDM front end currently is set up incorrectly and is referencing NodeA (primary node) for its database.I want to fix this but im unsure if i should:
-point the MDM front end to the cluster name, so it wont matter what server the databsae is on?
-create an Availability Group Listner, which would also decoupple the database referenced from a particular server.
Do I need to rebuild my indexes on my High Availability listeners?
When I do a full index rebuild on my primary DB's. Does rebuilding also send the rebuild to the listener(s)?
I need to check connectivity to AG listener remotely and log that to a table/file. What is the best way to do that? Powershell?
View 4 Replies View RelatedI am not able to connect listener after manual failover.
(This is test environment)
Server1,Server3 -> Both synchronous (Within Same data center)
Server 3 -> Async (At DR location) -Forced Failover
Test1:
Failover Server1 to Server2 --> Able to connect Listener
Failover Server2 to Server1--> Able to connect Listener.
Failover Server1 to Server3--> Able to connect Listener.
Failover Server3 to Server1 or 2 --> Unable to connect Listener. Unable to ping Listener.
Failover Server 1or2 to Server3--> Able to connect Listener.
I am using below sub-nets:
10.11.192.0/22 10.11.192.130
10.12.192.0/22 10.12.192.140
Assuming all windows servers belonging to the WSFC are on the same subnet, will the AG listener become a single failure point in system if all Application servers connect to the AG through the listener? If the answer is yes, what are the options to resolve this issue?
View 3 Replies View RelatedWe are trying to build HA and DR environment, combining AG and FCI. So we have 3 servers added to a cluster, 2 of them sharing the same storage and working as ACTIVE-PASSIVE cluster instance. The other server has a stand alone instance with its local storage, with the same drivers letters as the cluster instance.
Between the Active FCI and the Stand Alone, we set up an Availability Group. They are running fine, except by the listener. When the stand alone instance owns the Primary Replica, I am able to access the SQL Server instance by the listener, but when the Primary Replica is owned by the FCI, I can't reach the database by the listener (name or IP).
I've opened the same ports in both servers, it hasn't worked though.
We are using SQL Server 2005 (not on SP1), and keep getting the following message in the SQL Server log:
IO Completion Listener (0x15e8) Worker 0x00B7E0E8 appears to be non-yielding on Node 0. Approx CPU Used: kernel 0 ms, user 0 ms, Interval: 35092.
After receiving this message, the server slows down considerably and we receive numerous messages saying:
SQL Server has encountered 61 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [xxxxx.MDF] in database [xxxx] (22). The OS file handle is 0x00000CDC. The offset of the latest long I/O is: 0x000000fa21a000
I have not been able to find any documentation or explanation of what the IO Completion Listener message is about or how to correct whatever problem is causing it.
Any help would be greatly appreciated!
We are rolling out the use of Availability Group listeners to our SQL Server 2012 Environment which has a 2 node multi-subnet cluster. The Primary is R/W and the Secondary is a non-readable node that would be manually failed over to in a DR scenario
I have set up the AGL and asked the sysadmins to create a DNS record in both subnets with fixed IP's.
The issue I have having is that when I ask the app developers to connect to the databases using the AGL it is totally random whether the AGL resolves to the Primary or DR node - as a result that are having problems getting their apps to connect.
I was thinking of asking the sys admins to remove the DNS record in the DR subnet and then add it back in should we need to fail over - but I was thinking there must be a better way.
I am trying to build out an AlwaysOn AG with 2 nodes each in a different subnet (in AWS if that matters), windows 2012r2 / SQL 2014 RTM
I created a AG Listener with 2 ip address, 1 for each subnet (checked that neither ip address are used). But whenever i failover the AG to the secondary, and try and connect via the listener it fails,
I am trying to connect via SSMS from the primary instance. and just time out, If i roll over to the primary i can connect no issues, I've tried playing with the connection settings, upping the time out to 30 secs, adding the MultiSubnetFailover=true. etc but not getting any joy.
Say I have 2014 AlwaysOn setup and working:
SQLNode1 ->Instance01
SQLNode2 ->Instance02
When I setup my listener: ListenerA...Do I need to use the instance name in it?
ListenerAInstance01 or ListenerAInstance02 depending on which SQLNode is the "active" availability group?
Am I better off to use the same instance name for both nodes, since my goal is to have all databases on both instances in the same availability group and sync'd? When SQLNode1 migrates over to SQLNode2 I will need to update the instance name in my connection string on the listener from ListenerAInstance01 to Instance02? When I connect with SSMS do I just use: ListenerAInstance01 (or 02)?
We have a server A and a server B setup with SQL2014 High Availability - working fine.
I need to add an additional listener to our new DR site.
What is the best way to do this without impacting production - can I just add the additional replica from nodea as a secondary replica?