Event for payment grouping

Dear all,
In which event in we can able change the value of field 'PYGRP' payment grouping in the table dfkkop in invoicing process. I have worked on event 600 but it doesn't make sense to our requirement.
Susmita
Edited by: susmitha harini on Sep 10, 2010 8:03 AM
Edited by: susmitha harini on Sep 10, 2010 8:05 AM

Dear susmitha,
Not sure what the requirement is but I would advise you to review note 568966 especially item 6 & 8:
6. Payment group (DFKKOP-PYGRP)
This is a freely selectable grouping field with 10 places that can be set during the posting/changing of a document. Thus items with different contents in this field are paid separately; items with the same contents in this field can be paid together if all other conditions mentioned here are also fulfilled. In certain cases the system sets the payment group within the program in order to group items together that were announced together or assigned together. For that purpose special payment groups, which start with special characters "/" and "&", are used.
8. Payment group (PAYGR) from event 0600
This is a freely selectable field with 50 places that can be set at event 0600. A typical application is a logic for which the payment group is equal to the contract number if "Individual payment" is selected in the contract.
regards,
David

Similar Messages

Payment group

Hi All,
What is the transaction code for Payment group of the company code?
Regards,
Swetha

Hello,
If you were talking about Payment grouping, please check the SAP note 305414. This is a consulting note explaining
the grouping of payment in the automatic payment program.
REgards,
REnan

The payment group could not be authorized for payment:

Hi All,
I am facing one issue when ever I try to submit the order.Mention issues log below.
at java.lang.Thread.run(Thread.java:619)
17:30:09,608 INFO [CommitOrderFormHandler] DEBUG Acquired local write lock using id 140023
17:30:09,631 INFO [CommitOrderFormHandler] DEBUG beforeSet created transaction TransactionImple < ac, BasicAction: -53edde10:dc90:51a34807:1077 status: ActionStatus.RUNNING >
17:30:09,632 INFO [CommitOrderFormHandler] DEBUG no form errors - staying on same page.
17:30:09,635 INFO [CommitOrderFormHandler] DEBUG no form errors - staying on same page.
17:30:09,637 INFO [CommitOrderFormHandler] DEBUG no form errors - staying on same page.
17:30:09,720 WARN [ValidatePaymentGroupByType] Returning default transition value 0 for unregistered property value cashOnDelivery.
17:30:09,763 INFO [CommitOrderFormHandler] DEBUG PipelineError: key=FailedPaymentGroupAuth:pg50002; error=The payment group pg50002 could not be authorized for payment: The given PaymentGroup {0} cannot be processed because a processor was not configured for its type..
17:30:09,763 INFO [CommitOrderFormHandler] DEBUG adding form exception: FailedPaymentGroupAuth:pg50002: The payment group pg50002 could not be authorized for payment: The given PaymentGroup {0} cannot be processed because a processor was not configured for its type..
17:30:09,764 INFO [CommitOrderFormHandler] DEBUG root cause of exception: null
17:30:09,764 INFO [CommitOrderFormHandler] DEBUG Transaction Marked as Rollback - redirecting to: error.jsp
17:30:09,765 INFO [CommitOrderFormHandler] DEBUG afterSet sees currentTransaction as TransactionImple < ac, BasicAction: -53edde10:dc90:51a34807:1077 status: ActionStatus.ABORT_ONLY >
17:30:09,765 INFO [CommitOrderFormHandler] DEBUG afterSet committing transaction TransactionImple < ac, BasicAction: -53edde10:dc90:51a34807:1077 status: ActionStatus.ABORT_ONLY >
17:30:09,766 INFO [CommitOrderFormHandler] DEBUG Released local write lock using id 140023
Could you please give suggestion how to resolve this issue.
Thanks,
Raj

