CMS: Automatic Scripts failed to run [Line: 7/8] (null)

Doc ID:    SOLN229504
Version:    12.0
Status:    Published
Published date:    08 Aug 2017
Updated:    02 Oct 2018


We create automatic CMS script, but cannot running well, we get error [Line: 7/8] (null)

This issue happens for both Supervisor R16.3, R17 & R18 versions

Problem Clarification

Error messages from the cvs log file:

05-21-2013 07:13:05 Begin Script Host

05-21-2013 07:13:05 CreateServer: TEST AutoLogWrite NORMAL sUserName=$DEFAULT$, sServer=, sLanguage=ENU

05-21-2013 07:13:05 CreateServer: TEST AutoLogWrite MINIMAL sUserName=$DEFAULT$, sServer=, sLanguage=ENU

05-21-2013 07:13:41 Can't create Server ObjectLogin failed.

05-21-2013 07:13:41 (null)

[Line: 7/8] (null)

05-21-2013 07:13:44 Error 2147614977 occured within the Script Host Engine.

05-21-2013 07:13:44 End Script Host

05-21-2013 12:03:00 Application Terminated



We have duplicated the same in the lab. Basically we need to use other CMS Supervisor User ID(Administration User ID) here instead of the “cms” user, as “cms” user has the Shell permission, it will bring the autoscripts to Solaris Shell instead of the CMS application.


In CMS Supervisor Tools -> Options -> Scripting -> Set User to set up a different User ID (Administration User ID) here instead of “cms”, then test the autoscripts again, the issue should be resolved after this.
Check to make sure this user is able to log in.  In at least one instance, the password for the script user had expired.

Also make sure to use "automatic login" instead of "manual login" and user reset user name and password in Scripting option as shown above.

Can also be resolved by updating CMS Supervisor to R18 MA.48.

2: Another option was to test by going back to old password for the user

Additional Relevant Phrases

CMS auto scripts crash when run manually or via Windows Task Scheduler. Automatic Scripts failed to run with error: (null) [Line: 8] (null) acsauto

Please rate this article

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy