search cancel

No schedule information returned for AgentBasedPolicySerializer item. This is probably because no schedule information has been defined or the schedule is disabled.

book

Article ID: 244427

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

The customer noticed the following messages in the NS logs when trying to import software to MDM (Modern Device Management):
 
  1. No schedule information returned for AgentBasedPolicySerializer item: 'Jabber' (e96b6eb9-01a1-4e65-a416-cfff5d091f10) This is probably because no schedule information has been defined or the schedule is disabled.
  2. Supplied xml file 'E:\Altiris 8.0 Client Management suite\Workspaces\Api\uploads\34c1ec95-7a13-4031-bd2f-f318073ee1df\CiscoJabberMac-12.8.2.302955.pkg' is not valid
  3. File : E:\Altiris 8.0 Client Management suite\Workspaces\Api\uploads\34c1ec95-7a13-4031-bd2f-f318073ee1df\CiscoJabberMac-12.8.2.302955.pkg is not valid xml.

Environment

ITMS 8.6 RU2

Cause

These messages are trace level and internal. Our process is just trying to identify different types of Installation Files

Resolution

Those messages are by design for now. Those are logged as trace (these are not errors /warnings). These messages are not impacting functionality. The customer should ignore those messages as they are trace level, not an error. 

When a package is importing, our code tries to understand what package we have and tries to parse file for different installation file types, ding it one by one until type is found. If type does not match, it writes trace to log saying that "type is not matching because package is not valid XML". When type matches, it does not write anything to log. That's why we see those messages - it is just one of attempts to identify package installation file type.

Additional Information

https://bsg-jira.broadcom.net/browse/CRE-10473