SQL Server 2012 :: Restart Service On Remote App After Cluster Fail Over?
Oct 22, 2015I need to be able to restart an application service after the SQL Cluster fails over. how to accomplish this as a SQL job?
View 1 RepliesI need to be able to restart an application service after the SQL Cluster fails over. how to accomplish this as a SQL job?
View 1 RepliesI'm trying to figure out a way to automatically restart the SQL Agent service when an AG fails over to a secondary node. I've created a job on each AG node that runs every 15 seconds and detects when a fail over has happened. It then issues a SQL Agent stop command and then a SQL Agent start command. The problem is that once the stop command happens the start command never fires because the SQL Agent is now stopped.
View 3 Replies View RelatedIs there such a thing called 'Load balancing' on fail over cluster?
View 2 Replies View RelatedMy environment is a 64 bit Windows Server 2012 Standard edition that is running SQL Server 2012 SP1 Standard Edition (64 bit) which has an Active Passive Cluster set up and I unfortunately had no involvement in this cluster build. The person who did is no longer with the company and is not responsive to questions.
This morning this following errors popped up:
Event ID: 1230 - Cluster resource 'Databases' (resource type 'Physical Disk', DLL 'clusres.dll') did not respond to a request in a timely fashion. Cluster health detection will attempt to automatically recover by terminating the Resource Hosting Subsystem (RHS) process running this resource. This may affect other resources hosted in the same RHS process. The resources will then be restarted.
The suspect resource 'Databases' will be marked to run in an isolated RHS process to avoid impacting multiple resources in the event that this resource failure occurs again. Please ensure services, applications, or underlying infrastructure (such as storage or networking) associated with the suspect resource is functioning properly.
Event ID: 1146 - The cluster Resource Hosting Subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually associated with recovery of a crashed or deadlocked resource. Please determine which resource and resource DLL is causing the issue and verify it is functioning properly.
When I saw these errors, I brought the "Databases", "Logs", and "Quorom" disks back online and all was well. I then proceeded to check Application and System Logs noticing there where some VMWare/SAN errors that caused the CPU spike resulting in the Cluster errors.
Regarding the questions, why didn't a failover occur and What can I do to mitigate this process are now what I am focusing on. Researching the above errors, I discovered that you could a policy based what happens in a situation like occurred this morning. You can set policies at the Role level, "Server" level, and at the disk level.
The Role Policy seems to be a little less involved, screenshot RoleProperties.png show these. I assume these are defaults. The server name properties are set to the following screenshot, Servername_Properties_Policy.png. This seems to be correct to me, but there is where I am lacking. I think this means that if it fails at this level all associated resources, disks, etc will failover to node 2.Now where I think the issue is, the third screenshot, Database_Properties_Policy.png. There is no policy set to for situation where a disk resource fails. Which I believe is what happened this morning. Some questions:
1. Do I need to set this similar to what is in the ServerName screenshot?
2. What happens if I check the box for "If restart is unsuccessful, fail over all resources in the role"? Will this only fail over this one disk? If so, it doesn't seem like that would be ideal. Would it fail over at the Role level and move over all associated resources?
I am also not sure what time limits I should set for Period restarts, maximum restarts, delay between restarts, etc...
When I re-boot the machine, if the sql server is set to "automatic", will the service re-start when re-booting the machine?
View 1 Replies View RelatedI inherited a SQL 2012 Ent server sitting on a 2008R2 server using AlwaysOn High Availability, two nodes.
Available Mode: Synchronous commit
Failover Mode: Manual
Connection in Primary role: Allow all connections
Readable secondary: No
seesion timeout: 10
Somebody decided to give SQL server priority boost so I need to change this ASAP. So I plan on doing the following.
1. Manually fail over to the secondary, which does not have the priority boost set to true
2. change the setting
3. restart the service
4. Manually fail over
My question is with the service restart. How does SQL handle if the DB changes on the new primary while the secondary is having the service restarted. Where can I see if the DB are sync again or if not where are they in the sync process.
How to change the sql service passwords on a SQL 2012 cluster.
View 3 Replies View RelatedGreetings,
First I am fairly new to SQL Server 2005 Clustering so this is why I was to see if any of you might be able to help me.
Are current setup is as follows:
CRM1 SERVER 2K3 R2 xxx.xxx.xxx.74
CRM2 SERVER 2K3 R2 xxx.xxx.xxx.75
HP MSA1000 xxx.xxx.xxx.75
MSDTC IP xxx.xxx.xxx.77
SQL INSTANCE xxx.xxx.xxx.78
Now are CRM guys are trying to connect to xxx.xxx.xxx.78 for there SQL instance or RDP into this ip address and they can’t…Now the question is should they be able yto logon to the SQL Instance via RDP?
Thanks,
CujoX
hello,
View 1 Replies View RelatedThis is the 1st time we are building a active/passive cluster with 1 node each. we usually install default instance and setup domain account as service account which will have an spn delegated. Now for active/passive cluster is it ok to use same domain account as service account for both clusters with both creating as default instance again as the windows was built as SERVER1 and SERVER2.
View 4 Replies View RelatedI am trying to install SQL Server 2012 onto an already configured and validated windows failover cluster (server 2012) but the process is hanging after installing the setup files.
The last entry in the log is:
running discovery on remote machine
and I've left it hanging like this for 4 hours and nothing happens.
Hi,
A few months ago, I was trying to install SQL Server 2005 SP2 on a cluster (Active-Active), the Cluster has 3 instances, 2 lives in one node and the other one in the other node. When I try to make the deployment an error message appear, I do not have the error right now but it€™s something like €œCould not connect to the passive node, installation failed€?. The worst part of the error was all instances shut down and I couldn€™t bring on line and I have to reinstall all instances. I need to install SP2 but I€™m a little afraid fail again. Do you know the best way to deploy the SP2 on a cluster? Maybe move all instances in one node before install SP2? Can you help me with your comments. Do you think I have problems with the windows cluster?
Thanks and Regards,
Hi
We have been having a problem with on of our servers, applications connecting to it are experiencing poor performance, even though the server is only running at a peak of 50%.
The odd thing is that after a sql service restart we couldnt connect at all on the SQL port. We were only able to re-connect after rebooting the actuall box. Is there anything that can be done about this? Its strting to look like a network related problem instead of SQL
I have got the error “a network related or instance specific error occurred sql server 2012 “.I have enabled tcp/ip, restarted the services. The sql server service is getting stopped even after the manual restart. I have checked in event viewer and I noticed a error. Here is the error...The log scan number (43:456:1) passed to log scan in database ‘model’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication.
View 1 Replies View RelatedI have a service that depends on SQL Server service. Basically we make sure that our service only starts after SQL server service started. Unfortunately this dependency does not ensure that database is available.
Basically I observed in Application log that SQL server reports that it started to listen on a port. And then I see that recovery process started. As I understand SQL server is not available while database is in the recovery state.
Note: I might have not used a correct terminology to describe SQL server recovery process as I don't have access to Application log with the exact message at the moment. I can verify the message if necessary.
Because SQL server service is started our service starts and attempts to connect to the database. Service fails to connect to database, because of the restoration process. Once restoration is done service connects successfully.
I observed that restoration process starts every time machine is rebooted. It only takes a few minutes to run, but it is enough to generate a number of error messages in event log about failed SQL connections.
My first question is: Is it normal for database to enter into recovery state every time machine is rebooted?
My second question is: If it is a normal operation, is there any way to detect that SQL server is truly available, so our code does not have to try retry establishing connection many times
we had activity last night we need to truncate Transactional Logs we pressed Restart button to initiate service , but it stopped successfully and failed to start the SQL Server service.We did not find anything find anything unusual in log file. Please confirm are we facing any bug or needing any fixes to installed on the server.Windows Server 2008 R2 Standard Service Pack 1Â ( 64bit)
View 6 Replies View RelatedHi,
I'm having trouble with restoring the master db on w2k3 sql2000 sp3a to a Secondary Standby server.
Firstly, I place the server in Single user mode and then restore the master db. The sql server then tries to restart sql services but immediately stops as soon as it starts up.
Can anyone help ?? Please !
Thx, Steve
After I have set the maximum sql server memory in sql server 2014 using sp_configure, do I need to reboot whole server or restart sql service?
View 4 Replies View Relatedi installed sql server express, but i did not select to use mixed mode (the reason being for this that every time i did i got a install coruption error) i want to be able to connect the database remotly using the sqlservers jdbc driver. however i need a user name and password. therefore to do this i believe i need to be able to acess the database remotly.
ive tried everthing:
1. changing the surface area remote conenctions to allow remote connections using tcp and ip only
2. restarted the database
3. restarted the server
4. restarted the browser
5. checked the tcp/ip settings are enabled.
but when i do the follwing in command line i get this:
C:>osql -E
[SQL Native Client]VIA Provider: The specified module could not be found.
[SQL Native Client]Login timeout expired
[SQL Native Client]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.
which indicates that its still not allowing remote conenctions, any ideas?
When the setup program tries to start the database service (the last step of installation), it indicates an error 29503.
The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (17058)
Any help would be appreciated.
I´ve been reading that SQL Server 2012 Always On is dependent on having a Windows Failover Cluster setup. Is that correct ?
View 6 Replies View RelatedI have an intermittent issue where some remote PC's occasionally fail to execute select queries that have a join or return multiple result sets, however simple one table select queries continue to work okay. When it does happen the PC's needs to be rebooted to get to work again. This may only happen some PC's while others continue to work away okay.
I am using a VB6 application and ADO to connect to the database and the error message I get is a General Network Error, Server Not Found when it fails to execute the query. I have ran SQL Profiler on the server and while simple select queries continue to run away okay, a query a join does not even seem to show up in the profiler. The program has been working fine for 15 years with 1000's of users and has only now become an issue on one site for a number of users. Have tried moving the database to a different server and swapping network cards on the local PC's but can't seem to find the cause. The processor and the memory don't seem to be under load, but I am not sure if there is something else in SQL that is causing it to hang under certain conditions.
There have been network analysts experts in to run scans on the network, but I have not had the results of this back yet. Other applications do not seem to be affected so if this analysis does not show up anything.
Can I build a cluster by adding the cluster service, then the SQL instances, then add the other nodes and their passive SQL instances?I would lean to building the cluster first, the add the SQL instances.
View 4 Replies View RelatedWe have Active/Passive cluster on Windows 2003. It is a 2 nodes cluster. The active server came down and the Cluster didn't failover. Then we had to manually failover. Can you help me to decipher the Cluster.log to find out why it didn't failover?
00000d08.000012a8::2007/10/12-04:04:40.847 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000d08.000012a8::2007/10/12-04:04:40.847 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Query timeout expired
00000d08.000012a8::2007/10/12-04:04:40.847 ERR SQL Server <SQL Server>: [sqsrvres] OnlineThread: QP is not online.
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [CP] CppRegNotifyThread checkpointing key SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1MSSQLSERVER to id 4 due to timer
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] QfsGetTempFileName C:DOCUME~1SVC_CL~1LOCALS~1Temp, CLS, 13522 => C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D2.tmp, status 0
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] QfsDeleteFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D2.tmp, status 0
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] QfsRegSaveKey C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D2.tmp, status 0
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [CP] CpSaveData: checkpointing data id 4 to quorum node 1
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [CP] CppWriteCheckpoint checkpointing file C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D2.tmp to file Q:MSCS 592a048-5457-426a-a46d-996441ef0182 0000004.CPT
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] QfsCreateDirectory Q:MSCS 592a048-5457-426a-a46d-996441ef0182, status 183
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] QfsOpenFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D2.tmp => 3, 36cf960 status 0
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] QfsOpenFile Q:MSCS 592a048-5457-426a-a46d-996441ef0182 0000004.CPT => 2, 36cf8d0 status 183
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] ReadFile 928 (regf) 32768 16384, (0=>0) 0 status 0
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] WriteFile 95c (regf) 16384, status 0 (0=>0)
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] ReadFile 928 (regf) 32768 0, (0=>0) 0 status 0
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] QfsFlushBuffers 95c, status 0
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] QfsCloseHandle 928, status 0
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] QfsCloseHandle 95c, status 0
0000077c.000003dc::2007/10/12-04:04:43.785 INFO [Qfs] QfsDeleteFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D2.tmp, status 0
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [CP] CppRegNotifyThread checkpointing key SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1MSSQLSERVER to id 4 due to timer
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] QfsGetTempFileName C:DOCUME~1SVC_CL~1LOCALS~1Temp, CLS, 13523 => C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D3.tmp, status 0
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] QfsDeleteFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D3.tmp, status 0
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] QfsRegSaveKey C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D3.tmp, status 0
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [CP] CpSaveData: checkpointing data id 4 to quorum node 1
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [CP] CppWriteCheckpoint checkpointing file C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D3.tmp to file Q:MSCS 592a048-5457-426a-a46d-996441ef0182 0000004.CPT
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] QfsCreateDirectory Q:MSCS 592a048-5457-426a-a46d-996441ef0182, status 183
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] QfsOpenFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D3.tmp => 3, 36cf960 status 0
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] QfsOpenFile Q:MSCS 592a048-5457-426a-a46d-996441ef0182 0000004.CPT => 2, 36cf8d0 status 183
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] ReadFile 95c (regf) 32768 16384, (0=>0) 0 status 0
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] WriteFile 928 (regf) 16384, status 0 (0=>0)
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] ReadFile 95c (regf) 32768 0, (0=>0) 0 status 0
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] QfsFlushBuffers 928, status 0
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] QfsCloseHandle 95c, status 0
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] QfsCloseHandle 928, status 0
0000077c.000003dc::2007/10/12-04:06:23.084 INFO [Qfs] QfsDeleteFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D3.tmp, status 0
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [CP] CppRegNotifyThread checkpointing key SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1MSSQLSERVER to id 4 due to timer
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] QfsGetTempFileName C:DOCUME~1SVC_CL~1LOCALS~1Temp, CLS, 13524 => C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D4.tmp, status 0
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] QfsDeleteFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D4.tmp, status 0
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] QfsRegSaveKey C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D4.tmp, status 0
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [CP] CpSaveData: checkpointing data id 4 to quorum node 1
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [CP] CppWriteCheckpoint checkpointing file C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D4.tmp to file Q:MSCS 592a048-5457-426a-a46d-996441ef0182 0000004.CPT
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] QfsCreateDirectory Q:MSCS 592a048-5457-426a-a46d-996441ef0182, status 183
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] QfsOpenFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D4.tmp => 3, 36cf960 status 0
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] QfsOpenFile Q:MSCS 592a048-5457-426a-a46d-996441ef0182 0000004.CPT => 2, 36cf8d0 status 183
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] ReadFile 7e0 (regf) 32768 16384, (0=>0) 0 status 0
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] WriteFile 95c (regf) 16384, status 0 (0=>0)
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] ReadFile 7e0 (regf) 32768 0, (0=>0) 0 status 0
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] QfsFlushBuffers 95c, status 0
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] QfsCloseHandle 7e0, status 0
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] QfsCloseHandle 95c, status 0
0000077c.000003dc::2007/10/12-04:08:08.259 INFO [Qfs] QfsDeleteFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D4.tmp, status 0
0000077c.00000844::2007/10/12-04:09:11.323 INFO [Qfs] GetDiskFreeSpaceEx Q:MSCS, status 0
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [CP] CppRegNotifyThread checkpointing key SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1MSSQLSERVER to id 4 due to timer
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] QfsGetTempFileName C:DOCUME~1SVC_CL~1LOCALS~1Temp, CLS, 13525 => C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D5.tmp, status 0
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] QfsDeleteFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D5.tmp, status 0
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] QfsRegSaveKey C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D5.tmp, status 0
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [CP] CpSaveData: checkpointing data id 4 to quorum node 1
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [CP] CppWriteCheckpoint checkpointing file C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D5.tmp to file Q:MSCS 592a048-5457-426a-a46d-996441ef0182 0000004.CPT
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] QfsCreateDirectory Q:MSCS 592a048-5457-426a-a46d-996441ef0182, status 183
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] QfsOpenFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D5.tmp => 3, 36cf960 status 0
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] QfsOpenFile Q:MSCS 592a048-5457-426a-a46d-996441ef0182 0000004.CPT => 2, 36cf8d0 status 183
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] ReadFile 928 (regf) 32768 16384, (0=>0) 0 status 0
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] WriteFile 7e0 (regf) 16384, status 0 (0=>0)
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] ReadFile 928 (regf) 32768 0, (0=>0) 0 status 0
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] QfsFlushBuffers 7e0, status 0
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] QfsCloseHandle 928, status 0
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] QfsCloseHandle 7e0, status 0
0000077c.000003dc::2007/10/12-04:09:56.652 INFO [Qfs] QfsDeleteFile C:DOCUME~1SVC_CL~1LOCALS~1TempCLS34D5.tmp, status
Anyone know of a query that will cycle the SQL service?
View 6 Replies View RelatedI've been trying to install the following update: Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896). I always recieve the following error: 2B22,
Please advise on a fix for this.
Regards,
Hi All,Im testing error handling on my website and if I stop my local sql server 2000 then run the web app, I get a SqlException which is good, but when I restart the sql server then I get a System.InvalidOperationException that will not go away. ( its coming from a ExecuteScalar() call) This happens on my remote database as well.It also happens if I kill the connection on my remote machine then reconnect. after I reconnect I can access the database using dbvis so I know its there.Am I not clearing something after the first error? If I restart the machine all is well.Thanks in advance for you help!-Keith
View 2 Replies View RelatedHello.
Has anyone attempted and successfully installed SQL Server 2000 SP4
via remote desktop on the cluster.
The reason I am asking is that SP4 readme file has this:
"...
4.3 Systems Management Server Distributed Installation
You cannot install Database Components SP4 from a remote location.
..."
Currently SQL Server has SP3a installed.
Thank you in advance.
I have sql 2000 sp4 running on a cluster, we had to fail over to other cluster, and now the sql agent choice to use a mail profile is grayed out. I can go to sql mail and test the profile and it works, but I can't change it for the sql agent? Anyone seen this before
View 3 Replies View RelatedI have had a serious issue with a production AlwaysOn cluster whereby the service did not successfully transition to the secondary node and I cannot find the root cause of the issue.
Some details: It is a 2 node cluster (same datacenter) with a shared disk quorum, Windows Server 2012, both are virtual machines running on VMWare vSphere  5.5. SQL Server version is 2012 Enterprise SP2 CU6
The failover occurred because of a network incident (a spanning tree recalculation caused a connection timeout between both nodes). Initial entries in the SQL Log look normal for this event, for example:
05/08/2015 11:18:06:Â A connection timeout has occurred on a previously established connection to availability replica 'FIN-IE-PA078' with id [6910F4A9-87E7-4836-BA79-0F41BE90266D]. Â Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.
05/08/2015 11:18:06:Â AlwaysOn Availability Groups connection with secondary database terminated for primary database 'UserManagement' on the availability replica with Replica ID: {6910f4a9-87e7-4836-ba79-0f41be90266d}. This is an informational message only. No user action is required.
[code]....
My interpretation of this is that the cluster failover attempts failed, because the network condition still persisted. The network interruption lasted approximately 2 minutes, and I would have expected the cluster to come back online at this point, after the restart delay period as suggested in the last entry in the error log. However this did not happen.
I am having trouble with a linked server using MSDASQL. I'm connecting to a PostgreSQL database and pulling over data. This process has been working fine.
In trying to pull data from a different client database (same schema), I received an error that the MSDASQL couldn't read the column names.
The actual problem I want help on is that after this happens, I am no longer able to make valid connections to any of my Linked Servers using MSDASQL. The only way I can get my other linked servers to work again is to restart the SQL Service. Usually this is impossible for me to do because of the number of active users.
Two questions:
1) Is there another way to restart a more targeted service or sub-set to reset MSDASQL connections, and clear out my problem?
2) Any idea why I'm getting this error connecting to PostgreSQL on a large dataset when it worked fine for a small dataset using the same linked server? "The provider reported an unexpected catastrophic failure."
Any help is appreciated.
Every so often I get an error when I pull up an ASP.NET 2.0 site using
SQL Express. It tells me that the login failed. If I go
into the server's administrative tools > services and restart SQL
Express and then refresh the site, it works just fine. Is this
some sort of bug or memory issue? Does the application need to
connect every so often or end up falling out somewhere?
Thanks
Every once in a while a scheduled restore of a production database backup to a development server will fail with the following error.
RESTORE cannot operate on database 'XXX' because it is configured for database mirroring or has joined an availability group
While it is true the production database is involved in database mirroring, the development server does not have database mirroring enabled. This error tells me something within the backup is telling the development server the database is configured for database mirroring.
However the perplexing part for me is that we only receive this error maybe 5% of the time, if that, and only on a couple of our databases. We have numerous other restores of mirrored production databases to development servers that have never produced this error. So my question is what is causing this error to occur, and why is it not happening all of the time? We get around this error by deleting the DEV database and re-running the restore job.