Select to view content in your preferred language

WorkflowDataStoreException: Failed to create schema

3180
8
Jump to solution
11-10-2021 06:20 AM
Ranga_Tolapi
Frequent Contributor

Create Workflow Item is running for sometime and failing with the below error. Error was captured from ArcGIS Server logs.

! @7ljj2046l - Internal server error, for (POST) [/workflow/admin/createWorkflowItem?name=Workflow%20Item%205&token=1vwTx2yA8HsT9PghnM34DYo2qjxnoGKyngpZEep_Zy9QOMrTwuaKOvdY9vIou8Drv0ziA6QHqnLJnZeg2LmH0AZhFqqSZg9dclJq99SrSFeAmqdF_tdSmoJ96YFV3igUtTsoEv-dqlih2xiIkIC0Qpiu2GuPBJ-FP4tg4mrGDX5_Dm2mM1qBfhAq6me5qEslKTsucKqh8kcswQ2GuG5LWvJ-OfKy3PUHJCfU-l45GuiCtiAPek2cnFs33sRvJMfG8JAWzmvFvvEdiw..] -> play.api.UnexpectedException: Unexpected exception[WorkflowDataStoreException: Failed to create schema] at play.api.http.HttpErrorHandlerExceptions$.throwableToUsefulException(HttpErrorHandler.scala:355) Caused by: esri.workflow.exceptions.WorkflowDataStoreException: Failed to create schema at esri.workflow.exceptions.WorkflowDataStoreException$.apply(Exceptions.scala:68)

Environment:

  • OS: Windows Server 2012 R2 Standard
  • ArcGIS Workflow Manager 10.9

Patches applied:

0 Kudos
1 Solution

Accepted Solutions
Ranga_Tolapi
Frequent Contributor

With the help of Esri technical team got to know that, root cause of this issue is the self-signed certificate (without Subject Alternative Name) of the web server (IIS) where Portal and ArcGIS Server web adaptors were installed.

Recreated the self-signed certificate with Subject Alternative Name and bind it to IIS. With this, Workflow Manager connectivity issue from ArcGIS Pro was successfully resolved.

View solution in original post

8 Replies
JFarmer
Esri Contributor

@Ranga_Tolapi 

When you say that the create workflow item process is running for sometime, how long does it go before this error occurs? Are you able to create regular hosted layers in your Portal environment? 

Is there any security software in this environment? If so, what is it? 

All this may help narrow it down a bit.

Thanks,

Jonathan

0 Kudos
Ranga_Tolapi
Frequent Contributor

Create workflow item process took around 65 sec. before the error occurred. Enclosed the trimmed video on the same.

Unable to create regular hosted layer in Portal. Enclosed the screenshot of the error.

0 Kudos
JFarmer
Esri Contributor

Hi @Ranga_Tolapi 

Thanks. It does sound like this may not be Workflow Manager related but an issue with Portal hosted layers itself. When you create a workflow item in the Workflow Manager Web App, we are creating 3 things in your Portal

1. Workflow Item

2. Hosted layer containing all of your data

3. Hosted layer view containing information on your job locations.

I'd recommend you work with Tech Support to get the Portal issues sorted out and then see if that resolves your create workflow item problem. But, until you can create a regular hosted layer in your Portal, this likely won't work either.

0 Kudos
Ranga_Tolapi
Frequent Contributor

Hi @JFarmer 

Thank you.

After multiple attempts of restarting Portal windows service and the machine itself, was able to create Workflow Item successfully.

Now the issue is with connecting to Workflow Item from ArcGIS Pro (version 2.8.3).

Under Workflow pane in Pro, able to select Workflow Manager Portal and can see Workflow item.

Ranga_Tolapi_0-1636684061999.png

However, after selecting the workflow item and clicking on Connect button, getting an error. Please refer to the below screenshot.

Ranga_Tolapi_1-1636684237831.png

 

0 Kudos
Ranga_Tolapi
Frequent Contributor

With the help of Esri technical team got to know that, root cause of this issue is the self-signed certificate (without Subject Alternative Name) of the web server (IIS) where Portal and ArcGIS Server web adaptors were installed.

Recreated the self-signed certificate with Subject Alternative Name and bind it to IIS. With this, Workflow Manager connectivity issue from ArcGIS Pro was successfully resolved.

JFarmer
Esri Contributor

@Ranga_Tolapi 

Good news on the item creation!

For Pro, have you federated your Workflow Manager Server machine using a web adaptor? Or over port 6443? If you used the port, you'll want to switch that to use a web adaptor.

If that isn't it, I'm going to reiterate my suggestion to work with Tech Support. There are some troubleshooting steps they can take to get more information, including setting up logs in Pro. 

Jonathan

0 Kudos
Ranga_Tolapi
Frequent Contributor

@JFarmer 

Initially used ArcGIS Enterprise Builder 10.8.1 for base deployment, later upgraded the deployment using ArcGIS Enterprise Builder 10.9.

Both ArcGIS Workflow Manager Server and ArcGIS Workflow Manager Web App were installed on the same machine that of base deployment.

ArcGIS Enterprise Builder federated ArcGIS Server using web adaptor only, please refer to the below screenshot.

Ranga_Tolapi_0-1636782103876.png

Enabled server roles are:

Ranga_Tolapi_1-1636782709400.png

Note: ArcGIS Pro installed on a separate machine, it got access to "Service URL", but no access to "Administration URL" of above screenshot.

0 Kudos
JFarmer
Esri Contributor

@Ranga_Tolapi 

I don't see anything off in that configuration. ArcGIS Pro should be using that services URL to do what it needs.

I'd say next steps would be setting up and looking at logs in Pro. I've included a screen shot below of what that should be. These are entries into the registry editor on your Pro machine. You'll need to add the WorkflowManager folder and then the entries for the log level and path manually. The path is a location you choose and the level should be set to 5. Once this is setup, open ArcGIS Pro and try to connect.