SAP Agent 24.4.4 fails to start with "LogService is not set" when using -I INI parameter.
search cancel

SAP Agent 24.4.4 fails to start with "LogService is not set" when using -I INI parameter.

book

Article ID: 437685

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine Automic SaaS

Issue/Introduction

After upgrading the Automic SAP Agent to version 24.4.4, the agent fails to start. The following symptoms are observed:

  1. LogService Error: When starting the agent (either with or without the -I switch), the process terminates with the following exception:
Exception in thread "main" java.lang.IllegalStateException: LogService is not set.
        at com.automic.util.logging.api.LogServiceFactory.getLogger(LogServiceFactory.java:28)
        at com.uc4.ex.logging.LogService.log(LogService.java:81)
        at com.uc4.ex.logging.LogService.log(LogService.java:144)
        at com.uc4.ex.sap.UCXJR3X.main(UCXJR3X.java:74)

Environment

  • Component: SAP Agent (UCXJR3X)
  • Version: 24.4.4
  • Upgrade Path: Upgraded from version 24.2.0

Cause

There is a non-ASCII character in the INI file.

Resolution

 

The INI file contains an invalid non-ASCII character—specifically, the Unicode replacement character (Hex UTF-8 bytes EF BF BD)—on line 263:

; This section only affects Job objects. File Transfer or FILE Event�Objects are not affected.

 

Once this corrupted character is removed, the SAP agent starts as expected. The corrected line should read as follows:

; This section only affects Job objects. File Transfer or FILE EventObjects are not affected.