Difference between revisions of "Troubleshoot regify client"
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
== usage == | == usage == | ||
| + | ===Im not able to send SMTP mails using a google mail account=== | ||
| + | The regify client is currently not able to use SSL secured SMTP servers. Google mail is one of the rare SMTP servers that do not allow any other connection. Upon this, the regify client is currently not working together with google mail SMTP accounts. | ||
| − | ' | + | ===I'm having connection problems=== |
| + | Common problems are: | ||
| + | * Error 58 -> Problem with SSL certificate | ||
| + | * Error 2 -> Missing internet connection (check proxy and connectivity) | ||
| + | It may help you to activate the debug log (described on this page). The CURL entries are giving more information about reasons. | ||
| − | : | + | ===The regify client complains "The given file can not get opened (no regify file)."=== |
| + | German: "Die angegebene Datei kann nicht geöffnet werden (keine regify® Datei)." | ||
| − | + | Up to version V3.6.5 of the regify-client, this error occurs if there are more than 15 to 22 attachments added to the regify file (depending on the length of the filename and the version of the regify client used for regify generation). To fix this, update to a client newer than V3.6.5 or open the regify-file by uploading to the regify portal of your regify-provider. | |
| − | : | + | ===I'm getting an Error: 20 when trying to read regify emails=== |
| + | Most of the time this happens because the recipient is trying to read an email that is addressed to one of their email addresses that is not registered with their regify account. Up to 5 email addresses can be registered with a regify account. Log into the provider portal and add the missing email address. | ||
| + | In rare cases this error can be caused by older regify clients when the recipient email address was passed in as mixed case. Example Jane.Doe@company.com. To resolve this, the sender needs to upgrade their regify client or insure that the recipient email address is lowercase, in our example: jane.doe@company.com | ||
| − | + | ===The regify client complains with error 59 while opening a message (Internal Protocol Error)=== | |
| + | Due to a bug in the regify Client-SDK, the error messages for Errorcodes 21 and 22 are displayed as error 59. The most possible reason is, that the sender decided the recipient to be authenticated. Please authenticate yourself (the recipient) at your regify portal. If the authentication-option is not visible, please contact your regify-provider directly. This bug is fixed since regify-client V3.7. | ||
| − | + | == setup == | |
| − | + | ===I like to install the client without installing a Outlook or Thunderbird AddIn=== | |
| − | + | Please choose the custom install option while setup. You can disable the Outlook AddIn and the Thunderbird AddIn in the further dialog. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | ===''Module c:\-path-\regify client\regifyAddIn.dll failed to register. HRESULT -2147467259. Contact your support personnel.''=== | ||
| + | ===''Fehler beim registrieren von Modul c:\-path-\regify client\regifyAddIn.dll. HRESULT -2147467259. Wenden Sie sich an den Support.''=== | ||
| − | + | The most likely cause of the error is an installed Microsoft Outlook with 64 Bit. The regify AddIn is only able to run on 32 Bit Outlook installations. Please uninstall your Microsoft Office and reinstall the 32 Bit version. If you do not plan to use the Outlook AddIn, you may exclude the AddIn from installation by using the custom setup option. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== debugging == | == debugging == | ||
| − | + | ===Start extended debug logging=== | |
Beginning with version 3.8.0 of the regify-client, you can get a detaild debug-log. To activate debugging, please open the regify client ini-file (''%APPDATA%\regify\regify_client.ini'') and insert the following value in the [REGIFY] section: | Beginning with version 3.8.0 of the regify-client, you can get a detaild debug-log. To activate debugging, please open the regify client ini-file (''%APPDATA%\regify\regify_client.ini'') and insert the following value in the [REGIFY] section: | ||
[REGIFY] | [REGIFY] | ||
| Line 59: | Line 38: | ||
To deactivate loggin, please remove this entry or set DebugLevel = 0. | To deactivate loggin, please remove this entry or set DebugLevel = 0. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 14:51, 18 June 2012
Contents
- 1 usage
- 1.1 Im not able to send SMTP mails using a google mail account
- 1.2 I'm having connection problems
- 1.3 The regify client complains "The given file can not get opened (no regify file)."
- 1.4 I'm getting an Error: 20 when trying to read regify emails
- 1.5 The regify client complains with error 59 while opening a message (Internal Protocol Error)
- 2 setup
- 2.1 I like to install the client without installing a Outlook or Thunderbird AddIn
- 2.2 Module c:\-path-\regify client\regifyAddIn.dll failed to register. HRESULT -2147467259. Contact your support personnel.
- 2.3 Fehler beim registrieren von Modul c:\-path-\regify client\regifyAddIn.dll. HRESULT -2147467259. Wenden Sie sich an den Support.
- 3 debugging
usage
Im not able to send SMTP mails using a google mail account
The regify client is currently not able to use SSL secured SMTP servers. Google mail is one of the rare SMTP servers that do not allow any other connection. Upon this, the regify client is currently not working together with google mail SMTP accounts.
I'm having connection problems
Common problems are:
- Error 58 -> Problem with SSL certificate
- Error 2 -> Missing internet connection (check proxy and connectivity)
It may help you to activate the debug log (described on this page). The CURL entries are giving more information about reasons.
The regify client complains "The given file can not get opened (no regify file)."
German: "Die angegebene Datei kann nicht geöffnet werden (keine regify® Datei)."
Up to version V3.6.5 of the regify-client, this error occurs if there are more than 15 to 22 attachments added to the regify file (depending on the length of the filename and the version of the regify client used for regify generation). To fix this, update to a client newer than V3.6.5 or open the regify-file by uploading to the regify portal of your regify-provider.
I'm getting an Error: 20 when trying to read regify emails
Most of the time this happens because the recipient is trying to read an email that is addressed to one of their email addresses that is not registered with their regify account. Up to 5 email addresses can be registered with a regify account. Log into the provider portal and add the missing email address.
In rare cases this error can be caused by older regify clients when the recipient email address was passed in as mixed case. Example Jane.Doe@company.com. To resolve this, the sender needs to upgrade their regify client or insure that the recipient email address is lowercase, in our example: jane.doe@company.com
The regify client complains with error 59 while opening a message (Internal Protocol Error)
Due to a bug in the regify Client-SDK, the error messages for Errorcodes 21 and 22 are displayed as error 59. The most possible reason is, that the sender decided the recipient to be authenticated. Please authenticate yourself (the recipient) at your regify portal. If the authentication-option is not visible, please contact your regify-provider directly. This bug is fixed since regify-client V3.7.
setup
I like to install the client without installing a Outlook or Thunderbird AddIn
Please choose the custom install option while setup. You can disable the Outlook AddIn and the Thunderbird AddIn in the further dialog.
Module c:\-path-\regify client\regifyAddIn.dll failed to register. HRESULT -2147467259. Contact your support personnel.
Fehler beim registrieren von Modul c:\-path-\regify client\regifyAddIn.dll. HRESULT -2147467259. Wenden Sie sich an den Support.
The most likely cause of the error is an installed Microsoft Outlook with 64 Bit. The regify AddIn is only able to run on 32 Bit Outlook installations. Please uninstall your Microsoft Office and reinstall the 32 Bit version. If you do not plan to use the Outlook AddIn, you may exclude the AddIn from installation by using the custom setup option.
debugging
Start extended debug logging
Beginning with version 3.8.0 of the regify-client, you can get a detaild debug-log. To activate debugging, please open the regify client ini-file (%APPDATA%\regify\regify_client.ini) and insert the following value in the [REGIFY] section:
[REGIFY] DebugLevel = 5
To deactivate loggin, please remove this entry or set DebugLevel = 0.
