Select to view content in your preferred language

Issue while federating notebook server with portal

195
2
Jump to solution
a month ago
wizgis
by
Frequent Contributor

Hi All,

We are on ArcGIS Enterprise and Notebook server 11.3 and we have two machines with following set-up:

  • Machine 1 has the base deployment (DataStore, Server, Portal & Web Adaptor of Portal and Server) as well as WebAdaptor of notebook server
  • Machine 2 has notebook server successfully installed and configured 

On federating the notebook server site with portal we are getting the following error message: "Unable to load ArcGIS Server backing store and/or the ArcGIS Server license information". We went through the following article : https://support.esri.com/en-us/knowledge-base/error-unable-to-load-the-arcgis-server-backing-stores-... and imported the domain certificate (server & root) from IIS to the admin page of notebook server. 

We then unfederated the notebook server site and federate it again however, still getting the same error. We also restarted the windows service of ArcGIS Server still getting the same error.

On checking the logs following error message is consistently observed:  An error trying to webhook configured on server <FQDN of notebook server> 

Any inputs on this would be really helpful.

 

 

0 Kudos
1 Solution

Accepted Solutions
wizgis
by
Frequent Contributor

Hey @Leena_Abdulqader 

Thank you for sharing your insights. 

The issue was resolved after importing/installing the certificates (Server & Root) on the machine itself.

View solution in original post

0 Kudos
2 Replies
Leena_Abdulqader
Frequent Contributor

Hello @wizgis, this might be silly, but what URL do you use to federate? 

Can you access the Portal URL from the Notebook server machine? and vice versa? 

Can you confirm that this port is open 11443? If not, allow it and restart the Windows services.

Clean the cache of the browser and/or use a different browser. 

Hope that helps.

 

 

0 Kudos
wizgis
by
Frequent Contributor

Hey @Leena_Abdulqader 

Thank you for sharing your insights. 

The issue was resolved after importing/installing the certificates (Server & Root) on the machine itself.

0 Kudos