RE: ERR VSS: Got Component: Cluster Database

Ernie,

Only time we've seen those errors saying "no node is available" during a
failover, is when one of the resources was missing a node as being a
Possible Owner.

Since that's not the situation in your case, I would recommend calling
Microsoft Product Support Services (PSS) and having a case created for
further troubleshooting.

--------------------
Hope this helps,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
<http://www.microsoft.com/info/cpyright.htm>

-----Original Message-----
> From: <ebferro@xxxxxxxxxxxxxxxxxxxxxxxxx>
> Subject: RE: ERR VSS: Got Component: Cluster Database
> Date: Mon, 23 May 2005 13:16:16 -0700
>
> Mike:
> Yes, both nodes are listed.
> Ernie
>
>
> "Mike Rosado [MSFT]" wrote:
>
> > Ernie,
> >
> > Have you checked all the resources to make sure they list both nodes as
> > Possible Owners?
> >
> > --------------------
> > Hope this helps,
> > Mike Rosado
> > Windows 2000 MCSE + MCDBA
> > Microsoft Enterprise Platform Support
> > Windows NT/2000/2003 Cluster Technologies
> >
> > ====================================================
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> > ====================================================
> >
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > <http://www.microsoft.com/info/cpyright.htm>
> >
> > -----Original Message-----
> > > From: <ebferro@xxxxxxxxxxxxxxxxxxxxxxxxx>
> > > Subject: RE: ERR VSS: Got Component: Cluster Database
> > > Date: Sat, 21 May 2005 08:58:01 -0700
> > >
> > > Mike:
> > > Thanks for your reply. I may actually have a problem and a big one
at
> > that.
> > > I don't know that these errors are related to it but they're on the
node
> > on
> > > which I've got a problem. I'm running SQL Server clustered on a two
node
> > > cluster. I've made it SOP to move all clustered resources to one
node or
> > the
> > > other and then do a windows update on the node that has no clustered
> > > resources on it whenever I do a windows update. I tried to move all
of
> > the
> > > resources to node 2 today to do a windows update on node 1. Node 2
is
> > the
> > > node on which I'm getting these error messages. When I attempted to
move
> > the
> > > clustered instance of SQL today, I got an error indicating that there
was
> > no
> > > node available for the move. When I did a properties on the SQL
cluster
> > > resource, it only had node 1 as a possible owner of that resource so
I
> > added
> > > node 2 as a possible owner. I know that I had both nodes as possible
> > owners
> > > when I set the SQL cluster up about 3 months ago. I tried to move
the
> > SQL
> > > cluster resource to node 2 once again and received the same error
> > message.
> > > When I did a directory on node 2, I noticed that there is no SQL
> > subdirectory
> > > on the hard drive. Now, I'm sure that I installed it and that I was
able
> > to
> > > fail SQL over to either node when I initially installed 3 months ago.

