![]() Solution: If this is a dynamically generated configuration file, contact NetIQ Support. The two definitions, however, have different types.Ĭause: The driver configuration file being processed has global variable definitions that could not be resolved. These variables exist in both the source and target Driver Sets. The following Driver Set based global variables could not be resolved: Solution: If this is a dynamically generated configuration file, contact NetIQ Support otherwise, move the element under a element. Tree population components will be ignored.Ĭause: The driver configuration file being processed has a element under a element, which is not permitted. ![]() Tree population is not supported from a Driver Set configuration. Otherwise, edit and correct the configuration file being imported. ![]() Deploy again, then send the trace to NetIQ Support. In the Trace window, select the check box for Include XML Processor Traces. To do this, select Window > Preferences > Designer for IDM Trace > Enable Tracing. Solution: Turn on XML tracing for the Import/Deploy plug-in. The specified driver configuration file does not contain a valid driver configuration.Ĭause: Designer attempted to process a dynamically generated driver configuration file with an invalid format. Identify the incorrect parameter in Designer, correct the setting, and redeploy. Deploy again and analyze the generated driver configuration file to see if all integer attribute values are correct. All integer fields in Designer should validate the content when it is set. The following 'Number Format Exception' was thrown.Ĭause: An integer value in the driver configuration file being deployed is invalid. Attempt to deploy again, then send the trace file to NetIQ Support. This is probably an internal error because driver configuration files are dynamically generated by Designer for deployment. The following 'XML DOM Exception' was thrown.Ĭause: The Driver Configuration XML document is incorrectly formatted. Solution: Import a driver configuration file. The file cannot be imported.Ĭause: The Driver Configuration file being imported from the file system is a valid XML document but is not a valid driver configuration file. The XML contained the file named is not a driver configuration file. Solution: Fix the Driver Configuration file format. Ĭause: The Driver Configuration file being imported from the file system does not contain a valid XML document. The driver configuration file is not a valid XML document.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |