If a problem is not covered here, or the solution does not work, contact Accredo Support or your Accredo QSP, see Accredo Help and Error Messages.
Bad Signature |
Bad signature means Accredo is asking for the first 4 bytes of the file to check that it contains the expected value and it does not. This implies something other than Accredo has changed the files. Accredo files all start with either ADAT or AKEY to indicate Accredo data or index files. Accredo never writes to the file signature, it is in the files which are copied from the live subdirectory when a new company database is created. Accredo checks the signature on each initial open and never writes to the signature after creation. If the signature is anything other than the expected value, you will get a bad signature error. Bad signature errors may be early sign of media or file system damage, as in memory corruption, or has been the case in a number of reports, the first error indicating a Ransomware file locking virus. Damaged Index files can be fixed by a file recovery since this rebuilds them. Damaged data files will require a restore to backup. |
Assertion Failure |
These errors are Accredo saying it explicitly assumes this should never happen and it has. It may be Accredo sanity checking responses from Windows or Printer Drivers, or an internal state Accredo doesn't think should occur but has. |
Access Violation |
Memory access rules have been violated, and some code (not necessarily in Accredo) is being either read, written to or executed when it is not supposed to be. Data execution protection can trigger these errors and we recommend it is turned off for Accredo on servers if you are using MAPI or Outlook integration for email, such as under Remote Desktop Host. |
System Error |
These are errors Accredo is getting back from Windows as a result of requesting a service from the operating system. Accredo is not causing the error, it is just reporting it with as much information as it can extract. |