ColdFusion 9 Fails after SQL 2008 Cluster Failover

All,
I have a ColdFusion 9 app server that seems to be failing when my SQL 2008 cluster fails over to the passive node. By failing, my IIS server does not respond to any .cfm requests about 4-5 minutes after the failover. It serves out static and .asp pages just fine. Restarting ColdFusion server service and rebooting the server itself does not fix the problem. The only fix is to fail the SQL cluster back to the original node.
Specs are as follows:
SQL - SQL 2008 SP1 64-bit active/passive cluster VM
CF - CF9 running on Windows 2008 SP2 64-bit VM
Erick

Problem solved. We had a linked server defined in SQL that pointed to an Oracle instance. We could successfully run the "Test Connection" in SQL Management Studio for the linked server when our SQL 2008 cluster was on node 1. However, we got an "OraOLEDBpus10.dll: The specified module could not be found" error message when trying to test the connection when the cluster was on node 2. The fix was to add the Oracle folder path to the Windows PATH environment variable on node 2. The Oracle installer is supposed to do this automatically, so we don't know why it was missing.
The reason CF would become unresponsive was that we had a template with a query that used the linked server. The purpose of this template was to monitor the status of the linked server. Using CF Server Monitor, we were able to see active requests to that template which would keep running and not terminate even though we set a timeout value in CF Admin.
Erick

Similar Messages

Build a SQL 2008 R2 Failover clustering

Hi,
Am looking for a 2 node active passive SQL server clustering for testing purpose
I believe that for building a cluster we need a AD, DNS and DHCP and shared disk ..
I have searched in Internet and as of now I haven't found a complete solution for a SQL Server 2008 R2 fail over clustering
I have tried my self for building a SQL cluster with the available information in internet . But every time am getting one or other error...
Could some one here help me here to find out a COMPLETE solution for building a 2 node active passive SQL Server 2008 R2 fail over cluster.
Video links or step by step screen shot will be much appreciated.
Oracle VM virtual manager , and Starwind I have used to create a Windows cluster.

Hi Nirmal,
You are right. Cluster
configured Quorum automatically
But when am installing SQL am getting this error - SQL Server network name
I have tried with Windows cluster name and DTC name in SQL Server network name
But throwing the error
"The SQL server failover cluster instance name already exit as cluster resource. Specify a different failover cluster instance name"
When am trying with a different name am getting the below error.
"The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid."
How to resolve the issue.
Am using
win 2008 R2 SP1, SQL 2008 R2
Oracle VM virtual box, and Star wind software

DPM 2012 R2 protecting a SQL 2008 Cluster/Vss Writer problems on SQL Server

Hola,
I am running DPM 2012 R2 rollup 4. My Server OS is 2012 Datacenter. I have a SQL 2008 Active/Passive cluster and MS support has kicked this to the SQL team for review. OK hear we go ..When I run the vssadmin list writer I do see the SQL Writer. Also
says no errors. When I run diskshadow /l c:a.txt from an admin command prompt the output does show the SQL Writer information but under that should display all the meta data for each connection to the database so DPM can expand the SQL database to
be chosen for protection. I am already confused.
I am going to include a snippet from the vssadmin and the diskshadow command:
vssadmin list writers:
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {8d773b6f-0196-4c34-9943-f258f99c2d9a}
   State: [1] Stable
   Last error: No error
