failure in creating an Investigation

[Felix10546]

Hi all,

    I am previously using ArcGIS knowledge til April 2022. It worked fine when I created an investigation. However, I sudden cannot login the my portal in May so I reinstalled the enterprise. After that, I encountered

Creation failed
ERRO: Create Service error: Failed to create the service 'Hosted/new_investigation.KnowledgeGraphServer'., Generic Server Error., Internal server error.

I tried to days to fix this but still cannot tackle it.

My settings:

There are two machines used:

Machine1 (base,  enterprise10.9.1)                  

- portal                                                                   

- server                                                                 

- datastore (relational, tile)

Machine2 (knowlege server 10.9.1)

- knowledge server [federated to portal]

-  datastore (graph) [point to machine1 domain]

https://knowledge.local:6443/arcgis/manager/

In the portal -> federation setting, there is no error after validation.

I have also assigned knowledge server license to admin and a new member. 

I have imported and used a server cert for the 2 domains:

- IIS port:443,

- base.local:7443: portal/portaladmin   (machine->edit)

- base.local:6443: arcgis/admin               (machine->edit)

- knowledge.local:6443: arcgis/admin   (machine->edit)

- base.local:2443:          (through command ./updatesslcertificate.bat <certname>.pfx <password> <alias>)

----------------------------

I only failed to change the certificate in knowledge.local:2443, when I use the same command,

An error message saying that "The data store may not have been initiated" but I see it is running in services. I guess it is only for relational database like the updatelicense tool?

======================================

Clearer pic are attached.

Thank you for everyone trying to solve my problem.

[MandarPurohit · Accepted solution]

Hi,

I recommend applying Knowledge server patch to your ArcGIS Servers, and Pro 2.9 patch 3  to your Pro.

Also, verify the graph store is working:

1) Run c:\Program Files\ArcGIS\DataStore\tools\describedatastore.bat and verify that the graph store is listed in the results.

2) Open a new browser on the Knowledge server machine (knowledge.local) and navigate to https://<datastore_machine_name>:9829   This should open a database web page asking for login info.

If these steps do not address the problem, then we can take a look at the server logs.

[Felix10546]

Hi MandarPurohit, the patch helps! It is the best moment in this week!

I followed the instruction to install  ArcGIS Server 10.9.1 Setup Program Patch before the patch for  Knowledge server patch

I can now successfully create an investigation.

I get 3 questions. If they are answered, I will be much relieved.

Q1. A message "337047686" pop up. Is it because I am using a self-signed certificate? I never seen this in the past.

Does it affect the functionality if security is not considered?

==========================

Q2. I checked with the datastoredescribe.bat. It shows:

I see it pointed to my host server for base enterprise but the portal url is ""

I checked that I already configured the datastore 

does it matter?

Q3. I reached port 9829 successfully but failed to login

I tried the portal account / server account / datastore account.

Is it enough if a page appear on this port?

[MandarPurohit]

1) The certificate verification error could be related to the self signed certificate.  This needs to be fixed. Could you please try a domain or CA certificate?

2) The graph store looks good. Portal url "" would not affect the functionality.

3) Yes, we were only checking if the server machine can reach the database. That page is enough.

[Felix10546]

I see. You made it clear. Thank you with your detailed explanation.

[xingchenc]

Hi Felix,

To solve the "certificate verify failed" error you can download your self-signed certificate and installed on your local machine (the same machine that has ArcGIS Pro installed). When installing, be sure to import the certificate to the "Trusted Root Certification Authorities" category. This should make the error message disappear.  

[Felix10546]

Thank xingchenc for the solution. The warning message disappeared now using the self-signed certificate.