System log
This window displays important and current information about DC++ and your
interactions with the program. If DC++ behaves unexpectedly, you can look in
this window for a possible explanation.
There are two kinds of messages can appear in the System log : events
and errors. While the first kind of messages are usual, you may want
to pay more attention to the latter ones. Error messages shown in the log
may come from some failed automatic operation or as a result of your latest
interaction with the program interface. The very last message entry in the
log is shown in the statusbar of the main DC++ window. You can check the
tooltip of the status bar for the last few log entries.
Note that not all error messages appear in the System log. Some
windows (like Download Queue or Search) have their own functional status bar
and messages related to those windows may appear only on their own place.
Context menu commands
Messages may contain path of file(s) associated with them. The path appears
between <brackets> and a right click in it will bring up a context
menu with possibility to open/check the particular file in Windows Explorer.
- Open
- Opens the file with its respective external viewer software. You should have
the appropriate viewer / player software installed and correctly registered
to be able to open the file.
- Open folder
- Opens the selected folder (or the folder containing the selected file) in
Windows Explorer.
- Shell menu
- Opens the Windows shell menu as submenu items. This menu contains the same
items as in the context menu of Windows Explorer. Note that the submenu
elements will be loaded the time when it is opened. If you have large number
of context menu items registered with Windows it may take a few seconds to
show the full menu.
Event messages
- File list refresh initiated
- This message means that shared folders has been started to check for new or
changed files. The process can be initiated automatically (once at startup
and then periodically according to the Auto file list
refresh setting) or manually by the Refresh file list menu command in
the File menu. The new or changed content will be
(re)hashed and a log entry will be added for each hashed file (see below).
- File list refresh finished
- This indicates an end of the current hashing procedure. As long as your
shared files remain unchaged the filelist reflects the current state of your
share.
- File list [path] generated
- A new file containing your own file list has just been generated. Own file
lists are created before the first upload request.
- Finished hashing: [path] ([size] at [speed])
- Shown for each successfully hashed file including the full path, filesize
and hashing speed. Speed value may won't be added for small files.
- [Nick]: matched [x] files
- This message is shown when someone's filelist has just matched to your
queue. [x] shows the number of found matches.
- The queued file %1% already exists in your share, removing from the queue
- You have the Don't download files already in share setting
enabled and tried to download an already shared file. The operation was
prevented accordingly.
- Duplicate file will not be shared: [path1] (Size: [size]) Dupe matched
against: [path2]
- This means that since you have Keep duplicate files in your
file list setting disabled, a file ([path1]) beeing indexed and already
shared (as [path2]) won't be added to your share again.
- Hash database rebuilt
- Informs you about the finish of a full hash database rebuilding process
which can be initiated by the /rebuild chat command
- Disconnected user leaving the hub: [nick]
- You have Automatically disconnect users who leave the hub
setting enabled and this message informs you about its effect.
- MAGNET Link detected: [link]
- The client received a magnet link handle request.
- Generated new TLS certificate
- As Security certificates enabled but no existing TLS
certificate files found (or they are invalid), new certificate files
generated in the 'Certificates' subfolder of the directory where DC++
configuraton files are stored.
- Port mapping: Successfully created port mappings (Transfers: [port1],
Searches: [port2], Encrypted transfers: [port3]) on the [router name] device
with the [interface identification] interface
- DC++ has managed to automatically create port forwarding rules on the router
using NAT-PMP or UPnP.
- Port mapping: Successfully removed port mappings from the [router name]
device with the [interface identification] interface
- DC++ has managed to remove the existing port forwarding rules from the
router made by NAT-PMP or UPnP.
- Connectivity: Determining the best connectivity settings...
- This message signals that Automatic connectivity setup has
started.
- Connectivity: Public IP address detected, selecting active mode with direct
connection
- It means that Automatic connectivity setup determined that
you have a public IP address so it assumed that you are directly connected
to the Internet.
- Connectivity: Local network with possible NAT detected, trying to map the
ports...
- Automatic connectivity setup determined that you have a private IP address and it started to discover for a possible
gateway (router) capable of automatic port mapping.
- Connectivity: Active mode could not be achieved; a manual configuration is
recommended for better connectivity
- Automatic connectivity setup did not find any way to
configure any kind of active connection so as a last resort it selected
passive connection mode with NAT traversal capability.
Error messages
Some errors shown in the log contain additional system messages provided by
the operating system. These messages usually tell you more about the exact
problem; they are marked as [error message] in the description of possible
logged errors below. Note that system messages are always shown in the
language of your operating system even if you have chosen another one for
DC++.
- Error registering dchub:// link handler
- Error registering adc(s):// link handler
- Error registering Magnet link handler
- These errors mean that DC++ was unable to register the appropriate link
handler(s) in Windows, per the Register with Windows to handle
magnet: URI links and Register with Windows to handle
dchub://, adc:// and adcs:// URL links settings. The most common reason
of an unsuccesful registration is that the user account under which DC++ is
running does not have appropriate rights for (write) access the required
parts of the Windows Registry.
- Port mapping: Failed to get external IP
- This error message can appear when DC++ tries to map ports for incoming
connections via NAT-PMP / UPnP and means that although port mappings were
successful, DC++ couldn't get the external IP address from the gateway
(router) device. If this message persists, it may be because of broken
NAT-PMP / UPnP support of the device. This is not very important, since DC++
can still gather the external IP from connected hubs if it is
allowed to do so.
- Port mapping: Another port mapping attempt is in progress...
- This means that an Automatic connectivity setup attempt was
started too soon (the previous operation has not been finished). Try
restarting DC++ if this message persists. If restart DC++ does not help the
most probable reason is broken NAT-PMP / UPnP support of your (router)
device.
- Port mapping: Failed to initalize the [interface identification] interface
- DC++ failed to initalize one of its NAT-PMP or UPnP interfaces and will try
to use the next one in the row.
- Port mapping: Failed to map the [Transfer/Encrypted transfer/Search] port
([port number] [TCP/UDP]) with the [interface identification] interface
- The currently used port mapping interface failed to map the shown port. This
error message can appear when DC++ tries to map ports for incoming
connections via NAT-PMP / UPnP. It means that no compatible device could be
found or that the device in question is not responding. DC++ will try to use
the next automatic port mapper interface in the row. This message can occur
during Automatic connectivity setup, when DC++ is trying to
discover a possible NAT-PMP / UPnP device for setting up active mode. This
message is a real problem only if you selected the 'Let DC++ configure my
router (NAT-PMP / UPnP)' option manually in Incoming connection
settings. In this case, refer to the port mapping FAQ
for more information.
- Port mapping: Failed to remove port mappings from the [router name] device
with the [interface identification] interface
- DC++ has failed to remove the existing port forwarding rules from the router
made by NAT-PMP or UPnP. This message can appear at
shutdown or during an Automatic connectivity setup attempt
and it means that existing port mappings created earlier couldn't be removed
successfully. If this message persists the most probable reason is broken
NAT-PMP / UPnP support of the (router) device.
- Connectivity: Unable to open TCP/UDP/TLS port(s); connectivity settings must
be configured manually
- You can get this message only when Automatic connectivity
setup is enabled and DC++ failed to open port(s) before trying to
determine the available conncetion types. Possible reasons include the
choosen port(s) are already occupied by another application or DC++ is blocked by a software firewall.
- The encrypted transfer port cannot be the same as the transfer port,
encrypted transfers will be disabled
- The two kind of transfers cannot use the same port therfore the secure one
had to be disabled. You have to specify different TCP port for the different
transfers in the Incoming connection settings or review the
current connectivity setup.
- Not listening for connections - please restart DC++
- An unrecoverable low level networking error keeps DC++ from listening for
connections. Search and download won't work until you restart DC++.
- Connectivity error: [error message]
- Connectivity restored
- Because of a low level networking error DC++ does not listen for file
transfer connections. The problem lasts until the next 'Connectivity
restored' message.
- Search disabled: [error message]
- Search enabled again
- Because of a low level networking error DC++ does not listen for search
results. The problem lasts until the next 'Search enabled again' message.
- Failed to load certificate file
- There was a problem loading your own certificate file, its contents are
damaged or invalid.
- Failed to load private key
- There was a problem loading your own private key file, its contents are
damaged or invalid.
- Failed to load trusted certificate from [path]
- There was a problem loading one of the trusted certificate files, its
contents are damaged or invalid.
- TLS disabled, failed to generate certificate: [error message]
- TLS certificate files are missing or could not be opened. DC++ tried to
regenrerate them but it wasn't successful, either. Make sure you have write
access rights to the 'Certificates' subfolder of the directory where DC++
configuraton files are stored.
- TLS disabled, no certificate file set
- TLS can't be used because no certificate files set. You should set or
generate them properly in the Security & certificates
page.
- Certificate verification for [CA name] failed with error: [error message]
(certificate KeyPrint: [keyprint])
- The security certificate verification of user or hub with keyprint
[keyprint] has failed because of [error message].
- CRC32 inconsistency (SFV-Check) : [path]
- You have automatic SFV checking enabled and a downloaded
file is not passed the SFV-check. The file will be downloaded again.
- File list refresh in progress, please wait for it to finish before trying to
refresh again
- Only one file list refreshing operation can be run at the same time.
- File list refresh failed: [error message]
- The background process for refreshing file list is failed to start.
- Hashing failed: [error message]
- Error occured during indexing or share rebuilding.
- Error hashing [path]: [error message]
- Error when hashing the file specified in [path].
- Error saving hash data: [error message]
- Error when creating or updating hash index file (HashIndex.xml).
- Error creating hash data file: [error message]
- Error when creating hash data file (HashData.dat).
- [path] not shared; calculated CRC32 does not match the one found in SFV
file.
- Before sharing files DC++ will automatically check them against an .SFV file
(if one exists in the same directory) to make sure that no corrupted files
will be shared. If you get this error then either your file(s) are corrupted
or the control data in the corresponding .SFV file is outdated or damaged.
- Unable to move [path1] to [path2] ([error message]); renamed to [path3]
- Moving a finished download [path1] from the unfinished downloads folder to
its target place [path2] wasn't successful because of [error message] so the
file is left in the unfinished downloads folder and renamed to its orginal
name ([path3]).
- Unable to move [path1] to [path2] ([error message1]) nor to rename to
[path3] ([error message2])
- Moving a finished download [path1] from the unfinished downloads folder to
its target place [path2] wasn't successful because of [error message1] so
the file is left in the unfinished downloads folder. DC++ tried to rename it
to its orginal name [path3] but the rename operation has failed either,
because of [error message2].
- Unable to open filelist: [filename]
- There were problems opening a downloaded filelist, its corrupted or its size
is bigger than the maximum size allowed to open.
- Unable to send file [path]: [error message]
- There was a problem preparing file [path] upon an upload request by a peer.
- Invalid regular expression: [regex]
- There was a problem applying a regular experssion [regex] specified in one
of the filter functions.
- HTTP file download failed to create file [filename], error: [error message]
- The built-in HTTP downloader couldn't save the file it has downloaded
because of [error message].