Part No. 816-4731-11
This document provides late-breaking information not included in the documentation for the Capacity Reporter 6.0.1 (Capacity Reporter) software. See the documentation provided with Capacity Reporter for additional installation and use information.
*** Special Global Reporter Update ***
Installation and Configuration Issues
Patch for Quota Used Percentage Errors
If you receive error #80040e57 or #2147749463 while running the Global Reporter software, download and install Patch ID#[TBD] from www.sunsolve.sun.com.
The following are known installation and configuration issues relating to this release of Capacity Reporter:
Windows NT
file MSINET.OCX may be required for installation of NAS or
NetWare devices
The Windows NT file MSINET.OCX is provided on the product CD at \capacity\i386\MSINET.OCX. If you receive an error message informing you this file is missing, copy it from the product CD.
Additional Capacity Reporter Software Prerequisites
To check the compatibility setting, run sp_dbcmptlevel against the SQL server.
Prerequisite Check Does Not Fail on Incorrect Windows NT
Service Packs
The prerequisite
check fails to display an error message when it encounters a Windows NT Service Pack lower than SP5, which is the required Service Pack for an installation of Capacity Reporter software.
Do not Change the Web Destination Location When Installing Capacity Reporter
During installation, the installation procedure prompts the user
for the SRM Web destination location. For the installation to work
properly, do not change the destination location after
clicking Next on the
Choose Destination Location
dialog box. Otherwise, the installation starts prematurely.
Capacity Reporter Database and SQL Maintenance
Upgrade to SQL 7.0 SP2 for SQL maintenance tasks to work properly. If you do
not want to upgrade, use SQL Enterprise Manager to remove the CkCat qualifier
from the SQLMAINT command. Contact Customer Support for more information on editing the SQL maintenance task.
Ksh (Korn Shell) is Required When Installing a Capacity Reporter Agent on a Linux
Machine
As a prerequisite, a Linux machine must have
ksh installed on it before a successful Capacity Reporter Agent installation on that machine can
occur. The latest pdksh rpm
can be downloaded from the Red Hat
web site.
Solaris Agent Upgrade Causes Disks to be Rediscovered
If you upgrade from a version
5.0.5 (or earlier) Solaris agent to the version 6.0 Solaris agent, subsequent
scans "rediscover" existing disk drives. The original disk drives are reported
as missing and will eventually be removed during system
clean up.
Solaris Agent Upgrade Installation Directory
When you upgrade a Solaris agent from version 6.0.0 to version 6.0.1, the installation directory remains 6.0.0.
Installing the Capacity Reporter Agent for Solaris multiple times leaves
port numbers reserved
Each time you
install the Agent for Solaris you will be asked to supply a new, unused service
name and port number for the Agent to listen on. This information is used
to generate entries in the /etc/services and /etc/inetd.conf files. When
the Agent is removed, these entries are deleted. Reinstalling the Agent
without removing the prior instance will result in multiple entries being left
in the /etc/services and /etc/inetd.conf file, effectively reserving multiple
ports for use by the Agent. Only the entries from the last installation
will be removed from these files when the Agent is uninstalled, so you will have
to remove any additional entries manually. This can be avoided by
uninstalling any instance of the Agent before reinstalling it rather than
attempting to install over the existing kit.
Database Scanning: Reporting on a Mirrored Sybase Disk Device
The Capacity Reporter software does not report on Sybase device status or on device mirror status.
Database Scanning:
Reboot Proxy Machine after Installing Oracle PC Client
If you install the Oracle PC client on
the proxy machine, you must reboot the proxy machine before scanning.
Failure to do so may result in database scans hanging.
Database Scanning: Edit the CLASSPATH Environment Variable for Viewing Charts and Graphs (Sybase only)
If a typical Sybase PC Client installation has
been performed on the same machine from which you are browsing to Capacity Reporter
for Database Servers, the charts and graphs do not display properly. This
problem is caused by an older version of the graphing package embedded in
certain Sybase PC Client components. The recommended solution is to browse to
Capacity Reporter for Database Servers from a machine that does not have Sybase PC
Client installed. However, if this is not possible and you want to view charts
and graphs, you must edit the CLASSPATH environment variable, as follows:
Database Scanning: Virtual Memory problems on Capacity Reporter Server
Using equipment that does not meet specified prerequisites for the Capacity Reporter Database Plug-In software can cause virtual memory errors. To avoid this problem, be sure your equipment meets the Capacity Reporter Server prerequisites listed in \PlugIns\Database\database_readme.htm on the product CD-ROM.
Plug-In Registration Wizard for the 6900/3900 device does not accept
the period (".") as a valid character in the SRM Display Name
field.
The Plug-In Registration Wizard for the 6900/3900 device does
not allow the input of the period (".") as a valid character in the SRM
Display Name field. If you wish to enter a fully qualified name, you may
cut-and-paste content into the field. Alternatively, when filling out the
Service Processor Name field, the SRM Display Name field is populated with a
fully qualified name including the port number; delete the port number and leave
the name.
Install may fail when installing databases whose names contain a
hyphen
When attempting to install a database with a name
that includes a hypen ("-"), the install may fail. Do not use hyphens when
installing databases to avoid this issue.
Exchange not accessible through Master Console in Capacity Reporter
v6.0
If you upgrade to Capacity Reporter v6.0
from a previous version, there are no longer any links to SRM for Exchange.
If you need to manage existing SRM for Exchange Agents, visit the following URL
to gain access:
http://%SRMServer%/SRM/SRMforExchange.asp where
%SRMServer% is the server where Exchange is installed.
File Reporter: Do not Install a Capacity Reporter Server or a Capacity Reporter Agent on the Same Machine as the File
Reporter Software
Installing File Reporter software on a machine that is running Capacity Reporter or a Capacity Reporter Agent
is not supported.
File Reporter: Windows 2000 Installations
When installing File Reporter software on a Windows 2000 server, you must manually establish
the Microsoft Transaction Server account as follows:
File Reporter: If a Capacity Reporter Agent Has no Admin Shares, Change .csv File Path Names
To synchronize partition information between File Reporter and Capacity Reporter Agents that have no Admin shares, edit the agent's .csv file path names.
To do this, perform the following on the Capacity Reporter Agent computer:
File Reporter: The File Reporter Service Account Must Have Local Admin Privileges on Monitored Capacity Reporter Agents
To collect detailed file information on a Capacity Reporter Agent, File File Reporter needs access to the agent's administrative shares. To gain access, File Reporter's Service Account must have Local Admin privileges.
File Reporter: Use a 'Regular Identifier' for File Reporter Database
During the install process, when entering the name of the File Reporter database, it is necessary to use a 'regular identifier'. See SQL Server documentation for details on identifiers and naming conventions.
File Reporter: Temporary Directory Left Behind
Setup.exe does not remove a directory created in the System Temporary directory. An example of the directory name is
GLF10.dir
. You must
manually delete this directory.
File Reporter: Prerequisite Log Text is Appended
Each time setup.exe is run, a prerequisite check is made on the
computer. Errors are written to PrerequisiteLog.txt, available
from the Details button on the Prerequisite Failed dialog box.
Each time the file is generated, the information is appended,
not overwritten.
File Reporter: Windows NT Local Language Must be Set to US English
Windows NT local language must be set to US English for .CSV file creation, or file import will fail.
The following are known issues relating to this release of Capacity Reporter:
Hitachi Data
Systems HiCommand Server reports Storage Capacity Differently than Capacity
Reporter Software
The HiCommand Server calculates storage space as follows:
| 1 KB = 1000 bytes |
| 1 MB = 1000 KB |
| 1 GB = 1000 MB |
| And so on... |
The Sun StorEdge T3 Array Console Reports Storage Capacity Differently than Capacity Reporter Software
The Sun StorEdge T3 Array console calculates storage space as follows:
| 1 KB = 1000 bytes |
| 1 MB = 1000 KB |
| 1 GB = 1000 MB |
| And so on... |
Import from a Universal Security Group
When importing User or Directory Group members from a Universal
Security Group defined in Domain A, where the Universal Security Group contains
users defined in Domain A and Domain B, only Users or Directories owned by
accounts defined in Domain A will be imported. It is possible that Users defined
in Domain A that are not part of the Universal Security Group may be imported
inadvertently.
When importing User or Directory Group members from a nested Global Group only those Users or Directories listed in the parent group will be imported. Members of any 'sub groups' will not be imported.
Receiving "The page cannot
be displayed" Error Message While Accessing Capacity Reporter
Software
While accessing the product when running IIS 5.0 in conjunction with an anti-virus software
application, you may receive the "The page cannot be displayed" error message.
If you encounter this error, close your browser session, and then shut down
and restart the anti-virus software.
Missing Package May Be the Cause of Linux Agent not Returning SCSI Information
If computer scans on a Linux machine fail with errors such as "sh:/sbin/scsi_info: No such file or directory", the scsi_info utility is not installed or available. To fix this problem, download and install the kernel-pcmcia-cs package from Red Hat or from your Linux distribution CD.
File Scanner Ignores Alternate Data Streams
Files on NTFS can have an
arbitrary number of independent data streams. The Capacity Reporter file
scanner, like most programs, ignores all but the primary data stream. Alternate
streams are not well known, but are occasionally used to
hide information or to maliciously fill up a disk. By ignoring the alternate
streams, Capacity Reporter software ignores files that should be on the large
file list and, on Windows 2000, produce
per-user usage that differs from the Windows 2000 quota code.
See the Microsoft web site for more information on working with streams.
File System Scans Fail when Host of an NFS Mount Point is Unreachable
On UNIX machines, file system scans fail if the host of an NFS mount point is unreachable.
Missing SmartArray Logical Drive
Capacity Reporter software cannot detect that
a logical drive has failed or disappeared until the system containing the
SmartArray controller is rebooted.
Grown Defects Reporting
By default, Grown Defects reporting is disabled by setting the SKIP_DEFECTS option to TRUE in uagent.cfg. This can reduce scan times and also prevent error messages from accumulating in T3 Array message logs.
If you enable Grown Defects reporting, error messages appear in T3 Array message logs, because T3 Arrays do not support grown defects reporting.
Adding UNIX
directories on the Add Directories page
When adding UNIX directory entries on the Add Directories page, it is possible to create an entry whose path appears to be correct, but whose file system component of the path is incorrect. If this happens, the managed directory will appear to be missing after a scan occurs.
To avoid this problem, take one of the following actions:
Note: The managed directory's path is formed by concatenating the file system with the entered directory. For example, to manage /export/home/mbh , if the correct file system selection is /export , enter /home/mbh as the directory entry.
Or
Importing Capacity Reporter User and Directory Group members from ADS
In all cases when importing User and Directory Group members from
ADS "NT Style" naming conventions must be used in place of the Active Directory
names. For example:
SERVERNAME\Administrator is required instead of Administrator@SERVERNAME.DOMAIN
.
Uninstall/Reinstall Capacity Reporter Server Will Reset Capacity Reporter Settings
If you uninstall/reinstall a Capacity Reporter Server, settings such as Remote Install
Scripts and E-mail Alert text changes will be lost.
Upgrade Does Not Remove Backup Plug-In
Capacity Reporter no longer supports the Backup Plug-In. However, if you upgrade to Version 6.0 from a previous version of the software, the Backup Plug-In user interface pages still display. A clean installation of Capacity Reporter software, Version 6.0 removes the Backup Plug-In user interface pages.
Automatic Deletion of Remote Install Scripts
If you uninstall Capacity Reporter software while keeping the database, any remote
install scripts created through Capacity Reporter are deleted.
Do Not Use the Help Window's Refresh Button When Using Internet Explorer 5.5 or
Internet Explorer 5.5 SP1
Clicking
Refresh
while viewing the Help in IE 5.5 or IE 5.5 SP1 may display a run-time error and a dialog box asking if you want to debug the application. If this dialog box displays, click
No when asked to debug the application.
This problem does not occur on IE 5.0 or IE 5.5 SP2.
Clicking on the Help window's back button when using Internet Explorer 5.5 SP2 can cause Index or Search tabs to blank outInternet Explorer 5.0 SP1, 5.5 SP2, or 6.0 Required for Remote Installation
To perform
remote installations of the Capacity Reporter agent, you must use Internet Explorer 5.0 SP1,
5.5 SP2, or 6.0, with appropriate security patches for each version.
Java Virtual Machine (JVM) Must Be Installed to View Charts and
Graphs
Any Internet Explorer browser used to view charts and graphs must have the Java Virtual Machine installed.
Java Developer's Kit (JDK) May Interfere with Display of Charts and Graphs
If you open the application from a computer that also has the Java Developer's Kit installed, charts and graphs may not display. To allow charts and graphs to display, disable the Java plug-in on the browser.
Mounted Volumes without Drive Letters not Reported in File System
Report
In some cases if a volume has been created but not assigned a
drive letter, it may not be reported in the File System Report after a
scan. To ensure that volumes are consistently reported they must be given
a drive letter upon creation.
Disk Reports on UNIX Platforms Display a "Filesystem Section Start On
Disk" value of 0.00MB
The "Filesystem Section Start On Disk" value
for Disk Reports on UNIX platforms shows a value of 0.00MB, which may be
incorrect.
Solaris Systems Running Solstice DiskSuite Prior to V4.1 are Unsupported
The Capacity Reporter software does not support Solaris systems running Solstice DiskSuite (Sun volume manager) prior to V4.1. To work around this restriction, add the path /usr/opt/SUNWmd/sbin to the root login Bourne shell path environment variable, or make the utilities contained in /usr/opt/SUNWmd/sbin accessible to the Capacity Reporter Agent.
Capacity Reporter Cannot Determine Disk Controller Type on Systems Using SBUS Architecture
On Solaris systems using the SBUS architecture, the Capacity Reporter software cannot determine the type of disk controller in use. The application reports the controller for the disk as "unknown".
Capacity Reporter Cannot Always Collect Information about Physical Disks on Solaris 5.6 or Earlier Operating System
The Capacity Reporter software can have problems collecting information about physical disks, such as make, model, firmware, or rotational speed. In these cases, reports display "unknown" for those items.
Version 6.0.1 UNIX Agent Upgrade on Veritas Clusters
If you upgrade to the version 6.0.1 UNIX agent on a Veritas cluster, subsequent scans cause the cluster alias and virtual servers to appear grayed out. To fix this, rerun the registerca script. NOTE: You may lose some history as a result of rerunning this script.
Capacity Reporter Display Name must Match Network Appliance Device Name
When assigning a Capacity Reporter display name to a Network Appliance device, you must assign the Network Appliance device's true network name. Scans fail if the Capacity Reporter display name does not exactly match the Network Appliance device's true network name.
Date-Time User-Defined Attribute
When using the date-time data type for a user-defined attribute, the following settings are valid:
Database Scanning: Use a Single
Capacity Reporter Proxy Server to Scan Sybase Databases on the Same Database
Server Instance
Do not set up two different Capacity Reporter Proxy Servers to scan Sybase databases on the same database server instance. This may cause a temporary database deadlock situation, which could result in Sybase terminating the connection, thereby causing a scan failure.
Database Scanning: Scan Requests Not Functioning
Database scans may timeout. Subsequent scans should continue
to function. If you want to increase the timeout value, contact Sun Support.
Remote Scanning: Scanning Limitations on Windows NT if Disk Administrator Has Not Run
If the disk administrator has not run at least once on a Windows NT computer, the Capacity Reporter proxy agent does not report:
Note that the disk drives will be assigned signatures based on index. When the disk registry does become available, it generates true signatures. The user interface reports the new drives while the signatures based on index appear as lost.
Remote Scanning: Download Failures Function Might Be Unreliable with Earlier Versions of Internet Explorer
The Download Failures function of CSV bulk registration behaves reliably with Netscape and Internet Explorer Version 5.5, Service Pack 2. If you use an earlier version of Internet Explorer, you might see unexpected results, which can include "Page not found" messages or unexpected values written to the failure.csv file.
Norton AntiVirus Scanner can Interfere with Capacity Reporter Scanning
The Norton AntiVirus scanner can interfere with Capacity Reporter scanning. To avoid this problem,
disable Norton AntiVirus on the Capacity Reporter Server machine.
How to Get Adobe Acrobat Reader
The documentation on the CD-ROM is in PDF format. If you do not have Adobe Acrobat Reader, go to www.adobe.com to obtain a
free copy.
Unlabeled Disks not reported when Veritas Volume Manager is present
When Veritas Volume Manager
is installed, Unlabeled Disks may not get reported, and will not be visible
through Capacity Reporter. Unlabeled disks will be reported and visible in
Capacity Reporter if Veritas Volume Manager is not installed.
Event Log will Fill Quickly if Computer Groups are Left Empty and Scanned on Schedule
If a computer group is intended to be left empty, it's scan schedule should be set to scan on demand only. This will prevent the application log filling quickly.
LDAP Lookup Does Not Function if Capacity Reporter Server Is Not In Same or Trusted Domain as Exchange Server
In order for the LDAP lookup to work correctly (allowing directory aliasing), the Capacity Reporter Server needs to be in the same, or a trusted domain as the Exchange Server. If it isn't, then other email alert functionality continues to work as expected, making it possibly difficult to troubleshoot the LDAP not working. The Capacity Reporter server can send email by sending it out port 25 (SMTP) and then uses a DNS server to lookup the Exchange Server. The Exchange Server's LDAP directory is configured with access permissions, which will be denied if the Capacity Reporter Server is not in the proper domain.
If the 9900 Series RAID Array Contains an ESCON Card, Some Scan Details May Be Incorrect
Due to limitations
of the Hitachi Data Systems HiCommand Server 2.0 API, if the 9900 Series RAID
Array being scanned contains an ESCON card, then the mainframe Parity Groups and
mainframe LDEVs will list the following discrepancies:
Removing a Failed 9900 Series Device From the RAID Report
Does Not Do an Implicit Full Unregister Of The BVO
If you have a failed 9900Series Device in your RAID Report
and you click on the device then Remove it, this will remove the device from the
RAID Report in Capacity Reporter but will leave the Link and Launch Button in
the HiCommand interface.
Do not upgrade
to Capacity Reporter v6.0 from the beta version of 6.0.
Upgrading
Capacity Reporter v6.0 from the beta version may result in database
layouts working incorrectly. Do not upgrade from beta to v6.0.
File Details
Report and Directory Details Report icons on the Summary Report for File
System page for NAS and NetWare devices may not launch
correctly
The File and Directory Details Reports may not launch
correctly from the Summary Report for File System page, even when the "Collect
file details on these file systems" check box was checked.
File Reporter: Manually Starting a File Collection Starts Scheduled File Collections
If a partition group file collection is started manually, file collections for
other partition groups scheduled for the current day will start once the manually
scheduled collection is complete. If you run partition group file collections
manually, disable the day's other currently scheduled partition group file collections.
Once the manual collection is complete, re-enable the scheduled collections.
File Reporter: Read-only .csv Files Not Deleted After Import
If an SRMFileData.csv file on a Capacity Reporter Agent machine’s partition is Read-only,
it will not be deleted from the File Reporter software’s Staged File directory after
import into the SRMFC SQL Server database. This will cause the CopyFile in next
processing run of the same .csv file to fail. Ensure that SRMFileData.csv files
are not Read-only on the Capacity Reporter Agent machine partitions.
File Reporter: SynchLog.log File
During installation, the File Reporter software creates a log file named SynchLog.log
in the \wwwroot\FileReporter folder of the File Reporter server machine. This file logs
information regarding synchronization attempts between File Reporter and
Capacity Reporter. If the file is deleted, it will be recreated during the next synchronization
event.
File Reporter: Trace Log Becomes Too Large to Open
If left on, the trace log continues to grow and eventually becomes too large
to open. To keep the Trace Log active, periodically suspend FCService (when
no jobs are queued) and backup/delete the existing Trace Log.
File Reporter: Do not Open Multiple Sessions of the File Reporter Console
Opening multiple sessions of the File Reporter Console on the same or on different
machines can cause database access problems.
File Reporter: Use Certain Operators and Values When Performing Query Builder Date Queries
On the Query Builder page, the second date Value field for each date type (Creation, Access, or Modified) is only applicable to queries using the
Between
operator. For all other date queries, use only the first date Value field with any of the remaining operators (=,<,>,<>).
File Reporter: Enter the Drive Letter with a Colon When Performing Query Builder Partition
Queries
On the Query Builder page, when performing a search on a partition name, you must enter the partition's drive letter along with a colon in the Partition Name's Value field. Otherwise the query may fail.
File Reporter: SQL Server Setup Can Cause Query Builder "All File" Report to Display No Data
If the SQL Server has been configured to restrict tempdb file growth and if insufficient space has been allocated for the tempdb file, the Query Builder all file report may display "No records meet your report criteria", even though data was collected. You may also find error #1105 in the application Event Viewer log.
To correct this problem, Sun suggests that you select the tempdb parameter Unrestricted File Growth.
File Reporter: The File Size (MB) Field Cannot Accept Multiple Values
On the Query Builder page, the File Size (MB) field cannot support multiple values entered in its Value field.
File Reporter: If the File Reporter Machine's SQL Server Service is Stopped, Stop and Restart the FCService Service
If the File Reporter machine containing the SRMFC database stops its SQL Service, the File Reporter Service must be stopped and restarted. Otherwise, .csv file collection will not continue.
File Reporter: Directory, Files, and Data Source Left Behind
When uninstalling the File Reporter software, the Remove All option does not delete the
File Reporter program directory,
Program Files\File Reporter
.
In addition, Remove All does not delete the File Reporter ODBC data source.
Remove All also leaves two files in the
\Install
directory: