Veritas Configuration Manager 6.1 Release Notes

Article:TECH66330  |  Created: 2008-01-29  |  Updated: 2008-01-30  |  Article URL http://www.symantec.com/docs/TECH66330
Article Type
Technical Solution


Environment

Issue



Veritas Configuration Manager 6.1 Release Notes

Solution



Release Notes
RELEASE (BUILD 6.1.1703.0)
21st NOVEMBER 2008
Copyright © 2008. Symantec Corporation. All rights reserved.


Symantec, the Symantec logo, and Configuration Manager are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any.

THIS DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be "commercial computer software" and "commercial computer software documentation" as defined in FAR Sections 12.212 and DFARS Section 227.7202.

Symantec Corporation
20330 Stevens Creek Blvd.
Cupertino, CA 95014
www.symantec.com

Build Definition
These are the release notes for Veritas Configuration Manager. The following information fully captures and describes the context within which this build of software was produced.


External Name
Veritas Configuration Manager

Build #
Veritas_Configuration_Manager_Server_6.1.1703.0
Veritas_Configuration_Manager_Agent_6.1.1703.0

Build Version
6.1.1703.0


Configuration Manager Upgrade Information
The Veritas Configuration Manager 6.1 product includes an upgrade kit for existing 6.0 agents.

Refer to the Upgrading Veritas Configuration Manager section of the Veritas Configuration Manager Installation Guide for additional information about upgrade prerequisites and considerations.

New Features
The Veritas Configuration Manager 6.1 release contains the following new features.

New Agent Platforms

Veritas Configuration Manager now includes new Agent platform support for:

HP-UX 11.23 PA-RISC 64-bit

HP-UX 11.23 Itanium 64-bit

Red Hat Enterprise Linux 4.0 64-bit multiprocessor

RedHat Enterprise Linux 5.0 SP0, Intel x86, 32-bit and 64-bit multiprocessor

Windows Server 2008 Standard and Enterprise SP1, 32-bit and 64-bit

Refer to the Supported Platforms topic in the online Help for additional information about the platforms Veritas Configuration Manager supports.

Licensing Changes

The licensing functionality has been changed from the last release. In VCM 6.1, the licensing model is one of trusted compliance. If your license is not in compliance, you will be informed that you are out of compliance by messages in the log files and an alert in the UI for the Server. Despite being in violation of the license terms, VCM will continue to be fully functional.

Veritas Configuration Manager licensing controls two aspects of VCM: the length of the license term and the number of nodes under management. Contact your Symantec Customer Care representative if you need a license or your license is no longer compliant.

Refer to the Veritas Configuration Manager Licensing topic in the online Help for additional information about licensing.

New Database Support

Veritas Configuration Manager now includes database support for SQL Server 2005, certified on Standard edition.

New Default Profile

For the 6.1 release, a new default profile has been created which is less aggressive than the old default profile. The new profile has some change tracking features turned off, and various other configuration parameters are set to less aggressive values. This new default profile is intended to reduce system resource usage on the Agent. This change will not affect existing agents; it will only affect newly activated agents and those explicitly assigned to the new default profile.

DAS

The Domain Administration Server is supported on Windows 2003 only.

Upgrade Support

The product will only support upgrade from VCM 6.0 to 6.1.

The Domain Administration Server supports upgrade from 1.1 to 1.2

Issues Resolved in the Current Release



Issue:
A crash was seen on Windows 2003 computers after the VCM Agent was installed.

Fix Description:
On Windows 2003 machines with the VCM Agent and TrendMicro Messaging Security Suite installed, a crash was seen. The Trend Micro driver (tmtdi.sys) caused compatibility issues with the VCM driver, which caused the crash. The VCM driver was updated to work around the incompatibility issue.

Tracking ID:
1107705


 

Issue:
On Windows VCM agents, the driver was generating notifications whenever a removable media volume (such as CDROM or USB drive) was added or removed from the system. The notifications could trigger excessive CPU consumption on the agent due to rebuilding the primary filter matrices.

Fix Description:
The driver no longer generates notifications on removable media volume mount and unmount

Tracking ID:
1178040


 

Issue:
The default profile assigned to Agents during installation is very aggressive, which can result in performance issues.

Fix Description:
A new default profile has been created which is less aggressive. The new profile has some change tracking features turned off, and various other configuration parameters are set to less aggressive values. This change will not affect existing agents; it will only affect newly activated agents and those explicitly assigned to the new default profile.

Tracking ID:
1262662


 

Issue:
Many of the shipping models in the 6.0 model file started with an underscore. Customer created models start with an underscore by default, which made it difficult to distinguish between the two types of models when the customer model files are upgraded manually.

Fix Description:
The underscores at the start of the shipping model files have been removed. The shipping models are now easy to distinguish from customer models.

Tracking ID:
1157270


 

Issue:
On Windows machines, rename operations on files were not being filtered from change tracking even though the path to the file was excluded from change tracking. If rename operations are frequent, this caused performance issues on the machine.

Fix Description:
Rename operations are now filtered properly and are excluded from change tracking when the path to the file is excluded.

Tracking ID:
1174061


 

Issue:
Crashes were experienced on Windows 2003 Agents.

Fix Description:
The driver registry callback code was not handling context correctly between driver disconnects. This issue was fixed and crashes are no longer occurring on Windows 2003 Agents.

Tracking ID:
1118113


 

Issue:
When there are multiple IP addresses assigned to one NIC card on an AIX machine, only one of the IP addresses was discovered and shown in the DNS tab. The address discovered was the first address shown in the ifconfig output.

Fix Description:
Multiple IP addresses are now discovered and shown on the DNS tab.

Tracking ID:
1281091


Known Issues
The following tables disclose information about product issues and workarounds that might be helpful to Veritas Configuration Manager users. Workarounds and tracking identification numbers are provided where applicable.

Upgrade
Known Issue
Description

Issue:
Agent upgrade may take a significant amount of time if Server is under load.

Description:
Upgrading an Agent while the server is under load may cause the agent to be unresponsive for a significant amount of time. Do not stop the upgrade process, the agent will recover fully and the upgrade process will finish.

Workaround:
Do not cancel the upgrade process.

Tracking ID:
889598


 

Issue:
If a Linux server is under load during an agent upgrade, the upgrade may fail.

Description:
On a Linux server that is under load during the agent upgrade process, the installation of the reliagent package into the RPM package database may time out, and the upgrade will fail.

Workaround:
Run the upgrade process again.

Tracking ID:
889830


 

Issue:
Configuration Manager Server may fail to start after upgrade on Windows.

Description:
During the standard Windows Server upgrade process, the Configuration Manager Server restarts automatically once upgrade is complete. After the upgrade, the Configuration Manager Server may fail to start automatically if the files it needs to access are locked.

Workaround:
Wait for the lock on the files to expire and restart the Server manually.

Tracking ID:
891048


 

Issue:
Agents may not appear to be connected in the UI after a build to build upgrade on Solaris 2.8 with the minimum OS installed.

Description:
Once the Agent has upgraded successfully it can appear disconnected in the UI because the following areas are not functional: Agent administration functions, Applications contents tab browsing, and Agent diagnostic functions.

Workaround:
Restart the Agent from the command line on the server.

Tracking ID
891081


 

Issue:
If the AT daemon is not running during a Linux Agent upgrade, the upgrade hangs.

Description:
On Linux computers, the Agent upgrade attempts to restart the Agent by queueing an AT (or cron) job. The AT job is dependent on the AT daemon running during upgrade. If the AT daemon is not running the upgrade will hang and the Agent will not restart.

Workaround:
Ensure that the AT daemon is running when you do an upgrade on a Linux Agent. You can also manually restart the Agent after upgrade is complete

Tracking ID:
1391448


 

Issue:
After a VCM Server upgrade on Windows 2003, you may see errors in the last screen of the upgrade.

Description:
On Windows 2003 Server upgrades, although the upgrade is successful, you may see the following errors in the last screen of the upgrade:

- Insertion into unupgrade tree failed:  Veritas Configuration Manager Server
- Insertion into unupgrade tree failed: Configuration Manager Server
- Insertion into unupgrade tree failed:  Configuration Manager Common Files
- Insertion into unupgrade tree failed:  Configuration Manager Software
- Insertion into unupgrade tree failed:  EmxVersions
- Insertion into unupgrade tree failed:  Generic Files
- Insertion into unupgrade tree failed:  WinBinFiles
- Insertion into unupgrade tree failed:  Common Files
- Insertion into unupgrade tree failed:  WinCommonBinFiles
- Insertion into unupgrade tree failed:  JDK
- Insertion into unupgrade tree failed:  Tomcat

The errors appear to be caused by a corrupted "VPD registry" maintained by InstallShield. To find the VPD registry, you can search on the machine where server is installed for a file called "vpd.properties" - typically it is located in "c:\program files\common files\installshield\universal\common\Gen1".

Workaround:
The upgrade is still successful and this issue can safely be ignored as long as the VCM Server Service remains running, you can log in to the VCM UI, and you can see that the InstallShield VPD registry error has occurred.

Tracking ID:
1425936


 

Issue:
After HPUX 11.11i Agent upgrades from 6.0 to 6.1, the EmxWatchdog file is seen in the common\bin directory.

Description:
The common\bin directory is supposed to be empty after an upgrade from VCM 6.0 to 6.1, but the EmxWatchdog file is found in that directory after upgrade.

Workaround:
None. The file has no effect on the functioning of VCM, and can be safely deleted or ignored.

Tracking ID:
1443787


 

Issue:
On HP-UX 11.23 IA, build to build upgrades performed through the UI fail.

Description:
Attempts to run a build to build upgrade on an HP-UX 11.23 IA Agent through the UI will fail.

Workaround:
Perform build to build upgrades on HP-UX 11.23IA via the command line. This issue will be addressed in the next release.

Tracking ID:
1390228


Domain Administration Server
Known Issue
Description

Issue:
The VCM Server does not receive the message to remove itself from the Domain Group when the DAS and the VCM Server times are not synchronized.

Description:
When the time is not synchronized between a VCM Server and the DAS, the VCM Server will not get the message that it has been removed from the DAS. The VCM Server Domain Group activation state will remain "Approved" and all of the data that has been replicated to this VCM Server will still be stored in the database and displayed through the UI.

Workaround:
 Ensure that the VCM and DAS times are synchronized.

Tracking ID:
1036361


 

Issue:
Updated VCM Domain information does not get replicated in the DAS until the VCM Server is restarted.

Description:
When a VCM Server joins a DAS, VCM Domain Member information is sent to the DAS. In VCM, if you then update the VCM Domain Member information, the changes are not replicated to other Domain Members and are not visible in the DAS UI. Once you restart the VCM Server, the changes are replicated.

Workaround:
 Restart the VCM Server to update its Domain information on the DAS.

Tracking ID:
1036286


 

Issue:
After upgrading from DAS version 1.1 to DAS version 1.2, the VCM Domain Administration Server is listed twice in the Add/Remove Programs list.

Description:
There are two listings for the VCM Domain Administration Server in the Add/Remove Programs list after performing an upgrade from DAS 1.1 to DAS 1.2.

Workaround:
None. There is no negative impact to the functioning of the Domain Administration Server, and the Domain Administration Server can be uninstalled successfully.

Tracking ID:
1442416



Dependencies/Dependency Maps
Known Issue
Description

Issue:
A single unknown may be replicated in multiple Dependency Maps.

Description:
When two domains replicate the same unknown the two unknowns are not rolled up into one Dependency Map. Instead, they may be repeated in multiple maps.

Workaround:
Install an Agent on the unknown box and wait for the information to replicate to the domains. The Dependency Map will update with the appropriate Application and Dependency information.  The unknown dependency will disappear after the dependency lifetime has timed out.

Tracking ID:
891098


 

Issue:
After upgrade, network connections report as being down.

Description:
The Agent will update its dependency statistics during the restart that follows an Agent upgrade. At this point the crawl has not yet completed, so the Agent will therefore have no known connection state to send. Because of this, all the dependency stats are displayed as being Down, despite the fact that they are actually Up.

Workaround:
Select the Update Stats button on the Dependencies tab of the Server Detail panel to get the correct network statistics. Additionally, the statistics will automatically be corrected at the next scheduled Agent dependency update (by default, every 30 minutes).

Tracking ID:
891709


 

Issue:
Applications with over 1,000 dependencies causes application failed errors in the UI.

Description:
When you attempt to view a dependency map for an application with over 1,000 dependencies, you will get an application failed error in the UI, and the dependency map will not display.

Workaround:
None.

Tracking ID:
1031666


AppSense


Issue:
Removing an image from the Image Exclusion Filters list for an agent's AppSense settings may not be immediately represented in the Contents tab for the Component. Therefore, there may be inconsistencies with what is listed in the Image Exclusion List and what is shown in the Contents tab.

Description:
When you add an image to the Image Exclude Filters list for an agent's AppSense, the change is immediately reflected in the Contents list for that AppSense Component. However, when you subsequently remove the image from the Image Exclude Filters list the change is not always immediately represented in the Contents tab for the AppSense image.

Workaround:
Refresh the Contents information for the AppSense Component. After a few minutes, the Contents data should be correct. This issue will be resolved in a future release.

Tracking ID:
889366


Agent
Known Issue
Description

Issue:
Agent continues to observe (poll) the load balancer after the load balancer is removed.

Description:
If you configure an agent(s) to observe the Load Balancer and then you remove the load balancer from the UI, the agent(s) continue to poll the load balancer.

Workaround:
After you remove the Load Balancer from the UI, remove the Load Balancer from each agent configured to monitor it.

Tracking ID:
886210


 

Issue:
Packages have specified files change tracked, but do not have them displayed as contents.

Description:
If multiple packages are specified as sharing a set of files, those files are change tracked, with each package being assigned a record for each event. If the contents of these packages are browsed, however, the files are not shown as owned by any of the packages.

Workaround:
None.

Tracking ID:
N/A


 

Issue:
Ambiguous ownership of non-specified files for packages causes tracking of those files to be excluded.

Description:
If a Package owns a set of files and directories, and additional files and directories are present in subdirectories of the owned set, then the additional files are tracked. However, if another package (even a package installation of the same name, but different version) claims ownership of the specified files, making them now shared files, then the additional files and directories are classed as ambiguous, and no package tracks those files.

Workaround:
None.

Tracking ID:
N/A


 

Issue:
Severe error exceptions can occur on Windows Agents which cause Configuration Manager to shut down.

Description:
A problem with the Windows COM server can occasionally cause severe error exceptions to occur on Windows Agents. Once the error occurs, Configuration Manager will shut down. Configuration Manager makes repeated attempts to start back up. These start up attempts will fail.

The following text is part of the error message associated with this issue:

java.lang.Exception: getSystemInfo failed: Exception CSystemException: 8004100A : WMI_Init()

Workaround:
In some cases, a system reboot may clear up the problem. Otherwise you should contact Microsoft support to resolve the problem.

Tracking ID:
890352


 

Issue:
LPP package exclusion filters require a * to take effect. This differs from the behavior of the other Agent exclusion filters.

Description:
LPP packages that are added to the package exclusion list for an Agent will still be detected by Configuration Manager unless a "*" is appended to the end of the package name. For example, adding csm.client to the package exclusion list will not result in that package being excluded. Adding csm.client* will result in that package being excluded.

Workaround
Add a * after the LPP package name.

Tracking ID:
890524


 

Issue:
Agent user mode JVM hangs occur on AIX machines.

Description:
The AIX JVM version has been updated to J2RE 1.4.2 IBM AIX build ca142-20050609, and the hang may still occur. The cause of the hang is a known IBM issue with signal handling, covered by IBM case number 73443BL6Q PMR 73443.

Workaround:
The Agent is restarted when a JVM hang occurs.

Tracking ID:
891364


 

Issue:
Shut down of a zone on Solaris 10 may cause unmount failures on an Agent.

Description:
When a zone on a Solaris 10 machine is shutdown improperly, such as from a reboot or a halt, you may see unmount failures on the Agent.

Workaround:
Shut down the Configuration Manager Agent prior to a halt or a reboot of a zone.

Tracking ID:
891987


 

Issue:
Directory paths longer than 260 characters cause a warning message.

Description:
When the Agent attempts to crawl a file with a path longer than 260 characters, a warning message is written to the Agent log files.

Workaround:
None.

Tracking ID:
995963


 


Issue:
When restarting an Agent, it can take a few minutes before the Agent reconnects.

Description:
The amount of time that an Agent takes to reconnect will vary depending on a number of factors, including the amount of configuration data present and the speed of the disks in the system, among other things. An Agent may take slightly more time than you expect to reconnect, but this does not indicate a problem.

Workaround:
None. The Agent will reconnect successfully after a few minutes.

Tracking ID:
1034674


 

Issue:
Adaptive exclusion functionality does not apply for configuration data change history events.

Description:
If a configuration file that is being parsed for configuration data changes an excessive number of times, that configuration file will be put on the adaptive exclusions list. Files on the adaptive exclusions list are not change tracked and history events are not reported until the frequency of changes to that file has dropped. Currently, even though a configuration file is on the Adaptive Exclusions list, changes to the configuration data within that file still get reported as history events.

Workaround:
To ensure that the changes do not get reported as change history, edit the ConfigDataSet for the file and add or edit the configDataQuery so that the specific configuration data properties are excluded.

Tracking ID:
1009425


 

Issue:
After Agent restart and a dependency statistics update, the Agent to Server dependency state may be reported as down, when the connection is actually up

Description:
When an Agent is restarted and its dependency statistics are updated, the dependency state between the Agent and Server may display the connection as down. Although the connection is reported as down, its state is actually up. The Agent to Server connection is not reported as being up until the Agent detects the connection again in real-time.

Workaround:
None.

Tracking ID:
898944


 

Issue:
Agents running on Solaris with Secure Extensions may crash.

Description:
Running VCM Agents on a Solaris machine which is configured with the Base Security Module (also known as Secure Extensions) is not supported. A Solaris machine configured with the Base Security Model and an installed VCM Agent may crash. The security features of Secure Extensions conflict with our kernel driver.

Workaround:
Do not install Secure Extensions on a Solaris Machine on which the VCM Agent is also installed.

Tracking ID:
1198318


 

Issue:
Setting primary filters for an Agent that excludes multiple paths to a directory (i.e., */logs or */tmp) can cause a large amount of memory to be used when the Agent starts up.

Description:
When a multi-path exclusion filter is created on an Agent to exclude many instances of a directory from the file system crawler and system observer, the Agent uses a large amount of memory upon startup. This large amount of memory usage may cause out of memory errors.

Workaround:
Do not create multi-path exclusion filters on your Agents. Instead, create explicit exclusion filters to alleviate the large amount of memory used at Agent startup.

Tracking ID:
1063939


 

Issue:
RedHat Agent platform support limitations

Description:
RedHat Enterprise Linux 5.0 supports Network Access Control Lists, but this feature is not supported in VCM 6.1. Privilege changes affecting Access Control Lists are not tracked or reported.

New File Systems/clustering (XFS and AFS) are not supported.

Workaround:
None

Tracking ID:
None


Mounted Drives


Issue:
On Windows, the Configuration Manager agent does not dynamically observe events on remote mounted file systems.

Description:
The Configuration Manager agent fails to observe changes on remote mounted file systems. Consequently, change tracking, file dependencies, and dynamic recognition of newly installed applications and components based on files located on a remote mounted file system do not appear in the UI until the next time the agent crawls the file system.

Workaround:
None. Will be resolved in a future release.

Tracking ID:
886446


 

Issue:
When an automounted filesystem becomes unmounted, and monitor automounts is set to false, the filesystem remains monitored.

Description:
After the automounter has unmounted a filesystem, and the monitor automounts agent configuration is set to false, the Filesystem tab shows the filesystems as being unmounted and monitored, and the applications detected on those filesystems remain in the data shown on the tab.

Workaround:
None. Will be resolved in a future release.

Tracking ID:
889182


 

Issue:
Mapped drives are not supported on Windows 2003 or 2008.

Description:
With Windows 2000, it is possible for the Configuration Manager agent to detect mapped drives, and for these to be monitored. With Windows 2003 and 2008, this behavior is no longer available.

Workaround:
None.

Tracking ID:
889562


 

Issue:
Processes running on mounted drives are discovered as AppSense components.

Description:
Normally, some processes running on an un-mounted drive would be discovered by existing models and some would be discovered by the AppSense feature. For mounted drives, all processes are discovered as AppSense Components. Additionally, processes discovered on a mounted drive cannot be modeled.

Workaround:
None. Will be resolved in a future release.

Tracking ID:
889601


 

Issue:
Activity on a mounted drive may not be detected on AIX Agents.

Description:
If a mounted drive was not detected at startup, Configuration Manager will not detect activity on that drive because it is not aware of it. This occurs when the driver starts and a remote filesystem is not mounted, which means that Configuration Manager is not aware of the filesystem.

Workaround:
Configuration Manager re-checks to verify what filesystems are mounted every 10 minutes. Once Configuration Manager detects a filesystem it begins tracking it. No user action is required.

Tracking ID:
890666


UI


Issue:
Contents of previously excluded LPP packages do not display in the UI.

Description:
When you remove a package from the LPP package exclusion filter, you are unable to view the contents of these packages even though Configuration Manager has discovered them.

Workaround:
Restart the agent and the previously excluded package contents will be available.

Tracking ID:
890706


 

Issue:
The DNS Domain field for remote Domains sometimes displays incorrectly in the UI.

Description:
If the value for the DNS domain field for a Server is blank in the database, when you look at that Server as a remote Domain, the DNS field may show as blank, instead of  "not present" which is what is expected.    

Workaround:
None.

Tracking ID:
890742


 

Issue:
The UI may become unresponsive on Solaris 10 Servers.

Description:
Occasionally, the UI may become unresponsive on Solaris 10 Servers and Tomcat errors are written to the log.

Workaround:
None.

Tracking ID:
891956


 

Issue:
Some dialogs, such as the Save As dialog for Server Logs, will appear in the UI and then disappear.

Description:
When attempting to access pop up dialogs, such as the Save As dialog for logs, the UI behavior may not be as expected. This issue is related to the security settings in Internet Explorer. By default, the automatic download security setting in Internet Explorer Version 6.0.3790.1830 is set to disable. This causes the problems with pop up dialogs.

Workaround:
Adding the VCM Server URL to the trusted sites list will fix this issue:

1. Go to Tools - Internet Options.
2. Click the Security tab.
3. Click "Trusted Sites".
4. Click the "Sites" button.
5. Uncheck "Require server verification (https:) for all sites in this zone".
6. Add the VCM server URL to the list of trusted sites.
7. Click "Close".

Tracking ID:
892057


 

Issue:
Poor VCM UI display at a high zoom setting in Internet Explorer 7.0.

Description:
When viewing the VCM UI with Internet Explorer 7.0, setting the zoom level higher than 100% causes poor UI display.

Workaround:
Keep the zoom level at 100% for the best UI display.

Tracking ID:
892336


 

Issue:
On occasion, when logged into multiple http sessions with the same VCM login information on Internet Explorer, you may be involuntarily logged out of one session.

Description:
When viewing the VCM UI with Internet Explorer, if you open a browser window or tab which reuses an existing HTTP session, other windows using the same session can be invalidated. This causes you to be logged out of VCM. When you open a browser window or tab and a new HTTP session is created, other existing windows or tabs are not affected.

When viewing VCM in Internet Explorer, you cannot determine when Internet Explorer will reuse an HTTP session and when it will create a new session. Therefore, different scenarios may cause the involuntary logout. For example, in Internet Explorer 7.0, you may have one VCM session open in one tab, and then login to the same VCM Server using the same login ID in another tab. In this situation, one of those sessions may get bumped.

Workaround:
Only open one VCM session at a time in Internet Explorer.

Tracking ID:
933233


 

Issue:
The DNS Domain field can display inconsistent data.

Description:
If the name you have set for your machine on your system and the name of the machine in DNS are not the same, the DNS Domain field in the Servers Detail Panel General/Architecture tab may display inconsistent data.

Workaround:
Be sure to set your machine name on your system and the machine name in DNS the same.

Tracking ID:
892350


 

Issue:
When viewing the UI with IE 7.0 on Windows 2003 machines, the detail panel may not display properly.

Description:
Infrequently, the detail panel in the main or administration UI may fail to display properly on Windows 2003 machines which are using IE 7.0 as the browser. When the detail panel fails to display, you will see the following error message:

"IE cannot display the page"

Workaround:
Navigate to the page again, and the UI will display properly.

Tracking ID:
1315484


Modeling


Issue:
On occasion, exceptions may be thrown which result in the Agent failing to crawl. This could occur on any platform.

Description:
The  model file can't support regular expressions where two variable assignments are made in succession. An expression like the one shown in the following example would cause the exception to be thrown:

...foo)={firstvar})={secondvar}

Once the exception is thrown, the Agent fails to complete its crawl.

Workaround:
In the model file, add an expression between assignments that will not match. The following example shows how the previous example could be resolved:

..foo)={firstvar})((/)?))={secondvar}

The introduced expression (in bold) is a conditional expression, so it is OK that it never matches.

Tracking ID:
1020117


 

Issue:
Model files containing blank values cause problems with model loading.

Description:
If your model file contains a blank value attribute for a property, then Agent upgrade and model import will fail.

Workaround:
Do not include blank values in your model file.

Tracking ID:
1047810


 

Issue:
The Windows generic model may not detect some installed applications.

Description:
The Windows Generic Model discovers most but not all applications installed using the Microsoft Installer technology. Some installed applications might not be detected

Workaround:
None.

Tracking ID:
91705


 

Issue:
The configuration data tab is not editable for Configuration Data Source models in the Model Wizard.

Description:
In the model.xml file, if a configDataSet model has either a <minimum/> or <detect/> element in it, the configuration data is not editable through the Model Wizard. If Configuration Data Source models do not contain the <minimum/> or <detect/> elements, they may be editable through the Model Wizard.

Refer to the Modeling Guide.pdf for additional information.

Workaround:
Edit the Configuration Data Source model in the model.xml file.

Tracking ID:
1067716


Other


Issue:
Changes to the property space identifier for Weblogic/iPlanet configuration data discovered through packageDetail models will not generate configuration data change history events.

Description:
In Configuration Manager, the Weblogic/iPlanet Propertyspace name that is used to group attributes is also shown as an attribute. If this value is changed, the expected behavior would be for a configuration attribute change event to be generated in the history. However, a change event is not generated, because Configuration Manager views the property space as being removed and re-added instead of changed.

Workaround:
The default 6.0 version of the VCM model file replaces the packageDetail models for the Weblogic domain models with a configDataSet model. This will resolve the issue and configuration data change history events will be generated when the property space identifier changes. As a workaround for the iPlanet model, replace its associated packageDetail models with the new configDataSet models (part of new Deeper Application Configuration feature) and configuration data change history events will be generated when the property space identifier changes.

Tracking ID:
889490


 

Issue:
If a FIFO is part of an application, a comparison run on that Application may not be accurate.

Description:
When a FIFO is part of a modeled application and a comparison is run on that Application, you will see differences appear in the Comparison even though none exist.

Workaround:
None. This issue will be fixed in a future release.

Tracking ID:
891199


 

Issue:
If the user does not have the correct database permissions, the Configuration Manager Server install may be successful but experience problems during operation.

Description:
If an Oracle user does not have the Create Sequence and Create Type permissions, the Configuration Manager installation is successful but Configuration Manager will not function properly. You will not see dependency details and traces will appear in the logs.

Workaround:
None.

Tracking ID:
890816


 

Issue:
AIX systems may hang when executing a large number of forced unmounts.

Description:
The forced unmount process has a race condition, which could cause the system to hang if a large number of forced unmounts are executed.

Workaround:
None.

Tracking ID:
891407


 

Issue:
Installation on all Unix operating systems requires binary calculator package.

Description:
InstallShield version 11 requires binary calculator package to be installed on all Unix operating systems.

Workaround:
None.

Tracking ID:
891421


 

Issue:
On all supported Solaris platforms, if the SUNWxcu4 package is missing the Configuration Manager Agent or Server installation will not work.

Description:
Our minimum package set does not include the SUNWxcu4 package. If this package is missing installation of Configuration Manager will not be successful without performing the following workaround.

Workaround:
df $TMP (df /tmp to get free disk blocks of /tmp)
FREE_DISK_BLOCKS=[number of free disk blocks]
export FREE_DISK_BLOCKS
run installer again (./clarity-server_5.0.1103.0-SunOS-sparc.bin -is:tempdir /tmp -console)

Tracking ID:
891439


 

Issue:
The Configuration Manager UI reports the wrong permissions on Solaris machines.

Description:
On Solaris boxes we will report the Exclusive File Lock permission bit as a Set Group ID without execute permissions.

Workaround:
None.

Tracking ID:
891244


 

Issue:
On Solaris 10, the Configuration Manager Server may fail to properly stop the EmxWatchdog process.  

Description:
At times, attempts to stop the Configuration Manager Server were not successful because the EmxWatchdog process failed to stop. The Configuration Manager Server needs to stop during the uninstall and upgrade process, and the failure of EmxWatchdog to stop means that these procedures will not be successful.

Workaround:
Manually kill the EmxWatchdog process and continue on with the upgrade or uninstallation.

Tracking ID:
892041


 

Issue:
When memory is viewed with top on HP-UX, Agents can at times appear to be using a large amount of memory.

Description:
Some HP-UX Agents may appear to be using large amounts of memory due to the version of top on a machine. Some versions of top report on Java processes with large libraries, and this causes the memory usage numbers to appear to be very large.

Workaround:
None.

Tracking ID:
892071


 

Issue:
If you upgrade the operating system from a major version to major version without uninstalling the Agent, this caused the system to crash.

Description:
Upgrading the operating system for a machine on which the Agent is installed from a major to major version of Solaris (for example, 2.8 to 2.9), caused the system to crash. This action is not supported.

Workaround:
Remove the Agent before upgrading the Operating System from a major to a major version. Once the upgrade is complete, re-install the Agent on the machine.

Tracking ID:
961640


 

Issue:
Agents running against RPM 4.2.1 could experience RPM pkg database locking issues.

Description:
Due to issues with RPM 4.2.1, Agents using that RPM version could experience locking issues. For additional information on the issue, refer to https://rhn.redhat.com/errata/RHBA-2004-501.html.

Workaround:
Upgrade to RPM 4.2.3 or higher.

Tracking ID:
892365


 

Issue:
If certain patch revisions are installed on Solaris systems with the VCM Agent installed, the VCM Agent may not start.

Description:
SPARC Platform

Solaris 8 with patch 109147-36 through 109147-39 and without patch 109147-40
Solaris 9 with patch 112963-21 through 112963-24 and without patch 112963-25
Solaris 10 with patch 117461-03 through 117461-07 and without patch 117461-08

x86 Platform

Solaris 8 with patch 109148-36 through 109148-39 and without patch 109148-40
Solaris 9 with patch 113986-17 through 113986-20 and without patch 113986-21
Solaris 10 with patch 118345-05 through 118345-13 or 121208-01 and without patch 121208-02

Workaround:
If one of the patches that causes problems is installed on a Solaris system, install the corresponding fixed version, or a later version. For additional information on this problem, refer to:

Sun Document ID : 101995, which can be found on http://sunsolve.sun.com

Tracking ID:
1000680


 

Issue:
The initial synchronization of the integration program after an adapter has initialized causes a severe error to be written to the logs. This error only appears if there is remote data (because that VCM Server is connected to the DAS).

Description:
A severe error is written to the Server log files during the initial synchronization after an adapter restart. However, the synchronization works correctly, and the data is transferred without problems. This error can safely be ignored.

Workaround:
None.

Tracking ID:
1039347


 

Issue:
When a single consistency check is scheduled to run more than once at the same time, the consistency checks continue running and do not complete, and the database deadlocks.

Description:
The deadlock issue occurs when a single consistency check has more than one scheduled task which call for that single consistency check to be run more than once at the same time. The consistency check run cannot complete in this situation, and any other consistency checks scheduled to run subsequently are stuck in the queue.

Workaround:
The VCM Server must be restarted to clear the deadlock. Additionally, the tasks that are scheduled to run at the same time should be rescheduled to run at different times so this situation does not occur again.

Tracking ID:
1025462


 

Issue:
Running a repaired install of VCM can cause damage to your database.

Description:
Installing VCM over an existing VCM installation can cause a loss of data and/or damage to your database.

Workaround:
None.

Tracking ID:
892309


 

Issue:
Occasionally, the Dependencies tab for Server or Application snapshots can take a significant amount of time to display.

Description:
The Dependencies tab for Server and Application snapshots can take more time than expected to display, and in the case of Server snapshots with many dependencies, it may not display at all.

Workaround:
Run Oracle database statistics and the performance of the snapshot Dependencies tab will improve.

Tracking ID:
924640


 

Issue:
HPUX Agents were running in driverless mode after Agent reinstallation.

Description:
When reinstalling VCM versions with the same build number on HPUX systems, the install will be successful, but the Agent will start up in driverless mode.

Workaround:
When you uninstall VCM on an HPUX machine, restart the machine before reinstalling VCM.

Tracking ID:
972451


 

Issue:
When a consistency check was run against a pre 6.0 Agent, and that Agent is later upgraded, there is no indication that the consistency check results may be invalid.

Description:
When a consistency check is run against a pre 6.0 Agent, you are notified in the UI that you have selected an "old" Agent. Your consistency check will run successfully, but you may get results which show differences which may not be what you expect. Your results may show differences where differences do not actually exist. In VCM 6.0, a software comparison allows you to exclude files and directories, but the pre 6.0 Agent does not have the capability to exclude those same files, and it will therefore return those files as present, which will show up as a difference in the consistency check results.

This notification that an Agent is "old" helps you determine whether the differences that are showing for in a consistency check are actually valid. When you create a consistency check that is run against a pre 6.0 Agent, and that Agent is then upgraded to VCM 6.0, you are not notified that the consistency check was created when the Agent had not been upgraded yet. Because of the differences between the way pre 6.0 and 6.x consistency checks were created, you may see invalid results for that consistency check, but will not have any notification of this in the UI.

Workaround:
None.

Tracking ID:
1022125


 

Issue:
Installation on Unix systems was not successful without enough space in the /var/tmp directory.

Description:
Installation could not complete successfully on Unix systems that did not have enough available space in the /var/tmp directory. In addition to the space required for the installation, the /var/tmp directory should have a minimum of 200MB of available space.

Workaround:
Ensure that you have a minimum of 200MB of available space in your /var/tmp directory.
If you don't have enough space under /var/tmp, you can redirect where the installer extracts temporary files by using the option -is:tempdir <directory>

Tracking ID:
892358


 

Issue:
When the propertySpace attribute specifies a blank group in a CDS model, the UI displays the text: {No Name}.

Description:
When you create a ConfigDataSet with two slashes as the start of your property space definition, it is treated as an empty group and the text {No Name} appears in the UI, instead of what you had specified as your propertySpace name. For example, if you specified a propertySpace of "//configNoFile_Group", the top level group will be {No Name}, when you were expecting it to be "/configNoFile_Group".

Workaround:
Set the propertySpace attribute in your configDataQuery for the associated configDataSet, and do not use // before the name.

Tracking ID:
1029053


 

Issue:
When changes are made to a Symlink, the differences are not displaying correctly in Comparison and Consistency Check results.

Description:
The UI for comparison and consistency check results is inconsistent in how differences in either the name of the Symlink or the target directory of the Symlink are displayed. For example, you could change the name of a Symlink, after a snapshot had been taken, and then run a comparison on it. The results of a comparison should show that there are differences, but the main level will not show any differences because it is comparing the target of the Symlink, not the name. If you expand the directory, the details will show that there are differences, due to the name change.

With Consistency Check results, there is no way to expand the data, so this difference would not be visible at all.

Workaround:
None.

Tracking ID:
1005191


 

Issue:
Symlinks are not identified as Symlinks in the UI for Unix Packages.

Description:
In the VCM UI, Symlinks for Unix Applications are identified as being symlinks by displaying in the following way: foo.txt -> /opt/JRUN_SOL/changehistory.pl. For Unix Packages, Symlinks do not display with an arrow to indicate that they are Symlinks, and instead appear to be the same as regular files. The Symlinks for Unix Packages still show the properties of the target, such as file size, permissions, etc.

Workaround:
None.

Tracking ID:
1036416


 

Issue:
When files that are part of a Unix Package but are located in a directory outside of any of the Unix Package's installation directories, are excluded from a Consistency Check, invalid differences occur.

Description:
For example, say you have two Unix Packages on two different Servers that are identical. You go into a Consistency Check definition and exclude a file, which happens to be in a directory outside of any of the Unix Package's installation directories. When the Consistency Check runs, differences show in the results - even though both packages are identical. Simply excluding the file which resides outside of the installation directories from the Unix Package has caused invalid differences to appear.

Workaround:
If you are seeing invalid differences, remove exclusions from the directory showing invalid differences.

Tracking ID:
1037556


 

Issue:
Setting the Frequency of the Database Purge to 0 causes the Edit Purge dialog to become inaccessible.

Description:
In the Edit Purge dialog, there is a configuration parameter which determines how frequently (in days) database purge is run. If you change this setting to 0, the database purge functionality is disabled, and the Edit Purge dialog becomes inaccessible. When the Edit Purge dialog is inaccessible, there is no way to turn database purge functionality back on from the UI.

Workaround:
To re-enable database purge functionality:

1.  Shut down the server
2.  Delete the emx.properties.alt file
3.  Edit the emx.properties file to change the value of the following field from 0 to 1:

.com.relicore.framework.dbmgr.datamgr.dbpurgemgrconfig;interval=1

4.  Restart the server

Tracking ID:
1048035


 

Issue:
Running database purge twice in a row can cause a UI error on page.

Description:
After running a database purge from the VCM UI, immediately running another database purge may causes a UI Error on Page.

Workaround:
Click in another area of the product, such as the Navigation Tree on the left side of the screen, to clear the page error. If you click on another server admin tab and click back to the database tab to perform another purge, you may see the "Stop Purge" button enabled, rather than the "Purge Now" button. To fix the problem, click "Stop Purge" and satisfy the dialog to confirm the stop purge. At that point, the "Purge Now" button will be displayed.

Tracking ID:
1046956


 

Issue:
Screen pop urls and port numbers sent with notifications can be incorrect when the VCM Server uses https.

Description:
If your VCM Server is configured to use https, the screen pop urls and port number information sent with the notification can be incorrect.

Workaround:
None.

Tracking ID:
1002162


 

Issue:
Configuration data change history events are not generated from configDataSet models that only use bound variables.

Description:
Configuration data change history events are not generated for configuration data discovered through ConfigurationDataSet models that use only bound variables.

Workaround:
If you would like Configuration data change history events to be generated, use a packageDetail model with the bound variables.

Tracking ID:
1027098


 

Issue:
Certain Internet Explorer settings cause the gold software selection dialog to hang when creating a consistency check.

Description:
If your Internet Explorer settings are configured to check for new versions of temporary internet files on "Every visit to the page", the gold software selection dialog will hang when you are creating a consistency check definition.

Workaround:
Do not configure your Internet Explorer settings to check for new versions of temporary internet files on every visit to the page.

Tracking ID:
1005124


 

Issue:
Removing a multi-channeled USB device without using the unmount command from a machine on which VCM is installed caused the machine to crash.

Description:
When a multi-channeled USB device was physically removed from the usb port without first running the unmount command, a machine with VCM installed crashed.

Workaround:
Be sure to unmount a multi-channeled USB device from the machine before physically removing it from the usb port.

Tracking ID:
1025846


 

Issue:
When a VCM Server is removed, consistency checks which use that Server as the Gold Server appear to be deleted in the UI.

Description:
When you create a consistency check and use a Server as the Gold Server (either as a Snapshot or as a Live Server), and then remove the Gold Server - subsequent runs of that consistency check will indicate in the Consistency Check Detail panel that the Consistency Check has been deleted.

In the case of the live gold server, the Consistency Check should actually show up as damaged (because of the missing Server), not removed. In the case of the snapshotted gold server, the status should not be damaged or removed, because the snapshot is looking at the system at the moment in time that the snapshot was created, not the current configuration.

In addition, scheduled tasks based on the consistency checks will fail, and will display an indication that the consistency check was deleted.

Workaround:
None.

Tracking ID:
1048278


 

Issue:
In some cases, there may be no property space defined for configuration data. Unix packages do not have property spaces defined for configuration data, but this situation may occur for other types of software as well. For software items like this, Consistency Check will not display configuration data results when there are differences.

Description:
For example, a consistency check which is set up to compare the configuration data of a Unix package will not display results if there are differences found. If there are differences between the two packages you will see the following message:

No data is available to compare because of a problem fetching data from one or both sides of the comparison

However, if there are no differences found between the packages, you will see a message indicating that there are no differences.

Workaround:
None.

Tracking ID:
1038523


 

Issue:
After sorting the Models Summary panel multiple times in a row, the login screen is displayed in the Models Summary panel.

Description:
When you sort the Models Summary panel multiple times in a row (usually two to three), the Models Summary panel can be replaced with the login screen. You are logged out and must log back in to VCM again.

Workaround:
Wait to click on the page again until it is fully sorted and loaded.

Tracking ID:
1045376


 

Issue:
An error message in the log files may make it appear that there is a problem with the database.

Description:
At times, you may see the following error message in your logs:

WARNING ConnectionPool

getConnection: Database under heavy use; created an overflow connection in pool

Dependency in thread SubscriptionDispatcher0-4.

Although this message seems to indicate that there is a problem with the database, this is not the case. The database is functioning fine, and the message can safely be ignored.

Workaround:
None. You can safely ignore this message.

Tracking ID:
1257273


 

Issue:
Running Symantec BackUpExec on the same machine as VCM can cause errors.

Description:
If you are running Symantec BackUPExec on the same machine where the VCM Agent is running you may see the following error message in the System Application Log:

FCB::RemoveAlternateStreams: Operating system error 6(The handle is invalid.) occurred while creating or opening file 'C:\Program Files\Symantec\Backup Exec\Data\BEDB_Dat.mdf'.

Diagnose and correct the operating system error, and retry the operation.

The error occurs on the backup service startup.

Workaround:
None. These errors are benign and can be safely ignored.

Tracking ID:
1212693


 

Issue:
Application virtualization will not be recognized by change tracking on Windows 2008 computers.

Description:
Windows 2008 includes Registry Virtualization technology which enables legacy applications to run in non-administrator accounts and results in redirecting registry write operations for HKEY_LOCAL_MACHINE\Software to another physical registry location based on the user account name. The VCM registry change tracking feature would show the virtual path and not the physical path for any changes. The result is that change tracking data would appear as though the application is not virtualized even though it is.

Workaround:
None.

Tracking ID:
1218039


 

Issue:
Installer log files on Windows 2008 display the time in Greenwich Mean Time (GMT).

Description:
When installing VCM on Windows 2008, the installation logs display time stamps in GMT. This occurs even if the computer VCM is being installed on is set to Eastern Standard Time.

Workaround:
None.

Tracking ID:
1303043


 

Issue:
Deleting the common\bin directory after installation would cause problems with the discovery of the VCM components.

Description:
After installation or upgrade of the VCM Server, Agent, or DAS components, a common\bin directory is created. The common\bin directory is empty, but it must be left in place or problems will occur with discovery of the components. It is important that the common\bin directory is left in place.

Workaround:
None. Do not delete the common\bin directory.

Tracking ID:
1315848


 

Issue:
An error occurs during shutdown on Solaris 10 machines.

Description:
During the shutdown process on Solaris 10 machines, the following error is generated:

RemoteAdminTimer] 07/11/08 09:26:16.402 INFO     KernelLogger Kernel shutdown initiated at 7/11/08 9:26 AM by com.relicore.framework.remoteadmin.RemoteAdminMgr$StopAgentTask.run()

[WorkItemThread_0] 07/11/08 09:26:29.321 SEVERE   ObserverServiceLogger processNotification: Observer CrawlerManager failed with java.lang.NullPointerException: null

-----------

java.lang.NullPointerException at  com.relicore.analysis.rules.defaultapp.DefaultApplicationAttributionMgr.attribute Resource(DefaultApplicationAttributionMgr.java:433)
at com.relicore.analysis.rules.defaultapp.DefaultApplicationMgr.attributeResource
(DefaultApplicationMgr.java:499)
at com.relicore.analysis.rules.AgentRuleMgr.attributeResource
(AgentRuleMgr.java:3662)
at com.relicore.analysis.rules.AgentRuleMgr.processNotification
(AgentRuleMgr.java:1285)
at com.relicore.analysis.NotificationHandler.processNotification
(NotificationHandler.java:677)
at com.relicore.framework.data.NotificationManagerImpl.publish
(NotificationManagerImpl.java:118)
at com.relicore.framework.data.DataService$1.processNotification
(DataService.java:148)
at
com.relicore.xapi.notification.NotificationListenerMulticaster$NotificationListener
Filter.filterAndDispatchNotification
(NotificationListenerMulticaster.java:141)
at
com.relicore.xapi.notification.NotificationListenerMulticaster.processNotification
(NotificationListenerMulticaster.java:256)
at com.relicore.observer.service.ObserverService.processNotification
(ObserverService.java:1743)
at com.relicore.observer.service.AbstractObserver.processNotification
(AbstractObserver.java:675)
at com.relicore.observer.service.AbstractObserver.notification
(AbstractObserver.java:662)
at com.relicore.observer.service.AbstractObserver.notification
(AbstractObserver.java:508)
at com.relicore.observer.system.crawler.CrawlerManager.crawlElementExists
(CrawlerManager.java:1119)
at
com.relicore.observer.system.crawler.process.ProcessCrawlerFactory$Notification
Adapter.crawlEnded(ProcessCrawlerFactory.java:279)
at com.relicore.observer.system.crawler.process.ProcessCrawlerTask.run
(ProcessCrawlerTask.java:79)
at com.relicore.framework.kernel.ThreadMgr$WorkItemTaskAction.run
(ThreadMgr.java:127)
at java.security.AccessController.doPrivileged(Native Method)
at com.relicore.framework.kernel.ThreadMgr$WorkItemThread.run
(ThreadMgr.java:217)

Workaround:
None. This error is harmless and can be safely ignored.

Tracking ID:
1362073


 

Issue:
On Windows 2000, 2003, and 2008  computers severe Javascript Exception errors may be reported while crawling when an rt.jar file is found to be corrupt.

Description:
An error is reported to in the VCM log file if your environment contains an rt.jar file that is corrupt. Sun resolved a problem between the JRE 1.4 and 1.5 where the 1.4 JRE did not recognize corrupted rt.jar files.  

The following is an example of the errors that may be seen:

[Parser Thread Group-1] 07/17/08 08:29:12.117 SEVERE   ScriptEnv : WrappedException call JavascriptScriptParser[ EMX_SunJREVersionDetect_JS ]: invalid entry CRC (expected 0x0 but got 0xaa3f5b76)

[Parser Thread Group-1] 07/17/08 08:29:12.117 WARNING  ParserCrawlerController log: Parser ParseTaskData[directive: ParserCrawlDirective[Parser = EMX_SunJREVersionDetect_JS, accessors = {rtJarFile=ParserAccessor[name = rtJarFile, resource = c:/program files/javasoft/jre/1.3.1_02/lib/rt.jar, type = file]}, args = {}, config data query hash = 0], fail count: 0, crawl id: 133 "ParserCrawlDirective[Parser = EMX_SunJREVersionDetect_JS, accessors = {rtJarFile=ParserAccessor[name = rtJarFile, resource = c:/program files/javasoft/jre/1.3.1_02/lib/rt.jar, type = file]}, args = {}, config data query hash = 0]", user name: null, session user name: null] encountered the following error: com.relicore.plugin.parser.ParserException: java.util.zip.ZipException: invalid entry CRC (expected 0x0 but got 0xaa3f5b76) : invalid entry CRC (expected 0x0 but got 0xaa3f5b76) : invalid entry CRC (expected 0x0 but got 0xaa3f5b76)

Workaround:
None - this is a fix to the JRE.

Tracking ID:
1364160


 

Issue:
Running the Agent installation in graphical mode on Unix machines causes errors to display.

Description:
When you install the Agent in graphical mode on Unix machines, you will see errors in the console about missing .gif file errors. The error messages are seen when installing the product on platforms where the System look and Feel is Motif. The error messages vary slightly from one operating system to another, but the following errors are representative of what you may see:

com.sun.java.swing.plaf.motif.MotifLookAndFeel/icons/UpFolder.gif not found.
com.sun.java.swing.plaf.motif.MotifLookAndFeel/icons/ListView.gif not found.
com.sun.java.swing.plaf.motif.MotifLookAndFeel/icons/Computer.gif not found.
com.sun.java.swing.plaf.motif.MotifLookAndFeel/icons/File.gif not found.

Workaround:
None. The Agent installation is successful and the errors can be safely ignored.

Tracking ID:
1365406


 

Issue:
The Agent's Parsing State at Restart and Parsing State for Restricted Parsers at Restart parameters settings do not always reflect the parsing state upon Agent restart.

Description:
If you explicitly set the Agent's Parsing State or Parsing State for Restricted Parsers parameters to disabled, the Agent will correctly disable parsing and the parsing will remain disabled after Agent restart unless you explicitly set the parameter to enabled again. However, the Parsing State at Restart and Parsing State for Restricted Parsers at Restart parameters, which are not editable, is always set to "enabled"

This can cause confusion because it may appear that, when you have disabled parsing on an Agent, once that Agent restarts and you see that the Parsing State at Restart parameter is set to "enabled" - when the Agent starts that parsing would be enabled. In fact, parsing for that Agent will remain disabled after restart.

Workaround:
The Agent's parsing state upon restart is reflected in the setting for the Parsing State and Parsing State for Restricted Parsers parameters. Look at the settings for those two parameters to determine the parsing state and restricted parsers parsing state.

Tracking ID:
1396614


 

Issue:
The EMX_PATCH table can get very large, and is not purged when database purge is run.

Description:
Some customers may experience a large number of rows in the EMX_PATCH table, and the issue is not solved by running a database purge because this table is not purged when a purge is run. The performance of the VCM UI may be negatively affected because of the large number of rows in the EMX_PATCH table.

Workaround:
None.

Tracking ID:
1265668


 

Issue:
When a tracked hard disk volume (or an mount point) is dynamically added or removed from the system, the VCM agent might need to recalculate the primary filters used by the driver.

Description:
When a tracked hard disk volume (or an mount point) is dynamically added or removed from the system, the VCM agent might need to recalculate the primary filters used by the driver. Note that this does not include CDROM, USB drives and other removable media. On the systems with high volume mount/unmount rate this might result in a noticeable CPU consumption shown by the agent (EmxWatchdog process).

Workaround:
None.

Tracking ID:
1178044


 

Issue:
Process exclude filters do not fully filter items with spaces in the names.

Description:
When primary filters are specified which have spaces in their names, the process is not discovered and change tracked (which is working as designed), but it does appear in Top Analysis and it can affect the machine's performance.

Workaround:
To ensure complete filtering, make sure that your filters do not include spaces in the names.

Tracking ID:
1061992


 

Issue:
On HP-UX 11.11 Agents may exceed the default maximum per process thread limitation.

Description:
HP-UX 11.11 has a default maximum per process thread limitation of 64. This can potentially cause problems for the Agent because its thread count approaches that limit, especially during a crawl. Crawling adds threads to the existing total. Exceeding the thread limit causes the following error:

   java.lang.OutOfMemoryE


Legacy ID



316968


Article URL http://www.symantec.com/docs/TECH66330


Terms of use for this information are found in Legal Notices