Select to view content in your preferred language

Publish scene fails - ERROR 001887: Failed to create couchdb database: Failed to execute (Publish Portal Sevice)

7617
2
Jump to solution
01-07-2019 03:19 AM
Harald_ØysteinLund1
Esri Contributor

When we try to publish a 3D scene with ArcGIS Portal 10.6, we are getting the following error:

ERROR 001887: Failed to create couchdb database: Failed to execute (Publish Portal Sevice).

We are using SSL and have tried all of the suggested approaches to handle SSL between ArcGIS Server Host machine and DataStore machine.

1. Adding requesting URLs to trusted sites - not working

2. Enabling SSLv3 - not working

3. Also made sure that writing request also uses SSL. - not working

Turning of SSL is not an option.

Upgrading to 10.6.1 is not an option at this point.

Is there any one else struggling with this out there?

0 Kudos
1 Solution

Accepted Solutions
Harald_ØysteinLund1
Esri Contributor

Yes we have tried this, but meanwhile we have seen that we forgot to run the updatelicense command. After doing so and now got a bit further, but there is a problem with primary/standby issue here. ERROR 001886: Failed to create scene service. ERROR: code 500. This operation must be performed on the primary data store machine. Not allowed on the standby machine. Generic Server Error. Internal server error. Failed to execute (Publish Portal Service).

Oddly everything seems correct set up, but the tilecache datastore and the spatial datastore has different primary machines. It fails when we try to set the same server as primary for both of them, but that fails as well. May be because of the operation may have been interrupted.

After a changing allowed inbound ip to communicate with the two Datastore serveres, missing the ip of each of the datastore servers was the reason for the problem with setting primary/standby of the datastore. So main reason, missing update of license and then the security tightening that was done, had forgot to allow internal communication between the two datastore servers on the datastore port.

View solution in original post

2 Replies
RussRoberts
Esri Notable Contributor

If you have disabled SSLv3 and you are still seeing this issue. 

look at your Internet Explorer privacy settings.  If security level is medium / high it prevent it. To resolve this issue:

 

  1. Stop Server
  2. On the Server machine open Internet Explorer (ensure you login as the server account before opening IE or use Run As different user and log into IE using server account. This is important)
  3. In IE Options dialog go to Security tab and select Trusted Sites
  4. In the Trusted Sites dialog uncheck Require server verification (https) option
  5. Enter server and data store machine http and https URLs as shown below:
    http://<subdomain.domain.com> and
    https://<subdomain.douman.com>
    Add similar URLs for the datastore machine (if installed on a different machine)
  6. Once done re-start server.
Harald_ØysteinLund1
Esri Contributor

Yes we have tried this, but meanwhile we have seen that we forgot to run the updatelicense command. After doing so and now got a bit further, but there is a problem with primary/standby issue here. ERROR 001886: Failed to create scene service. ERROR: code 500. This operation must be performed on the primary data store machine. Not allowed on the standby machine. Generic Server Error. Internal server error. Failed to execute (Publish Portal Service).

Oddly everything seems correct set up, but the tilecache datastore and the spatial datastore has different primary machines. It fails when we try to set the same server as primary for both of them, but that fails as well. May be because of the operation may have been interrupted.

After a changing allowed inbound ip to communicate with the two Datastore serveres, missing the ip of each of the datastore servers was the reason for the problem with setting primary/standby of the datastore. So main reason, missing update of license and then the security tightening that was done, had forgot to allow internal communication between the two datastore servers on the datastore port.