DPM 2012 R2 CU4 protecting SQL 2014 AlwaysOn AG with Failover Cluster vs. DR location

Hello!
We have a problem protecting any Database of SQL 2014 AlwaysOn Availability Group with SQL Failover Cluster Instance when moved to DR location. Everything is protected using DPM 2012 R2 CU4 from Primary location.
FACTS
- all servers are Windows Server 2012 R2
- all servers are Virtual (except Hyper-V hosts obviously:)
- that means virtualization is based on Windows Server 2012 R2 Hyper-V
- all clusters (SQL, Exchange,...) are Guest Clusters on Hyper-V
- SQL 2014
- DPM 2012 R2 CU4
- Primary and DR location
SETUP
SQL
- Primary location: SQL 2014 Guest Cluster with SQL Failover Cluster Instance using Shared VHDX disks
- DR location: SQL 2014 Standalone using VHDX disks
- AlwaysOn Availability Group expands between the primary and DR location.
DPM
- Primary location: DPM 2012 R2 CU4
- DPM 2012 R2 CU4 Agents installed on every possible SQL 2014 Server.
SCENARIO
- DPM is backing up all the SQL Databases normally as long as they exist on any SQL Cluster Node on Primary location.
- As soon as any Database is moved to DR location, that Database is not backed up anymore with the following error.
DPM ERROR
Starting synchronization on SqlServerName\DatabaseName failed:
Error 104: An unexpected error occurred while the job was running.
Error details: The system cannot find the path specified (0x80070003)
Recommended action: Retry the operation.
TROUBLESHOOTING
- Tried to modify SQL Protection Group in DPM Server while Database was active on DR location
> error enumerating volumes or drives D:\, E:\, F:\ (I don't have exact error atm)
> this looks like DPM is not aware that DPM is active on DR location to me
- Checked Technet, blogs and forums; no useful information
QUESTION
Is this expected or by-design behavior? Is this a bug? I am aware there were quite some issues backing up AG's from DPM 2012 SP1 ans SQL 2012 on.
Does anybody have a lab of that kind to try it out?
Thank you!
Best Regards,
Damjan Grimšič
Lpd

OK. The issue has been resolved. Issue was related to possible Disks Owners in Failover Cluster Manager Console for SQL Cluster.
In Primary's site SQL Cluster Failover Manager Console / Storage / Disks.
SQL Server(s) from Secondary location need(s) to be unchecked as Possible owner(s) in Advanced Policies for all relevant Volumes.
Lpd

Similar Messages

SSAS 2012 (SP2) - Connecting to a Named Instance in a Failover Cluster

I posted this question some months ago and never got a resolution...still having the same problem. (http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4178ba62-87e2-4672-a4ef-acd970ac1011/ssas-2012-sp1-connecting-to-a-named-instance-in-a-failover-cluster?forum=sqlanalysisservices)
I have a 3 node failover cluster installation (active-passive-passive) configured as follows:
Node1: DB Engine 1 (named instance DB01)
Node2: DB Engine 2 (named instance DB02)
Node3: Analysis Services (named instance DBAS)
Obviously, the node indicated is merely the default active node for each service, with each service able to fail from node to node as required.
Strangely, when I attempt to connect to the SSAS node using the cluster netbios "alias" (dunno, what else it would be called, so I apologize if I am mixing terminology or somesuch), I am only able to do so by specifying the the alias _without_ the
required named instance. If I issue a connection request using an external program or even SSMS using Node3\DBAS or Node3.domain\DBAS, it appears that the SQL Server Browser is offering up a bogus TCP port for the named instance (in my case TCP/58554), when
in reality, the SSAS service is running on TCP/2383 (confirmed with netstat) -- which if I understand correctly after much, much reading on the subject is the only port that can be used in a failover cluster. In any case, I'm puzzled beyond words. As I think
through it, I believe I've seen this issue in the past, but never worried about it since it wasn't necessary to specify the named instance when I had SSAS requirements... It's only a showstopper now because I'm finalizing my implementation of SCVMM/SCOM 2012
R2, and for some strange reason the PRO configuration in VMM gets all butthurt if you don't offer up a named instance...
Thank you much for reading. I appreciate any help to get this resolved.
POSSIBLY NOT RELEVANT...?
I've properly configured the SPNs for the SSAS service (MSOLAPSvc.3) and the SQL Browser (MSOLAPDisco.3), with the former mapped to the SSAS service account and the latter to the cluster "alias" (since it runs as "NT AUTHORITY\LOCALSERVICE"
as is customary) and have permitted delegation on the service and machine accounts as required. So, I'm not getting any kerberos issues with the service...any more, that is... ;) I'm not sure that's important, but I wanted to be forthcoming with details to
help solve the issue.

When connecting to SSAS in a cluster, you do not specify an instance name. In your case, you would use the name of the SSAS IP address to connect.
See:
http://msdn.microsoft.com/en-us/library/dn141153.aspx
For servers deployed in a failover cluster, connect using the network name of the SSAS cluster. This name is specified during SQL Server setup, as
SQL Server Network Name. Note that if you installed SSAS as a named instance onto a Windows Server Failover Cluster (WSFC), you never add the instance name on the connection. This practice is unique to SSAS; in contrast, a named
instance of a clustered relational database engine does include the instance name. For example, if you installed both SSAS and the database engine as named instance (Contoso-Accounting) with a SQL Server Network Name of SQL-CLU, you would connect to SSAS using
"SQL-CLU" and to the database engine as "SQL-CLU\Contoso-Accounting". See
How to Cluster SQL Server Analysis Services for more information and examples.

Migrate from server core 2008 r2 hyper-v with failover cluster volumes to server core 2012 r2 hyper-v with failover cluster volumes on new san hardware

We are getting ready to migrate from server core 2008 r2 hyper-v with failover cluster volumes on an iscsi san to server core 2012 r2 hyper-v with failover cluster volumes on a new iscsi san.
I've been searching for a "best practices" article for this but have been coming up short. The information I have found either pertains to migrating from 2008 r2 to 2012 r2 with failover cluster volumes on the same hardware, or migrating
to different hardware without failover cluster volumes.
If there is anyone out there that has completed a similar migration, it would be great to hear any feedback you may have on your experiences.
Currently, my approach is as follows:
1. Configure new hyper-v with failover cluster volumes on new SAN with new 2012 r2 hostnodes and 2012 r2 management server
2. Turn off the virtual machines on old 2008 r2 hyper-v hostnodes
3. Stop the VMMS service on the 2008 r2 hostnodes
4. copy the virtual machine files and folders over to the new failover cluster volumes
5. Import vm's into server 2012 r2 hyper-v.
Any feedback on the opertain I have in mind would be helpful.
Thank you,
Rob

Hi Rob,
Yes , I agree with that "file copy " can achieve migration.
Also you can try "copy cluster wizard " :
https://technet.microsoft.com/en-us/library/dn530779.aspx
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

DPM 2012 R2 Repoting Protection Status as OK but no replica exists for the volume

2012R2 server running 2012R2 DPM. I am using LeftHand SAN as my DPM disks for storing backups. Our production SAN is an EMC VNX5300. I have created a mount point of a LUN and attached it to the DPM server. I have attached a snapshot to the mount point. When
I brought the volume online in Disk Management, it assigned it a drive letter. I removed the drive letter and connected it to a mount point in an empty folder in C:\ActiveVolumes. I am able to browse the folder and look at data in the folder without issue
(except having to elevate for some of the folders when browsing through GUI). In DPM, I created a new protection group. I added the mount point path (C:\ActiveVolumes\MyMountPoint) as a member of the PG. I walked through the wizard and configured my short
term and long term protection options as I have done for other jobs. I had it create the group. At the end of the process, it reported success. Based on having done this with other mount points in similar ways, I was expecting the volume to spend some hours
creating its replica as it is multiple hundreds of gig in size. After less than 15 minutes, it was sitting there with a Green OK display for Protection Status. That seemed entirely to quick so I started to investigate. When I tried to create do anything, it
failed. I looked in Monitoring/Failed jobs for yesterday and today. There was a failed job for the PG that said as follows:
Type: Replica creation
Status: Failed
Description: The Operation failed since DPM was unable to access the file/folder
\\?\Volume{GUID}\Company\Logs\Cleanup\filename.txt on dpm01.domain.pri. This could be due to the file/folder being corrupt or the file system on the volume being corrupt. (ID 2036 Details:
The file or directory is corrupted and unreadable (0x80070570))
There is a second error stating that No recovery point was created, either because synchronization has not occurred since the last recovery point was created, or because no changes were found during synchronization. (ID 208)
When I check the file in question on the original source, it is fine. When I connect to the mount point on the dpm server, browsing to the location, I find that the file says it is indeed corrupt. I will open a call with EMC as well, but it is a little concerning
that a single file can prevent a whole replica from being created. I also tried deleting the corrupt file and tried to synchronize again and it failed on another file in the same folder.
Some additional stuff I noticed as different:
In PG setup wizard, when expanding the DPM server under available members, after a few minutes, I get the following error:
"DPM is unable to enumerate contents in <longalphanumericstring> on the protected computer dpm01.domain.pri. Recycle Bin, System Volume Information folder, non-NTFS volumes, DFS links, CDs Quorum Disk (for cluster) and other removable media cannot
be protected. (ID:38)"
Followed by the following:
"The database of this DPM server is located on a remote instance of SQL server.
To protect the database of this DPM server, you must install a protection agent on the computer running the remote instance of SQL server. After the protection agent is installed, open this wizard, navigate tot eh remote instance of SQL server, and select
the DPM database for protection.
Production server name: dpm01.domain.pri
DPM SQL DB name: MSSQLSERVER
DPM Protection agent: Not Installed"
The above is inaccurate because I am running the SQL on the same machine as my DPM server in the default SQL instance name. I have gotten both of the above errors before when trying to backup other mount points but I was able to back up those mount points
without issue.
I also noticed a difference since I created my first mount point backup. I created two folders on the root of the C: drive. ActiveVolumes and StaticVolumes. I had attached mount points under StaticVolumes previously (c:\staticvolumes\imagefolder1, etc.)
and was able to back those up without issue. When I was configuring that one, it allowed me to select to backup StaticVolumes and then it gave me a warning about mount points and did I want to back those up to. To which I replied yes, back them up. When I
was configuring this one, backing up ActiveVolumes was not an option, only the mount point below it. And it never gave me the warning about mount points. I don't know if this has anything to do with this problem.
Any assistance you can provide on figuring out why this isn't working would be much appreciated. I tried deleting the PG and starting over and got the same results. I am at a loss for how to back this up right now.

Hi,
Not sure what you want help with. Did you fix the underlying volume corruption issue ? For future posts, please limit the scope to a single well defined problem so the community can assist you best.
Please re-define a single problem statement if you still want assistance, other wise mark the post as resolved.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 setup to remote SQL 2012. SSL cert error

First of all, the category I selected, which was for SQL server reporting services was as close as I could get. There wasn't a way to select System Center DPM server from the list. As this relates to the Report Server portion of the setup, I chose this category.
I am setting up DPM 2012 SP1 on a single use server (Windows Server 2102 R2 Standard) and remotely connecting to a new DB server (MSSQL 2012). I keep getting error ID:812 when trying to install, and the logs show that it is trying to set up report server,
but that it cannot establish a trust relationship for SSL/TLS.
* Exception : => System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS
secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
I'm not clear on how to proceed. Invalid cert means it wants something very specific.
I have installed a domain issued cert from the DC on the SQL reporting server and have bound that cert to SSL using report server configuration. I then imported the cert into the DPM server in the trusted and personal certs. The DPM server has our DC as
a trusted source. That clearly doesn't work.
Thinking I may not be able to use a self-signed cert, I then installed our wildcard cert onto both the SQL server and the DPM server. I ran through the Report Server configuration again and bound that wildcard. This is a Godaddy wildcard cert.
Same problem no matter what I do. Clearly, this is matter of a cert issue, but I'm lost. There are zero instructions I've found on how to ensure Windows server 2012 cert requirements are met as it relates to SQL and DPM.
Thanks for your advice.
Kaden

Hi Kaden,
This thread is for reporting service and I hope i can provide some useful informaiton from reporting service side while i don't work on DPM at all. You may still need to find out the forum for the DPM and check there.
Regardingless of DPM, Reporting Service can usually create HTTP link and HTTPS link together. For the HTTP one, a certificate is needed. HTTPS is not needed excep you have the concern with security.
Usually application like DPM/SCOM will connect to the web service link provided by Reporting Service and work on that.
If the application requires a HTTPS link, then same thing has to be setup on reporting.
You need to install a certificate and add it to trust store and then configure reporting service to listening on HTTPs 443 port from the reporting service configuration manager.
You can find the steps here.http://technet.microsoft.com/en-us/library/ms345223(v=sql.110).aspx
After you create the HTTPS link successful, try to open the https web service link both remotely or locally from IE. If you can open it there without any error, reporting service is working fine.
For some applications, they would need special certificates installed on reporting service and used. You may check with the related product on this then.
In a summary, if you can configure a HTTPS link for reporting service can open it correctly, configuration steps on reporting service is fine.
If there is still any error from DPM, you would need check additional resource from DPM part.
Thanks,

Migration of sql agent jobs in SQL 2014 AlwaysON

Hi All,
We are in process of implementing AG in SQL 2014. I am facing issues while checking jobs.
I have created the jobs on both nodes. However, I want the jobs to be executed only on primary.
For this, I started introducing a new step inside the sql agent job which will be my 1st step which checks whether it is Primary or not.
If not primary, I want the job to quit with Success else I want to proceed to next step as it is Primary.
But i wasn't able to adjust the Advanced option of 1st step where i am checking whether isPrimary or not. Can we adjust the advanced options of setting @on_success_step_id programmatically in 1st step itself... or Is there a better way to do this.
If anyone share that piece of logic would be a great help.
Thanks in Advance.

Hi jmcmullen,
This works fine. Thank you. But it is changing the behavior of the job.
Lets say for example I have node-a n node-b.
for eg: if the job is started at step1 on secondary(i.e. node-b) and we are checking if primary or not.if not primary , then we are the above action i..e
EXEC dbo.sp_update_jobstep
    @job_name = N'Test',
    @step_id = 1,
   @on_success_action=1,
   @on_success_step_id=0,
   @on_fail_action=1,
   @on_fail_step_id=0;
GO
At this stage , step1 options are changed i.e OnSuccess of step1 -> it is changed to "quit with a success".
Doing so, there is a problem. at this now lets say failover happened, the job now started on node-B which is primary now, and now the options are wrongly set for step1 which is OnSuccess it has to "go to next step" but it is quiting
with success. In GUI it shows below warning
WARNING: The following job steps cannot be reached with the current job step flow logic:
Is this the intended behavior?
Does it makes sense ??

DPM 2012 R2 Bug: Unable to backup a VM with the same name as an old VM

Scenario:
You have a VM called "Virtual Machine 1" running on a Windows Server 2012 R2 Hyper-V cluster and you backup this virtual machine using DPM 2012 R2.
You remove "Virtual Machine 1" from DPM, selecting delete replicas and expire all tape backups, and then delete the VM from the cluster as it is no longer required.
Later you create a new virtual machine called "Virtual Machine 1" on the same cluster. You attempt to backup the VM with DPM however when attempting to add the VM to a protection group you get the error "DPM cannot access the path \Online\Virtual
Machine 1 because part of the path has been deleted or renamed. Check the path and enter it again". Refreshing the data source/clearing the cache doesn't help
The only solution I could find that worked was to delete the data source record in DPMDB..tbl_IM_DataSource for the virtual machine. This also required deleting records that referenced the DataSourceId in other tables.

Hi
yo need to clear the Cache on the ProtectionGroup Wizard.
Seidl Michael | http://www.techguy.at | twitter.com/techguyat |
facebook.com/techguyat |
youtube.com/techguyat

Adding SQL Server AlwaysOn to existing Failover Clusters

