5 Replies Latest reply on Jul 26, 2012 11:32 PM by Segal-Oracle

    Process is Already Running Error on New Issue of Nutrient Profile

      Hello, we wanted to post our issue here first to see if Dev has any suggestions before we open an SR.

      We have custom validation code that on Save of a Nutrient Profile validates that the user has populated a Custom Section on the Ext Data tab with a product and brand code.
      If the Product Brand Reference has been entered then the validator connects to and reads form our legacy Nutritional database, and creates another Custom Section called Nutrient Profile Import Control with a Formula ID. This second CS allows the user to choose whether to pull in 100g Data and/or Fact Panels later in the process using that ID when the NP is workflowed.

      When we create a New Issue of an existing NP of course it pulls forward the Nutrient Profile Import Control custom section. However if we Save or Save & Close without removing that CS first we receive the follwoing error:
      ErrorType: First| ErrorCount: 0| App: GSM| SessionId: 559ee82b-0e22-ae8f-ad2c-faf9235ef47c| UserId: autena| IsNewSession: False| ServerID:| Misc: | Exception: System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> Xeno.Prodika.Common.AssertionException: Process is already running. at Xeno.Prodika.Common.Assert.Fail(String msg) at Xeno.Prodika.Common.Assert.True(Boolean value, String msg) at Xeno.Prodika.Services.Specification.SpecificationService.Save(Boolean bStayInEditMode, Boolean bDelayWorkflowResolution) at Xeno.Prodika.Services.Specification.SpecificationService.Save(Boolean bStayInEditMode) at prodika.XManagedSpecBaseForm.SaveSpec(Boolean stayInEditMode, Boolean reResolveWorkflow) at prodika.frmNutrientProfile.OnSaveAndClose() at prodika.ctlActionMenu.OnSaveClose() at prodika.ctlActionMenu.ExcuteByEventName(String eventName) at prodika.ctlActionMenu.hdnCommand_Click(Object sender, EventArgs e) at System.Web.UI.HtmlControls.HtmlInputHidden.OnServerChange(EventArgs e) at System.Web.UI.HtmlControls.HtmlInputHidden.RaisePostDataChangedEvent() at System.Web.UI.HtmlControls.HtmlInputHidden.System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent() at System.Web.UI.Page.RaiseChangedEvents() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace --- at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.baseforms_frmnutrientprofile_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

      Our validation code on save looks to see if this CS exists already, and if it does, it simply exits our code and continues on to whatever is after that in Oracle code.

      If we remove the CS from the new issue BEFORE saving, our validation code sees that the section doesnt exist, creates the section, and the New Issue saves correctly with no errors.

      My programmers are at a loss as to why we get the Process Already exists error after we exit our validation code because we lose visibility in debug. Any ideas? If you need code samples I can get those too...