Applies To:

Show Versions Show Versions

Release Note: Data Manager version 3.0.0
Release Note

Updated Date: 09/17/2010


These release notes document version 3.0.0 of the F5 Data Manager.


- User documentation for this release
- Minimum system requirements and supported browsers
- Network requirements
- Supported ARX releases
- Supported file servers
- Upgrading Data Manager
- NFS Support for File System Inventory
- NFS Support for Storing Inventories
- Enhancements in this release
- General notes
- Known issues
     - File Server Discovery
     - ARX Configuration
     - Data Manager Client Access
     - File System Inventory and Reports
     - Installation
     - Miscellaneous
- Contacting F5 Networks

User documentation for this release

The documentation is available from the following locations:

  • From the Data Manager GUI navigation panel Documentation link.
  • On the AskF5 Technical Support web site, along with an extensive solutions database.
  • In the root directory of the product CD-ROM.
[ Top ]

Minimum system requirements and supported browsers

Data Manager will run on a general-purpose server; however, take care to select a server that is not overburdened with applications and users. In particular, note the following requirements and recommendations.

You can install and run Data Manager on any Microsoft® Windows® platform that meets the following set of minimum requirements:

  • Operating System: Windows operating system (XP, Vista, Windows 7, 2003 Server, 2003 R2 Server, 2008 Server, 2008 R2 Server).

    Note that Windows 2000 is not supported for installation of Data Manager v2.6.0 or later.

    Microsoft provides localized versions of its Windows operating system. For Data Manager, each distribution must be qualified separately. Currently, Data Manager provides support for the following language distributions: Japanese, Simplified Chinese, Korean, German, Czech, Russian, French, Spanish.

  • CPU: Pentium 4 or equivalent. Dual-core server is recommended. A minimum of 2 cores is required when using advanced reporting features.
  • Memory: 1GB available RAM. (2GB is recommended.) A minimum of 2GB is required when using advanced reporting features.
  • Disk Space: 1GB for the application, configuration data, and logging. Additional space is required for File System Inventories and Reports. The total space required for storage of inventories and reports is based on your inventory frequency and your retention policy.

Supported browsers for accessing the Data Manager GUI:

  • Microsoft Internet Explorer®: version 7.x, 8.x.

    Internet Explorer version 8 (IE8): disable Compatibility View for Data Manager web pages.

  • Mozilla® Firefox® 2.x or later and other browsers that use the Mozilla engine. (v3.x is recommended.)

    Note that Javascript must be enabled on the web browser.


[ Top ]

Network requirements

During the process of using Data Manager features, you will need the following:

  • For file server discovery, access to administrator credentials for the file server management interfaces.
  • For file server discovery, TELNET or SSH enabled on file servers to be discovered.
  • For RPC-based discovery on Windows, access to ADMIN$ and IPC$ shares.
  • For file server discovery and file system inventory, verified network connectivity to the file server(s) with which the Data Manager or the ARX will be communicating.
  • For file system inventory, access credentials to CIFS shares and NFS exports.
  • For file server discovery and file system inventory (highly recommended) , network name resolution (DNS, local files).
[ Top ]

Supported ARX releases

Data Manager supports the automatic generation of configuration scripts suitable for applying to all F5 ARX switch models. You can use the generated configuration files on switches running DMOS 3.x and above.

Using the File System Inventory Module, you can inventory an ARX VIP running any DMOS version.

[ Top ]

Supported file servers

Data Manager supports a full discovery of configuration information on the following file servers:

  • IBM N Series. At code levels: ONTAP 6.5.7, 7.0.x, 7.1.x, 7.2.x, 7.3.x. Protocols: CIFS, NFS.
  • IBM 500 G. At code levels: AIX 5L, 5.2B. Data Manager supports discovery of configuration information and NFS exports.
  • IBM 300 G02. At code levels: Windows 2000 Server, Windows 2003 Server.Data Manager supports discovery of configuration information and CIFS shares.
  • IBM AIX. At code levels: AIX 5.1, 5.2, 5.3. Data Manager supports discovery of NFS exports.
  • EMC Celerra NSX. At code levels: DART 5.4.x, 5.5.x, 5.6.x. Protocols: NFS, CIFS.
  • NetApp FAS. At code levels: ONTAP 6.5.7, 7.0.x, 7.1.x, 7.2.x, 7.3.x. Protocols: CIFS, NFS.
  • Linux Intel-based. At code levels: Redhat Enterprise 3.x, 4.x, 5.x. Protocol: NFS.
  • Solaris. At code levels Solaris 8, 9, 10. Protocol: NFS.
  • Microsoft Windows. At code levels: Vista, Windows 2000, Windows XP, Windows 2003 (clustered and non-clustered), Windows 2008 (clustered and non-clustered). Protocol: CIFS.

    Microsoft provides localized versions of its Windows operating system. For Data Manager, each distribution must be qualified separately. Currently, Data Manager provides support for the following language distributions: Japanese, Simplified Chinese, Korean, German, Czech, Russian, French, Spanish.


You can perform a partial discovery that includes CIFS shares and NFS exports on file servers that are not listed above. (For details, see Generic discovery.)

Data Manager supports inventorying file system shares/exports on file servers that support the following protocols: NFSv2, NFSv3, CIFS, Samba.

[ Top ]

Upgrading Data Manager

Data Manager does not support upgrading from a Beta release to the official GA release. Beta users are required to uninstall and remove their Beta database before installing the GA-released version. You may opt to keep your inventories and reports.

When upgrading Data Manager, consult the F5 Data Manager Installation Guide which contains troubleshooting information as well as general installation guidance.

Special Considerations

  • If you upgrade your trialware version and time has not expired on the initial trialware installation, you must save your database or you will invalidate the remainder of your trial period.
  • Data Manager stores licenses in its database so if you remove your database (i.e, for a clean install), you will have to enter your license keys again.
[ Top ]

NFS Support for File System Inventory

Data Manager version 3.0.0 includes native support for NFS inventories (built-in NFS client). Secondary NFS client packages are no longer required. The Data Manager NFS client always connects to NFS exports as root (i.e, UID=0). Be sure to verify that root requests are allowed on the export you are trying to inventory.

NFS Support for Storing Inventories

Data Manager requires NFS support on Windows platforms for optional storage of Inventories and Reports on NFS Exports

The following table summarizes the NFS client packages required on specific Windows platforms. For details, see the appendix in the User's Guide, Using UNIX Services on Microsoft Windows.

Windows Platform Windows Service Required
XP Windows Services for UNIX (SFU).
Windows Server 2003 Microsoft Services for NFS or Windows Services for UNIX (SFU).
Windows Server 2003 R2 (64 bit) Microsoft Services for NFS. You cannot install SFU on a 64-bit OS.
Windows Vista Ultimate and Enterprise Microsoft Services for NFS. Do NOT install SFU.
Windows Server 2008 Services for NFS (Client for NFS). Do NOT install SFU.
Windows 7 Services for NFS (Client for NFS). Do NOT install SFU.
[ Top ]

Enhancements in this release

The version 3.0.0 release provides the following enhancements to the previous release:

  • Significantly enhances the Data Manager File System Inventory module

    Data Manager now defaults to collecting full metadata so users can get information on largest files, directory activity, storage trends, and other parameters.

    Users can also get information on suspected duplicate files by selecting an option in both the Inventory and the Report wizards.

  • Data Manager now provides additional statistics in File System Detail reports, as follows:
    • Top-N UIDs for NFS (by files and capacity)
    • Top-N GIDs for NFS (by files and capacity)
    • Top-N Largest Files
    • New storage usage trend analysis graphs
  • A new report, Suspected Duplicates, that reports on Top-N Suspected Duplicate Files.
  • A new report, Directory Activity, that reports on the following:
    • Top-N Most Active Directories by modify time
    • Top-N Most Active Directories by access time
    • Top-N Least Active Directories by modify time
    • Top-N Least Active Directories by access time
  • A built-in NFS client for file system inventory that:
    • Eliminates the need for Microsoft Services for UNIX (SFU)
    • Provides real NFS support
    • Eliminates NFS inventory loops due to symbolic links
    • Provides NFS reporting on UIDs, and GIDs.
  • Addition of the optional Advanced Reporting module that provides the ability to create sophisticated, customized file system reports

    A new module, Advanced File System Reporting, enables the creation of reports based on file criteria, which are filters that match a subset of files in the inventory database. File criteria are based on matching file system metadata attributes (for example: size, age, and so on). You can upload and import criteria from a CSV text file or create criteria from within the application.

    Advanced reports are supported for file system Detail, Trend, Cumulative, Suspected Duplicates, and Directory Activity report types.

    Advanced reporting:

    • Allows users to create any of the file system reports on a subset of files in one or more file systems
    • Allows users to configure a set of file criteria for rolling up file counts and capacity
    • Allows users to run multiple advanced reports by iterating over a set of owners, file criteria, extensions, and other criteria
    • Provides a new report type, the Fileset report, which uses file criteria to generate a text report of all files that match the criteria
  • Miscellaneous enhancements:
    • GUI performance, scalability and usability improvements
    • Ability to create Credentials objects for reuse in file server discovery, inventory, and AD group resolution
    • Data Manager Control Panel for starting/stopping the application and configuring application-wide settings
[ Top ]

General notes

Data Manager will not install on a domain controller. (336481)

In Data Manager version 3.0.0, the user will receive an error dialog during the installation process stating that Data Manager cannot be installed on a domain controller. This is not supported.

Data Manager creates a backup of the installation database as part of the upgrade procedure. (337238)

During the upgrade process, Data Manager now creates a file in the db directory that contains the "old" database.

Data Manager requires uninstall of old version before installation of new version. (34777)

Currently, the Installer informs you that a previous version of Data Manager is installed and instructs you to uninstall it manually before you can proceed with a new installation.

Never install a Trial version over a Full version

A Trial version of Data Manager should never be installed over a full version. For more information on installation issues and details, consult the Installation Guide.

A GUI option to no longer generate the ARX special file report is now available.

Using a option (called Generate ARX Special File Report) in the Inventory wizard and the edit page for the task, you can decide whether or not to record any special files that are discovered during the inventory process. The default is to NOT record special files.

Special file logging now has its own log file.

"Special" files are now logged to a separate report file (no longer in the inventory task log), and placed in the reports directory. It follows the same naming convention as the inventory task log and the task inventory database (db) file:

host(or ip)-sharename-dateAndTime-special.rtf

Import of the local discovery data for Windows servers may fail if the Local Discovery script that generated it is not same version as the Data Manager server.

When using Windows local discovery, make sure you are using the local discovery script that comes with your version of Data Manager.

Local discovery files (named *.dsc) are temporary and are not meant to be forward-compatible with new versions of Data Manager.

To guarantee a successful local discovery:

  1. Download the Local Discovery script from the Documentation page of the currently-running version of Data Manager.
  2. Execute the local discovery script on the Windows file server. (File Servers > File Server Summary > Add/Rediscover).
  3. Import the discovery data.

For details on local discovery, see the User's Guide, Performing Local Discovery for Windows File Servers.

RPC-Based Windows Server Discovery Requires Special Privileges

To perform RPC-based discovery on Windows servers, you must use a local or domain administrator account that has "Log on as a service" privilege on the remote machine. This privilege is not granted by default. For details, see the F5 Data Manager User's Guide section on Performing RPC-Based Discovery on Windows.

When discovering UNIX/Linux-based file servers and EMC Celerra file servers where the shell prompt has been customized, you must inform Data Manager of the customized prompt.

If you are having difficulty discovering UNIX/Linux-based file servers or EMC Celerra file servers, it may be due to an issue with the shell prompt. Data Manager assumes a default prompt of $ (dollar sign). Log in to the file server and note the shell prompt. If it does not end in $, you must inform Data Manager of the customization in the Discover File Server wizard. Attempt the discovery again. In the wizard Shell Prompt field, type the customized character. The prompt is associated with these specific file servers only. It is used for the current discovery and saved for rediscoveries. It does not effect the default settings for UNIX/Linux-based file servers.

When discovering Windows servers with TELNET, be sure it is not authenticating with NTLM.

To ensure that TELNET is not authenticating with NTLM:

  1. On the Windows server from a DOS prompt (as administrator), enter the tlntadmn command to view the current settings.
  2. Review the output.
  3. The setting Authentication Mechanism : NTLM, Password indicates authentication using NTLM.
  4. If the Authentication Mechanism lists NTLM, enter the following command to remove NTLM as an authentication mechanism: tlntadmn config sec=-NTLM
  5. If the configuration mode is Console, enter the following command to change the configuration mode from console to stream: tlntadmn config mode=stream
  6. To have these changes take effect, restart TELNET by clicking the Windows Start button and then clicking: Programs > Administrative Tools > Services
  7. In the Windows Services GUI in the Name column, select Telnet and then click the restart link.
[ Top ]

Known issues

The following items are known issues in the current release. For issues that are being tracked on the F5 internal database, note the tracking numbers that appear in parentheses.

File Server Discovery

File servers that asynchronously log messages to the console could interrupt discovery. (30868)

File servers that allow messages to be streamed to the console asynchronously, run the risk of interrupting the Data Manager file server discovery process. Data Manager recognizes the prompt characters and uses them to identify the completion of discovery commands. If console messages corrupt the prompt string, Data Manager will fail to recognize the completion of the command.

If this is a chronic issue with the file server, due to the logging level or environmental issues, you may need to disable console messages during the discovery process.

If a discovery failed, then the Discovery report is not accessible from the Reports Summary page. (37225)

If a file server discovery fails, then the user can access the report by clicking on the discovery status link on the file server summary page. The problem that remains is that the Reports Summary page also has a row dedicated to this failed task, but you cannot access the report from this page.

ABE discovery fails due to failed DNS lookups.(37146)

If ABE is enabled for discovery and the user had provided the correct credentials but discovery was unable to resolve the DNS entries for some of the CIFS servers from the desktop (the Data Manager server), discovery will fail.

The Discovery report tells you what fails, but the fact that the failure is related to ABE and that you can rediscover with ABE discovery turned off is not provided to the user or to Support in a way that is easy to understand. Use the following to assist users.

In the Discovery report, search for the following message:

Authenticating CIFS IPC Credentials

The lines following this message will provide more information on the failure.

Not discovering CIFS shares using Generic Discovery on an NetApp file server from a Data Manager server installed on Windows 7. (37078)

Generic discovery of a CIFS-capable file server fails with the message, "The stub received bad data".

Data Manager servers running on Microsoft Windows 7 and Windows 2008 R2 (64bit) server may see issues discovering older CIFS-capable file servers using the generic file server type in the Data Manager Discovery wizard. The generic file server type discovery uses the MS Windows native "net view" command. The "net view" command will execute successfully on Windows XP, Windows 2003, and other Windows OS versions.

Looking at the resulting capture files from failed discovery task, you will see

$ net view \\<File Server>

System error 1783 has occurred.

The stub received bad data.

You will see the following in the File Server Discovery report:

Discovering CIFS Shares

Warning: The discovery of CIFS shares for file server failed:

System error 1783 has occurred.

Warning: The discovery of CIFS shares for file server failed:

The stub received bad data.

The only known workaround is to discover the file server from a Windows server that can successfully execute the "net view" command against it.

NFS ACL warnings appear in the Discovery report as "not supported." (30927)

ACL warnings appear in the Discovery report as "not supported." The customer receives these warnings even though the storage can be mounted and accessed from an ARX.

For most of the NFS ACL option warnings there is a general explanation. Many of these flagged options are associated with changing the filer's behavior on a per client basis and are not associated with client authorization and access. These behavioral options are not implemented on the ARX and therefore will not be enforced. Secondly, since the ARX is acting as a proxy between the file server and the client machine, the file server cannot distinguish between different client machines.

For example, suppose there are 2 different clients for an NFS export, 1 client has an option and the other does not. The ARX as a proxy does not distinguish between those clients and appears to the filer as a single client. So, both clients will get the same option setting.

Discovery of Window servers with ABE discovery enabled fails if the NetBIOS name of the server cannot be resolved. (37084)

During discovery of Windows servers, if ABE discovery is enabled, the process must be able to resolve the NetBIOS name of the file server being discovered. If it cannot, then the ABE discovery phase will fail and if the ABE discovery phase fails, the entire discovery task will fail.

Workaround: On the Data Manager server, edit the hosts file so that the Data Manager server can resolve hostnames when unable to communicate with the DNS server in the data center environment. The default location of the hosts file is C:\Windows\System32\drivers\etc\hosts.

Windows file system capacities in cluster resource groups are marked as 0 on the inactive node. (35621)

Data Manager cannot discover the capacity for a disk that is not currently mounted on the discovered node. Hence, some file systems are marked as having 0 capacity. Data Manager discovers capacity accurately for cluster resource groups that are currently active on the node.

Quotas not discovered properly for Windows clustered file systems on the inactive node. (35622)

Data Manager does not discover quotas accurately for the file systems (disks) that are not active on the node. Data Manager does discover quotas accurately for the file systems (disks) that are discovered in cluster resource groups that are currently active on the node.

Thus, you should discover all nodes in the cluster and compare the discovered quota data.

Discovered Windows server share names containing question marks. (36461)

In share names discovered using TELNET, SSH, or RPC discovery methods, Data Manager renders the Unicode characters that are not part of target system's OEM code page as question marks.

For example, if the share name on the target server is currency-€, the share appears in Data Manager as currency-?.

This could result in confusion if there is another share on the target named, for example, currency-元, which would also appear in Data Manager as currency-?.

This issue is not exclusive to English language systems but can be observed on any system where a share name contains a character that is not available in the target's OEM code page.

To determine if a share name contains any characters affected by this issue:

  1. Open a Windows command shell.
  2. CD into the parent of the suspect directory.
  3. Execute the DIR command and examine the listing for share names containing question marks.

Workaround: Use the local discovery method, which renders share names correctly.

Selecting the wrong IP address for local Windows cluster file import throws off the CIFS server assignments. (36027)

It is important to enter (as the primary service address) the IP address associated with the physical node. Do not select an IP address associated with a cluster resource group when importing the local discovery file.

You can obtain the correct IP address from the discovery file (*.dsc) by entering a type command from the DOS prompt. In the following examples, substitute your .dsc filename in place of "file.dsc."

To list the file server IP addresses, enter:

>type file.dsc | findstr /R /C:"IP Address. . . . . . . . . . . . :"

To list the resource IP addresses, enter:

>type file.dsc | findstr /R /C:"Address                          [0-9]"

Then, note an IP address from the first list which is not in the second list.

If the cluster service is unreachable, Windows cluster discovery fails to assign shares to the correct resource groups. (36380)

If cluster services become unavailable, Data Manager is unable to gather the cluster resource group assignment information necessary to display the allocation of resources (shares) to resource groups (virtual CIFS servers). In these cases, any resources (shares) that are currently active on the node being discovered appear as if they are assigned to that physical node.

Windows RPC-based discovery is not compatible with Simple File Sharing. (33945)

RPC-based discovery does not succeed on a Windows system that has Simple File Sharing enabled. When Simple File Sharing is enabled, remote users authenticate as Guest and Guest accounts do not have administrative rights which are required to execute a successful remote discovery.

ARX Configuration

Script (rmtshare) that grants proxy user share-level access uses rmtshare which could overwrite existing permissions. (32280)

This note is a warning about rmtshare behavior.

If you follow the current virtualization workflow (non-subshare case), new hidden shares are created on the ARX (using rmtshare) and then existing permissions are copied from the original shares to the new shares. Then, a rmtshare is run to grant the proxy user access to the shares.


The script rmtshare sometimes overwrites any existing share permissions, leaving only the proxy user having access.

Add share scripts do not create clustered shares for Windows Cluster Server. (30638)

Data Manager currently uses rmtshare.exe for all share creation in the scripts. This works for Windows Cluster Server but Data Manager doesn't create "clustered" shares that will fail over.

After completing the execution of the ARX script, you must manually modify your cluster configuration to include the appropriate shares.

Recover NFS exports script is missing ACLs for generated names. (35334)

When an NFS simple configuration selects an import level that causes the NFS export path to be generated (the import is the parent of the original NFS export), then the script to recover the NFS exports is missing the ACL after the path. In addition, the path defined in the script is for the generated import, not the original export.

The virtualization backout process should reset the file server to the original state which means that it should not include Data Manager-generated share names. The process should tell you to remove the generated share/export names.

Data Manager does not handle an EMC share explicitly assigned to multiple CIFS servers. (31366)

Data Manager misses a CIFS server assignment on a share when the share is configured using the Celerra GUI for multiple CIFS severs.

Data Manager Client Access

Internet Explorer 8 support. (36719)

Internet Explorer 8 includes a Compatibility View option which is designed for Web applications developed for older browsers. Data Manager does not support Compatibility View and it must be disabled when viewing Data Manager pages. When Compatibility View is enabled, pages are not displayed properly.

File System Inventory and Reports

The Capacity chart on the Directories tab (By Capacity subtab) does not display initially. (339777)

If you encounter this issue where the Capacity chart is not being displayed, click away from the By Capacity subtab and then click on it again. The chart should display properly.

Uploading an MS Excel created File Criteria CSV file into Data Manager may not succeed. (38224)

To correctly create the CSV file in Microsoft Excel, do the following:

  1. In Excel, ensure all the columns are formatted for text:
    1. Select all columns, then right-click to display the menu.
    2. In the menu, click on Format Cells, then select text.
  2. When entering values in each cell:
    1. Start each entry with two single quotes.
    2. End each entry with a single quote.
  3. The following example shows how to create a file criteria that can be used to identify files that are less than 1 week old.

    Enter the following in the first three cells of the first row.

    In cell 1, type: ''File Group 1'
    In cell 2, type: ''OneWeekOld'
    In cell 3, type: ''RM<(1.0 weeks)'

CIFS inventory cannot recognize a directory with a . (dot) at the end of its name. (39748)

Directories ending with a dot come across to Data Manager as ending in a tilde followed by a number. Data Manager does not received the directory name information correctly and cannot report it correctly. Such directories show up in the File System Inventory Details page (Files/Dirs tab, General subtab, Special Files section) as 0 for the parameter Directory Names ending in '.'.

CIFS inventory not detecting files with named streams on NetApp with UNIX security file system. (39393)

When completing an inventory on a discovered NetApp file server CIFS share, if the discovered CIFS Shares have a file system type ofUNIX, Data Manager will fail to correctly identify files which have named streams attached to them. There is no workaround currently.

For more information on files/directories with named streams, consult the Data Manager User's Guide.

Reports in XLS format cause Excel to display warnings about file's format. (338331)

When Data Manager reports are saved in XLS format and users double-click on the files to open them, Excel starts, but a warning message is displayed, stating that the files do not appear to be in Excel format and warning the user about proceeding. If the user agrees to proceed, the files are displayed correctly.

User should accept the warning and proceed.

Detail report for local inventory lists number of directories reported more than inventoried in the files and directory section. (338590)

Data Manager counts the root as a directory as part of the inventory process. Remember that directory counts include the root directory.

File system inventory does not work on shares that are a DFS root. (38649)

Please note that Data Manager does not support inventorying shares with remote redirects.

File system inventory task takes too long or never finishes.

If you have shares that appear to contain recursive links resulting in a scanning process never finishes, even after the size and file count are well above the actual numbers, the problem could be caused by one of the following:

  • Snapshot directories. You have not instructed Data Manager to ignore snapshot directories during the inventory process.

    The Inventory wizard lets you specify a list of directories to be ignored during the inventory process. The snapshot directories are not included in the default list and if not explicitly excluded, Data Manager will inventory through all retained snapshots.

  • CIFS environment containing reparse points. In CIFS environments, Data Manager inventories follow reparse points, not shortcuts. You can disable this behavior through an option in the Inventory wizard. If you have circular links, you may want to change the Inventory setting to avoid following reparse points.

Section selection does not work for a standard File System Detail report in RTF format. (32576)

If you generate a standard File System Detail report and choose the Customize option on the first page of the Inventory wizard and then select only the first sections for inclusion in the report (General Information, Files And Directory Information, Capacity, CIFS Information) and, finally, select RTF for the report format, the result is a complete summary report including ALL sections and not just the selected sections.

The section selection is not supported in RTF format.

Hard links are not reported for the Windows shares. (30730)

The user can create hard links on Windows and they behave as they do in UNIX, but the Report function does not recognize them. This appears to be an OS/network problem. Based on research on the call made by Data Manager: "Depending on the underlying network components of the operating system and the type of server connected to, the function may fail, return partial information, or full information for the given file."

Mapped drives on Data Manager server cannot be (locally) inventoried. (30526)

When attempting to inventory a mapped drive (non-local), Data Manager reports that the path is not found. Data Manager cannot inventory mapped drives through the "local drive" method.

The task of inventorying a Windows share from Data Manager fails, but succeeds after reboot. (34173)

You encounter this connection error on a Windows server when trying to inventory a remote system due to problems with an unknown username or password error (as indicated in the inventory log). Repeated attempts result in failure with the same error message, even though you specify the correct credentials. Should you encounter this connection error, check for the following problems which can cause problems connecting to a remote share:

  • Persistent network connection with an invalid password.
  • Service using a user account with an invalid password.
  • Trust relationship has been broken.
  • Network error reaching domain controller. (Can you reach anything else in the same domain?)
  • DNS server connection issue.
  • Permissions have changed on the share.
  • Date skew on the local machine. (Possibly the password has expired.)

Workaround: Rebooting clears this issue. For more information, see the Microsoft article, Troubleshooting Unwanted "Access Denied" Messages in Domain-Based Networks (Windows NT 3.x and 4.0).

Long multibyte character report name wraps on front page of report, causing the front page to increase to two pages. (34755)

When generating batch Summary reports, enter short names for the report because the inventory name gets appended to the report name and if the report name is too long, it will wrap to a second line, causing the front page to increase to two pages. This issue occurs only for batch Summary reports. In the Reports wizard, the user is constrained to a maximum number of characters allowed in the report name field (UI) to 40. Both single byte and multibyte characters fit in one line.

Cannot open report with multibyte character filename. (34779)

If you use more than 28 multibyte characters to name a report file, you can encounter problems when trying to open that file through the link on the Report Summary page when using Firefox or any Mozilla-based browser. No issues have been seen when using IE 7.

Workaround: Open the file outside the browser (or use IE7). The file is located in the Reports directory. You can view the path to the Reports directory on the File System Inventory Module Settings page.

Compressed files may cause capacity inventoried to appear greater than total/used space. (32378)

You can see Total of all inventoried file sizes in the Capacity tab:

File System Inventory > Inventories > File System Inventory Details > Capacity tab > Disk Capacity Information > Total of all inventoried file sizes

If you have compressed files (CIFS only) and then inventory the file system containing the compressed files, you may see the reported total capacity inventoried as greater than both the used space and total space of the file system. This occurs because Data Manager defines capacity inventoried as the total uncompressed size of all files inventoried.


Data Manager user is removed, but directory is left behind. (35946)

During the uninstall process, Data Manager attempts to remove the Data Manager user and the Data Manager user's profile. In some instances, Windows requires a reboot to remove the directories associated with an active profile. If the Data Manager user directory is left behind, you can reboot your system and then remove the directory manually at your convenience.


If the application port setting has changed, users may have to logoff current sessions to refresh URL links. (28676)

When the application port setting is changed, the acopia.url file is updated. Data Manager uses this file to direct the desktop icon and "Launch Data Manager" programs item to open a Web browser to the Data Manager application. When the application port setting is changed, the acopia.url file is updated.

If the application does not launch after these settings are changed, you may have to log off and log in to the Windows OS to clear any cached file data.

Regardless. for the new port setting to take effect, you must first manually restart Data Manager using the Data Manager Control Panel.

Corrupt is created when memory usage of the Web application is high. (30735)

If you attempt to collect diagnostics and the file is corrupted, it may be because memory usage on the Data Manager server is high (more than 260 M). Restart Data Manager and you should be able to collect diagnostics successfully.

[ Top ]

Contacting F5 Networks

  Phone: Contact your local Sales Engineer.
Fax: (206) 272-6802

For additional information, please visit

Was this resource helpful in solving your issue?

NOTE: Please do not provide personal information.

Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)