Hello,
We use two seperate ms sql server 2012 clusters. We have two sites. All nodes are in same domain.
In the first site, NOD1 and NOD2 are in SITE A cluster group. (INSTANCE A) They have a shared SAN storage.
In the second site, NOD3 and NOD3 are SITE B cluster group. (INSTANCE B) They have a shared SAN storage too.
Can we use alwayson between two sites? If it is possible , how can we do it? and documents, web site etc.
Thank you.

Hi,
Windows cluster can straddle multi sites. If they are in the
same WSFC cluster, you can.
Please download the “AlwaysOn Architecture Guide: Building a High Availability and Disaster Recovery Solution by Using Failover Cluster Instances and Availability Groups”
Word document from the following link.
http://msdn.microsoft.com/en-us/library/jj215886.aspx
Thanks.
Tracy Cai
TechNet Community Support

SQL 2014 Linked Servers with Availability Groups

Good afternoon All. Hope your well. We have SQL 2014 Availability group setup over multiple Subnets.
So basically Instance A(In Primary DC), and Instance B (Secondary Replica, in secondary DC), with AG1 (Availability Group)
When I connect to the instance Directly (using SQL management Studio), and attempt to create a linked Server to another SQL 2014 instance (Instance D, Both use the same Service Account), I am able to successfully connect, and run query on the Linked Server.
However when I connect to the Availability group, I attempt to open the linked server (to Instance D) and receive the following error:
Login Failed for User 'NT Authority\Anonymous Logon'
This above only happens when I connect to the AG1, and not the instances directly. I have given the Service account permissions to Read and Write its own SPNs (Using ADSI Edit). Researching this people have stated to add the Availability Group Name as an
SPN to the Service account;
Setspn -A MSSQLSVC\AG1.mydomain:1433 mydomain\ServiceAccount
However, Im a little unsure at this stage, should the port in the above command reflect what the AG1 endpoint ports are? As I have done that (as well as trying port 1433), and unfortunately the error still happens. Your assistance would be appreciated,
kind regards,

Hi Nsaneone,
>> Setspn -A MSSQLSVC\AG1.mydomain:1433 mydomain\ServiceAccount
>>However, Im a little unsure at this stage, should the port in the above command reflect what the AG1 endpoint ports are?
The port in the above command should reflect the port which the availability group listener is listening on, but not the endpoint port.
>> Login Failed for User 'NT Authority\Anonymous Logon'
According to the error message, it always occurs when the Kerberos authentication fails in SQL Server, there are proposals for you troubleshooting the issue.
1. Make sure that your service accounts have “Trust this user for delegation to any service (Kerberos only)” enabled in Active Directory.
2. Make sure that SPN’s are registered successfully for all SQL Server instances.
3. The server must be using TCP/IP or named pipes network connectivity.
For more details about the error, please review the following links.
http://mssqlwiki.com/tag/login-failed-for-user-nt-authority-anonymous/
http://blogs.msdn.com/b/karthick_pk/archive/2009/01/23/kerberos-authentication-in-sqlserver.aspx
Thanks,
Lydia Zhang

SQL 2014 License mapping with physical cores during/after installation

Hi,
I have ESX Machine with 24 cores. I have to purchase SQL Server 2014 Enterprise physical core based license for 24 cores. so my question is- how SQL 2014 License will mapping/hosted/linked with physical cores during/after installation on ESX machine?
Please help!!

You are most welcome Satendra :-)
Please close the thread, by marking the answer/s (the link under each response) and you can vote for responses as well (the link in the left of the response)
Ronen Ariely
[Personal Site] [Blog] [Facebook]

Question on Quorum : Windows Server 2012 R2 + SQL 2014 AlwaysOn AG

OS on all nodes : Windows Server 2012 R2
SQL on all nodes : SQL Server 2014 CU2
2 cluster nodes in primary data center and AlwaysOn AG doing Sync Transfer between these nodes with auto failover.
2 cluster nodes in DR data center(Different subnet) and AlwaysON AG doing an Async Transfer between primary replica and these nodes with manual failover.
As this is a multi sub-net cluster we are giving DR nodes 0 vote. 2 nodes on primary DC has votes and a file share on the primary DC has a vote.
If the primary DC is gone,then should we re-assign node votes to the 2 nodes in DR site and again manually configure a file share witness and give it a vote?
Whats the best strategy here? Any recommendation is highly appreciated.
Thank you,

Anup,
Think if we have network issues between Primary DC and DR DC. DR node might think…Hey, I’m the only one running now. I can take all the resources. We do not want nodes in the secondary site to contribute to a decision to take the cluster offline
when there is nothing wrong with the primary site. Do you mean to say Dynamic Quorum is smart enough to handle this situation?
Is it smart enough on it's own? No. That's why someone has to determine which site they want to stay up.
If you're using dynamic quorum, a new property was introduced called "LowerQuorumPriorityNodeID" which is set at the cluster level. Give it the node of one and only one of the secondary site servers. Set a fileshare witness (if possible) as the
odd vote and make sure both sites can see it equally well. Set this property on the cluster for a node on the secondary site.
http://technet.microsoft.com/en-us/library/dn265972.aspx#BKMK_TieBreak
Assume that the fileshare goes down and you have 2 nodes at the local site and 2 nodes at the DR site. Suddenly, communicates between the two are severed. If you have dynamic quorum set and the property I mentioned above, the secondary site will shut down
and the local site will stay up as the secondary site is set for a lower precedence.
Please note, the only reason I brought this up was because you're on Windows Server 2012R2 as this is when it was first introduced.
-Sean
Sean Gallardy | Blog | Microsoft Certified Master

DPM 2012 R2 Online Protection - Online Recovery Point Creation Failed

Hi
We are moving from protecting our DPM server with another server to use an Azure Data Vault. 2 of the Protection Groups work fine, but the third - protecting a pair of Folders - fails. On the DPM MMC it shows Online recovery point creation
failed, and in the Event Log it shows -
Creation of online recovery points for D:\ on blah.blah.co.uk have failed. The last online recovery point creation failed for the following reason: (ID: 3188)
The operation attempted cannot be performed at this time because a backup or restore operation is currently running. (ID: 100049)
The DPM server is the only one conducting any backups. The target server is Win 2003 (for the moment).
Could anyone give me any pointers?
Thanks

Ok, nobody any more ideas?
The latest test involved 9.75GB on the protected server. I created the protection group and this was the outcome:
Replica volume: 15.98 GB allocated, 0 KB used | Recovery point volume: 3.70 GB allocated, 0 KB used
I then create a recovery point and then deleted all 9.75GB on the protected server. And did a full restore from DPM. It then gave following outcome:
Replica volume: 15.98 GB allocated, 9.85 GB used | Recovery point volume: 3.70 GB allocated, 654.86 MB used
Then after the creation of the first recovery point (sync + recovery point), I get this:
Replica volume: 15.98 GB allocated, 4.79 GB used | Recovery point volume: 13.70 GB allocated, 3.27 GB used
As you can see DPM took the 9.75GB and added it to the recovery volume. And strangly it took away half of the replica volume.
In addition I get 3 entried in my logs:
1) The used disk space on the computer running DPM for the recovery point volume of E:\ has exceeded the threshold value of 90% (DPM accounts 600 MB for internal usage in addition to free space available). If you do not allocate more disk space,
synchronization jobs may fail due to insufficient disk space. (ID: 3169)
2) Synchronization jobs for E:\ on ****** have failed. (ID: 3115)DPM has run out of free space on the recovery point volume and will fail synchronization for E:\ on ***** in order to prevent existing recovery points from being
deleted. (ID: 30195)
3) Creation of recovery points for E:\ on ****** have failed. The last recovery point creation failed for the following reason: (ID: 3114)DPM does not have sufficient storage space available on the recovery point volume to create
new recovery points. (ID: 214)
I hope someone can help me with this.
regards,
Maurice

SSMS 2012 crashes when opening new query on instance with Failover Clustering installed (not 2012 R2)

Hi,
I'm trying to start a new query in SSMS, but every time I click the "New Query" button on the tool bar or open a new query window by Object Explorer -> right-click -> Script as -> New Query Editor Window, SSMS hangs with (Not Responding)
and has to be restarted.
I'm running SSMS 2012 (v11.0.3381.0) on Server 2012 6.2.9200. I'm connecting to the primary node of an AlwaysOn Availability Group, and SSMS is located on the primary node itself.
I'm aware of KB2908806, which describes the same symptoms, but this only applies to Windows 6.3.x. Is there an equivalent fix for 6.2.x, or another workaround?
EDIT: To confirm behaviour: "New Query" works intermittantly, Script as ... to -> New Query Editor Window always crashes.

