Missing Template Name (MU) in tasks throws multiple errors "cannot read MU [X][Y], err=[3]"
Article ID: 368565
Updated On:
Products
Issue/Introduction
The "Template name" on a template task throws a lot of errors in the universe.log in case the name introduced on it does not correspond to a management unit defined locally.
Example, we create a template task and set as Template Name "MU_NAME" (that does not exist as MU).
After creating it, we obtain the following three errors in universe.log:
|ERROR|X|IO |pid=p.t| owls_mu_read | cannot read MU [MU_NAME][A000000044], err=[3]
|ERROR|X|IO |pid=p.t| o_mutz_get_mu | Unable to read MU MU_NAME on NODE node_name (error: 600).
|ERROR|X|IO |pid=p.t| o_mutz_mu_to_sys | Unable to get time offset for MU ADRIAN on NODE node_name
The same can occur if we close the Tasks menu in UVC and open again the list of Tasks or if we launch a uxtrace of the node.
Environment
Dollar Universe 6.x and 7.x Application Server (DUAS Node)
Cause
Defect
Resolution
Update to a fix version listed below or a newer version if available.
Fix version(s):
Component: Dollar Universe Application Server (DUAS Node)
Dollar Universe 7.01.01 - Planned to be released end of September 2024
Additional Information
Defect ID: DU_AS-7632
Feedback
