I have a workflow that creates cases from emails. I also have a simple SLA that is associated to the cases.
Recently I have noticed a large number of the case creation jobs failing with an error like this:
Plugin Trace:
[Microsoft.Xrm.Sdk.Workflow: Microsoft.Xrm.Sdk.Workflow.Activities.CreateEntity]
[CreateStep6]
[Microsoft.Crm.Service.ObjectModel: Microsoft.Crm.Service.ObjectModel.CasePostCreatePlugin]
[ffde44b1-a685-4948-85b8-e4091bc2a98b: CasePostCreatePlugin]
[Microsoft.Crm.ObjectModel: Microsoft.Crm.Extensibility.InternalOperationPlugin]
[46f6cf4c-14ae-4f1e-98a1-eae99a37e95c: ExecuteWorkflowWithInputArguments]
Starting sync workflow 'Case Follow Up', Id: b5983018-1027-e611-80bb-0050568f6e8c
Entering ConditionStep1_step: Case Follow Up
Entering ConditionStep5_step: Check condition step - Applicable When- KPI1
Entering ConditionStep7_step:
Entering ConditionStep9_step:
Sync workflow 'Case Follow Up' terminated with error 'PopulateBusinessClosureRequests Failed'
Error Message:
Unhandled Exception: Microsoft.Xrm.Sdk.InvalidPluginExecutionException: PopulateBusinessClosureRequests Failed
We do have working hours that is linked to a holiday schedule.
I cant seem to find a cause for the "PopulateBusinessClosureRequests" failure.
This is CRM 2016 U0.1 on-prem
We raised the issue with Microsoft, and it turns out that there is an issue in the product.
At the time of this answer they were working on a fix to be included in a service pack.
Related
I've data that is on Dremio and I'm looking to connect it with Alteryx.
It was working fine until once I had cancelled the Alteryx workflow in the middle of the execution. After that that instance - it is always giving the below error which I'm not able to figure out why.
Error: Input Data (1): Error SQLExecute: [Dremio][Connector] (1040) Dremio failed to execute the query: SELECT * FROM "Platform_Reporting"."PlatformActivity" limit 1000
[30039]Query execution error. Details:[
RESOURCE ERROR: Query cancelled by Workload Manager. Query enqueued time of 300.00 seconds exceeded for 'High Cost User Queries' queue.
[Error Id: 3a1e1bb0-18b7-44c0-965a-6933a156ab70 ]
Any help is appreciated!
I got this response from the Alteryx Support team:
Based on the error message it seems the error sit within Dremio itself I would advice to consult the admin to check: https://docs.dremio.com/advanced-administration/workload-management/
I would assume the cancellation of a previous pipeline was not send accordingly to the queue management and thus the error.
I see a bunch of 'permanent' failures when I fire the following command:-
.show ingestion failures | where FailureKind == "Permanent"
For all the entries that are returned the error code is UpdatePolicy_UnknownError.
The Details column for all the entries shows something like this:-
Failed to invoke update policy. Target Table = 'mytable', Query = '<some query here>': The remote server returned an error: (409) Conflict.: : :
What does this error mean? How do I find out the root cause behind these failures? The information I find through this command is not sufficient. I also copied OperationId for a sample entry and looked it up against the operations info:-
.show operations | where OperationId == '<sample operation id>'
But all I found in the Status is the message Failed performing non-transactional update policy. I know it failed, but can we find out the underlying reason?
"(409) Conflict" error usually comes from writing to the Azure storage.
In general, this error should be treated as a transient one.
If it happens in the writing of the main part of the ingestion, it should be retried (****).
In your case, it happens in writing the data of the non-transactional update policy - this write is not retried - the data enters the main table, but not the dependent table.
In the case of a transactional update policy, the whole ingestion will be failed and then retried.
(****) There was a bug in treating such an error, it was treated as permanent for a short period for the main ingestion data. The bug should be fixed now.
The Job called "Contract States job" fails every times it runs with the following message.
"Async Handler for Update Contract States Operation encountered some
errors, see log for more detail.Detail: "
I've tried setting trace to verbose even but can't see the log, or any errors why this job is failing every time. This job is crucial to the contract entity as it need to renew (via plugin) promptly so to generate contract-detail lines in time for other process to follow.
Could someone please point me to this log or how I can trap this error causing this job to fail?
Trace displayed errors on some contracts not being able to update state because the TotalPrice was not equal to the sum of its contract lines. Further diffing showed that another "unsupported script" would change contract states - thus causing this operation to fail on these contracts.
The fix was to have a look at the "unsupported script" rather.
I am facing this error since some time, it is very intermittent in nature so, unable to understand why this error and what needs t be done t fix this.
Issue:
We have a workflow 4.5 WCF service. Everything goes well, but intermittently we see suddenly that a workflow instance gets suspended with an error in the table "DurableInstancing.InstancesTable"
The error is "Keyword Not supported: 'DB Name,1433';Initial Catalog'.
Since most times this ust workd fine without any error, I do not think this problem is related to web.config entry for connectionstring. Most times the workflow completes without any error. We have verified multiple times that the connection string is proper and there is no issue with parsing the connection string.
I suspect this issue is happening while Workflow instance is being recreated from persistence storage, and because some reason it is unable to recreate , the workflow is getting suspended with this error in DB.
I really appreciate any help in getting us through this error.
Thanks,
GD
What we found was it was an issue with permission in Database. We gave "dbo" user permission to the workflow database, and after that we have not seen this problem occur again. Has the error or exception that gets logged in the table is mre informative then it would have been better.
Thanks,
GD
I am working on php . I submit my transaction to paypalsandbox
but transaction is not completed and gives error
An error occurred while processing your request. Before submitting this again, log in and check your Account History to ensure that the transaction didn't complete.
If any one know the solution please help me.
Thanks
I'm having this in testing too. It was working about 9 hours ago, and as I'm testing from 3 different servers with two different configs, it may be that it's a PayPal issue rather than a user error.
Later:
Found this which suggest it happens from time to time. I'm seeing this error now, rather than the one reported previously.
https://www.x.com/content/resolved-intermittent-errors-during-checkout-sep-21