Version 2.0.0 Page 52
access to any of the defined fileshares, the
authorization list for the fileshare needs to be
expanded to include an Active Directory group
that includes this user.
An LDAP error occurred trying to
retrieve the selected file share
destination.
Cause: The LDAP lookup failed.
Resolution: See section 8.2 above.
Cause: The LDAP lookup succeeded but the attribute
chosen for the replacement value does not exist or
has no value.
Resolution: See section 7.2.2 for editing an existing
fileshare.
No UNC Path has been defined for this
destination.
Cause: The UNC Path option for the Fileshare was
not defined.
Resolution: See section 7.2.2 for editing an existing
fileshare.
The scanned file size and saved file size
do not match.
Cause: After the file is scanned, the number of bytes
scanned is compared to size of the file written,
and they are not the same.
Resolution: This typically means the fileshare is full
or the user has reached their disk quota. Check
the free space / disk quota on the fileshare.
User does not have read access to the
file share; unable to verify the file size.
Cause: After the file is scanned, the number of bytes
scanned is compared to the size of the file written
to insure no error occurred. The user does not
have read access to the fileshare so the file size
cannot be determined.
Resolution: The user needs to be given read access to
the fileshare.
Invalid filename specified. Cause: An invalid character was included as part of
the filename provided by the user.
Resolution: The user cannot include the following
characters in the filename: |, <, >, \, /, *, ?, ;, :, or
^.
An error occurred connecting or writing
to the File Share.
Cause: The UNC Path used the IP address of the file
server.
Resolution: In order to connect to the fileshare using
the user’s credentials, the hostname of the file
server must be used. See section 7.2.2 for editing
an existing fileshare.
Cause: The hostname of the file server could not be
resolved to an IP Address.
To Next Page
Loading...
