nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Server site creation using SSM

MikaelJ

Hey,

currently we are exploring the options of automatic deployments of ArcGIS Enterprise in AWS.

For some internal regulations we cannot use Powershell DSC, Cloudformation, AMIs, Chefcookbooks.

We've decided to try with PowerShell scripts and SSM.

Currently via SSM I am failing with running createsite.bat. It won't work.

I am able to create with the same PowerShell snippet locally running from RDP or just via regular browser.

Does anyone have any insights what may be causing this?

Specs:

ArcGIS Server 11.5

AWS EC2

service account running the ags service: LocalSystem

Regards,

Find more posts tagged with

Accepted answers

MikaelJ

Hey @GlenterpriseUK @ArchitSrivastava ,

yes, I've tried with properties files as an argument the result was exactly the same.

I was able to move on, with rest/admin HTTP call to create ArcGIS Site.

Right now, I am observing similar situation, but with ArcGIS DataStore.

Can you shed the light how one can troubleshoot SSM in ArcGIS Enterprise context?

edit:

--- STDOUT ---
"Error: AGSDATASTORE variable is not set."

After setting the value:
$env:AGSDATASTORE = $InstallDir

it ran flawlessly, so SSM was missing this env setting which is regularly being set during the installation process.

Thank you for your commitment @ArchitSrivastava @GlenterpriseUK

Regards,

All comments

MikaelJ

Hey @GlenterpriseUK @ArchitSrivastava ,

yes, I've tried with properties files as an argument the result was exactly the same.

I was able to move on, with rest/admin HTTP call to create ArcGIS Site.

Right now, I am observing similar situation, but with ArcGIS DataStore.

Can you shed the light how one can troubleshoot SSM in ArcGIS Enterprise context?

edit:

--- STDOUT ---
"Error: AGSDATASTORE variable is not set."

After setting the value:
$env:AGSDATASTORE = $InstallDir

it ran flawlessly, so SSM was missing this env setting which is regularly being set during the installation process.

Thank you for your commitment @ArchitSrivastava @GlenterpriseUK

Regards,

archit_esri

Hello @MikaelJ ,

I agree with @GlenterpriseUK point about the SSM session context is where I would start as well.

Since the same script works when you run it from RDP, or when you create the site through the browser, it feels like the issue may be less about createsite.bat itself and more about how the command is being run through SSM.

A few things I would check:

What account the SSM command is actually running under, likely NT AUTHORITY\SYSTEM
Whether that account has the permissions you expect
Whether you are calling createsite.bat using the full path
Whether the script sets the working directory before running createsite.bat
Whether the config store and server directories paths already exist
Whether the account running the command can create or write to those folders
Whether any path uses a mapped drive, since those usually do not exist in a non-interactive SSM session
Whether passwords or special characters are being handled differently when passed through SSM/PowerShell
Whether stdout, stderr, and the exit code are being written to a log file

I would also try using a createsite.properties file instead of passing everything directly in the SSM command. That might make the test cleaner and avoid some quoting or escaping issues, especially with passwords and folder paths.

For example:

Set-Location "C:\Program Files\ArcGIS\Server\tools\createsite"
.\createsite.bat -f "C:\Temp\createsite.properties" *> "C:\Temp\createsite_ssm.log"

If the same properties file works from RDP but fails through SSM, that would help narrow it down to the SSM execution context, permissions, working directory, or folder access, rather than the site creation parameters themselves.

Hope it helps!

GlenterpriseUK

Hi @MikaelJ,

What is the error that you get via SSM?

Have you tried runnning createsite.bat with the following parameters [-u <arg>] [-p <arg>] [-d <arg>] [-c <arg>] or have you also tried with the option of having a createsite.properties file containing parameters as specified here: https://enterprise.arcgis.com/en/server/11.5/install/windows/silently-install-arcgis-server.htm#:~:text=An%20example%20of%20the%20createsite.properties%20file%3A

I have a feeling that the issue you are observing is likely happening because SSM runs your script in a non-interacive session under the system account which behaves differently from an RDP session.

Regards,

Glen

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.