You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It will then create a directory in the user profile: C:\Users\username.cinc\local-mode-cache\cache\cinc-client-running.pid
This causes issues, when the user profiles are managed on a share (E.g. when it can't create that directory). The command will then throw an error and stop.
In those cases it is better to use the command: cinc-solo -j C:\cinc\templates\arcgis-enterprise\10.9.1\windows\arcgis-enterprise-primary.json (as it used to be with Chef Client).
The possibility to use the command cinc-solo was not documented in the wiki, nor on cinc webpage.
So please add this information (possibility of using the cinc-solo command) to the single machine installation documentations.
The text was updated successfully, but these errors were encountered:
Thanks @jesa-esrich, this is an excellent suggestion! We will look to improving the wiki documentation\readme's to include a note that cinc-solo is also a valid command to use.
In the arcgis-cookbook wiki for deploying a base ArcGIS Enterprise deployment on a single machine, the command prompt for running the cinc client is:
cinc-client -z -j arcgis-enterprise-primary.json
It will then create a directory in the user profile: C:\Users\username.cinc\local-mode-cache\cache\cinc-client-running.pid
This causes issues, when the user profiles are managed on a share (E.g. when it can't create that directory). The command will then throw an error and stop.
In those cases it is better to use the command:
cinc-solo -j C:\cinc\templates\arcgis-enterprise\10.9.1\windows\arcgis-enterprise-primary.json
(as it used to be with Chef Client).The possibility to use the command
cinc-solo
was not documented in the wiki, nor on cinc webpage.So please add this information (possibility of using the cinc-solo command) to the single machine installation documentations.
The text was updated successfully, but these errors were encountered: