In the process model I'm trying to execute an unattended write to the databa

In the process model I'm trying to execute an unattended write to the database smart service. I'm getting "error with Task" see attached.
Any suggestions?
Thanks...

OriginalPostID-129103

OriginalPostID-129103

  Discussion posts and replies are publicly visible

  • What does the complete error message read (under alerts) Also check the application server log to find out what error is being thrown.
  • Here is the application error log message

    2014-11-17 01:05:11,765 [http-/0.0.0.0:8080-2] ERROR com.appiancorp.ap2.PortalResponse - Error: 404 Message: /suite/framework/1933
    2014-11-17 01:05:11,766 [http-/0.0.0.0:8080-2] ERROR com.appiancorp.asi.components.common.BackgroundAction - The response was committed prematurely when loading a requested URI. statusCode=404, uri=1933
    2014-11-17 01:05:11,952 [http-/0.0.0.0:8080-4] ERROR com.appiancorp.ap2.PortalResponse - Error: 404 Message: /suite/framework/1933
    2014-11-17 01:05:11,953 [http-/0.0.0.0:8080-4] ERROR com.appiancorp.asi.components.common.BackgroundAction - The response was committed prematurely when loading a requested URI. statusCode=404, uri=1933
    2014-11-17 01:07:33,820 [http-/0.0.0.0:8080-2] ERROR com.appiancorp.common.struts.BaseAction - Error executing action: null
    java.lang.NullPointerException
              at com.appiancorp.asi.components.common.BackgroundAction.main(BackgroundAction.java:174)
              at com.appiancorp.common.struts.BaseViewAction.executeImpl(BaseViewAction.java:125)
              at com.appiancorp.common.struts.BaseAction.execute(BaseAction.java:450)
              at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
              at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
              at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
              at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
  • Looking at the stack trace I see those errors are not related to your nodes, you should reproduce the issue and monitor the log for new errors. You should also be receiving an alert with more details.