> > I've
> > > not done any windows updates since then nor have I deleted any files
from
> > the
> > > drives on either of the nodes. So, I'm really confused. SQL seems
to be
> > > running just fine on node 1. Any ideas what might have caused this
and
> > what
> > > I can do to fix it? Right now, I've got a one node clustered
instance of
> > SQL
> > > server running and that doesn't provide much failure protection.
> > > TIA
> > > Ernie
> > >
> > > "Mike Rosado [MSFT]" wrote:
> > >
> > > > Hi Ernie,
> > > >
> > > > As a test, I would use the NTBackup to do the System State Backup
and
> > then
> > > > check the Cluster Log to see if the same is there. If it is not,
then
> > it
> > > > is just something that NetBackup is logging.
> > > >
> > > > If the error still is there, you may be able to do one of a couple
> > things
> > > > to see if you can remove it. The first would be to add the Cluster
> > Account
> > > > with explicit control.
> > > >
> > > >
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vss/base/se
> > > > curity_considerations_for_requestors.asp
> > > >
> > > > Explicitly Controlling User Account Access to a Requestor
> > > >
> > > > There are cases where restricting access to a requestor to
processes
> > > > running as Local System, or under the local Administrators or local
> > Backup
> > > > Operators groups, may be too restrictive.
> > > >
> > > > For example, a given writer process (perhaps a third-party
non-system
> > > > writer) might not ordinarily need to be run under an Administrator
or
> > > > Backup Operator account. For security reasons, it would be best
not to
> > > > artificially promote the processes privileges to support VSS.
> > > >
> > > > In these cases, a secure registry location needs to be modified to
> > instruct
> > > > VSS that a given user is safe to run a VSS writer. The following
> > example
> > > > grants access to the "MyDomain\MyUser" account:
> > > >
> > > > HKEY_LOCAL_MACHINE
> > > > SYSTEM
> > > > CurrentControlSet
> > > > Services
> > > > VSS
> > > > VssAccessControl
> > > > MyDomain\MyUser = 1
> > > >
> > > > You would add the VssAccessControl key with the REG_DWORD value of
> > > > MyDomain\MyUser (the domain and Cluster account) and data of 1.
For
> > this
> > > > to take affect, you would
> > > > need to stop and start the Volume Shadow Copy Service if it is
already
> > > > running.
> > > >
> > > > The second thing we may want to do is go into the Component
Services
> > MMC
> > > > Snap-in and add the Cluster Account under the Default COM Security
> > > > permissions (Access and
> > > > Launch).
> > > >
> > > > 1. START button
> > > > 2. RUN menu
> > > > 3. Type in DCOMCNFG and press <ENTER>
> > > > 4. Go under the Component Services
> > > > 5. Go under the COMPUTERS
> > > > 6. Right mouse click on My Computer and choose PROPERTIES
> > > > 7. Go to the Default COM Security tab.
> > > > 8. Choose the Access Permissions button and add the Cluster Service
> > account
> > > > 9. Choose the Launch Permissions button and add the Cluster Service
> > account
> > > >
> > > > When doing this option, you must reboot the machine in order for
the
> > COM
> > > > Permissions to actually take effect.
> > > >
> > > > Let us know how this goes by posting back to the newsgroup.
> > > >
> > > > --------------------
> > > > Hope this helps,
> > > > Mike Rosado
> > > > Windows 2000 MCSE + MCDBA
> > > > Microsoft Enterprise Platform Support
> > > > Windows NT/2000/2003 Cluster Technologies
> > > >
> > > > ====================================================
> > > > When responding to posts, please "Reply to Group" via your
newsreader so
> > > > that others may learn and benefit from your issue.
> > > > ====================================================
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > > <http://www.microsoft.com/info/cpyright.htm>
> > > >
> > > > -----Original Message-----
> > > > --------------------
> > > > > Thread-Topic: ERR VSS: Got Component: Cluster Database
> > > > > thread-index: AcVW/W4x2flTq5lRSmKgNNKYxL79zA==
> > > > > X-WBNR-Posting-Host: 66.211.192.20
> > > > > From: "=?Utf-8?B?ZWJmZXJybw==?="
<ebferro@xxxxxxxxxxxxxxxxxxxxxxxxx>
> > > > > Subject: ERR VSS: Got Component: Cluster Database
> > > > > Date: Thu, 12 May 2005 07:18:12 -0700
> > > > > Lines: 13
> > > > > Message-ID: <21B2BFE0-0436-483C-B803-BA0485CE1FF0@xxxxxxxxxxxxx>
> > > > > MIME-Version: 1.0
> > > > > Content-Type: text/plain;
> > > > > charset="Utf-8"
> > > > > Content-Transfer-Encoding: 7bit
> > > > > X-Newsreader: Microsoft CDO for Windows 2000
> > > > > Content-Class: urn:content-classes:message
> > > > > Importance: normal
> > > > > Priority: normal
> > > > > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> > > > > Newsgroups: microsoft.public.windows.server.clustering
> > > > > NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> > > > > Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> > > > > Xref: TK2MSFTNGXA01.phx.gbl
> > > > microsoft.public.windows.server.clustering:6626
> > > > > X-Tomcat-NG: microsoft.public.windows.server.clustering
> > > > >
> > > > > I'm getting the following errors in the cluster log on one of the
> > nodes
> > > > of my
> > > > > cluster.
> > > > > 190:cac.04/28[04:30:01.424](067277) ERR VSS: Got Component:
> > 0x00269d10
> > > > > 190:cac.04/28[04:30:01.424](067277) ERR VSS: Got component:
Cluster
> > > > Database
> > > > >
> > > > > Should I be concerned about this? The same two errors seem to
occur
> > in
> > > > > pairs and since April 28th, those two errors have occurred 8
times.
> > The
> > > > > cluster seems to be running fine. There are no problems with it.

> > When I
> > > > > view the logs, this error is in red so it sticks out like a sore
> > thumb
> > > > but
> > > > > there appear to be no issues with that node or the cluster in
general.
> > > > >
> > > > > TIA
> > > > > Ernie
> > > > >
> > > >
> > > >
> > >
> >
> >
>

.

Loading