HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- DC replication fails after upgrade to newer PSP
Server Management - Systems Insight Manager
1832651
Members
2925
Online
110043
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2009 01:50 AM
12-09-2009 01:50 AM
DC replication fails after upgrade to newer PSP
We are experiencing problems when upgrading one of our Domain Controllers to PSP 8.25.
The current installed PSP on the DC is 8.15.
This week we tried to update the PSP for the 2nd time, and after the server rebooted we had the same problem:
No NTDS replication between the DC's and the following event is logged.
Event ID 1053 Source UserEnv.
Windows cannot determine the user or computer name. (There are no more endpoints available from the endpoint mapper. ). Group Policy processing aborted.
So one of the drivers in the PSP must be causing this I guess. Could it be that port 135 is being blocked by, for example, the NIC driver?
The other DC was succesfully upgraded to PSP 8.25.
I can't work out yet what to look for.
Any help will be appreciated :)
The current installed PSP on the DC is 8.15.
This week we tried to update the PSP for the 2nd time, and after the server rebooted we had the same problem:
No NTDS replication between the DC's and the following event is logged.
Event ID 1053 Source UserEnv.
Windows cannot determine the user or computer name. (There are no more endpoints available from the endpoint mapper. ). Group Policy processing aborted.
So one of the drivers in the PSP must be causing this I guess. Could it be that port 135 is being blocked by, for example, the NIC driver?
The other DC was succesfully upgraded to PSP 8.25.
I can't work out yet what to look for.
Any help will be appreciated :)
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2009 07:29 AM
12-10-2009 07:29 AM
Re: DC replication fails after upgrade to newer PSP
Are you using NIC teaming? It can cause problems sometimes. Maybe the PSP updated the NIC drivers and broke something with the NIC teaming. Either try breaking the team or downgrade the NIC driver back to the old version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2009 01:21 AM
12-15-2009 01:21 AM
Re: DC replication fails after upgrade to newer PSP
Yes, we are using teaming.
And together with the problem I mensioned above, the following event was logged many times:
Faulting application wmiprvse.exe, version 5.2.3790.3959, faulting module HPWinHostedEthernetTeam.dll, version 2.2.1.0, fault address 0x00005e70.
I'm sure this could be also the reason the Endpoint mapper problems arose.
And together with the problem I mensioned above, the following event was logged many times:
Faulting application wmiprvse.exe, version 5.2.3790.3959, faulting module HPWinHostedEthernetTeam.dll, version 2.2.1.0, fault address 0x00005e70.
I'm sure this could be also the reason the Endpoint mapper problems arose.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP