I have been trying to use Microsoft Workflow Foundation 4.0 in .Net Framework 4.5.
I've been following tutorials from https://learn.microsoft.com/en-us/dotnet/api/system.activities.workflowapplication.resumebookmark?view=netframework-4.8
I'm facing a problem with ResumeBookmark method.
I receive BookmarkResumptionResult success, but the resume actually failed. From my understanding, getting BookmarkResumptionResult success only meant that the bookmark resumption was successfully scheduled.
How to find out whether the actual resumption succeed or failed?
Related
I am working with elsa workflow framework in dotnet core. The first two steps in the workflow work fine. However in the third step, I am getting the error displayed in image ""Fault: Response has already started"". The sample flowchart image is . Thanks in advance
This happens when a response has already started. There are many reasons I can think of that would cause this, but from looking at your workflow, it's hard to see why.
One reason could be that you have multiple workflow instances in the system that are somehow being resumed at the same time. This happens when a workflow isn't correlated, and the signal being received triggers all of them. This would cause multiple attempts to write an HTTP response.
Another reason could be that there's a bug in Elsa 1. For that, you could submit an issue on GitHub with steps to reproduce the problem.
However, Elsa 1 is no longer being maintained, so you might want to consider migrating to Elsa 2.
Alternatively, if you (have to) stay with Elsa 1, you might consider cloning the source code and reference the projects directly and use the debugger to set breakpoints at various places to see where and why an HTTP response is started. This way, you are bound to find out that an HTTP response is written (could be a simple status code that is being set) from at least two places during the same request.
I am using JxBrowser (6.23.1) on windows 10 and using the 64-bit library. however, when i startup the demo application I get the following Log message.
SEVERE: [0528/084716.632:ERROR:browser_process_stub.cpp(279)] NOT IMPLEMENTED
Can anyone shed light on this and whether this is an issue?
I have tried to find anything in relation to above error code, but did not find anything.
The browser_process_stub.cpp(279)] NOT IMPLEMENTED message means that Chromium engine tries to get access to the specific code of JxBrowser which is not implemented at the moment due to the fact that this functionality is not supported by JxBrowser at the moment. This method does not affect the existing JxBrowser functionality, so you can safely ignore this error message.
I just downloaded and installed both the Core 2.2 SDK and the Core 2.2 Runtime. I also updated my version of Visual Studio 17 to the latest version.
To test 2.2, I created a simple ASP.NET Core website and, without changing anything, when I run the application I get the 502.5 error. The same thing happened on a similar setup on my notebook.
I would think that out-of-the box, this should work so I'm thinking something else is going on here. If I create a Core 2.1 application it is fine.
Any suggestions? The given link on the error page seems to cover this generically.
Common causes of startup issues like 502.5 (Process Failure) is listed below:
1. The application process start application process failed to start.
2. Started but then stopped.
3. The application started but failed to listen on the configured port.
Things you can try :
1) Add CaptureStartupError() and UserSetting() in their Main/program.cs file as
suggested here
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/error-handling?view=aspnetcore-2.2#startup-exception-handling
2) Review eventlog.xml for error or exceptions.
3) Enable stdoutLogFile
https://learn.microsoft.com/en-us/aspnet/core/hosting/aspnet-core-module#log-creation-and-redirection
4) When Detailed Errors is set to true and Capture Startup Errors is true, a detailed error page is displayed in response to every request to the server.
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/error-handling#startup-exception-handling
Try this:
Close any running apps.
Change default port to something else.
Run VS as Administrator.
Actually i was working on an application which is using the Windows workflow foundation (State Machine Workflow) , Initially we were getting the Error "Workflow with ID ""XXXX" not found in the state persitance store and we found the root cause , this was due to the reason our workflow was getting completed but it should not get completed for the particular cases.
How to stop the Windows Workflow foundation with some conditions
Use TerminateWorkflow activity.
In Tridion 2011 SP1 GA, I constantly am getting this strange error at random times.
Publish a page, page is successfully written to the file system, but in the publishing queue it would be stuck in "Waiting for Deployment"
One day it would be successful and the next it would be stuck.
Any ideas why this is happening?
This could be happening because your transport service has stopped polling the deployer because the polling intervals/max poll time which are configured in the the Transport Service configuration file reach their limits. Assuming that is the case, the Deployer has continued to deploy files, but the Transport Service has given up checking. However, I would expect to see the status eventually report failed in the Publishing Queue.
It is not clear if you are using GA or SP1 of SDL Tridion 2011. There are a number of hot fixes which will help solve these issues for GA and HR1, all of which are bundled into SP1. Specifically these solve some issues relating to returning responses to the Transport Service after some sort of (non-catastrophic) failure in the Deployer after it gets a large queue of items or a a particularly large transaction to deal with. I strongly suggest you install the latest patches that before trying to adjust the behaviors through configuration.
If you have already applied all the patches, please double check that you have applied them correctly (copied all the new jars etc) to the CD side (Deployer and Broker etc) as well as the CM side.