Novell ACCESS MANAGER 3.1 SP1 - EVENT CODES Manual page 28

Event codes
Hide thumbs Also See for ACCESS MANAGER 3.1 SP1 - EVENT CODES:
Table of Contents

Advertisement

Event Code
100902085
100902086
300902087
100902088
100902089
100902090
100902091
100902092
100902093
100902094
28
Novell Access Manager 3.1 SP1 Event Codes
Description
Error - Exception thrown in the
creatElement method of
vcdn.application.sc.core.DeviceConfig
Error - Exception thrown in the
setLastModified method of
vcdn.application.sc.core.DeviceConfig
Warning - Exception thrown in the
getLastScheduledWorkID method of
vcdn.application.sc.core.DeviceGroupMan
ager
Error - Could not get version from device.
Make sure it is running properly.
Error - NamingException thrown in the
importDevice method of
vcdn.application.sc.core.DeviceManager
Error - VException thrown in the
importDevice method of
vcdn.application.sc.core.DeviceManager
Error - InvocationTargetException thrown
in the importDevice method of
vcdn.application.sc.core.DeviceManager
Error - Exception thrown in the
importDevice method of
vcdn.application.sc.core.DeviceManager
Error - Could not find esp cfg SCC to
remove in cluster container.
Error deleting the trusted IDP entry for
ESP.
Remedy
Cause: Internal XML error.
Action: Submit the
app_sc.0.log
resolution.
Cause: Internal XML error.
Action: Submit the
app_sc.0.log
resolution.
Cause: The last executed command status
ID could not be read.
Action: Non-fatal error.
Cause: Could not get version from device.
Action: Make sure the server component is
running properly, then click Repair Import to
resolve the issue. Otherwise, submit the
app_sc.0.log
file for resolution.
Cause: Error importing device.
Action: Make sure the server component is
running properly, then click Repair Import to
resolve the issue. Otherwise, submit the
file for resolution.
app_sc.0.log
Cause: Error importing device.
Action: Make sure the server component is
running properly, then click Repair Import to
resolve the issue. Otherwise, submit the
app_sc.0.log
file for resolution.
Cause: Error importing device.
Action: Make sure the server component is
running properly, then click Repair Import to
resolve the issue. Otherwise, submit the
app_sc.0.log
file for resolution.
Cause: Error importing device.
Action: Make sure the server component is
running properly, then click Repair Import to
resolve the issue. Otherwise, submit the
app_sc.0.log
file for resolution.
Cause: Error deleting improperly imported
server.
Action: Non-fatal error.
Cause: Error accessing config store.
Action: Ensure the config store is
functioning properly. Otherwise, submit the
app_sc.0.log
file for resolution.
file for
file for

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents