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!
