|
NOTE
|
|
In some cases, it may not be possible to resolve the problem with the steps described here.
|
|
Cause
|
A file required to connect to a folder registered as a library (iwu file) that should be in said folder, for some reason cannot be found.
The registered folder was not found. (If the folder was shared, someone might have deleted it, etc.)
|
|
Remedy
|
Cancel the registered library and register it again.
|
|
Cause
|
Connected to the Document Server Library but could not find or access the library.
|
|
Remedy
|
Check to make sure that the library exists.
Check also that you have access rights to the library and grant the access rights as necessary.
|
|
Cause
|
IIS or the site is stopped on the Document Server you attempted to connect to.
|
|
Remedy
|
Check the service status of the server.
|
|
Cause
|
When connecting to the Document Server Library, connecting to a server with an unknown protocol failed.
|
|
Remedy
|
Check that the server you are attempting to connect to is a supported server version.
|
|
Cause
|
When connecting to the Document Server Library, you entered an incorrect user name or password three times in a row at the login authentication.
|
|
Remedy
|
Enter your correct user name and password.
Alternately, check whether the user is registered in the server you are connecting to.
|
|
Cause
|
When connecting to the Document Server Library, an operation was executed that the login user is not permitted to perform on the specified library.
|
|
Remedy
|
Check that you have access rights to the library you connected to and grant the access rights as necessary.
|
|
Cause
|
Cannot find or cannot access a file in a network folder of a local library.
|
|
Remedy
|
Check to make sure that the network folder and the file exist.
Also, check to make sure that you have permission to access the network folder and file.
|
|
Cause
|
The settings file of a monitoring target folder does not exist.
|
|
Remedy
|
Check whether the settings file of the monitoring target folder exists.
|
|
Cause
|
Reading or writing of the settings file of a monitoring target folder failed.
|
|
Remedy
|
Check the settings file of the monitoring target folder.
Or restart Desktop Browser.
|
|
Cause
|
Selection or cancelation of a folder as a monitoring target failed.
|
|
Remedy
|
Check the settings file of the monitoring target folder.
Or restart Desktop Browser.
|
|
Cause
|
Desktop Editor failed to start.
|
|
Remedy
|
If Desktop Editor does not start correctly, reinstall Desktop.
|
|
Cause
|
The user currently operating does not have the write permission for folders.
|
|
Remedy
|
Check your user permission level.
|
|
Cause
|
An access error occurred when accessing a temporary folder.
|
|
Remedy
|
Grant permission to access the temporary folder.
|
|
Cause
|
Desktop Editor failed to start.
|
|
Remedy
|
If Desktop Editor does not start correctly, reinstall Desktop.
|
|
Cause
|
Tried to delete a folder with 10 or more subfolders.
Deleted with many files left in the Recycle Bin.
|
|
Remedy
|
Select fewer documents to delete at once and try the operation again.
Delete subfolders and their contents, from the deepest subfolder up to the 10th level.
Try again after emptying the Recycle Bin.
|
|
Cause
|
Tried to register a file with a library, even though registering that file was prohibited by Document Server.
|
|
Remedy
|
Check the following settings on Document Server.
File types to be blocked
Maximum file size to be uploaded
|
|
Cause
|
With Desktop running, an addition was made by a Document Server setting to the types of files to block, and a target file was checked out or uploaded in Desktop.
|
|
Remedy
|
Delete the target file type from the types of files to block.
Restart Desktop, and execute the check out or upload again.
|
|
Cause
|
An access error occurred when accessing the network.
|
|
Remedy
|
Check the network conditions.
|
|
Cause
|
An access error occurred when accessing the network.
|
|
Remedy
|
Check the network conditions.
|
|
Cause
|
imageRUNNER ADVANCE Settings
The setting of [Settings/Registration] > [Function Settings] > [Store/Access Files] > [Advanced Space Settings] > [File Formats Allowed for Storing] is not [All].
|
|
Remedy
|
imageRUNNER ADVANCE Settings
Select [Settings/Registration] > [Function Settings] > [Store/Access Files] > [Advanced Space Settings], and set [File Formats Allowed for Storing] to [All].
|
|
Cause
|
An access error occurred when accessing the network.
|
|
Remedy
|
Check the network conditions.
|
|
Cause
|
The download target file does not exist.
|
|
Remedy
|
Refresh the display to show the latest information, and then check again whether the file exists.
|
|
Cause
|
An access error occurred when accessing the network.
|
|
Remedy
|
Check the network conditions.
|
|
Cause
|
An access error occurred when accessing the network.
|
|
Remedy
|
Check the network conditions.
|
|
Cause
|
An error occurred when connecting to Document Server.
|
|
Remedy
|
Check the connection status of the Document Server.
|
|
Cause
|
An access error occurred when accessing the network.
|
|
Remedy
|
Check the network conditions.
|
|
Cause
|
The document is currently opened by another user.
|
|
Remedy
|
Close the document opened on the computer of the other user.
|
|
Cause
|
The document is not currently opened by another user, but the computer considers it to still be opened
|
|
Remedy
|
Wait over 10 seconds, and then open the document again.
|
|
Cause
|
An access error occurred when accessing a file, temporary folder, or check out folder.
|
|
Remedy
|
Grant permission to access the file, temporary folder, or check out folder.
|
|
Cause
|
An access error occurred when accessing a file or temporary folder.
|
|
Remedy
|
Grant permission to access the file or temporary folder.
Check whether the file is corrupted.
|
|
Cause
|
It occurs when converting a Word file to a PDF on Desktop Browser.
|
|
Remedy 1
|
Change any of the following optional settings for Word, and then convert to PDF on Desktop Browser again.
Select [Basic Settings] > [Microsoft Office User Settings], and enter characters other than a space into [User Name] and [Initial]
Select [Advanced Settings] > [Print], and deselect the [Print in background] check box
|
|
Remedy 2
|
A version older than Microsoft Office 2007 may be installed. Desktop supports Microsoft Office 2007/2010/2013/2016.
In this case, perform the following procedure to perform PDF conversion. 1. Open the document with the application associated with the document.
2. In the application, select [Canon Desktop Document Writer] as the printer and perform printing.
3. Select the [File] menu in Desktop Editor > [Export as PDF].
|
|
Cause
|
Creation of a unique folder failed.
|
|
Remedy
|
Check the free disk capacity, and check the permission to write to temporary folders.
|
|
Cause
|
The folder for storing the cabinet information settings file (AppData\Local\Canon\iWDT\x.x\DMS\Neutral\Cabinets) does not exist.
The cabinet information settings file (Cabinets.xml) does not exist.
The contents of the cabinet information settings file (Cabinets.xml) are invalid.
|
|
Remedy
|
Restart Desktop Browser.
|
|
Cause
|
Access to a file failed.
|
|
Remedy
|
Check whether you have permission to access the file, and whether the file is corrupted.
|
|
Cause
|
More than 20,000 documents are managed in the database of a Network Library (database).
|
|
Remedy 1
|
Change the settings of the selected Network Library (database) to not perform database management.
|
|
Remedy 2
|
Cancel database management for folders in the selected Network Library (database) that include documents that do not require database management to reduce the number of managed documents. The administrator of Desktop must change the database management settings.
Setting and Management Range in the Database (Administrator Guide)
|
|
Cause
|
The capacity of the database for document management in a Network Library (database) is 2 GB.
|
|
Remedy 1
|
Change the settings of the selected Network Library (database) to not perform database management.
|
|
Remedy 2
|
Cancel database management for folders in the selected Network Library (database) that include documents that do not require database management to reduce the number of managed documents. The administrator of Desktop must change the database management settings.
Setting and Management Range in the Database (Administrator Guide)
|
|
Cause
|
One of the following is true for the database for document management in a Network Library (database).
More than 20,000 documents are managed by the database
The capacity of the database is 2 GB
|
|
Remedy 1
|
Change the settings of the selected Network Library (database) to not perform database management.
|
|
Remedy 2
|
Cancel database management for folders in the selected Network Library (database) that include documents that do not require database management to reduce the number of managed documents. The administrator of Desktop must change the database management settings.
Setting and Management Range in the Database (Administrator Guide)
|
|
Cause
|
An error occurred while writing to a checkout management file.
|
|
Remedy
|
As required, move the checkout management file to a backup location (or delete it), and then restart Desktop Browser.
|
|
Cause
|
The duplicate process launch control settings file (ProcessControlSetting.xml) could not be read.
|
|
Remedy
|
Check access permission for the duplicate process launch control settings file (ProcessControlSetting.xml).
|
|
Cause
|
The format of InputBarConfigList.xml was invalid.
|
|
Remedy
|
Check whether the contents of the file are correct.
|
|
Cause
|
Reading of InputBarConfigList.xml was denied.
|
|
Remedy
|
Check the access permission for the file.
|
|
Cause
|
Reading of the InputBarConfigList.xml file failed.
|
|
Remedy
|
Check the status of the file.
|
|
Cause
|
An unexpected error occurred.
|
|
Remedy
|
Check whether an Advanced Space library is a monitoring target of your security software. If so, remove it from the monitoring targets in your security software.
Restart the application, and try the operation again.
If this does not resolve the problem, contact your system administrator or support center.
|
|
Cause
|
Access to a file or temporary folder failed.
|
|
Remedy
|
Grant permission to access the file or temporary folder.
Check whether the file is corrupted.
|
|
Cause
|
An access error occurred when accessing the network.
|
|
Remedy
|
Check the network conditions.
|
|
Cause
|
The read target shortcut file was a directory.
|
|
Remedy
|
Check the name of the shortcut file that you want to create.
|
|
Cause
|
A memory shortage occurred.
|
|
Remedy
|
Check the amount of free memory, and exit applications that you are not using.
|
|
Cause
|
Reading of the desktop.ini file failed.
|
|
Remedy
|
Grant access permission for the desktop.ini file.
|
|
Cause
|
Login authentication failed.
|
|
Remedy
|
Enter the correct user name and password.
|
|
Cause
|
An address book file cannot be found.
|
|
Remedy
|
Specify the correct address book file.
|
|
Cause
|
The directory containing the address book file cannot be found.
|
|
Remedy
|
Specify the correct address book file.
|
|
Cause
|
A .NET Framework exception occurred when acquiring the address book of a device (network error).
|
|
Remedy
|
Check whether you can connect to the fax, or check whether there is a network problem.
|
|
Cause
|
[Authentication Information Settings] is not set correctly in Desktop Communicator.
|
|
Remedy
|
Set [Authentication Information Settings] correctly in Desktop Communicator.
|
|
Cause
|
Desktop Communicator is not installed in the device.
The Desktop Communicator service is stopped on the device.
A device which you cannot obtain the address book from is specified.
|
|
Remedy
|
Check the status of the device.
|
|
Cause
|
There was not enough memory to start the Hot Folder periodic monitoring thread.
|
|
Remedy
|
Check the amount of free memory, and exit applications that you are not using.
|
|
Cause
|
An unexpected error occurred while displaying the manual.
|
|
Remedy
|
Reinstall Desktop.
|
|
Cause
|
An error occurred while opening an IWB document.
Execution of Desktop Editor failed.
|
|
Remedy
|
If Desktop Editor does not start correctly, reinstall Desktop.
|
|
Cause
|
Execution of Desktop Editor failed.
|
|
Remedy
|
If Desktop Editor does not start correctly, reinstall Desktop.
|
|
Cause
|
An error occurred during creation of a shortcut.
|
|
Remedy
|
Check the access permission for the file.
|
|
Cause
|
Print processing by an associated application failed.
|
|
Remedy
|
The application associated with the extension of the print target file may not be available, or the associated application may not support printing. Associate the extension with an application that supports printing.
|
|
Cause
|
Setting information cannot be saved because modification of an icon failed.
|
|
Remedy
|
This is an unexpected error. It cannot be avoided. (This error may occur in cases such as modification failure because the desktop.ini file is open when registering an SMB send button.)
|
|
Cause
|
Deletion of a backup of the desktop.ini file failed.
|
|
Remedy
|
Check the permission to access the backup of desktop.ini, and other reasons why deletion may have failed.
If other methods fail, delete the file manually.
|
|
Cause
|
WLS (Windows Login Service) is not enabled (the authentication service is not appropriate).
|
|
Remedy
|
Enable WLS (Windows Login Service).
Check that the device authentication service is using an appropriate authentication method (SDL/NTLM/department ID management authentication/Basic authentication).
|
|
Cause
|
The operation could not be completed because an error occurred (reading of the xml file failed).
|
|
Remedy
|
Reinstall Desktop.
|
|
Cause
|
Deletion of a backup of the desktop.ini file failed.
|
|
Remedy
|
Check the permission to access the backup of the desktop.ini file, and other reasons why deletion may have failed. If other methods fail, delete the file manually.
|
|
Cause
|
A user logged in to Document Server cannot complete a check out operation.
|
|
Remedy
|
Confirm that the target file in Document Server can be checked out.
|
|
Cause
|
Checkout failed.
|
|
Remedy
|
Refresh the display to show the latest information, and then confirm that the specified document is not already checked out.
|
|
Cause
|
Access permission has not been granted for the transfer destination folder.
|
|
Remedy
|
For scanned documents, or transfer destination folders for Hot Folder transfers, check access permission.
|
|
Cause
|
IIS is stopped.
|
|
Remedy
|
Check the connection status of the server.
|
|
Cause
|
Write permission for a document has not been granted.
|
|
Remedy
|
Grant write permission for the document.
|
|
Cause
|
A user logged in to Document Server does not have access permission.
|
|
Remedy
|
Grant access permission to the user logged in to Document Server.
|
|
Cause
|
A document of the same name already exists.
|
|
Remedy
|
Because a document with the same name already exists at the destination, move, delete, or rename the original file.
|
|
Cause
|
The license is invalid when connecting to a library.
|
|
Remedy
|
Check the license information.
|
|
Cause
|
There was not enough memory to generate a thread for uploading a file.
|
|
Remedy
|
Exit applications that you are not using.
|
|
Cause
|
A file was modified during upload processing.
|
|
Remedy
|
Do not modify a file during a file transfer.
|
|
Cause
|
A transfer to Document Server is continuing when the maximum upload size has been exceeded.
|
|
Remedy
|
Reduce the number of files being transferred at once, or reduce the file size.
|
|
Cause
|
File access failed.
|
|
Remedy
|
Check whether you have permission to access the file, and whether the file is corrupted.
|
|
Cause
|
An error occurred in the reference check of an executable file.
|
|
Remedy
|
A link file may be corrupt. Create the link file again.
|
|
Cause
|
Creation of a Hot Folder subfolder failed.
|
|
Remedy
|
Check the access permission of the common folder that you specified in the Transfer Source screen when creating an SMB send button. If permission has not been granted to create a folder, grant the permission.
|
|
Cause
|
A correct IP address or host name was not input, or the input was correct but network connection failed.
|
|
Remedy
|
Enter a correct IP address or the name of an existing host.
|
|
Cause
|
The device at the specified IP address failed to create an SMB send button.
|
|
Remedy
|
Check whether the specified IP address is the address of a device that can create an SMB send button, and specify a correct IP address.
|
|
Cause
|
A correct IP address or host name was not input, or the input was correct but network connection failed.
|
|
Remedy
|
Enter a correct IP address or the name of an existing host.
|
|
Cause
|
The device at the specified IP address or the device specified by entering a host name directly does not support the creation of an SMB.
|
|
Remedy
|
Check whether the specified IP address is the address of a device that can create an SMB send button, and specify a correct IP address.
|
|
Cause
|
A correct IP address or host name was not input, or the input was correct but network connection failed.
|
|
Remedy
|
Enter a correct IP address or the name of an existing host.
|
|
Cause
|
Failure to acquire the type of authentication function.
|
|
Remedy
|
A fault may have occurred on the network, such as a device losing power. Check the device and network environment.
|
|
Cause
|
Failure to acquire the type of authentication function.
|
|
Remedy
|
A fault may have occurred on the network, such as a device losing power. Check the device and network environment.
|
|
Cause
|
Authentication failure.
|
|
Remedy
|
A fault may have occurred on the network, such as a device losing power. Check the device and network environment.
|
|
Cause
|
A correct IP address or host name was not input, or the input was correct but network connection failed.
|
|
Remedy
|
Enter a correct IP address or the name of an existing host.
|
|
Cause
|
Failure to acquire the type of authentication function.
|
|
Remedy
|
A fault may have occurred on the network, such as a device losing power. Check the device and network environment.
|
|
Cause
|
An SMB send button to the device could not be created.
|
|
Remedy
|
Check that the device authentication service is using an appropriate authentication method (SDL/NTLM/department ID management authentication/Basic authentication).
|
|
Cause
|
An SMB send button to the device could not be created.
|
|
Remedy
|
Check that the device authentication service is using an appropriate authentication method (SDL/NTLM/department ID management authentication/Basic authentication).
|
|
Cause
|
An SMB send button to the device could not be created.
|
|
Remedy
|
If more than 15 minutes pass after login without a button being created, the login session becomes invalid. Check the authentication again in the authentication screen, or redo from the start.
|
|
Cause
|
A correct IP address or host name was not input, or the input was correct but network connection failed.
|
|
Remedy
|
Enter a correct IP address or the name of an existing host.
|
|
Cause
|
Failure to acquire the type of authentication function.
|
|
Remedy
|
A fault may have occurred on the network, such as a device losing power. Check the device and network environment.
|
|
Cause
|
The length of the specified path was too long.
|
|
Remedy
|
Enter the path within 250 characters including the folder name.
It is recommended that it be kept as short as possible because it stores files.
|
|
Cause
|
The folder could not be created because a reserved device name was used.
|
|
Remedy
|
Specify a name that is not a Windows reserved device name.
|
|
Cause
|
The folder could not be created because a reserved device name was used.
|
|
Remedy
|
Specify a name that is not a Windows reserved device name.
|