Hello,
there are many reasons your SSMS process would "hang", including bad server performance or internal SSMS processes being suspended due to locking.
When you open a new query window, what your SSMS application does internally is to open a new connection to your instance. You could be experiencing problems in your instance that are causing the logon process to take too long.
How does the bad performance issue generally happen? Is it only happening by connecting to the instance in SSMS? Does the same problem happen when you attempt to connect through an application, or by any other clients?
What happens if you try to connect to the instance through a remote computer?
Check your server's resource monitor for resource usage. Do you see any counters which could indicate performance problems?
Please post the results of @@Version for your server.
Can you open Activity Monitor in SSMS? How many sessions are listed? Does it also take a long time when you first log into the instance in SSMS, before opening a new query tab? Is the SSMS hanging for all databases when opening a new query window, or just
for the ones included in the availability group? Have you tried to connect to your instance by using a DAC connection?
DAC: http://technet.microsoft.com/en-us/library/ms178068%28v=sql.105%29.aspx
Do you have any server logon triggers? Are there any traces running other than the default trace? What are your server specifications? How many logical cores does it have? Is it being used in a production environment? Is there any CPU or I/O affinity set
for the instance? Whats your min/max memory settings? Run DBCC MEMORYSTATUS and post the results here.
Are there any error messages in the SQL Server errorlog? Is your server dedicated to the SQL Server Instance?
Run this query and post the results:
SELECT * FROM SYS.dm_os_process_memory

DPM unable to connect to SQL Rreporting during install

I'm attempting to install System Center 2012 R2 Data Protection Manager on the same machine I installed SQL Server 2014.
I configured the default instance of SQL Server with the database engine and Reporting Services - Native, the database was created for reporting and the reporting website comes up. I configured TCP/IP for all enabled and listening, removed the dynamic port
0 from the network devices and specified 1433 under IPAll. The firewall is turned off, the user is a domain admin and sysadmin, the SQL Browser service is running.
When I attempt to install DPM and connect to the local instance it keeps giving me the same error no matter what I try. "DPM setup is unable to connect to the specified instance of SQL Server Reporting Service. (ID: 33431)"
Has anyone gotten this to work yet? I see that SC DPM 2012 r2 and sql 2014 are compatible.

Hi,
DPM 2012 R2 does not support using SQL 2014 for database.
Please see
Preparing your environment for System Center 2012 R2 Data Protection Manager (DPM)
SQL Server Database
SQL Server 2012 with SP2 Standard or Enterprise 64-bit
SQL Server 2012 with SP1 Standard or Enterprise 64-bit
SQL Server 2012 Standard or Enterprise 64-bit
SQL Server 2008 R2 with SP2 Standard or Enterprise 64-bit
SQL Server 2008 R2 with SP1 2012 Standard or Enterprise 64-bit
However after you install
KB3009516 Update Rollup 4 (UR4) DPM 2012 R2 can protect SQL 2014 databases.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Trouble connecting to SQL 2014 Database using Power Query

I am trying to connect to a SQL 2014 Database using Power Query. My connection string requires that I set the "Application Intent" setting to a value of "readonly", The connection parameter is required by SQL 2014 because of
the failover cluster configuration.
I have successfully been able to connect via PowerPivot with the following connection string:
Provider=SQLNCLI11;Data Source=<Server>;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=<DB>;Application Intent=readonly
I cannot seem to find the correct syntax to connect via SQL 2014. This is the syntax that I have been attempting:
Sql.Database("<Server>", "<DB>",[Application Intent=readonly])
Is this currently supported?
Thanks, Barbara

It's not yet, I'm afraid, but it's something we're aware of and have vague plans to address :/.

DPM 2012 R2 CU4 protecting SQL 2014 AlwaysOn AG with Failover Cluster vs. DR location

Similar Messages

Maybe you are looking for