It seems like you have created a new payment group cashOnDelivery but have not configured the required property files required for its validation
1) In /atg/commerce/order/processor/ValidatePaymentGroupByType.properties add something as following
# Add a return code for your cash payment method
returnValues+=\
cashOnDelivery=5051
2) then in CommercePipeline.xml add the mapping for the integer value specified earlier to its validator processor, something as following
<pipelinechain name="validatePaymentGroup" transaction="TX_REQUIRED" headlink="dispatchOnPGType" xml-combine="append">
<pipelinelink name="dispatchOnPGType" transaction="TX_MANDATORY">
<processor jndi="/atg/commerce/order/processor/ValidatePaymentGroupByType"/>
<transition link="validateCashPG" returnvalue="5051"/>
</pipelinelink>
<pipelinelink name="validateCashPG" transaction="TX_MANDATORY">
<processor jndi="/atg/commerce/order/processor/ValidateCash"/>
</pipelinelink>
</pipelinechain>
3) Create a new ValidateCash component and its class(which implements a pipeline processor) and in this simply return the SUCCESS code, or put any validation logic that you want to put for validating your new cash paymentGroup.
This would solve the the current error you are getting,
and If the PaymentManager, PaymentPipeline(The new createCahInfo and ProcessCash processor etc),OrderTools component etc have been confgiured properly for your new payment group then you should be able to submit the order.
Thanks

F110 -Too many payment mediums created for this payment group

Hello Gurus,
Am getting below error after executing payment run F110.
BFIBL02160 Too many payment mediums created for this payment group
BFIBL02616 End of log for payment run 20140409 / DPA04 , PE1 / 500
We are not able to see the Payment advice note in the spool request.
Can you please share your ideas to resolve the issue
Thanks in advacne

HI,
Please let us know for account like vendor , customer you running the payment advice.
check if the customer ,vendor document is posted or not.
which customer, vendor number you had maintained in the f110 .
check that before you run it.
else.. create new document and start run the payment.
for single document fi you try more than once it will give the above error.
and also the check the program and variant as well.
let me know any corrections.
thanks.

DMEE error (Error Log - Too many payment mediums created for this payment group)

Hi Experts,
Please see the below error while generating the DMEE file.
Error Log - Too many payment mediums created for this payment group
Error is - Too many payment mediums created for this payment group
Please explain how to resolve this error.Send detail documentation how to rectify this error
Regards
Sreedhar

Hi Nimish Agarwal,
With reference to the error faced i.e. BFIBL02160 "too many payment
mediums created for this payment group", please review the information
provided in the long text of this error in detail.
Please ensure that the orders are not carried out several times.
Alternatively you can apply the optional usable message 166 (same
class: BFIBL02), so that you can prevent creating duplicates in future.
Please customize this message as an error so as to prevent the system
from creating duplicate files. You can customize this message in OBA5.
The message BFIBL02 160 always occurs, if you create more than one
file for the same payment run, in order to warn you not to send the
same file twice to the bank.
The SAPFPAYM program does not create 2 files at once. But if you
run this program more than once for the same payment run, more than
one file is created. From the second run on you receive the error
message BFIBL02 160. You can easily test it, by creating a new
payment proposal and creating a new file with this proposal and
SAPFPAYM. The first time you run this program you will not receive
the message.
Hope this clarifies.
Kind Regards,
Fernando Evangelista

Error Log - Too many payment mediums created for this payment group

Hi Experts,
When I am doing payment to customers through T-code F110, I am able to clear the open item. But when we are executing the Payment medium - DME Administration, generate the Payment Advice and when we see the print preview of the Payment Advice in spool request, System is showing the following errors,
"BFIBL02160 Too many payment mediums created for this payment group"
"BFIBL02616 End of log for payment run 20120123 / NAA02 , NSD / 200"
"This is line 1/column 45 on page 1"
Message no. SP01R116
Kindly help how to rectify the same
Thanks in advance
Regards,
Nimish Agarwal

