Friday, October 1, 2010

PCNS Event 6023,6025 Firewall Issue running on Windows 2008

When Running the PCNS (Password Change Notification service) with both Windows 2008 Domain Controller and ILM/FIM Synchronization Service server, allways remember to add a rule on the ILMFIM Synchronization Service server to allow inbound PCNS connections in (recommended) or disable the Firewall on the "Domain" Profile (not recommended.

If this is not in place, you will typically get the following event log errors on your DC's
Event ID 6023
(click on Image to enlarge)
Event ID 6025

(click on Image to enlarge)
On eventlog 6025 the typical eventlog data will look as follows

Log Name:      Application
Source:        PCNSSVC
Date:          2010/09/30 03:09:55 PM
Event ID:      6025
Task Category: (4)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DCname.domain.com
Description:
Password Change Notification Service received an RPC exception attempting to deliver a notification.
The password change notification target could not be contacted.
User Action:
The target server may not be running. Verify that the target server is running.
Additional Details:
Thread ID: 2804
Tracking ID: 9dd78d30-cda7-4163-96ec-04cb1312823b
User GUID: 82ed51a7-5c1c-4e9d-ac22-296db6190f5d
User: Domain\TestUser
Target: miisPCNS
Delivery Attempts: 42
Queued Notifications: 3
0x000006BA - The RPC server is unavailable.
ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 2
Status is 1722 - The RPC server is unavailable.
Detection location is 1710
Flags is 0
NumberOfParameters is 1
Long val: 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 18
Status is 1722 - The RPC server is unavailable.
Detection location is 1442
Flags is 0
NumberOfParameters is 1
Unicode string: ilmserver.domain.com
ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 18
Status is 1722 - The RPC server is unavailable.
Detection location is 323
Flags is 0
NumberOfParameters is 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 18
Status is 1237 - The operation could not be completed. A retry should be performed.
Detection location is 313
Flags is 0
NumberOfParameters is 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 18
Status is 10060 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Detection location is 311
Flags is 0
NumberOfParameters is 3
Long val: 49201
Pointer val: 0
Pointer val: 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 18
Status is 10060 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Detection location is 318
Flags is 0
NumberOfParameters is 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:34:54
Generating component is 18
Status is 1237 - The operation could not be completed. A retry should be performed.
Detection location is 313
Flags is 0
NumberOfParameters is 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:34:54
Generating component is 18
Status is 10060 - A connection attempt failed because the connected party did not properly respond after a period of time, or established con
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="PCNSSVC" />
    <EventID Qualifiers="49152">6025</EventID>
    <Level>2</Level>
    <Task>4</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-09-30T13:09:55.000Z" />
    <EventRecordID>224531</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DCname.domain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>2804</Data>
    <Data>9dd78d30-cda7-4163-96ec-04cb1312823b</Data>
    <Data>82ed51a7-5c1c-4e9d-ac22-296db6190f5d</Data>
    <Data>domain\TestUser</Data>
    <Data>miisPCNS</Data>
    <Data>42</Data>
    <Data>3</Data>
    <Data>0x000006BA</Data>
    <Data>The RPC server is unavailable.
</Data>
    <Data>ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 2
Status is 1722 - The RPC server is unavailable.
Detection location is 1710
Flags is 0
NumberOfParameters is 1
Long val: 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 18
Status is 1722 - The RPC server is unavailable.
Detection location is 1442
Flags is 0
NumberOfParameters is 1
Unicode string: ilmserver.domain.com
ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 18
Status is 1722 - The RPC server is unavailable.
Detection location is 323
Flags is 0
NumberOfParameters is 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 18
Status is 1237 - The operation could not be completed. A retry should be performed.
Detection location is 313
Flags is 0
NumberOfParameters is 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 18
Status is 10060 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Detection location is 311
Flags is 0
NumberOfParameters is 3
Long val: 49201
Pointer val: 0
Pointer val: 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:55:89
Generating component is 18
Status is 10060 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Detection location is 318
Flags is 0
NumberOfParameters is 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:34:54
Generating component is 18
Status is 1237 - The operation could not be completed. A retry should be performed.
Detection location is 313
Flags is 0
NumberOfParameters is 0
ProcessID is 2764
System Time is: 9/30/2010 13:9:34:54
Generating component is 18
Status is 10060 - A connection attempt failed because the connected party did not properly respond after a period of time, or established con</Data>
<Data>
The password change notification target could not be contacted.
User Action:
The target server may not be running. Verify that the target server is running.
Additional Details:
</Data>
  </EventData>
</Event>
Posted by at
Labels: , ,

1 comment:

  1. AnonymousJuly 23, 2019 at 6:13 AM

    Are you facing error while accessing the Bitcoin exchange account in Blockchain? Do you know where you can get trustworthy and accessible remedies related to the same account? If no, there is no need to get frenzy in Blockchain. You can approach the Blockchain professionals by dialing Blockchain customer service number who have hand in eliminating the errors and provide remarkable solutions to the users. Just grab the opportunity to tackle all the errors of Blockchain in an errorless manner. The service team is like a blessing for customers who have less information about it and unable to handle the attacks or errors occur in the Bitcoin exchange.

    ReplyDelete

Subscribe to: Post Comments (Atom)