Acronis Files Connect (formerly ExtremeZ-IP) indexed searches on 'Name' with parameters "ends with," "begins with," and "is" do not return any results.
Search on 'Name' with parameters "ends with," "begins with," and "is". You won't find anything.
This is a bug in Mac OS 10.4 Tiger and occurs in 10.4 - 10.4.2.
There is no workaround.
This bug is likely corrected in the Mac OS 10.4.3 update, which addresses multiple file search bugs.
Canto Cumulus returns the wrong graphic from its catalog when the user selects a graphic that exists on an Acronis Files Connect (formerly ExtremeZ-IP) volume.
By default, Cumulus stores files within its catalog based on file IDs, rather than file paths. When Acronis Files Connect reindexes a volume, it reallocates file IDs to the files within the volume, thus invalidating the entries in Cumulus. Starting with version 5, Cumulus can store file paths in its catalog rather than IDs. This setting can be changed by selecting:
Why are my Intel Macs getting a Connection Failed 2 error?
This error only happens if you are connecting to Microsoft Services for Macintosh (SFM) using the custom Microsoft User Authentication Module (MSUAM). This issue does not affect Acronis Files Connect because it uses either the built-in DHX or Kerberos User Authentication Modules which work fine on the Intel Macs.
As noted in a previous Knowledge Base article, there is a bug in Mac OS X 10.5.6 that causes it to report no search results when searching against AFP servers other than Mac OS X 10.5, including Acronis Files Connect (formerly ExtremeZ-IP), Mac OS X 10.4 (Tiger), Mac OS X 10.3 (Panther), and Microsoft's now discontinued Services for Macintosh (SFM) on Windows 2000 or Windows 2003.
Clients suffer from extremely slow performance (up to 8 times slower) when browsing or performing read/write operations against Windows 2003 Servers (SP1 or above).
The problem has been reported with Broadcom and other NIC Cards which are TOE (TCP Offload Engine) enabled.
Acronis Files Connect (formerly ExtremeZ-IP)
Mac clients connected to a EZIP share suffers slow performance compared to SMB.
MassTransit Server
During the initial launch or start-up of Acronis Files Connect (formerly ExtremeZ-IP), the following error message may appear in the Acronis Files Connect Operation Log, or the "Application Log" of the Windows Event Viewer:
Memory settings for this server are not optimized correctly. You should reconfigure your server to maximize throughput for network applications.
Attempting to rename or duplicate a file whose name is longer than 31 characters on an Acronis Files Connect (formerly ExtremeZ-IP) volume from a Mac OS X client causes the file name to be truncated to 31 characters.
Copy a file with a long name to an Acronis Files Connect volume from a Mac OS X client. Attempt to rename the file, or duplicate it. The file name will be truncated.
When "My Documents" or "Shared Documents" type folders are shared as volumes, why do they sometimes fail to initialize?
Windows folders such as "My Documents" and "Shared Documents" are virtual folders that are mapped by Windows to subfolders in a user's profile directory. Attempting to share these resources will often result in the Acronis Files Connect volume failing to initialize. In addition, search index file creation will fail for these volumes. It is recommended that these special directories are not shared as volumes.
I have been using the "mount volume" command to mount AppleTalk-based AFP server volumes. This command doesn't seem to work with Acronis Files Connect (formerly ExtremeZ-IP) servers. What's wrong?
The original "mount volume" scripting addition works only for AppleTalk volumes. This command used the following syntax:
mount volume "volume" on server "server" in AppleTalk zone "zone"
Performance when using 3com series 4200 switches in conjunction with Acronis Files Connect (formerly ExtremeZ-IP) is several times slower than expected.
Install Acronis Files Connect on a server where the clients are connecting thru a 3Com series 4200 switch set to its default settings.
Within the application, Adobe InCopy performs file check-ins and check-outs to support multiple users working within a single document. When a segment of a document is checked out, it is given a file lock, which can be seen on the server as an .IDLK file. The idea behind this is that all client computers will be watching for these lock files, see them, and both display and honor them when access is requested from another individual.
In testing, we have found this functionality to be problematic on network shares. The results of our testing three different workflows follow:
When I tried to copy some files from one location to another on the server using the Macintosh Finder, I got an error message that said "FILENA~1.TXT" already existed. What's wrong?
Note:The following description applies to Mac OS 9 clients, or Mac OS X clients that are not running Acronis Files Connect (formerly ExtremeZ-IP) 3.0. Acronis Files Connect 3.0/Mac OS X clients can work with files longer than 31 characters.
There is a known issue that can occur when a Mac client connected to a Windows server using SMB creates a file or folder with a trailing space in the name. Mac OS X 10.4 Mac clients can connect to the server using AFP / Acronis Files Connect (formerly ExtremeZ-IP) and list the entire volumes contents, but newer 10.5 and 10.6 Mac clients will stumble on the file or folder that contains the trailing space and fail to list all subsequent items.
There are 2 options to fix this issue:
When I logon to an Acronis Files Connect (formerly ExtremeZ-IP) server from a Mac OS 9 client, I can't add my password to the keychain because the option is disabled. Why?
Look in the "Acronis Files Connect Administrator" program and make sure the "Allow Workstations To Save Password" button is checked. If this is not checked, workstations will not be able to save their passwords to their keychains because the "Add to Keychain" option will be disabled.
If a Macintosh client attempts to connect to an Acronis Files Connect (formerly ExtremeZ-IP) DFS root volume from a network subnet that is not assigned to a site in Active Directory, you may see this error message in the Acronis Files Connect debug log. "Unable to determine site index for ip address x.x.x.x. This user will not be able to access DFS shares on volume X"
Why do some of my folders within an Acronis Files Connect (formerly ExtremeZ-IP) volume and/or the volumes themselves appear locked from OS 10.4.6 (and higher) clients?
In OS X 10.4.6, Apple added support for viewing and modifying the "locked" status of folders over the network. Acronis Files Connect has always reported certain folders as locked to Macintosh clients, but until OS X 10.4.6, the clients never displayed these folders as locked.
After upgrading from previous versions to 2.1.1x18 or v3.0x10, a Mac user mounts a volume using a NT domain account:
a) Some (or all) folder/files within the volume are not visible, even though the user has permissions in NT
b) User is unable to write or delete inside a folder where they have NT permissions
Will the new Daylight Saving Time schedule cause any issues with MassTransit or Acronis Files Connect (formerly ExtremeZ-IP)?
We do not make any assumptions as to when the Daylight Savings Time shift will occur in either MassTransit or Acronis Files Connect. As long as the underlying Operating System properly accounts for the earlier DST shift date this year, our applications will behave in the same way as they would in any other transition to Daylight Savings Time.
I have shared volumes with Acronis Files Connect (formerly ExtremeZ-IP), but when I connect from the Macintosh, I do not see the volumes listed, or they are grayed out.
If the volume is not listed, open Acronis Files Connect Administrator on the server, and view the Volumes window. The list of volumes includes status information about the various windows:
What causes Acronis Files Connect (formerly ExtremeZ-IP) to re-index a volume?
For performance reasons, Acronis Files Connect indexes each volume that it shares, saving the names of every file and directory contained within the volume. While the volume is normally only indexed once, re-indexing can sometimes occur if the index becomes corrupted. Acronis Files Connect will consider an index corrupted and re-index if any of the following occur:
Windows services can fail to start if a file or folder "C:\Program" exists. The simplest way to solve the problem is to delete or rename the C:\Program folder or file. If you don't want to delete the "C:\Program" folder or file, you can perform the following steps:
We have received reports from some users of Acronis Files Connect (formerly ExtremeZ-IP) running Symantec Corporate Antivirus that their server performance may degrade over time and hang the server. If you are running Symantec Corporate Antivirus - please consider updating the SYMEVNT.SYS file to the latest version.
Install Symantec Corporate Antivirus and Acronis Files Connect on the same server.
A bug in the Symantec Corporate Antivirus Symevent files.
What does the following error mean "Acronis Files Connect Service Failed to start. Error 1053"?
Error 1053 is a generic service failure code and could be caused by many different things. However, if you see this error while starting the Acronis Files Connect service the most likely cause is that there are no IP addresses available for the service to listen on. The most common reason is a network interface has been disabled because of an unplugged cable.
What does it mean if ExtremeZ-IP.exe is listed as the faulting process in a kernel dump (BSOD)?
Crashes in Microsoft Windows fall into two broad categories:
1. Application crashes.
When I save a file using SMB protocol, what information is saved in the "dot-underscore" (._) files? How is this information stored on an NTFS file system?
Answer: Macintosh files have 2 parts;
The data fork: This is where the data is saved by an application. It is the equivalent of a "file" on the PC.
The Volumes tab of the Acronis Files Connect (formerly ExtremeZ-IP) Administrator indicates a volume has "failed to initialize."
This problem can occur when
1. SYSTEM account does not have Full Control to a volume
2. Volume’s mapping stream is corrupted
3. When the free space on a drive begins to run out
Acronis Files Connect (formerly ExtremeZ-IP) can register service principal names (SPNs) in cluster environments when Kerberos login support is enabled. These changes can effect clients connecting to Acronis Files Connect using Kerberos authentication.
Acronis Files Connect will register SPNs against the role object. For example, when using local SYSTEM as the File Connect service account, the following setup:
Role object: ROLE01
Node 1: NODE01
Node 2: NODE02
domain: example.com
MassTransit runs and currently ships without a dongle, but for those customers running older (5.x and later) versions of MassTransit, the option is available as well. In order to convert your dongled MassTransit server to a dongle-less version you will need to obtain a dongle config file from Acronis. If you are interested, please contact us at sales@acronis.com or https://support.acronis.com/mobility and your rep will get in touch with you to begin the process.
How do I configure Acronis Files Connect so Mac OS X 10.2.8 and 10.3.x clients can manage permissions on an AFP share?
Please open a technical support case at https://support.acronis.com/mobility/