Diskshadow /l c:a.txt
* WRITER "SqlServerWriter"
  - Writer ID   = {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
  - Writer instance ID = {8d773b6f-0196-4c34-9943-f258f99c2d9a}
  - Supports restore events = TRUE
  - Writer restore conditions = VSS_WRE_ALWAYS
  - Restore method = VSS_RME_RESTORE_IF_CAN_REPLACE
  - Requires reboot after restore = FALSE
  - Excluded files:
* WRITER "BITS Writer"
  - Writer ID   = {4969d978-be47-48b0-b100-f328f07ac1e0}
  - Writer instance ID = {5ad5c4f7-5f68-4c1d-a4fc-92d5ef898881}
  - Supports restore events = TRUE
  - Writer restore conditions = VSS_WRE_UNDEFINED
  - Restore method = VSS_RME_UNDEFINED
  - Requires reboot after restore = FALSE
  - Excluded files:
   - Exclude: Path = C:\Windows\System32, Filespec = bits.log
   - Exclude: Path = C:\Windows\System32, Filespec = bits.bak
   - Exclude: Path = C:\ProgramData\Microsoft\Net
As you can see this did not return the expected results. I should see the meta data for each database. This is why DPM can't list the databases for backup in my 2008 production SQL cluster. Any thoughts? This has not been working for quite sometime. I was
hoping the update to rollup 4 would have fixed the problem. I know this is a SQL problem but has anyone had this experience?
Thanks
Steve J.

Update:
Uninstalled SQL Server instance and downloaded SQL Server 2012 SP1 image from link in error message. It takes you to the download page for the express edition of SQL Server 2012. I downloaded the SQLEXPRADV_x64_ENU file and used it to re-install
the SQL Server instance.
Ultimately I had to use the ISO image to upgrade the instance to Standard because the SQL Server Agent will not run under the express edition and caused the DPM install to fail.
The DPM installation then completed successfully and after immediately went to Windows Update and SQL Server 2012 SP2 was installed.
Evidently you cannot start with SP2 until the installation is complete.

High CMEMTHREAD after SQL 2008 R2 Service pack 2 (release version 10.50.4297.0)

Right after applying SQL 2008 R2 Service pack 2, we notice jump in wait time in CMEMTHREAD with high CPU usage ( ~90%).
Someone mention that Trace flag 8048 for newer machine with more than 8 CPU might be the cause of this issue. Can someone verify or confirm??
john

Both trace flag 8048 and soft NUMA is not set. However, trace flag 2335 is enable. I understand that CMEMTHREAD
indicate possible memory contention.
john

SQl 2008 R2 Failover Cluster does not failover after fresh install

I have installed a two node SQL Server 2008 R2 cluster. I used a Named Instance and the SQL Server and SQL Server Agent cluster resources are online on node 1. When I want to move the SQL Server group to node 2, the SQL Server resource fails to start (error
1205 and 1069).
I see in the application log that it is starting up database 'master'. After that I see: Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup etc...
It runs fine on node 1, so what goes wrong?

Hello,
Please verify DTC is configured correctly.
http://msdn.microsoft.com/en-us/library/dd897479(BTS.10).aspx
Please see the following resources also:
http://technet.microsoft.com/en-us/library/cc773525(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc756225(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc773447(WS.10).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Migrate from Existing SQL 2008 R2 Failover Cluster (Rackspace) to new offsite SQL 2008 R2 Cluster (our own cloud)

I have an existing cluster sitting in Rackspace. We have a new co-location with its own SAN that we want to migrate everything over to. Now, if we were keeping the SAN active in Rackspace, this wouldn't be an issue and I'd just add two new nodes to the cluster
and take down the two old nodes, but I need the data shipped to the new SAN so everything in Rackspace can be turned off. VPN is configured between sites (500mbps pipe), so bandwidth isn't a problem.
Should I be adding new shared storage to the existing cluster, replicate to that, turn off the old shared storage, then add new nodes and eventually disable old nodes? I'm trying to do this with the least downtime.
The picture can best be described as this (very simplified)
RACKSPACE CLUSTER - on its own SAN
Node 1: SQLSERVER1-RACK
Node 2: SQLSERVER2-RACK
SQL Server Name: SQLSERVER
NEW CLUSTER - on its own SAN
Node 1: SQLSERVER1-NEW
Node 2: SQLSERVER2-NEW

while this might be doable using SQL Server replication, log shipping is best on a continual basis, or use a backup restore for a one time copy.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

SCCM 2012 on SQL 2008 R2 cluster

Looking Positive and negative for SCCM 2012 SQL cluster configuration. I am looking for configuration for sql 2008 cluster.
can you any configured ? is yes please step by step configuration and preservative

positive: obviously, the SQL could have high availability and will auto fail over to another box if one of the boxes is down.
Juke Chou
TechNet Community Support

How do I install SQL Management Objects for SQL 2008 on a 2 node cluster?

Hi,
One of the software we use needs the SMO to be installed. This is on a SQL 2008 2 node cluster. In the control-panel, I do NOT see this installed, and I see the client tools SDK installed and I even did a repair of it. I still do not see it.
Can some one please help me with SMO install on this 2 node SQL 2008 cluster? I could not find a working link to install this.
Thanks!
Suresh.
Suresh Channamraju

Hi Suresh,
According to your descriptIon, you need to install SMO on two nodes of SQL 2008 cluster, right?
If you want to develop an application that uses SQL Server Management Objects (SMO), you should select the Client Tools SDK when you install SQL Server. To install the Client TooLs SDK without installing SQL Server, install Shared Management Objects from
the SQL Server 2008 Feature Pack.
http://www.microsoft.com/en-us/download/details.aspx?id=6375
By default, the SMO assemblies are installed in the C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies\ directory.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

SQL 2012 Cluster- How to or Steps to Move Tempdb Files from Local drive to Shared volume

Hi..
I did Installation of SQL Server 2012 Cluster. During this setup I installed Tempdb Files on Local drive. Now I want to move this tempdb files from local drive to Shared Drive . When I am trying to move I am getting below error.
Does any one can help me or provide the steps to move this tempdb files from local drive to Shared Drive ?
Msg 5184, Level 16, State 1, Line 1
Cannot use file 'Z:\Tempdb\tempdb.mdf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource
of the Sql Server does not have a dependency on it.
Thanks
Regards..
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

Hi,
The error message may be thrown out when you attempt to create a database on another shared cluster drive when the SQL Server resource is not dependent on that disk.
Check if you are in the scenario which mentioned in the following article:
How to create databases or change disk file locations on a shared cluster drive on which SQL Server was not originally installed
http://support.microsoft.com/kb/295732/en-nz
Here is a thread with similar issue:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c9f80af7-5b51-4c43-a2a0-f9c7d97aa41d/sql-disk-dependency-problem-on-sql-2008-cluster-including-errors
Hope it helps.
Tracy Cai
TechNet Community Support

SQL Server Agent fails to connect to DB after enabling mirror on failover cluster

Hello:
We have multiple databases running in a Failover Cluster instance: SQL 2012SP1 on Server 2008 R2 failover cluster (NOT AlwaysOn). We are trying to add a high-performance mirror in a standalone instance for DR. My understanding is that should be a perfectly
normal, supported configuration.
The mirroring is working properly; however, the clustered SQL Server agent is unable to run jobs that run in the mirrored databases.
We get the following in the job log: Unable to connect to SQL Server 'VIRTUALSERVERNAME\INSTANCE'. The step failed.
There is a partner message in the agent log: [165] ODBC Error: 0, Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported. [SQLSTATE IMH01]
The cluster is not a mulitsubnet cluster. All hosts are connected to the same subnets and there is no storage replication. I can not find any place where I can adjust the connect string options for SQL Agent.
Any guidance or suggestions on how to resolve this would be appreciated.
~joe

SQL Team - MSFT:
Thank you for taking the time to research and provide a clear answer.
This seems very much a workaround and very unsatisfactory.
You are correct, there is an IP dependency with OR condition. Moving to an AND condition is not viable for us. The whole point is to provide network redundancy. With an AND condition, if EITHER network interface fails, the service will go offline or fail
to come online without manual intervention. This is arguably worse for uptime than having a single interface available.
We are in process of rewriting all our SQL jobs to start in tempdb before transitioning to the appropriate target database. If this works for all of our jobs, I will mark the above response as answer.
Again, thank you for the answer.
Regards,
Joe M.

MS DTC not coming online on SQL Server 2008 R2 failover cluster

Dear Experts,
On a SQL Server 2008 R2 failover cluster, MS DTC cluster service is not coming online. It fails with below error message.
"The DTC cluster resource's log file path was originally configured at: E:. Attempting to change that to: M:. This indicates a change in the path of the DTC cluster resource's dependent disk resource. This is not supported. The error code
returned: 0x8000FFFF".
From the Component Services, we can see under the clustered DTCs, in the properties of the log file that it is configured for E drive. The 'Transaction list' and 'Transaction Statistics' are empty. When I try to change the log file path to
point to M drive I get this warning message.
"An MSDTC log file already exists in the selected directory. Resetting an existing MS DTC log file may cause your databases and other transactional resource managers to become inconistent. Please review the MSDTC Administrator's manual before
proceeding. Do you wish to reset the existing MS DTC log"
Could you please advise if this is safe to proceed with this warning as the 'Transaction list' and 'Transaction Statistics' are empty or would it cause any other issue.
Thanks,
MM

Tauseef
Did you tried using wmi....win32_share
$path = "location where to create the folder"
$share = $Shares=[WMICLASS]'WIN32_Share' # class in wmi for share
$Sharename = 'Sharename'
New-Item -type directory -Path $Path
$Shares.Create($Path,$Sharename,0,255,$Sharename)
$Acl = Get-Acl $Path # cmdlet for getting access control list
$Access = New-Object system.security.accesscontrol.filesystemaccessrule("Username","FullControl","ContainerInherit, ObjectInherit", "None", "Allow")
$Acl.AddAccessRule($Access)
Set-Acl $Path $Acl
Thanks Azam When you see answers please Mark as Answer if Helpful..vote as helpful.

The acount information could not be verified - SQL 2005 SP3 installation on Windows 2008 R2 Failover Cluster

Hi,
We have a problem when we are trying to install SQL SP3 on SQL 2005 cluster.
The problem is described bellow:
We installed a new Windows 2008 R2 x64 failover cluster with two nodes.
As a next step we installed SQL 2005 Enterprise edition x64 on this failover cluster. We have finished the installation without problems. After SQL installation we are trying to install SQL SP3 . We have logged on using a domain administrator account and
we start the installation of SP3 with that user. In authentication mode screen the test gives a success status using either domain administrator-windows authentication or sa-sql authentication. On remote user account screen, when we give the domain
administrator account we get the message "the account information could not be verified. Press ok to return to authentication mode screen to determine the reason for failure".
We have tried to give the SQL services startup user on remote user account screen but the error is the same.
the domain administrator account exists on security logins of SQL with sysadmin rights.
Can someone help?
Thanks.

Hi StelioMavro,
According to your error message, when you install SQL Server 2005 SP3 in your failover cluster, we need to verify if there was other instance that had been removed and the installation did not pass the login check. I recommend you use windows authentication
instead of SQL Server authentication when applying SP3. And the windows account used to run the SP3 setup program must have administrator privileges on the computer where SP3 will be installed.
For more information about how to install SQL Server 2005 SP3 in failover cluster, you can review the following article.
http://www.sqlcoffee.com/Tips0007.htm
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL 2008 R2 cluster installation failure - Failed to find shared disks

Hi,
The validation tests in the SQL 2008R2 cluster installation (running Windows 2008 R2) fails with the following error. The cluster has one root mount point with multiple mount points :
"The cluster on this computer does not have a shared disk available. To continue, at least one shared disk must be available'.
The "Detail.txt" log has alot of "access is denied" errors and here is just a sample. Any ideas what might be causing this issue?
2010-09-29 12:54:08 Slp: Initializing rule      : Cluster shared disk available check
2010-09-29 12:54:08 Slp: Rule applied features : ALL
2010-09-29 12:54:08 Slp: Rule is will be executed : True
2010-09-29 12:54:08 Slp: Init rule target object: Microsoft.SqlServer.Configuration.Cluster.Rules.ClusterSharedDiskFacet
2010-09-29 12:54:09 Slp: The disk resource 'QUORUM' cannot be used as a shared disk because it's a cluster quorum drive.
2010-09-29 12:54:09 Slp: Mount point status for disk 'QUORUM' could not be determined. Reason: 'The disk resource 'QUORUM' cannot be used because it is a cluster quorum drive.'
2010-09-29 12:54:09 Slp: System Error: 5 trying to find mount points at path
\\?\Volume{e1f5ca48-c798-11df-9401-0026b975df1a}\
2010-09-29 12:54:09 Slp:     Access is denied.
2010-09-29 12:54:09 Slp: Mount point status for disk 'SQL01_BAK01' could not be determined. Reason: 'The search for mount points failed. Error: Access is denied.'
2010-09-29 12:54:10 Slp: System Error: 5 trying to find mount points at path
\\?\Volume{e1f5ca4f-c798-11df-9401-0026b975df1a}\
2010-09-29 12:54:10 Slp:     Access is denied.
2010-09-29 12:54:10 Slp: Mount point status for disk 'SQL01_DAT01' could not be determined. Reason: 'The search for mount points failed. Error: Access is denied.'
2010-09-29 12:54:10 Slp: System Error: 5 trying to find mount points at path
\\?\Volume{e1f5ca56-c798-11df-9401-0026b975df1a}\
2010-09-29 12:54:10 Slp:     Access is denied.
Thanks,
PK

Hi,
We were asked by the PSS engineer to give the following privileges the account used to install SQL Server - i am referring to the user domain account as apposed to the SQL service account. These privileges were already applied to the
SQL service account prior to the SQL installation. Assigning these privileges to the user account resolved the issue.
Act as Part of the Operating Sywstem = SeTcbPrivileg
  Bypass Traverse Checking = SeChangeNotify
  Lock Pages In Memory = SeLockMemory
  Log on as a Batch Job = SeBatchLogonRight
  Log on as a Service = SeServiceLogonRight
  Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
Thanks for everyones assistance.
Cheers,
PK

Failed to start SQL SERVER cluster after port changed from 1433 to 61433

Hi
Today, I did Geo SQL2012 Cluster installation with with 2 VIP different subnet. Currently i'm getting problem in changing default port 1433 to 61433, after changing port Cluster group not coming up, SQL Failing. I don't know and not sure, if SQL
service is depend on Port. Please help us , its producion issue.

How you change port ,Changing Port in clustered environment required different procedure. You need to run the command of remove checkpoints and add checkpoints.
See below links
Remove-ClusterCheckpoint
http://technet.microsoft.com/en-us/library/hh847295.aspx
Add-ClusterCheckpoint
http://technet.microsoft.com/en-us/library/hh847255.aspx
--Please mark this Answer if it helps to solve the issue

Error Adding Node to SQL 2008 R2 Cluster

Windows Server 2008 R2 64bit. SQL 2008 R2 64bit.
The Windows Failover cluster is installed with 2 nodes. SQL Cluster was installed successfully on node 1. Ran SQL setup to add a SQL node 2. Made it to the service accounts screen. The SQL Server Agent service account name box is grayed out and nothing can
be entered. If I hit next I get the following error. I can't get past this. I looked for any cumulitive updates for R2, but there aren't any. Does anyone have a work around? If not I will have to scrap the install and go back to the non R2 version of SQL.
[Error Message]
The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password for the SQL Server Agent service.
[Details]
Microsoft.SqlServer.Configuration.Agent.InputValidationException: The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password for the SQL Server Agent service.
================================================================================

After searching around on the Net and reading a few other people with the same problem, it has to be a bug in the GUI.
Run the command line to initiate the setup and it will add the account settings automatically when you come to that page.
setup.exe /ACTION=AddNode /INSTANCENAME="<Insert Instance Name>" /SQLSVCACCOUNT="<SQL account used on other nodes>" /SQLSVCPASSWORD="<password for SQL account>" /AGTSVCACCOUNT="<SQL Server Agent account used on other nodes>"
/AGTSVCPASSWORD="<SQL Server Agent account password>"

ColdFusion 9 Fails after SQL 2008 Cluster Failover

Similar Messages

Maybe you are looking for