Hi Nimish Agarwal,
With reference to the error faced i.e. BFIBL02160 "too many payment
mediums created for this payment group", please review the information
provided in the long text of this error in detail.
Please ensure that the orders are not carried out several times.
Alternatively you can apply the optional usable message 166 (same
class: BFIBL02), so that you can prevent creating duplicates in future.
Please customize this message as an error so as to prevent the system
from creating duplicate files. You can customize this message in OBA5.
The message BFIBL02 160 always occurs, if you create more than one
file for the same payment run, in order to warn you not to send the
same file twice to the bank.
The SAPFPAYM program does not create 2 files at once. But if you
run this program more than once for the same payment run, more than
one file is created. From the second run on you receive the error
message BFIBL02 160. You can easily test it, by creating a new
payment proposal and creating a new file with this proposal and
SAPFPAYM. The first time you run this program you will not receive
the message.
Hope this clarifies.
Kind Regards,
Fernando Evangelista

JAEHYLEE , Calling Create_Accounting_Entry for PAYMENT EVENT에서 에러가 날때

PURPOSE
Calling Create_Accounting_Entry for PAYMENT EVENT에서 에러가 날때
Workaround
N/A
Solution Description
Symptoms
Debug Logfile of the Payables Accounting Process shows the following error :
Calling Create_Accounting_Entry for PAYMENT EVENT (ID = XXXXX) ...
Inside AP_Accounting_Main_Pkg package.
About to account for Payment Event (ID = XXXXX) for SOB ID XX ...
Inside Execute for Payment_Event_Core
Cannot Account for XXX bank account's check number XXX because some Invoice that it pays, is NOT accounted.
AE Line Accounted Status = CANNOT ACCOUNT FOR THIS EVENT
Cause
Invoice Event for the above Payment is already accounted but POSTED_FLAG is 'N' for invoice distribution lines.
Fix
Try the following fix in TEST instance first after taking a backup of the table, AP_INVOICE_DISTRIBUTIONS_ALL and AP_ACCOUNTING_EVENTS_ALL
update AP_INVOICE_DISTRIBUTIONS_ALL
set POSTED_FLAG = 'Y'
where INVOICE_DISTRIBUTION_ID in (Enter Invoice_Distribution_Id) ;
update AP_ACCOUNTING_EVENTS_ALL
set CANNOT_ACCOUNT_FLAG = null
where ACCOUNTING_EVENT_ID = Enter Event_Id for Invoice Event;
Ensure that the above scripts update correct number of rows.
Reference Documents
292102.1

Hi Abeer,
If the first payment was not accounted, then voided, the clearing that cannot account is most likely for the same check. Typically we would approach this in support by looking at the accounting that is created by the Payables Accounting Process and reports. It should show an error for the payment, but that lets us know if the problem with accounting the original payment and payment void events are due to an invalid account or an unbalanced accounting issue.
There is no way to get the accounting on the clearing event to work because it needs the actual numbers generated by the payment accounting to calculate the correct accounting.
A workaround of setting the payment and payment void to posted status sometimes works because those events net to $0. Without an actual amount to post to GL, we can do that.
In support, I would ask you to generate what we call an "aplist" or Invoice Data Collector script for one of the invoices paid by the payment and payment clearing that are not successful. That helps determine the best fix for the issue. We really need to find out if there is an error for that first payment event. Also, I'm assuming that the payment clearing that you created was for the first payment, and that you have uncleared it as well.
The accounting should be done in the following order:
Payment Event
Payment Clearing
Payment Unclearing
Payment Void
Check the dates on each event (in ap_ae_headers_all) to determine if you do indeed have four unposted events, and that they are in the correct payment order.
Cheryl Riniker, Oracle

Event for the remaining balance after payment posting

Hi,
I am looking for the event which will trigger after making the payment on account ( through any kind of payment source ) if the balance is 0 I need to trigger some process.
Could you please help
Thanks,
Kiran

Event which will trigger after making the payment on account
Following are the events which you can try :
111 : Clearing: Structure for Posting on Account
113 : Clearing: Transaction for Payment on Account
Cheers ,
Dewang

Payment Block Validation for User group

Dear SAP Validation Expert,
We like to allow only selected FI users to change Payment Block to ' ' (Free for Payment) in tcode: FB02, FB03 and FBL1N.
Curently we have managed to block other un-selected users from changing the Payemnt block to Free for Payment.
But our issues are Other fields also NOT able from changing/maintaining. For example in FB02, user NOT able to change Payment Block (BSEG-ZLSPR) from 'B' to ' ' (Free for Payment) which is expected but user also NOT able to maintain other field such as Payment term(BSEG-ZTERM), Baseline date (BSEG-ZFBDT), Assignment (BSEG-ZUONR) and Text Field(BSEG-SGTXT).
Below is our Validation, please advice how to improve it so that other fields can be changed too. Your swift reply is very much appreciated.
Pre-requisite:
( ( SYST-TCODE = 'FB02' ) OR
( SYST-TCODE = 'FBL1N' ) OR
( SYST-TCODE = 'FB03' ) AND
( BSEG-ZLSPR = ' ' ) AND
SYST-UNAME <> 'HIS20083'
Check:
BSEG-ZLSPR <> ' '
Message: E: You have no authorization.

Hi,
In your Validation small change has to be done.
Pre-requisite:
SYST-TCODE = 'FB02' ) OR ( SYST-TCODE = 'FBL1N' ) OR ( SYST-TCODE = 'FB03' )
Check:
SYST-UNAME 'HIS20083' AND BSEG-ZLSPR = ' '
Message: E: You have no authorization.
Try in the above procedure.
Thanks
Goutam

Workflow WS00400012 Release for Payment not getting triggred

Hi,
As mentioned in the help docs we have done the following settings for Release for payment, yet the Workflow is not getting triggered.
SPRO->Financial Accounting (New)->Accounts Receivable and Accounts Payable->Business Transactions->Release for Payment
Create Workflow Variant for Release for Payment
XX01     WS004MSBT Payment release
     Workflow var.   XX01
     Currency        INR
     WF var.name     WS004MSBT Payment release
     Prelimenary posting release
      Release from    1.00
      Subworkflow     WS00400012
     Payment release
     Release payment          X
     Creater permitted          X
      Payt release    1.00
      Pmnt rel.var.   CC
Assign Company Code Workflow Variant for Release for Payment
     Compamy Code     Workflow Var     WF Var. Name
     XXXX     XX01     WS004 Payment release
Define Release Approval Groups for Release for Payment
     0001     Vendor A
     0002     vendor B
     0003     Vendor C
     0004     G/L accounts
Define Release Approval Paths for Release for Payment
     0001     Vendor high
     0002     Vendor middle
     0003     Vendor low
     0004     G/L accounts
     0005     Other
Assign Release Approval Paths for Release for Payment
     Workflow Variant      Doc. Type      Release Group     Approval Path
     XX01     KR     0001     0001
     XX01     KR     0002     0002
     XX01     KR     0003     0003
     XX01     KZ     0001     0001
     XX01     KZ     0002     0002
     XX01     KZ     0003     0003
     XX01     SA     0001     0001
     XX01     SA     0002     0002
     XX01     SA     0003     0003
Assign Release Approval Procedure for Release for Payment
     Wrkf      ApPath     Amt To            Curr     Rel levels     Swf Amt rel     Swf pnmt rel
     XX01     0001     5,000.00      INR     1     WS10000052     WS00400011
     XX01     0001     10,000.00     INR     2     WS10000053     WS00400021
Define Relevant Document Types for Release for Payment
     Workflow Variant     Type
     XX01                       KR
     XX01                       KZ
     XX01                     SA
Define Users with Authorization to Payment Release
     XX01     1     1     5,000.00     INR
     Assigned Authorization Object
     Production manager
     XX01     1     2     10,000.00     INR
     Assigned Authorization Object
     Comp Admin
Carry Out Function Enhancements for Release for Payment
Define Payment Block Reason for Payment Release
           Free for payment
     *     Skip account
     A     Locked for payment
     B     Blocked for payment
     I     CML:InvestorContract
     N     Postprocess inc.pmnt
     P     Payment request
     R     Invoice verification
     V     Payment clearing
We are using Tcode FV60 for Park Vendor invoice
We are trying to post the Document thru Tcode FBV0 , But the Post field is grey and system shows error: func not possible as document is in not released. The Workflow is not getting triggered. And hence its not possible to release the doc.
The workflows have been activcated
We have done Eventlinkage and activated it.

In future when you post question please do some formatting. It seems like a novel.
Have you checked in SWEL whether the event CREATED of Business Object BSEG getting triggered. I hope you have activated the linkage between event and workflow from PFTC or SWE2 transaction code.
Thanks
Arghadip

Would Like to Get Report of Daily Emails In and Out from Members to a DL Exchange version : 2007 I am the supervisor for the group and want to quantify this information. I do not need to see the content, just quantity is it possible ?

Would Like to Get Report of Daily Emails In and Out from Members to a DL
Exchange version : 2007
I am the supervisor for the group and want to quantify this information. I do not need to see the content, just quantity
is it possible ?

Well, distribution groups don't really have a concept of "in" or "out". They only serve to distribute messages sent to them -- unless you're asking to know who was a member of the distribution group at the time a message was sent to the DL.
Message tracking logs hold the information you want, though. You'd have to look for EXPAND events that reference the distribution group and take the sender's e-mail address from that event. If the DL is a simple one that's not a member of any other groups
you could also look for RECEIVE events sent to the e-mail address of the group and get the sender's name from that event.
You can use Powershell extract the rows of data from the logs, but you'll have to write the code to get the data out of those rows and into a format you want. Perhaps LogParser could be useful in place of Powershell?
--- Rich Matheisen MCSE&I, Exchange MVP

Error while assigning user for release approval path for payment release

Hi everyone,
     I am trying to assign user for payment release in SPRO. I have defined upto 'Define relevant document types for release for payment', after that while assigning user in terms of position for release and save it, i am getting error 'Program error: ASSIGN with length 0 in program "MP120800" '.Because of it i can t proceed further.
The data in details below;
1. Create Workflow Variant for Release for Payment
   1000     SAP
2. Assign Company Code Workflow Variant for Release for Payment
1000     1000     SAP
3. Define Release Approval Groups for Release for Payment
0001     Vendor A
0002     vendor B
0003     Vendor C
0004     G/L accounts
4. Define Release Approval Paths for Release for Payment
0001     Vendor high
0002     Vendor middle
0003     Vendor low
0004     G/L accounts
0005     Other
5. Assign Release Approval Paths for Release for Payment
1000     KZ     0001     0001
1000     KZ     0002     0002
1000     KZ     0003     0003
6. Assign Release Approval Procedure for Release for Payment
1000     0001     20,000.00     KES     1     WS10000052     WS00400011
1000     0002     50,000.00     KES     2     WS10000052     WS00400021
1000     0003     1,000,000.00     KES     3     WS10000052     WS00400022
7. Define Relevant Document Types for Release for Payment
     1000     KR
1000     KZ
8. Define Users with Authorization to Payment Release
1000     0001     1     20,000.00     KES
1000     0001     2     50,000.00     KES
1000     0001     3     100,000.00     KES
here i have selected the option and tried to create Orgobject, i am getting following error
Program error: ASSIGN with length 0 in program "MP120800"
If any corrections in the definitions, Please let me know.
Thanks in advance!!

Hello,
Please start the report RSWOGIND, set also the checkbox "generate all
ObjTypes from new". This should solve the problem.
Best regards, Hana

Withholding tax -number could not be determined for numbering group ID0017

