Re: Event ID 1053

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I'm not worried about the clustering actually. I just want to eliminate the
1053 error message on startup.

Thanks

"Meinolf Weber" wrote:

Hello Tony,

To get the cluster run properly enable again the heartbeat. Please post an
unedited ipconfig /all from both cluster nodes and the DNS server. Also think
about posting to: microsoft.public.windows.server.clustering

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

I have a new server (actually two identical servers) that are
receiving an Event ID 1053 error message on boot.

The error says:

Windows cannot determine the user or computer name. (The specified
domain either does not exist or could not be contacted. ). Group
Policy processing aborted.

I can successfully run gpupdate /force from a command line. I also
see in the log that policies are being successfully applied later.
This seems to be only during boot. I've tried several things thinking
that it might be trying to establish communication before the NIC team
is ready.

I have disabled another NIC on a different network (this machine is
intended to be a cluster and I had the other interface configured as
the heartbeat connection). The only interface left is the team. I
have also applied the "wait for network" group policy and applied the
reg key from kb202840 among a number of other things while
troubleshooting this.

I can connect to \\mydomain\sysvol\mydomain successfully.

I have worked through an issue in DNS where for some unkown reason it
was querying an incorrect DNS though ipconfig showed it to be
configured correctly. DNS is now resolving correctly and the DNS
entry for the server is showing up correctly after removing it from
the domain and rejoining it. In addition, watching the network
traffic no longer shows the errant query.

This is just a pesky startup error that makes me hesitant to put
product clustered resources on the box (es).

I appreciate any suggestions.

Thanks




.

Relevant Pages

  • Re: Problem with multihomed 2-node w2003 DC
    ... "Cluster name" of course depends on cluster IP. ... "Meinolf Weber" wrote: ... DNS that occurs after fail-over is performed to the cluster. ... MyClusterName 192.168.2. ...
    (microsoft.public.windows.server.dns)
  • Re: Enable Full-Text Search
    ... I have the SPS search working without a problem. ... But when I got to enable full text search the error message I get is ERROR: ... a SQL cluster but it is a fail over. ... agents point another duplicate SQL server with the same name and IP address. ...
    (microsoft.public.sharepoint.windowsservices)
  • MS Search
    ... We have problem on our 2 original sql instances in a 4-node cluster. ... Both the 2 old instances get one warning and one error message in the ... The Gatherer property mapping file cannot be opened. ... An error occured during the online operation for instance <SQL Server ...
    (microsoft.public.sqlserver.clustering)
  • Re: sql server installation on cluster failing
    ... I'm trying to install sql server 2000 on windows 2003 SP1 and getting ... below error message. ... Do you actually have the MSCS cluster setup along with the necessary IP ... installation went well and no error messages this time. ...
    (microsoft.public.sqlserver.clustering)
  • SQL 2005 Cluster install error "The drive specified cannot be used for program location"
    ... NetApp-Storage (Cluster is up and running), setup fails with the following ... Note that KB913815 states a similar error message with possible valid ... Both nodes have identical C: and D: local drives with administrative shares, ...
    (microsoft.public.sqlserver.clustering)