A custom workflow is called during a Windows7 imaging process, being called direct from WinPE. The IE logs are returning the fact that there is no session ID.
Further investigation shows that the workflow call logs in IIS is the Composer.aspx file is not triggering a redirect to form.aspx and is instead returning HTTP code 200 rather than the expected 302. When properly running in WinPE and the code 200 is written to the IIS log, the following error is written to the workflow’s log file.
8816:0006 2013-05-23 13:58:25.981 Error System.Exception: The dialog session named 'rHvj2LNcMEyZLrnYGYWxGA' was not found
at LogicBase.Core.Models.Dialog.DialogSession.Load(HttpContext context, String sessionName)
at LogicBase.Core.Models.Dialog.DialogHttpHandlerBase.System.Web.IHttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
WinPE compatible version of Internet Explorer portable that was being used does not accept cookies. Therefore it cannot return session information to the Workflow.
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.