While positing the FB60 transaction with withholding tax for country Indonesia, the below error is coming:
A number could not be determined for numbering group ID0017
Message no. 7Q630
"The system could not determine a certificate number for the numbering
group.
Withholding tax types exist that are relevant to numbering. The system
cannot determine a certificate number because the Customizing settings
are incomplete.
Sysem Response
Payment cannot be made.
Procedure
Check the number ranges in the numbering group."
Already seen the wothholding tax number range and it is coorec. Please advise how to resolve.

Dear,
Please check whether you have assigned the number range to the number group in the below setting
Spro
Financial Account Global Setting> Withholding Tax> Extended Withholding Tax> Posting> India> Remittance Challan> Assign Number Range to Number Groups

Please wait for the group policy client - shutting down issues

Hi
I have issues with shutting down machines. When machine is connected to company's LAN everything works fine. However, if machine is connected to VPN - Juniper NC - 1 hour or more it always hangs when it is shutting down. When I shut down the machine
(verbose mode on), first stage is:
Please wait for the system Event Notification service.
This ends exactly
after 3 minutes. Next stage:
Please wait for the group policy client windows 7
...is never timed out (even after few hours). Machine never shuts down.
In Application logs there are always these 4 events when machine is unsuccessfully shutting down:
6005: The winlogon notification subscriber <Sens> is taking long time to handle the notification event (Logoff).
4627: The COM+ Event System timed out attempting to fire the Logoff method on event class {D5978650-5B9F-11D1-8DD2-00AA004ABD5E} for publisher and subscriber . The subscriber failed to respond within 180 seconds.
The display name of the subscription is "ISensLogon2". The HRESULT was 80010002.
6006: The winlogon notification subscriber <Sens> took 180 second(s) to handle the notification event (Logoff).
6005: The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (Logoff).
Sens is timed out after 3 minutes while there is no 6006 event for GPClient and machine is stuck there for ages (Please wait for the group policy client
stage). I noticed in System logs that machine always hangs if there is this error
5783: The session setup to the Windows NT or Windows 2000 Domain Controller \\server for the domain X is not responsive. The current RPC call from Netlogon on \\machine to \\server has been cancelled.
I made a group policy log and below you can see part of GPSVC log when machine is unsuccessfully shutting down:
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xe58
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Canceling pending calls
GPSVC(2d4.1cfc) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x71a
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Cancelled pending calls
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
GPSVC(438.1a04) 21:31:24:327 Waiting for user group policy thread to terminate.
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xe10
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Canceling pending calls
GPSVC(218.c88) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x525
GPSVC(2d4.1cfc) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x71a
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Cancelled pending calls
GPSVC(2d4.9c8) 21:31:24:327 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xdcc
GPSVC(218.1054) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0x20cc
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(2d4.9c8) 21:31:24:327 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xd90
GPSVC(218.1054) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(2d4.1cfc) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
GPSVC(218.d48) 21:31:24:342 Client_CompleteNotificationCall: failed with 0x525
GPSVC(218.d48) 21:31:24:342 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
GPSVC(218.1c04) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x525
GPSVC(218.1c04) 21:31:24:342 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Entering with event 0x2100
GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Entering with event 0x1264
GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
I tried with signing out from VPN before shutting down machine, I even switched off WiFi but machine still hung. If i tried to get GP results before shutting down machine it takes ages and it is stuck in "Getting the user name" stage.
Gpupdate /force never updates policy (It stops at Updating Policy...). I tired with installing different hotfixes which did not resolve the issue. I never have any
issues with logging in, no GP scripts are applied when user is logging off or on, no roaming profiles. The only issue is when machine needs to be shut down.
I excluded 1 machine from GP and left it on VPN for a few hours, several times. It always shuts down successfully. I applied GP back one by one and the one which is presumably causing an issue is Avecto which adds admin rights when VPN application
starts (event 100):
Process started with admin rights added to token.
Command Line: "C:\Users\User\AppData\Roaming\Juniper Networks\Setup Client\JuniperSetupClient.exe"
Process Id: 5540
Parent Process Id: 2252
Policy: EA-PrivilegeGuardSettings.UK Policy
Application Group: EA-PrivilegeGuardSettings.Applications Granted Admin Rights
Reason: <None>
File Name: c:\users\User\appdata\roaming\juniper networks\setup client\junipersetupclient.exe
Hash: 27D8463A913A802E555AEEF45717B122249AA993
Certificate: Juniper Networks, Inc.
Description: Juniper Setup Client
Application Type: exe
Product Name: Juniper Setup Client
Product Code: <None>
Upgrade Code: <None>
Product Version: 8.0.6.48695
I guess there is a DNS issues when machine is on VPN which leads that GP cannot be applied / updated. Not sure if or why Avecto would have an impact on this. When machine is trying to shut down it still somehow thinks it is connected to DC. What
I also noticed are several explorer crashes while machine is on VPN.
Does anyone have same issues? All machines are Dell with Juniper NC (VPN).
Thanks,

Hi,
According to event log, Winlogon process takes a long time to handle logoff event. That's to say winlogon process is waiting for response to logoff.
According to your description after, this problem is most probably caused by Avecto. You can try to disable or uninstall it temporarily for test.
To make further troubleshoot with this problem, you can try to use WPT (Windows Performance Tool) to make troubleshoot.
http://blogs.technet.com/b/askpfeplat/archive/2013/03/22/troubleshooting-windows-performance-issues-using-the-windows-performance-recorder.aspx
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Slow logins to domain, several event ID errors (group policy, netlogon, NTP errors)

We have a laptop user who was experiencing slow logons in a remote office.   (Remote office has 100 users, only 1 is reporting the issue). Helpdesk swapped computers to give the user brand new hardware.   The new laptop worked
fine while in the IT department in the main office, the user returned to their desk in their remote office after replacing the laptop and logged in and experienced the same slow logon issues as the older laptop.
Logons take up to 45 mins to process. (Login script hangs and does not process). During the process, you can check IPConfig and it received the proper DNS settings. you can ping the authenticating server by name. We have scanning
on our local copiers setup to scan to the users desktop, and this errors out. DNS on the AD controller shows the proper IP address for the machine and you can ping the machine by name.
System Event log is loaded with errors:
Event ID 5719 - Netlogon, computer not able to setup a secure session with a domain controller in the domain
Event ID 1129 - Group Policy, processing of Group Policy failed because of lack of network connectivity
Event ID 129 - Time Service, NTP Client was unable to set a domain peer to use as a time source
Event ID 5783 - NetLogon, The session setup to the WIndows NT or 2000 domain controller (xxx) for the domain is not responsive. RPC call cancelled.   (NOTE - you can ping this domain controller by name and by IP with no issues)
Event ID 130 - Time-Service, NTP client unable to set a domain peer
All these seem to point to RPC errors timing out because they cannot communicate to the network resources. The problem happens on wired or wireless connections. We had the user move to a different network connection (one we know is working for
another user) the problem persists.   The problem was on the original computer and continues to happen even after replacing the hardware with a brand new laptop.
I have tried running the following hotfix. Which does not resolve the issue:
http://support2.microsoft.com/kb/2459530 which technically this shouldn't be an issue because we use DHCP off the 2003 AD domain controller.
I have checked the domain controller, AD Replication is processing with no issues. DNS is working. The local DHCP server has no issues or events related to this account and neither does the local DNS server or the authenticating server (which
is in another remote office).

Hi,
As we know, most of the time error event 5719 is caused by network connectivity issues or name resolution issue, I suggest you refer to this link to make a further analysis
http://blogs.technet.com/b/instan/archive/2008/09/18/netlogon-5719-and-the-disappearing-domain.aspx
And this link:
Root Causes for Slow Boots and Logons
http://social.technet.microsoft.com/wiki/contents/articles/10130.root-causes-for-slow-boots-and-logons-sbsl.aspx
Yolanda Zhu
TechNet Community Support

Event for payment grouping

Similar Messages

Maybe you are looking for