Hi -
Recently I added some additional memory to a sever thats part of an active
passive cluster (for a total of 8GB). After which we started receiving an
error message when trying to move the cluster over to the passive server:
Source:ClusSvc
Event ID: 1117
Description: Cluster resouce SQL Server(InstanceName) failed to come offline
I did some searching online but the only thing I could find was a thread on
google news from October 2003 (link included below). I am wondering if
anyone else has also experienced this particular problem and if so how they
may have solved it.
Google Groups Link:
http://groups.google.com/groups?hl=e...3DN%26tab%3Dwg
Thanks!
Brad Baker
Anything in the SQL Error log?
Did you re-configure SQL to use the additional RAM?
--
Mike Epprecht, Microsoft SQL Server MVP
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Brad Baker" <bab5470@.no_sp@.m.rochester.rr..com> wrote in message
news:e78npbWfEHA.3964@.TK2MSFTNGP12.phx.gbl...
> Hi -
>
> Recently I added some additional memory to a sever thats part of an active
> passive cluster (for a total of 8GB). After which we started receiving an
> error message when trying to move the cluster over to the passive server:
>
> Source:ClusSvc
> Event ID: 1117
> Description: Cluster resouce SQL Server(InstanceName) failed to come
offline
>
> I did some searching online but the only thing I could find was a thread
on
> google news from October 2003 (link included below). I am wondering if
> anyone else has also experienced this particular problem and if so how
they
> may have solved it.
>
> Google Groups Link:
>
http://groups.google.com/groups?hl=e...3DN%26tab%3Dwg
>
> Thanks!
> Brad Baker
>
>
>
|||Anything in the SQL Error log?
> Other than the error mentioned in the event viewer I didn't see anything
> really pertinant.
Did you re-configure SQL to use the additional RAM?
> We enabled AWE and also enabled SQL to use 7GB of RAM. The only thing
> that might be noteworthy is that the active server has 8GB of RAM versus
> the passive system which has 4GB of RAM. We've run unbalanced cluster for
> quite some time though and only experienced this problem after adding the
> last 2GB.
Brad
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23AWVeqWfEHA.4092@.TK2MSFTNGP10.phx.gbl...
> Anything in the SQL Error log?
> Did you re-configure SQL to use the additional RAM?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Johannesburg, South Africa
> Mobile: +27-82-552-0268
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Brad Baker" <bab5470@.no_sp@.m.rochester.rr..com> wrote in message
> news:e78npbWfEHA.3964@.TK2MSFTNGP12.phx.gbl...
> offline
> on
> they
> http://groups.google.com/groups?hl=e...3DN%26tab%3Dwg
>
|||The error message indicates that the SQL Server recource fail to come offline. Instead of moving the group, try taking the SQL Server resource offline and see the results/errors ? If it goes offline then I would take all
resources in the SQL group offline, move the group to the other node and bring one resource online at a time -- starting with the resources that are not dependent on any resources i.e the disks first followed by sql ip
resoruce, sql network name and then sql server. Also, I will uncheck "restart" property for the resources to troubleshoot this issue (set it back to default after issue is resolved).
NOTE: Since AWE is enabled, max server memory is set to 7GB and passive node has 4GB, when you move the SQL Group to the passive node, SQL server instance will acquire almost all of the available memory
and leave ONLY up to 128MB fo memory free. For more info, please refer to SQL Server BOL topic "Managing AWE Memory".
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
Showing posts with label resource. Show all posts
Showing posts with label resource. Show all posts
Tuesday, March 27, 2012
Cluster Resource replacing physical server
We are replacing an existing SQL 2000 EE server with a clustered
resource by the same name. We have done this before, but are running
into an issue on this install. Here are the steps we have performed:
* Migrate databases as files
* Shut off original server
* Delete original computer account and replicate to all domain
controllers.
* Create cluster resource (third resource in this cluster)
We are having problems though with cluster recognizing the old server
account. We are getting Event ID 1210 on Clussvc on the install.
"Cluster resource 'SQL Network Name(ITSQLEE)' failed to go online
because its associated computer account (ITSQLEE) exists in Active
Directory and the Kerberos authentication is not enabled for the
resource. Client applications that are using Kerberos based
authentication (either directly or through the Negotiate security
package) will fail to authenticate when contacting a service by this
network name.
To bring the resource online, either enable Kerberos authentication or
delete the computer account."
In a prior event message, we get 1119 - Clussvc - Bad DNS Key. I have
tried this multiple times after waiting for Active directory to
synchronize and verifying with replmon. Any ideas? Thank you.
Hi Bowulf
The reason for this could be that the changes in Active Directory isn't
replicated around to all Domain Controllers. You could initiate Force
Replication but if you are in an enterprise environment this could cost in
terms of bandwith. Hence when you delete the computer account and it's not
replicated you would get this message.
Any help?
"Bowulf" wrote:
> We are replacing an existing SQL 2000 EE server with a clustered
> resource by the same name. We have done this before, but are running
> into an issue on this install. Here are the steps we have performed:
> * Migrate databases as files
> * Shut off original server
> * Delete original computer account and replicate to all domain
> controllers.
> * Create cluster resource (third resource in this cluster)
> We are having problems though with cluster recognizing the old server
> account. We are getting Event ID 1210 on Clussvc on the install.
> "Cluster resource 'SQL Network Name(ITSQLEE)' failed to go online
> because its associated computer account (ITSQLEE) exists in Active
> Directory and the Kerberos authentication is not enabled for the
> resource. Client applications that are using Kerberos based
> authentication (either directly or through the Negotiate security
> package) will fail to authenticate when contacting a service by this
> network name.
> To bring the resource online, either enable Kerberos authentication or
> delete the computer account."
> In a prior event message, we get 1119 - Clussvc - Bad DNS Key. I have
> tried this multiple times after waiting for Active directory to
> synchronize and verifying with replmon. Any ideas? Thank you.
>
|||Thanks for the reply. I had ensured with replmon that the 11 Domain
Controllers had all been synchronized with the each other, and that the
ADUC on each domain controller showed the computer as removed. The
entry was of course still present but tombstoned. I would hate to
think I would have to wait 90 days though.
ipconfig2 wrote:[vbcol=seagreen]
> Hi Bowulf
> The reason for this could be that the changes in Active Directory isn't
> replicated around to all Domain Controllers. You could initiate Force
> Replication but if you are in an enterprise environment this could cost in
> terms of bandwith. Hence when you delete the computer account and it's not
> replicated you would get this message.
> Any help?
>
> "Bowulf" wrote:
|||It is my understanding that this would be the behavior if DDNS did not
properly delete the entry, regardless of the status of the AD replication.
A simple ping of the name for the A record and reverse for the PTR would
indicate if it were still present.
Delete the DNS records manually.
Install the installation.
Create the virtual computer account manually if the Cluster service account
does not have sufficient rights.
Manually apply the SPN registrations for the SQL Server service account.
Then connect to cluster administrator to Enable Kerberos on the network name
resources.
Sincerely,
Anthony Thomas
"Bowulf" <bowulf@.gmail.com> wrote in message
news:1165709800.241227.11990@.79g2000cws.googlegrou ps.com...[vbcol=seagreen]
> Thanks for the reply. I had ensured with replmon that the 11 Domain
> Controllers had all been synchronized with the each other, and that the
> ADUC on each domain controller showed the computer as removed. The
> entry was of course still present but tombstoned. I would hate to
> think I would have to wait 90 days though.
> ipconfig2 wrote:
in[vbcol=seagreen]
not
>
resource by the same name. We have done this before, but are running
into an issue on this install. Here are the steps we have performed:
* Migrate databases as files
* Shut off original server
* Delete original computer account and replicate to all domain
controllers.
* Create cluster resource (third resource in this cluster)
We are having problems though with cluster recognizing the old server
account. We are getting Event ID 1210 on Clussvc on the install.
"Cluster resource 'SQL Network Name(ITSQLEE)' failed to go online
because its associated computer account (ITSQLEE) exists in Active
Directory and the Kerberos authentication is not enabled for the
resource. Client applications that are using Kerberos based
authentication (either directly or through the Negotiate security
package) will fail to authenticate when contacting a service by this
network name.
To bring the resource online, either enable Kerberos authentication or
delete the computer account."
In a prior event message, we get 1119 - Clussvc - Bad DNS Key. I have
tried this multiple times after waiting for Active directory to
synchronize and verifying with replmon. Any ideas? Thank you.
Hi Bowulf
The reason for this could be that the changes in Active Directory isn't
replicated around to all Domain Controllers. You could initiate Force
Replication but if you are in an enterprise environment this could cost in
terms of bandwith. Hence when you delete the computer account and it's not
replicated you would get this message.
Any help?
"Bowulf" wrote:
> We are replacing an existing SQL 2000 EE server with a clustered
> resource by the same name. We have done this before, but are running
> into an issue on this install. Here are the steps we have performed:
> * Migrate databases as files
> * Shut off original server
> * Delete original computer account and replicate to all domain
> controllers.
> * Create cluster resource (third resource in this cluster)
> We are having problems though with cluster recognizing the old server
> account. We are getting Event ID 1210 on Clussvc on the install.
> "Cluster resource 'SQL Network Name(ITSQLEE)' failed to go online
> because its associated computer account (ITSQLEE) exists in Active
> Directory and the Kerberos authentication is not enabled for the
> resource. Client applications that are using Kerberos based
> authentication (either directly or through the Negotiate security
> package) will fail to authenticate when contacting a service by this
> network name.
> To bring the resource online, either enable Kerberos authentication or
> delete the computer account."
> In a prior event message, we get 1119 - Clussvc - Bad DNS Key. I have
> tried this multiple times after waiting for Active directory to
> synchronize and verifying with replmon. Any ideas? Thank you.
>
|||Thanks for the reply. I had ensured with replmon that the 11 Domain
Controllers had all been synchronized with the each other, and that the
ADUC on each domain controller showed the computer as removed. The
entry was of course still present but tombstoned. I would hate to
think I would have to wait 90 days though.
ipconfig2 wrote:[vbcol=seagreen]
> Hi Bowulf
> The reason for this could be that the changes in Active Directory isn't
> replicated around to all Domain Controllers. You could initiate Force
> Replication but if you are in an enterprise environment this could cost in
> terms of bandwith. Hence when you delete the computer account and it's not
> replicated you would get this message.
> Any help?
>
> "Bowulf" wrote:
|||It is my understanding that this would be the behavior if DDNS did not
properly delete the entry, regardless of the status of the AD replication.
A simple ping of the name for the A record and reverse for the PTR would
indicate if it were still present.
Delete the DNS records manually.
Install the installation.
Create the virtual computer account manually if the Cluster service account
does not have sufficient rights.
Manually apply the SPN registrations for the SQL Server service account.
Then connect to cluster administrator to Enable Kerberos on the network name
resources.
Sincerely,
Anthony Thomas
"Bowulf" <bowulf@.gmail.com> wrote in message
news:1165709800.241227.11990@.79g2000cws.googlegrou ps.com...[vbcol=seagreen]
> Thanks for the reply. I had ensured with replmon that the 11 Domain
> Controllers had all been synchronized with the each other, and that the
> ADUC on each domain controller showed the computer as removed. The
> entry was of course still present but tombstoned. I would hate to
> think I would have to wait 90 days though.
> ipconfig2 wrote:
in[vbcol=seagreen]
not
>
Cluster resource could not be found.
After a reboot of one of my node I am currently receiving the following
message:
The disk associated with the cluster disk resource 'Disk T:' could not be
found. The expected signature of the disk was XXXXXXX. If the disk was
removed from the server cluster, the resource should be deleted. If the disk
was replaced, the resource must be deleted and created again in order to
bring the disk online. If the disk has not been removed or replaced, it may
be inaccessible at this time because it is reserved by another server cluster
node.
How can I create another GUID? Will the installation of the Windows SP1
create a new GUID?
Burley,
You are not lonely. I got the same problem on MSCS.
"Burley" wrote:
> After a reboot of one of my node I am currently receiving the following
> message:
> The disk associated with the cluster disk resource 'Disk T:' could not be
> found. The expected signature of the disk was XXXXXXX. If the disk was
> removed from the server cluster, the resource should be deleted. If the disk
> was replaced, the resource must be deleted and created again in order to
> bring the disk online. If the disk has not been removed or replaced, it may
> be inaccessible at this time because it is reserved by another server cluster
> node.
> How can I create another GUID? Will the installation of the Windows SP1
> create a new GUID?
|||Lemme guess, SCSI-based cluster?
Sometimes a SCSI-based cluster can have problems with one node blocking
access to the shared disk. This is most common during node startup and
especially common when two nodes are started up at the same time. Always
boot one node at a time in a SCSI cluster.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Burley" <Burley@.discussions.microsoft.com> wrote in message
news:591F9019-BCCB-49FD-A749-03267C6A4591@.microsoft.com...
> After a reboot of one of my node I am currently receiving the following
> message:
> The disk associated with the cluster disk resource 'Disk T:' could not be
> found. The expected signature of the disk was XXXXXXX. If the disk was
> removed from the server cluster, the resource should be deleted. If the
> disk
> was replaced, the resource must be deleted and created again in order to
> bring the disk online. If the disk has not been removed or replaced, it
> may
> be inaccessible at this time because it is reserved by another server
> cluster
> node.
> How can I create another GUID? Will the installation of the Windows SP1
> create a new GUID?
sqlsql
message:
The disk associated with the cluster disk resource 'Disk T:' could not be
found. The expected signature of the disk was XXXXXXX. If the disk was
removed from the server cluster, the resource should be deleted. If the disk
was replaced, the resource must be deleted and created again in order to
bring the disk online. If the disk has not been removed or replaced, it may
be inaccessible at this time because it is reserved by another server cluster
node.
How can I create another GUID? Will the installation of the Windows SP1
create a new GUID?
Burley,
You are not lonely. I got the same problem on MSCS.
"Burley" wrote:
> After a reboot of one of my node I am currently receiving the following
> message:
> The disk associated with the cluster disk resource 'Disk T:' could not be
> found. The expected signature of the disk was XXXXXXX. If the disk was
> removed from the server cluster, the resource should be deleted. If the disk
> was replaced, the resource must be deleted and created again in order to
> bring the disk online. If the disk has not been removed or replaced, it may
> be inaccessible at this time because it is reserved by another server cluster
> node.
> How can I create another GUID? Will the installation of the Windows SP1
> create a new GUID?
|||Lemme guess, SCSI-based cluster?
Sometimes a SCSI-based cluster can have problems with one node blocking
access to the shared disk. This is most common during node startup and
especially common when two nodes are started up at the same time. Always
boot one node at a time in a SCSI cluster.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Burley" <Burley@.discussions.microsoft.com> wrote in message
news:591F9019-BCCB-49FD-A749-03267C6A4591@.microsoft.com...
> After a reboot of one of my node I am currently receiving the following
> message:
> The disk associated with the cluster disk resource 'Disk T:' could not be
> found. The expected signature of the disk was XXXXXXX. If the disk was
> removed from the server cluster, the resource should be deleted. If the
> disk
> was replaced, the resource must be deleted and created again in order to
> bring the disk online. If the disk has not been removed or replaced, it
> may
> be inaccessible at this time because it is reserved by another server
> cluster
> node.
> How can I create another GUID? Will the installation of the Windows SP1
> create a new GUID?
sqlsql
Subscribe to:
Posts (Atom)