When using the RunAs user for a job that will run on a Windows Agent the following error is encountered: Application Integrator CM: UCM0001 = Run as password can't be empty From the logs you will see the following messages: 2016-10-12 13:16:29,465 INFO [Thread-94] (CLIRunLayer.java:902) - In XML's run as parameter ^M 2016-10-12 13:16:29,471 INFO [Thread-94] (CLIRunLayer.java:905) - Found matching account field: AI_RUNAS ^M 2016-10-12 13:16:29,476 INFO [Thread-94] (CLIRunLayer.java:908) - account field value: Corp\User-IMS-BMCRunas1 ^M 2016-10-12 13:16:29,482 INFO [Thread-94] (CLIRunLayer.java:863) - getRunAsUserPass ^M 2016-10-12 13:16:29,487 INFO [Thread-94] (OperationsAssist.java:675) - getExecTypeElem for exec-type value: ^M 2016-10-12 13:16:29,493 INFO [Thread-94] (OperationsAssist.java:682) - No execType found. Using first by default ^M 2016-10-12 13:16:29,498 INFO [Thread-94] (CmAccountDefinitionWrapper.java:77) - getField ^M 2016-10-12 13:16:29,503 INFO [Thread-94] (CmAccountDefinitionWrapper.java:78) - fieldName: AI_RUNAS_PASS ^M 2016-10-12 13:16:29,509 INFO [Thread-94] (CLIRunLayer.java:875) - getRunAsUserPass ended. ^M 2016-10-12 13:16:29,514 WARN [Thread-94] (ExecutorsHandler.java:197) - got CmException: Application Integrator CM: UCM0001 = Run as password can't be empty original message: Run as password can't be empty |
The below workaround is only necessary if you apply Fix Pack 3 after creating an Application Integrator Job Type that requires run as user on Windows. When creating the Job Type it should create the AI_RUNAS_PASS field for use in the Connection Profile section. If this field isn't automatically added to the new job type, ensure that AI Fix Pack 3 has been installed on the Control-M Enterprise Manager Server and client. As needed, there is a workaround for this problem, as follows: Workaround:
|