I’m using the Windows Task Scheduler to run a SmartConnect 2018 or SmartConnect 21 Integrations. Most of them execute successfully as expected, however one map does not. The Windows Task Executes successfully, however the map itself doesn’t actually execute. Why does this one not run successfully like the other?
In this case, the user had created the Windows Task the same as the rest of them – however for this map – the name had a space in it, which is not typical.
The eOne.SmartConnect.RunMapConsole.exe is a command-line interface that takes one parameter – the map name.
With a space in the map name, this is interpreted by Windows as two parameters – “MAP” and “SPACES”. When SmartConnect parses the command line, it uses the first parameter as the map name and here it would try to execute the map named “MAP” which does not exist.
The Windows Task does execute successfully as it started the exe, so that is why it reports “success” even though the map itself doesn’t run.
The solution to this problem is to put the map name in double quotes per the screenshot. This way, Windows interprets the entire contents of the string as one parameter – now when the eOne.SmartConnect.RunMapConsole.exe pulls the first parameter, it is “MAP SPACES” and not “MAP” and the integration named “MAP SPACES” will be executed as expected.
