| Initialising redirection module. |
Debug |
The Redirection module is about to be started. |
N/A |
| Initialising redirection module static fields. |
Debug |
Static fields in the Redirection module are about to be initialised. |
N/A |
| Disposing redirection module. |
Debug |
The Redirection module is about to be disposed. |
N/A |
| Disposing detector module |
Debug |
The Detector module is about to be disposed. |
N/A |
| Trimmed request history file 'file path' by removing
bytes removed bytes. |
Debug |
The Devices.dat file has been reduced in size, as some stored requests are
no longer relevant. |
N/A |
| Could not open request history file 'file name' in mode 'mode',
with access 'access' and share 'share'. |
Debug |
The Devices.dat file could not be modified. Check the app pool has modify
permissions for the file. |
N/A |
| Redirection module could not automatically be registered. Redirection
services will not be available unless the HttpModule is included explicitly in
the web.config file or Microsoft.Web.Infrastructure is installed. |
Warn |
The Redirection module was not registered automatically. |
The 51Degrees Detector must be explicitly added in the web.config.
See the config guide for more
information. |
| Creating provider from binary data file 'file path'. |
Info |
The Detector is about to create a provider from binary data. |
N/A |
| Created provider from binary data file 'file path'. |
Info |
The Detector has completed creating the provider from binary data. |
N/A |
| Creating provider from XML data files 'file paths'. |
Info |
The Detector has completed creating the provider from xml data. |
N/A |
| Created provider from XML data files 'file paths'. |
Info |
The Detector is about to create a provider from xml data. |
N/A |
| Adding to existing provider from XML data files 'file paths'. |
Info |
The Detector is about add additional data to the provider from xml patch
files. |
N/A |
| Added to existing provider from XML data files 'file paths'. |
Info |
The Detector has finished adding additional data to the provider from xml patch
files. |
N/A |
| Added to existing provider from XML data files 'file paths'. |
Info |
The Detector has finished adding additional data to the provider from xml patch
files. |
N/A |
| The data provided is not supported by this version of Foundation. The
version provided is 'version' and the version expected is 'version'. |
Fatal |
The data provided is not supported by the Foundation. |
Get the latest Foundation and data. |
| Creating provider from embedded device data 'resource name'. |
Debug |
Embedded data is about to be loaded. If you were expecting external data
to be loaded check for another log stating why it has not. |
N/A |
| Created provider from embedded device data 'resource name'. |
Debug |
Embedded data has finished loading. |
N/A |
| Exception processing device data from binary file 'file path', and
XML files 'file paths'. Enable debug level logging and try again to
help identify cause. |
Fatal |
An error occurred reading data files. The message should yield more
information. |
Follow the extra information. Try removing patch files, if any to isolate
the problem. Contact Us if this error persists. |
| Automatically updated binary data file 'file name' with version
published on the 'date'. |
Info |
Device data has successfully updated. |
N/A |
| Activated binary data file 'file name' with new version dated the
'data published date'. |
Info |
New data has been loaded. |
N/A |
| Exception auto update download binary data file 'file name'. |
Warn |
There was an error getting new device data. The message should carry more
information which should correspond with another issue in this table. |
Follow advice from the additional information, and then Contact Us if the
error persists. |
| MD5 hash 'hash' validation failure with data downloaded from update URL '51Degrees.com url'.
| Warn |
Occurs when the file expected was different than the one downloaded, or
the licence key is not valid. |
Check the correct licence key is installed and that there are no proxies
that could be manipulating the response. If the problem persists, contact us. |
| Exception validating data array |
Warn |
New device data has been downloaded and passed validation but cannot be used as
it is missing data. |
Contact Us. |
| Auto local file check thread aborted |
Warn |
The local file check thread stopped running. This may be because the
server ran out of memory or the thread was somehow interrupted. The error
message should show more detailed information. |
Information from the message should help diagnosing the problem. If that
doesn't help, contact us. |
| Auto update download thread aborted |
Warn |
The auto update thread stopped running. This may be because the
server ran out of memory or the thread was somehow interrupted. The error
message should show more detailed information. |
Information from the message should help diagnosing the problem. If that
doesn't help, contact us. |
| Examining disk for newer data file. |
Debug |
Logs whenever the detector looks on disk for a new data file. This is
useful for when a data is manually updated, or environments with multiple
worker processes, as another process may have already downloaded new data. |
N/A |
| Stopping usage sharing as remote name '51Degrees.com url' timeout count
exceeded 'timeout limit'. |
Debug |
Share usage has failed many times. This can happen for a variety of
reasons, such as a firewall blocking web requests, or slow network connections. |
N/A |
| Stopping usage sharing as remote name '51Degrees.com url' returned
status description 'status'. |
Debug |
This can happen if the share usage service is experiencing difficulty usually related to a large number of requests. |
N/A |
| Stopping usage sharing as insufficient permission to send device information to '51Degrees.com url'. |
Debug |
This happens when the identity of the application or if running on IIS the application does not have permission to make HTTP requests to send device information. |
N/A |
| Stopping usage sharing as remote name '51Degrees.com url' could not be resolved.'. |
Debug |
The share usage endpoint could not be resolved. |
This is likely to be due incorrect DNS settings on the web server. |