Network name problem
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Network name problem

 
Post new topic   Reply to topic    Windows Server Forum Index -> Clustering
Author Message
Guest






Posted: Thu Oct 20, 2005 12:50 pm    Post subject: Network name problem Reply with quote

Hi
I've been getting this error message produced by Checkpoint Manager in
the system event log on one clustered server (win2003,sp1) with two
nodes:

"Cluster service failed to restore a registry key for resource Cluster
Name when it was brought online. This error code was 3. Some changes
may be lost."

There are three cluster groups and each of them has a network name.
This behaviour occurs for every network name.
When I try to bring up a cluster resource of Network Name type, it
takes about 1 minute to become online (unusually long), and after that
it works OK, but the message mentioned above is produced. I've seen
similar posts about MSDTC, but I don't have problems with it. This one
is about Network names.

Could anyone help?
Back to top
Chuck Timon [MSFT]
Guest





Posted: Thu Oct 20, 2005 8:50 pm    Post subject: Re: Network name problem Reply with quote

Could be an issue if you have set "Require Kerberos" for the network name
resource. Also, if you have set "Require DNS" on the network name it would
take longer to come online.

--
Chuck Timon, Jr.
Microsoft Corporation
CCS Beta Engineer
This posting is provided "AS IS" with no
warranties, and confers no rights.
<sinisalucin@gmail.com> wrote in message
news:1129798317.756840.159370@g44g2000cwa.googlegroups.com...
Quote:
Hi
I've been getting this error message produced by Checkpoint Manager in
the system event log on one clustered server (win2003,sp1) with two
nodes:

"Cluster service failed to restore a registry key for resource Cluster
Name when it was brought online. This error code was 3. Some changes
may be lost."

There are three cluster groups and each of them has a network name.
This behaviour occurs for every network name.
When I try to bring up a cluster resource of Network Name type, it
takes about 1 minute to become online (unusually long), and after that
it works OK, but the message mentioned above is produced. I've seen
similar posts about MSDTC, but I don't have problems with it. This one
is about Network names.

Could anyone help?
Back to top
Guest






Posted: Fri Oct 21, 2005 12:50 pm    Post subject: Re: Network name problem Reply with quote

Thanks Chuck,
I'll give it a go and see what happens.

Regards

Sinisa Lucin
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Clustering All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB