PO cannot be cancelled

hello to anyone who help me.....
i made an application using DI that will upload a PO from another database... there is a certain CARDCODE which was inserted in a PO that was supposedly invalid, but the DI did not produce an error after executing the DOCUMENT.ADD() command.... after i figured out that i inserted a wrong CARDCODE... i tried to CANCEL the document through SAP, but SAP says "BP and Location is Invalid", which means i cannot cancel the PO...
what should i do?.... please help....

Hi,
If you aren't able to cancel the document through the user interface or by using the DI API then you'll need to log a support call with SAP Support. They will probably ask for a copy of your database so they can test a solution and then remotely correct your live database (via a webex session).
Kind Regards,
Owen

Similar Messages

How to create an infinite loop that cannot be cancelled?

Hi , im new around java and i need a program that keeps on repeating after each each input/uses(generally meant for different user) and cannot either stop using "Cancel" or "x" while stopping only using the "stop" button
I got a few lines of codes that look like this : String arg = "";
do{
JOptionPane.showInputDialog("hi");
}while ( arg != "y" || arg!= "Y");
and it cannot be stop with both cancel and"x"(which i wanted)
but when i used this logic with
Valid validUserInput = new Valid();
do {
userInput = validUserInput.validUserInput(a);
switch(userInput){
case 1 : validUserInput.optionOne(b);break;
case 2 : validUserInput.optionTwo(c);break;
case 3 : validUserInput.optionThree(d,e);break;
default : validUserInput.validUserInput(f);
}while(looping != "" || looping != " ");
it does not really work(while it will keep looping, it can be easily stop by pressing cancelled or "x")
So is there any logic or method that can prevent the program from being stop?
Thankyou!

elricscript wrote:
"That is helpful. It gives him a direction where he can focus his research. Namely, 'how to run a program in kiosk mode' rather than 'how to create an infinite loop that cannot be cancelled.'"
No... He already mentioned he wants to "e.g Interactive kiosk", so saying "properly kiosk it" isn't adding any new information. Rather it's just giving the person a dead point of: you're doing it wrong. Pointing out someone is wrong is not a positive enlightenment. Pointing someone in the right direction is more productive.
>"That is helpful. It gives him a direction where he can focus his research. Namely, 'how to run a program in kiosk mode' rather than 'how to create an infinite loop that cannot be cancelled.'"
No... He already mentioned he wants to "e.g Interactive kiosk", so saying "properly kiosk it" isn't adding any new information.
Yes it is. He asked how to do it using some Swing trickery, and I said it won't work. Which is true. The OP didn't already know that, clearly, hence the question. Now he does. That's pretty much new information if you ask me.
Rather it's just giving the person a dead point of: you're doing it wrong.Right. He is. However, the problem is now no longer related to Java, and not something I can help him with. You should try that: not answering questions you don't know the answer to. It's actually more helpful than posting misleading, wrong answers.
Pointing out someone is wrong is not a positive enlightenment. I'm giving basic technical help, not yoga lessons.
Pointing someone in the right direction is more productive.As already stated, I am as ignorant of how to make a Java application into a kiosk app as the OP is. What value can I add in light of that information? I began by answering a question that was not stated to be about kiosks. Once the question moved outside of my area of knowledge, I stopped trying to answer.
I notice you're not giving him any help, being more interested in admonishing others as you are.

Call cannot be canceled on iPhone

Using latest verson of Skype on iPhone 4 with most up to date iOS, the call cannot be cancelled when conversation ends. No red button comes up and if you try to close the app then it runs in the background. It is really painful as the only solution appears to be recall the same number a second time and cancel it. This seems to cancel both calls. Crazy but true.
I assume the latest developments work on iPhone 6 but somehow leaving other plder phones behind is the way forward???
Any ideas?

I am having similar issue but on a large scale. I have only a few printers that drop off while others stay. I notice this on my iOS devices, but if I check my macbook they all still display, so only on iOS devices it is disappearing.

"Retrobill Order cannot be cancel" == Standand Function?

Dears,
Is there any document describe about that retrobill order cannot be cancel ?
And this is Oracle standard function?
Thanks

Hi,
You need to discard/cancel or delete the PI sheet from CO60....check the below screen shot...once you delete the PI sheet you can teco the order...
Thanks
Kumar

Schedule Shutdown that Cannot be Canceled?

Would like to schedule a shutdown that cannot be canceled (except by Admin user obviously). So I can force my teenager off the computer at bedtime! Normal scheduled shutdown can be canceled by anyone.
Would be happy to pay for a 3rd party utility that permits this if needed.
Thanks

One idea: if your teen connects through a router, you often can configure the router to allow Internet access only at certain times.
Or, set up a separate, non-Admin user account for your teen's use.
Also, from OS X Help:
To set time limits on computer use:
Choose Apple menu > System Preferences and click Parental Controls.
Open Parental Controls preferences
Click the lock icon to unlock it, and then enter an administrator name and password.
Select the account you want to limit, and then click Time Limits.
To set a maximum amount of time that the computer can be used during the week (Monday through Friday), select the “Limit computer use to” checkbox under “Weekday time limits,” and then drag the slider to adjust the number of hours per day the computer can be used.
To set a maximum amount of time that the computer can be used during the weekend, select the “Limit computer use to” checkbox under“Weekend time limits,” and then drag the slider to adjust the number of hours per day the computer can be used.
To restrict computer use on evenings prior to a weekday (Sunday night through Thursday night), select the “School nights” checkbox under Bedtime and then use the up and down arrows to specify the time during which computer use is blocked.
To restrict computer use on Friday night and Saturday night, select the Weekend checkbox under Bedtime and then use the up and down arrows to specify the time during which computer use is blocked.
Message was edited by: inandoutofgrace

Historic deferred tax-related reconciliations cannot be canceled

I have a problem with a payment that i need to cancel, it sends me a message Historic deferred tax-related reconciliations cannot be canceled [3821-29]. This payment has the docdate feb-2009.
Any ideas?

The account seems fine, it's just that they've been doing reconciliations like this for years and have never needed the Automatic Reconciliation Differences Account defined. Just want to ensure everything is working fine. My concern we more so the remarks that were automatically populated 'Historic deferred tax-related reconciliations cann', as the Canadian localization doesn't deal with deferred tax. I can't explain why it was automatically populated and what is meant by that message.
Thanks,
Wendi

Incoming Payment cannot be Canceled.

My client is running SAP B1 version 8.8 PL 2. My client created an incoming Payment that was less than the balance due on the invoice and forgot to change the Total Payment field to reflect the actual amount paid. I canceled the Deposit, but when I tried to cancel the Incoming Payment, I got the error message " Transaction associated with System Reconciliations which cannot be automatically canceled [Message 3821-14]. No External Reconciliations have been performed. Since this appears to be an Internal Reconciliation issue, how can I fix this problem?

Hi,
The most possible reason for such error message when trying to cancel the Payment is that the same is associated to another payment.
Try to cancel the other associated payment in the Copy of the database in the Test Enviorment and see if it works.
Kind Regards,
Jitin
SAP Business One Forum Team

Lenovo cannot guarantee cancellation?

I placed my order on 11/5 and was given a ship date of 11/25. (order # 424326879) At first I was ok with this because my current computer was still limping along. Then my current computer finaly died and I needed to replace it promptly so I could keep working.
I called in on the 11/8 and placed a cancellation request. I was told the order would cancel within 48 hours. Over the weekend I went and spent my money on a new machine at a local retailer. By the 11th, when I did not see any change to my order status, I got on the phone with order support again.
That rep put in another cancelation request and then promptly told me:
"We cannot guarantee your cancelation, It is quite possible that China will go ahead an ship/charge you anyway!"
Really Lenovo? With a 17 day lead from cancelation request to estimated ship date you cannot guarantee my cancelation?
Of course now my ship date, just today, has been moved backwards to the 18th and my order status still hasn't changed. I am pretty concerned that Lenovo will go ahead and charge me even though I already spent my money. This means that when they post the charge to my bank account there will not be enough money to cover the charge and I will be struck with overdraft fee's. My bank told me that the only real recourse is to simply shut down my account. frankly I would prefer to avoid such action.
Anyone have any ideas for me?
Is there a higher level of support I can attain to?

I had the same experience. I called to cancel a week in advance of my currently scheduled Y2P ship date, and was told that because the order had "generated a PO#" that cancellation could not be guaranteed. I was told I would recieve an email verification of hte request to cancel within an hour (I never did) and that they would have to put in a request for cancellation that might or might not be effective. I was told that even if it ships I should accept the dlivery and their "no hassel return policy" would take care of returning it if I didn't want it.
Several days later my system shipped and I was charged for it.
While it seems reasonable that after some point cancelling an order may not be possible once it's close to shipping, Lenovo seems much worse in this regard than just about any other company I've dealt with, and there may be at least the suspicion that their sales organization could be deliberately ignoring cancellation requests in order to improve (at least temporarily) their sales figures and with the hope that once you have the machine in your hands you may well decide to keep it.
Z.

Cannot post Cancellation billing document (S1)to Accounting!

Hello SAP Gurus,
I need your help.
We have upgraded from 4.7 to 5.0 ECC couple of months back. We are able to create cancellation billing documents for billing documents created before upgrade but are not able to release them to accounting.
The error message is
<b>Tax statement item missing for tax code S0
Message no. FF805
Diagnosis
No tax item exists for tax code S0 in a G/L account item. A possible cause is an incorrect transfer of parameters by the application to the Accounting interface.
Procedure
Enter an OSS message.</b>
However, we are able to release cancellation billing documents to accounting for billing documents created after upgrade. Its only the cancellation billing documents for the billing documents created before upgrade that have issue.
We are using external tax system for tax calculation. I have looked into the configuration settings in SAP and everything looks good.
checked OSS notes...but of no help.
Please let me know if anyone has faced similar issue . Any suggestions in this regard will be greatly appreciated.
Thanks in advance.
Raj

hi raj
i am facing a similar problem, I am on an upgrade from 4.6c to Ecc6
FF805 Tax statement item missing for tax code O0
No tax item exists for tax code O0 in a G/L account item. A possible cause is an incorrect transfer of
parameters by the application to the Accounting interface.
Just wanted to know on how u did resolve the issue.
could u mail me on [email protected]
your help would be appreciated

Cannot Delete / Cancel / Reverse Service Purchase Order. Please Help....

If you create a service entry sheet, process the service entry
approval,post an invoice for an amount greater than the Service entry
then, cancel
the entry sheet and add a new service specification (i.e. same entry
sheet), the following problem occur:
1. You can no longer cancel the invoice if the services of the entry
sheet are deleted.
2. After changing the entry sheet and renewed acceptance of services
performed, a posting takes place where the value differs from the
value of the entry sheet.
Steps to Reproduce:
1. Create a Service Purchase Order of $2,675.00
2. Create a Service Entry against the Purchase Order for $2,675.00
3. Approve Service Entry against the Purchase Order for $2,675.00
a/c postings Dr Expense $2,675.00
Cr GR/IR $2,675.00
4. Create an Invoice against the Service Purchase Order for $6,452.50
a/c postings Dr Expense $3,777.50
Dr GR/IR $2,675.00
Cr Vendor $6,452.50
5. Create Credit Memo $1,537.00
6. Revoke the Service Entry against the Purchase Order for $2,675.00
I am expecting the Reversal of the Service Entry figure is $2,675.00, but instead, the Reversal of the Service Entry figure is $1,537.00. Why is that so? I need to be able to Reverse/Delete the PO. Please help...
Thank you.

Hi,
please check the folowing notes for further information:
856682    Goods receipt document cancelled with incorrect value
499575    FAQ: Invoice verification/goods receipt in service
440942    GR cancellation not equal to GR
Regards,
Edit

Check that GI cannot be cancelled after GR has been done.

Hi,
The user is complaining that even though he has posted goods receipt for the delivery of a stock transfer order, he is able to cancel the goods issue using 'VL09'. The system should block cancellation of goods issue after goods receipt is complete. Any special setting for this?
Thanks and regards,
Kasturi

hi friend
tell me clearly
with regards
dinesh

Cannot load cancelled check images on Fifth Third Bank site

''Duplicate post, continue here - [/questions/755742]''
Running Windows XP Profess. Serv. Pack 3 with Mozilla 3.6.10. Log into Fifth Third Bank site. Choose to display checking account information. Click on a check #. "An Error Has Occurred. If the problem persists, please contact a Customer Service Professional at 1-800-XXX-XXXX." Use IE Explorer, can display cancelled check images....no problem. According to Fifth Third Bank site, acceptable browsers include Mozilla 2.X and newer.

Fifth-Third did a major upgrade this past weekend, if you are seeing any differences in their services now in comparison to last week contact them.
I can't comment about your particular issue, because I haven't used that feature to view canceled check images in the last few years.
The change that I noticed was that the Username / Password on the Login page now has '''''autocomplete=off''''' which is a good change, IMO. Also, I had to change my online password (some were lost during the transition they told me). I was able to get Firefox to save the new password (using the popular bookmarklet), but it won't autofill properly not matter what I try - at least the User ID does.

URGENT: 22 Sync groups stuck in processing mode and cannot be cancelled

The below sync groups stopped working and keep displaying "Processing", I've tried to stop the job but no response, I've also tried to regenerate the sync agent keys, and tried to restart the agent, reboot the client PC, but all not working. They
seems all stop working at the same time 15 hours ago. But they are across different database, different subscriptions.
Can anyone please help me out for that? the problem sync groups are as below:
Sync Group ID
    f6d51362-7a47-47fb-84b3-9c23445626e3_East Asia
Subscription ID
    f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
    f1216549-eb83-4a2e-afa8-9135f1f92006_East Asia
Subscription ID
    f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
    6d45b9d2-0a57-43a9-8e14-004432512b73_East Asia
Subscription ID
    f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
    f14d2c29-08a4-4dd3-a49f-7bf0f7f8b2f3_East Asia
Subscription ID
    f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
    751dc6f2-8c85-4bae-a7cc-0bb89abcbb66_East Asia
Subscription ID
    f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
    574115d1-de83-40ce-8de3-5a424d8cdedc_East Asia
Subscription ID
    f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
    15a3a3c5-f867-4ba4-b7af-92fb5c8d36a6_East Asia
Subscription ID
    f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
    7ceaafb5-7af7-4b18-af5a-2de75890227a_East Asia
Subscription ID
    f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
    f4b4efb3-0a4c-4eb6-a826-316f5f22fbb2_East Asia
Subscription ID
    cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
    920b1c9a-5ba7-49af-ad1a-37470b6a47da_East Asia
Subscription ID
    cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
    9baf8167-9ee9-4ce4-bc88-abc0797a343f_East Asia
Subscription ID
    cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
    2ae3a888-7cb2-4e18-a0ec-9850bb91e01a_East Asia
Subscription ID
    45d375de-c29f-4a14-926c-1fe744d157b7
Sync Group ID
    734fcc26-46e6-444a-a0d1-d3ff4c5834f7_East Asia
Subscription ID
    cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
    0d315093-8977-4229-8ba4-ece0fb10c3f9_East Asia
Subscription ID
    cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
    58cb062a-57a0-4ec6-8e9d-21fe021cd5b5_East Asia
Subscription ID
    cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
    652e5ef2-c1db-4989-8d15-472590747463_East Asia
Subscription ID
    cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
    8cfe554c-f4df-4167-b449-23da5ed0cf68_East Asia
Subscription ID
    45d375de-c29f-4a14-926c-1fe744d157b7
Sync Group ID
    56c9e45b-51e1-4fe5-8a35-df86c0ab68b2_East Asia
Subscription ID
    a68811f9-f82a-4e7c-b93c-d1bee226f84b
Sync Group ID
    826c0497-b9e4-4664-b404-ee75f54b407d_East Asia
Subscription ID
    a68811f9-f82a-4e7c-b93c-d1bee226f84b
Sync Group ID
    4a604aad-e318-469d-adde-9ed4e1d52ead_East Asia
Subscription ID
    a68811f9-f82a-4e7c-b93c-d1bee226f84b
Sync Group ID
    db07173c-db1d-40df-98e1-47a158b6c873_East Asia
Subscription ID
    a68811f9-f82a-4e7c-b93c-d1bee226f84b
Sync Group ID
    9ad4eab4-6499-4976-b6f1-813b0ce93539_East Asia
Subscription ID
    a68811f9-f82a-4e7c-b93c-d1bee226f84b
EDITED: Should be 31 sync groups have encountered this problem, already have caused fatal impact for our business, hope anyone can help, workaround solution also welcome. Thanks!
Group Name
Sync Group ID
Subscription ID
ew_sync_a003
f6d51362-7a47-47fb-84b3-9c23445626e3_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a013
f1216549-eb83-4a2e-afa8-9135f1f92006_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a022
6d45b9d2-0a57-43a9-8e14-004432512b73_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a026
e267e22a-1764-4e19-9ee8-a62b079a3855_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a029
f14d2c29-08a4-4dd3-a49f-7bf0f7f8b2f3_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a032
ac6e92b5-f7a3-41db-b912-47f65de3d550_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a034
751dc6f2-8c85-4bae-a7cc-0bb89abcbb66_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a035
574115d1-de83-40ce-8de3-5a424d8cdedc_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a037
15a3a3c5-f867-4ba4-b7af-92fb5c8d36a6_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a038
7ceaafb5-7af7-4b18-af5a-2de75890227a_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a041
f4b4efb3-0a4c-4eb6-a826-316f5f22fbb2_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a044
911932b3-e7a3-4238-9e1c-d9adb05fba8b_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a045
1d144ceb-e564-437e-854d-0f73b08f9c4a_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a046
920b1c9a-5ba7-49af-ad1a-37470b6a47da_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a047
9baf8167-9ee9-4ce4-bc88-abc0797a343f_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a049
2ae3a888-7cb2-4e18-a0ec-9850bb91e01a_East Asia
45d375de-c29f-4a14-926c-1fe744d157b7
ew_sync_a052
734fcc26-46e6-444a-a0d1-d3ff4c5834f7_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a053
8d811816-9455-4283-ab4d-e7bbb39b1319_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a054
94f34eaa-cf1c-4af0-950e-7aa565ccc781_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a056
0d315093-8977-4229-8ba4-ece0fb10c3f9_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a057
58cb062a-57a0-4ec6-8e9d-21fe021cd5b5_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a058
652e5ef2-c1db-4989-8d15-472590747463_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a060
8cfe554c-f4df-4167-b449-23da5ed0cf68_East Asia
45d375de-c29f-4a14-926c-1fe744d157b7
ew_sync_a061
56c9e45b-51e1-4fe5-8a35-df86c0ab68b2_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a063
826c0497-b9e4-4664-b404-ee75f54b407d_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a064
41126d10-b858-468a-8590-d0bb03d2814c_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a069
4a604aad-e318-469d-adde-9ed4e1d52ead_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a071
db07173c-db1d-40df-98e1-47a158b6c873_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a073
a0208e66-7d96-4528-a0ac-70e7989e44e8_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a074
9ad4eab4-6499-4976-b6f1-813b0ce93539_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a076
5944edb5-4e2e-4fbf-8b7b-a880a8a6b27e_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b

Hi Sofiya,
Thanks for your help. According to the log from sync agent, it just like a normal log, without any error. We have set the sync to 5 minutes intervals, but seems the agent have not proceed the job as the cloud said another job is processing:
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:Main,
message:Microsoft SQL Data Sync Windows service is starting as a Windows Service.
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:OnStart,
message:Microsoft SQL Data Sync Windows service starting.
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:OnStart,
message:Starting a service worker thread.
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0, methodName:OnStart,
message:Started a service worker thread.
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0, methodName:OnStart,
message:Microsoft SQL Data Sync Windows service started successfully.
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0, methodName:StartUxWcfService,
message: Namedpipe e0ec8c56-cf3f-4aea-855b-2981f6313d06, BaseAddress net.pipe://localhost/e0ec8c56-cf3f-4aea-855b-2981f6313d06
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0, methodName:StartUxWcfService,
message: Opened WCF Host
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0, methodName:StartServiceThread,
message: GetEntryAssembly().Location: C:\Program Files (x86)\Microsoft SQL Data Sync\bin\LocalAgentHost.exe, GetExecutingAssembly().Location: C:\Program Files (x86)\Microsoft SQL Data Sync\bin\LocalAgentHost.exe, Process.GetCurrentProcess().StartInfo.WorkingDirectory:
LocalAgentHost 4/8/2014 6:57:01 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0, methodName:AgentConfigDataManager.DownloadAndCacheServiceUrisFromLocator,
message:Scale unit found
AgentCore 4/8/2014 6:57:01 id:AgentCore_InstanceStarted, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0
ThreadId:19. Dispatcher started. Waiting
ThreadId:20. GetRequest started.
ThreadId:19. Dispatcher calling GetRequest
ThreadId:21. GetRequest started.
ThreadId:22. GetRequest started.
ThreadId:23. GetRequest started.
ThreadId:24. GetRequest started.
ThreadId:25. GetRequest started.
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling PutRequest
ThreadId:19. Dispatcher started. Waiting
ThreadId:19. Dispatcher calling GetRequest
ThreadId:20. GetRequest finished. RequestId:f4d245ad-b209-463e-8c43-4c59c7ea6737
CommandAndControlClient 4/8/2014 7:17:20 id:CommandAndControlClient_GetRequest, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737
CommandAndControlClient 4/8/2014 7:17:20 id:CommandAndControlClient_AckRequest, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737
ClientRequestHandler 4/8/2014 7:17:20 id:ClientRequestHandler_Request, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737,
serializedRequest:<?xml version="1.0" encoding="utf-16"?>
<SyncRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<PostActionSucceededWork xsi:nil="true" />
<LogInfo>
<DetailedProviderTraces>false</DetailedProviderTraces>
<SyncGroupId>0d315093-8977-4229-8ba4-ece0fb10c3f9</SyncGroupId>
<SyncGroupMemberIdList />
<HubDbId>f8e45e70-020f-4b97-9ca8-c70e879a24a7</HubDbId>
<SyncGroupMemberId>87b18bc7-551f-4efe-9082-2ad47b8a99d9</SyncGroupMemberId>
<AgentId>f995868a-18fd-4786-875e-34996ffd5325</AgentId>
<AgentInstanceId>6fe18179-e983-4288-a660-2b9f16762603</AgentInstanceId>
<TracingId>f4d245ad-b209-463e-8c43-4c59c7ea6737</TracingId>
<DssServerId>edbf9ba4-b43f-4521-84a4-6349d490f5a8</DssServerId>
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
<SqlAzureActivityId>00000000-0000-0000-0000-000000000000</SqlAzureActivityId>
</LogInfo>
<ScopeName>AA499444-A041-47EA-B79B-6A1A503E6251</ScopeName>
<SyncGroupMemberId>87b18bc7-551f-4efe-9082-2ad47b8a99d9</SyncGroupMemberId>
<LocalDatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</LocalDatabaseId>
<RemoteDatabaseId>f8e45e70-020f-4b97-9ca8-c70e879a24a7</RemoteDatabaseId>
<ConflictResolutionPolicy>LocalWins</ConflictResolutionPolicy>
<SyncDirection>UploadAndDownload</SyncDirection>
<SqlSyncProviderBatchSizeInMB>24</SqlSyncProviderBatchSizeInMB>
<SqlSyncProviderMATSizeInMB>25</SqlSyncProviderMATSizeInMB>
<SqlSyncProviderMatRowCount>50000</SqlSyncProviderMatRowCount>
</SyncRequest>
ThreadId:19. Dispatcher calling PutRequest
ThreadId:19. Dispatcher started. Waiting
ThreadId:19. Dispatcher calling GetRequest
ThreadId:24. GetRequest finished. RequestId:68dfcf90-0823-4de3-87e8-79a0bc813d00
CommandAndControlClient 4/8/2014 7:17:20 id:CommandAndControlClient_GetRequest, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:68dfcf90-0823-4de3-87e8-79a0bc813d00
CommandAndControlClient 4/8/2014 7:17:20 id:CommandAndControlClient_AckRequest, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:68dfcf90-0823-4de3-87e8-79a0bc813d00
ClientRequestHandler 4/8/2014 7:17:20 id:ClientRequestHandler_Request, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:68dfcf90-0823-4de3-87e8-79a0bc813d00,
serializedRequest:<?xml version="1.0" encoding="utf-16"?>
<CleanupTombstoneRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<PostActionSucceededWork xsi:nil="true" />
<LogInfo>
<DetailedProviderTraces>false</DetailedProviderTraces>
<SyncGroupId>00000000-0000-0000-0000-000000000000</SyncGroupId>
<SyncGroupMemberIdList />
<HubDbId>00000000-0000-0000-0000-000000000000</HubDbId>
<SyncGroupMemberId>00000000-0000-0000-0000-000000000000</SyncGroupMemberId>
<AgentId>f995868a-18fd-4786-875e-34996ffd5325</AgentId>
<AgentInstanceId>6fe18179-e983-4288-a660-2b9f16762603</AgentInstanceId>
<TracingId>68dfcf90-0823-4de3-87e8-79a0bc813d00</TracingId>
<DssServerId>edbf9ba4-b43f-4521-84a4-6349d490f5a8</DssServerId>
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
<SqlAzureActivityId>00000000-0000-0000-0000-000000000000</SqlAzureActivityId>
</LogInfo>
<RetentionInDays>45</RetentionInDays>
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
</CleanupTombstoneRequest>
ClientRequestHandler 4/8/2014 7:17:21 id:ClientRequestHandler_Response, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:68dfcf90-0823-4de3-87e8-79a0bc813d00,
serializedResponse:<?xml version="1.0" encoding="utf-16"?>
<CleanupTombstoneResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<State>Succeeded</State>
<LogInfo>
<DetailedProviderTraces>false</DetailedProviderTraces>
<SyncGroupId>00000000-0000-0000-0000-000000000000</SyncGroupId>
<SyncGroupMemberIdList />
<HubDbId>00000000-0000-0000-0000-000000000000</HubDbId>
<SyncGroupMemberId>00000000-0000-0000-0000-000000000000</SyncGroupMemberId>
<AgentId>f995868a-18fd-4786-875e-34996ffd5325</AgentId>
<AgentInstanceId>6fe18179-e983-4288-a660-2b9f16762603</AgentInstanceId>
<TracingId>68dfcf90-0823-4de3-87e8-79a0bc813d00</TracingId>
<DssServerId>edbf9ba4-b43f-4521-84a4-6349d490f5a8</DssServerId>
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
<SqlAzureActivityId>00000000-0000-0000-0000-000000000000</SqlAzureActivityId>
</LogInfo>
<PostActionSucceededWork xsi:nil="true" />
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
<RowsDeleted>44</RowsDeleted>
</CleanupTombstoneResponse>
CommandAndControlClient 4/8/2014 7:17:21 id:CommandAndControlClient_RequestProcessedSuccessfully, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:68dfcf90-0823-4de3-87e8-79a0bc813d00
ThreadId:24. GetRequest started.
ThreadId:19. Dispatcher calling GetRequest
DatabaseProvider 4/8/2014 7:17:27 id:DbProvider_EnumChanges_CompleteEnumForAllTables, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9,
syncGroupMemberId:87b18bc7-551f-4efe-9082-2ad47b8a99d9, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737, databaseId:e09fdb20-5f7e-4d42-be36-0dd45e541005, sqlAzureActivityId:00000000-0000-0000-0000-000000000000,
totalBatches:0
DatabaseProvider 4/8/2014 7:17:27 id:DbProvider_EnumChanges_NewBatchAvailable, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9,
syncGroupMemberId:87b18bc7-551f-4efe-9082-2ad47b8a99d9, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737, databaseId:e09fdb20-5f7e-4d42-be36-0dd45e541005, sqlAzureActivityId:00000000-0000-0000-0000-000000000000,
totalBatchesSpooled:1, batchDetails:
Version :3.1
BatchId :e361f8fb-7e39-4b4b-8efc-fa0f621d24c5
Batch Number :1
Is Last Batch :True
Data Cache Size :188661
Table Watermarks :[dbo.aspnet_Roles,360253],[dbo.aspnet_Users,360265],[dbo.aspnet_UsersInRoles,360254],[dbo.aspnet_Membership,360263],[dbo.aspnet_Profile,360248],[dbo.ShopWorkdayDetail,358002],[dbo.OclClientXFileUpload,356449],[dbo.ReportTurnoverHeader,356425],[dbo.ReportTurnoverDetail,356446],[dbo.ShopWorkdayPeriodDetail,358007],[dbo.TableMaster,360288],[dbo.Roster,360002],[dbo.TxSalesHeader,360287],[dbo.TxPayment,360279],[dbo.TxSalesDetail,360285],[dbo.TxSalesDetailLog,360275],[dbo.TxSalesHeaderLog,360280],[dbo.TxSalesHeaderRevokeLog,356022],
SyncController 4/8/2014 7:17:27 id:SyncController_BatchSpooledEvent, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603,
syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, memberDbId:e09fdb20-5f7e-4d42-be36-0dd45e541005, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, currentBatchNumber:1, totalBatchesSpooled:1, batchFileName:e361f8fb-7e39-4b4b-8efc-fa0f621d24c5.batch
BatchTransferUtil 4/8/2014 7:17:28 id:BatchTransfer_ClientInitialized, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737
BatchTransferUtil 4/8/2014 7:17:28 id:BatchTransfer_Start, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
BatchTransferUtil 4/8/2014 7:17:56 id:BatchTransfer_ClientInitialized, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737
BatchTransferUtil 4/8/2014 7:17:56 id:BatchTransfer_Start, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737
SyncController 4/8/2014 7:17:56 id:SyncController_BatchAppliedEvent, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603,
syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, memberDbId:e09fdb20-5f7e-4d42-be36-0dd45e541005, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, currentBatchNumber:1, totalBatches:1
DatabaseProvider 4/8/2014 7:17:56 id:DbProvider_MAT_AllBatchesApplied, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9,
syncGroupMemberId:87b18bc7-551f-4efe-9082-2ad47b8a99d9, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737, databaseId:e09fdb20-5f7e-4d42-be36-0dd45e541005, sqlAzureActivityId:00000000-0000-0000-0000-000000000000,
madeWithKnowledge:ReplicaKeyMap: [(0:bfcb2abdd3e84634b1d944fd56a9a537) (1:d8cf66fd42b342dfaada1498d80c46a3)] ScopeRangeSet: [00:[(0:223078) (1:360289)]], madeWithForgottenKnowledge:ReplicaKeyMap: [(0:bfcb2abdd3e84634b1d944fd56a9a537) (1:d8cf66fd42b342dfaada1498d80c46a3)]
ScopeRangeSet: [00:[(0:142660)]], totalChanges:2, totalChangesApplied:2, totalChangesFailed:0, totalChangesPending:0, totalInserts:2, totalUpdates:0, totalDeletes:0
SyncController_SyncStatistics 4/8/2014 7:17:57 id:SyncController_SyncStatistics, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603,
syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, memberDbId:e09fdb20-5f7e-4d42-be36-0dd45e541005, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, DownloadChangesApplied:2, DownloadChangesFailed:0, DownloadChangesTotal:2, UploadChangesApplied:757, UploadChangesFailed:0,
UploadChangesTotal:757, SyncStartTime:4/8/2014 15:17:20, SyncEndTime:4/8/2014 15:17:57
ClientRequestHandler 4/8/2014 7:17:57 id:ClientRequestHandler_Response, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737,
serializedResponse:<?xml version="1.0" encoding="utf-16"?>
<SyncResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<State>Succeeded</State>
<LogInfo>
<DetailedProviderTraces>false</DetailedProviderTraces>
<SyncGroupId>0d315093-8977-4229-8ba4-ece0fb10c3f9</SyncGroupId>
<SyncGroupMemberIdList />
<HubDbId>f8e45e70-020f-4b97-9ca8-c70e879a24a7</HubDbId>
<SyncGroupMemberId>87b18bc7-551f-4efe-9082-2ad47b8a99d9</SyncGroupMemberId>
<AgentId>f995868a-18fd-4786-875e-34996ffd5325</AgentId>
<AgentInstanceId>6fe18179-e983-4288-a660-2b9f16762603</AgentInstanceId>
<TracingId>f4d245ad-b209-463e-8c43-4c59c7ea6737</TracingId>
<DssServerId>edbf9ba4-b43f-4521-84a4-6349d490f5a8</DssServerId>
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
<SqlAzureActivityId>00000000-0000-0000-0000-000000000000</SqlAzureActivityId>
</LogInfo>
<FailureLog />
<PostActionSucceededWork xsi:nil="true" />
<SyncGroupMemberId>87b18bc7-551f-4efe-9082-2ad47b8a99d9</SyncGroupMemberId>
<DownloadChangesTotal>2</DownloadChangesTotal>
<DownloadChangesApplied>2</DownloadChangesApplied>
<DownloadChangesFailed>0</DownloadChangesFailed>
<UploadChangesTotal>757</UploadChangesTotal>
<UploadChangesApplied>757</UploadChangesApplied>
<UploadChangesFailed>0</UploadChangesFailed>
<StartTime>2014-08-04T07:17:20.6974793Z</StartTime>
<EndTime>2014-08-04T07:17:57.6775945Z</EndTime>
<FailureType>None</FailureType>
</SyncResponse>
CommandAndControlClient 4/8/2014 7:17:57 id:CommandAndControlClient_RequestProcessedSuccessfully, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737
ThreadId:20. GetRequest started.
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest

Cannot cancel credit note

Dear Expert,
I would like to ask about Credit Note that cannot be cancel using VF11, it says No Billing Document were generated, I've checked the Document Flow of the CN, and I found Accounting Document were Cleared.
As far as I know , cancel billing can succeed when Accounting Document were Un Cleared..
I asked finance to uncleared, but they can't do it, they use TC=FBRA, it says "not possible to reverse the document in financial accounting" ..
Please help me to solve this problem...
Thank you very much
regards,
Zack

Please review the notes carefully to help solve your problem.
Particularly note 92592 as it has resolved this issue many times in the
past.
885774 Billing block at wrong point of time
352706 Double FI/CO documents for invoices
92592 VF04: FI docs w/o SD bill.docs/double FI docs
1.Please delete one of the duplicate documents as desribed in note 92592
2.Please implement note 885774 in order to avoid this issue in the
future.
Please also review and consider the attached note 978689.
I hope these notes help to resolve this issue.
Regards,
Krishna

HT4623 Updating to IOS and stuck on Rescue Email? Says optional email address to confirm your I.D. or reset a P/W but with or without typing an email address cannot move to Next screen or even cancel??? Pls help.

Updating to IOS and stuck on Rescue Email? Says Optional email address to confirm your I.D. or reset password but with or without typing email address in, cannot get past screen. Click on enter or Next and nothing happens. Cannot even cancel update. Pls help a.s.a.p. Thank you.

Updating to IOS and stuck on Rescue Email? Says Optional email address to confirm your I.D. or reset password but with or without typing email address in, cannot get past screen. Click on enter or Next and nothing happens. Cannot even cancel update. Pls help a.s.a.p. Thank you.

PO cannot be cancelled

Similar Messages

Maybe you are looking for