| Author |
Message |
PaulSe
Guest
|
 Posted:
Thu Oct 13, 2005 8:50 pm Post subject:
Cluster IP address resource could not create required TCP/IP |
|
|
We have a Windows Server 2003 EE cluster and we are receiving event 1045 and
event 1069 when we try to move any IP address resource from the 'A' node to
the 'B' node.
--------------------------------------------------------------------------------------------
Event Type: Error
Event Source: ClusSvc
Event Category: IP Address Resource
Event ID: 1045
Date: 10/13/2005
Time: 2:34:45 PM
User: N/A
Computer: HOSTB
Description:
Cluster IP Address resource 'xxx IP' could not create the required TCP/IP
interface.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 00 07 80
---------------------------------------------------------------------------------------------
We have confirmed that IP connectivity from the B node and that the netmask
on the IP resource and the IP adapter are the same. Heartbeat is on a
separate subnet and is working properly. We have tried resetting IP using
'netsh' and installed the latest NIC drivers. We increased logging level for
cluster.log to 3 and the following messages are listed:
00000814.00000b40::2005/10/13-18:34:45.115 ERR [ClNet]
INetConnectionManager_EnumConnections failed, status 80070005
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx IP>: Unable
to create new IP interface, status 2147942405
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx IP>: Failed
to created new IP interface, status 2147942405.
Found a similar post in this forum from August 2005, but there was no
resolution listed. We've reviewed KB811876 and it does not appear to apply.
Any thoughts? |
|
| Back to top |
|
 |
Chuck Timon [MSFT]
Guest
|
| Posted:
Mon Oct 17, 2005 4:50 pm Post subject:
Re: Cluster IP address resource could not create required TC |
|
|
You need to ensure DCOM is enabled on the server.
--
Chuck Timon, Jr.
Microsoft Corporation
CCS Beta Engineer
This posting is provided "AS IS" with no
warranties, and confers no rights.
"PaulSe" <PaulSe@discussions.microsoft.com> wrote in message
news:A0FD1C78-A68D-47E2-B5E1-DEB52A302C45@microsoft.com...
| Quote: | We have a Windows Server 2003 EE cluster and we are receiving event 1045
and
event 1069 when we try to move any IP address resource from the 'A' node
to
the 'B' node.
--------------------------------------------------------------------------------------------
Event Type: Error
Event Source: ClusSvc
Event Category: IP Address Resource
Event ID: 1045
Date: 10/13/2005
Time: 2:34:45 PM
User: N/A
Computer: HOSTB
Description:
Cluster IP Address resource 'xxx IP' could not create the required TCP/IP
interface.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 00 07 80
---------------------------------------------------------------------------------------------
We have confirmed that IP connectivity from the B node and that the
netmask
on the IP resource and the IP adapter are the same. Heartbeat is on a
separate subnet and is working properly. We have tried resetting IP using
'netsh' and installed the latest NIC drivers. We increased logging level
for
cluster.log to 3 and the following messages are listed:
00000814.00000b40::2005/10/13-18:34:45.115 ERR [ClNet]
INetConnectionManager_EnumConnections failed, status 80070005
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx IP>:
Unable
to create new IP interface, status 2147942405
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx IP>:
Failed
to created new IP interface, status 2147942405.
Found a similar post in this forum from August 2005, but there was no
resolution listed. We've reviewed KB811876 and it does not appear to
apply.
Any thoughts? |
|
|
| Back to top |
|
|
PaulSe
Guest
|
| Posted:
Tue Oct 18, 2005 8:50 pm Post subject:
Re: Cluster IP address resource could not create required TC |
|
|
Is there a specific component under DCOM that should be active? I can
compare from node A to node B but is there a specific entry that I should
focus on?
Thanks.
"Chuck Timon [MSFT]" wrote:
| Quote: | You need to ensure DCOM is enabled on the server.
--
Chuck Timon, Jr.
Microsoft Corporation
CCS Beta Engineer
This posting is provided "AS IS" with no
warranties, and confers no rights.
"PaulSe" <PaulSe@discussions.microsoft.com> wrote in message
news:A0FD1C78-A68D-47E2-B5E1-DEB52A302C45@microsoft.com...
We have a Windows Server 2003 EE cluster and we are receiving event 1045
and
event 1069 when we try to move any IP address resource from the 'A' node
to
the 'B' node.
--------------------------------------------------------------------------------------------
Event Type: Error
Event Source: ClusSvc
Event Category: IP Address Resource
Event ID: 1045
Date: 10/13/2005
Time: 2:34:45 PM
User: N/A
Computer: HOSTB
Description:
Cluster IP Address resource 'xxx IP' could not create the required TCP/IP
interface.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 00 07 80
---------------------------------------------------------------------------------------------
We have confirmed that IP connectivity from the B node and that the
netmask
on the IP resource and the IP adapter are the same. Heartbeat is on a
separate subnet and is working properly. We have tried resetting IP using
'netsh' and installed the latest NIC drivers. We increased logging level
for
cluster.log to 3 and the following messages are listed:
00000814.00000b40::2005/10/13-18:34:45.115 ERR [ClNet]
INetConnectionManager_EnumConnections failed, status 80070005
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx IP>:
Unable
to create new IP interface, status 2147942405
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx IP>:
Failed
to created new IP interface, status 2147942405.
Found a similar post in this forum from August 2005, but there was no
resolution listed. We've reviewed KB811876 and it does not appear to
apply.
Any thoughts?
|
|
|
| Back to top |
|
|
Chuck Timon [MSFT]
Guest
|
| Posted:
Wed Oct 19, 2005 8:50 pm Post subject:
Re: Cluster IP address resource could not create required TC |
|
|
Nope, just need to make sure DCOM is enabled.
--
Chuck Timon, Jr.
Microsoft Corporation
CCS Beta Engineer
This posting is provided "AS IS" with no
warranties, and confers no rights.
"PaulSe" <PaulSe@discussions.microsoft.com> wrote in message
news:6DE75FF2-ABBE-4CBE-A514-26C6BCECFA29@microsoft.com...
| Quote: | Is there a specific component under DCOM that should be active? I can
compare from node A to node B but is there a specific entry that I should
focus on?
Thanks.
"Chuck Timon [MSFT]" wrote:
You need to ensure DCOM is enabled on the server.
--
Chuck Timon, Jr.
Microsoft Corporation
CCS Beta Engineer
This posting is provided "AS IS" with no
warranties, and confers no rights.
"PaulSe" <PaulSe@discussions.microsoft.com> wrote in message
news:A0FD1C78-A68D-47E2-B5E1-DEB52A302C45@microsoft.com...
We have a Windows Server 2003 EE cluster and we are receiving event
1045
and
event 1069 when we try to move any IP address resource from the 'A'
node
to
the 'B' node.
--------------------------------------------------------------------------------------------
Event Type: Error
Event Source: ClusSvc
Event Category: IP Address Resource
Event ID: 1045
Date: 10/13/2005
Time: 2:34:45 PM
User: N/A
Computer: HOSTB
Description:
Cluster IP Address resource 'xxx IP' could not create the required
TCP/IP
interface.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 00 07 80
---------------------------------------------------------------------------------------------
We have confirmed that IP connectivity from the B node and that the
netmask
on the IP resource and the IP adapter are the same. Heartbeat is on a
separate subnet and is working properly. We have tried resetting IP
using
'netsh' and installed the latest NIC drivers. We increased logging
level
for
cluster.log to 3 and the following messages are listed:
00000814.00000b40::2005/10/13-18:34:45.115 ERR [ClNet]
INetConnectionManager_EnumConnections failed, status 80070005
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx IP>:
Unable
to create new IP interface, status 2147942405
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx IP>:
Failed
to created new IP interface, status 2147942405.
Found a similar post in this forum from August 2005, but there was no
resolution listed. We've reviewed KB811876 and it does not appear to
apply.
Any thoughts?
|
|
|
| Back to top |
|
|
PaulSe
Guest
|
| Posted:
Thu Oct 20, 2005 12:50 pm Post subject:
Re: Cluster IP address resource could not create required TC |
|
|
Ok, it is already enabled on both nodes. Also, the odd part is that this was
working after it was initially installed and has since started to not work.
Nothing has changed on the server, we cannot find any duplicate IP addresses.
We have re-checked all of the network adapter settings, including the
netmask, and they check out. Powering everything down and back up again has
not helped.
"Chuck Timon [MSFT]" wrote:
| Quote: | Nope, just need to make sure DCOM is enabled.
--
Chuck Timon, Jr.
Microsoft Corporation
CCS Beta Engineer
This posting is provided "AS IS" with no
warranties, and confers no rights.
"PaulSe" <PaulSe@discussions.microsoft.com> wrote in message
news:6DE75FF2-ABBE-4CBE-A514-26C6BCECFA29@microsoft.com...
Is there a specific component under DCOM that should be active? I can
compare from node A to node B but is there a specific entry that I should
focus on?
Thanks.
"Chuck Timon [MSFT]" wrote:
You need to ensure DCOM is enabled on the server.
--
Chuck Timon, Jr.
Microsoft Corporation
CCS Beta Engineer
This posting is provided "AS IS" with no
warranties, and confers no rights.
"PaulSe" <PaulSe@discussions.microsoft.com> wrote in message
news:A0FD1C78-A68D-47E2-B5E1-DEB52A302C45@microsoft.com...
We have a Windows Server 2003 EE cluster and we are receiving event
1045
and
event 1069 when we try to move any IP address resource from the 'A'
node
to
the 'B' node.
--------------------------------------------------------------------------------------------
Event Type: Error
Event Source: ClusSvc
Event Category: IP Address Resource
Event ID: 1045
Date: 10/13/2005
Time: 2:34:45 PM
User: N/A
Computer: HOSTB
Description:
Cluster IP Address resource 'xxx IP' could not create the required
TCP/IP
interface.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 00 07 80
---------------------------------------------------------------------------------------------
We have confirmed that IP connectivity from the B node and that the
netmask
on the IP resource and the IP adapter are the same. Heartbeat is on a
separate subnet and is working properly. We have tried resetting IP
using
'netsh' and installed the latest NIC drivers. We increased logging
level
for
cluster.log to 3 and the following messages are listed:
00000814.00000b40::2005/10/13-18:34:45.115 ERR [ClNet]
INetConnectionManager_EnumConnections failed, status 80070005
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx IP>:
Unable
to create new IP interface, status 2147942405
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx IP>:
Failed
to created new IP interface, status 2147942405.
Found a similar post in this forum from August 2005, but there was no
resolution listed. We've reviewed KB811876 and it does not appear to
apply.
Any thoughts?
|
|
|
| Back to top |
|
|
John Toner [MVP]
Guest
|
| Posted:
Fri Oct 21, 2005 4:50 pm Post subject:
Re: Cluster IP address resource could not create required TC |
|
|
The error messages all point to "access is denied" so you might want to
review the security settings for the cluster service account and check your
group policies to make sure that they aren't causing the problem.
Review the following KB article for a listing of the permissions that the
cluster service account should have on each node:
http://support.microsoft.com/kb/269229
Regards,
John
"PaulSe" <PaulSe@discussions.microsoft.com> wrote in message
news:BB9B52BF-3EA0-4FB9-8153-8D6DC527CAD4@microsoft.com...
| Quote: | Ok, it is already enabled on both nodes. Also, the odd part is that this
was
working after it was initially installed and has since started to not
work.
Nothing has changed on the server, we cannot find any duplicate IP
addresses.
We have re-checked all of the network adapter settings, including the
netmask, and they check out. Powering everything down and back up again
has
not helped.
"Chuck Timon [MSFT]" wrote:
Nope, just need to make sure DCOM is enabled.
--
Chuck Timon, Jr.
Microsoft Corporation
CCS Beta Engineer
This posting is provided "AS IS" with no
warranties, and confers no rights.
"PaulSe" <PaulSe@discussions.microsoft.com> wrote in message
news:6DE75FF2-ABBE-4CBE-A514-26C6BCECFA29@microsoft.com...
Is there a specific component under DCOM that should be active? I can
compare from node A to node B but is there a specific entry that I
should
focus on?
Thanks.
"Chuck Timon [MSFT]" wrote:
You need to ensure DCOM is enabled on the server.
--
Chuck Timon, Jr.
Microsoft Corporation
CCS Beta Engineer
This posting is provided "AS IS" with no
warranties, and confers no rights.
"PaulSe" <PaulSe@discussions.microsoft.com> wrote in message
news:A0FD1C78-A68D-47E2-B5E1-DEB52A302C45@microsoft.com...
We have a Windows Server 2003 EE cluster and we are receiving event
1045
and
event 1069 when we try to move any IP address resource from the 'A'
node
to
the 'B' node.
--------------------------------------------------------------------------
------------------
Event Type: Error
Event Source: ClusSvc
Event Category: IP Address Resource
Event ID: 1045
Date: 10/13/2005
Time: 2:34:45 PM
User: N/A
Computer: HOSTB
Description:
Cluster IP Address resource 'xxx IP' could not create the required
TCP/IP
interface.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 00 07 80
--------------------------------------------------------------------------
-------------------
We have confirmed that IP connectivity from the B node and that the
netmask
on the IP resource and the IP adapter are the same. Heartbeat is
on a
separate subnet and is working properly. We have tried resetting
IP
using
'netsh' and installed the latest NIC drivers. We increased logging
level
for
cluster.log to 3 and the following messages are listed:
00000814.00000b40::2005/10/13-18:34:45.115 ERR [ClNet]
INetConnectionManager_EnumConnections failed, status 80070005
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx
IP>:
Unable
to create new IP interface, status 2147942405
00000814.00000b40::2005/10/13-18:34:45.115 ERR IP Address <xxx
IP>:
Failed
to created new IP interface, status 2147942405.
Found a similar post in this forum from August 2005, but there was
no
resolution listed. We've reviewed KB811876 and it does not appear
to
apply.
Any thoughts?
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in