Troubleshoot regify client
- 1 Usage
- 1.1 I'm getting an Error: 20 when trying to read regify emails
- 1.2 Client does not start on Windows 2008 (R2)
- 1.3 I can't print from regify client window
- 1.4 My Mac tells me that regify client is outdated / not optimized for my Mac (32 bit application)
- 1.5 My regimail messages use weird characters instead of special characters in the default text
- 1.6 Known issues
- 2 Setup
- 3 Debugging
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: firstname.lastname@example.org
Client does not start on Windows 2008 (R2)
If you find the following message in your debug log:
Cant use cryptoc.dll. Please download the latest program-version and re-install.
In this case you need to manually install Microsoft Visual C++ 2008 Redistributable Package (x86) in order to run the regify client.
I can't print from regify client window
If you are running on Windows 7 with IE 9 or newer, you encountered a bug of Microsoft Windows. Try to print any website from Internet Explorer and you very likely will have the same issue there (independent of regify). The only suggestion is to copy the message body and paste it to Word. From there, you can print it.
A customer told us that he downgraded IE to version 8 on systems and this fixed the printing issues in both websites and regify client. Of course, they also forced end users to surf the Internet with Firefox or Chrome Browser.
We don't know from any other printing issues yet.
My Mac tells me that regify client is outdated / not optimized for my Mac (32 bit application)
We're currently developing a 64 bit version of regify client for Mac OSX (V4.3). Until then, please ignore this message.
My regimail messages use weird characters instead of special characters in the default text
This might happen if you freshly installed regify client 4.3.0. The UTF8 encoding was broken there. Please update to a more recent version of the regify client and then delete the file %APPDATA%\regify\regify_default_message.htm. Now, if you open or write a regimail, the template is getting updated automatically.
On some Lenovo systems the regify client freezes after opening a regify message due to a tool called Lenovo SmartUpdate (smartUpdate.exe). Removing the tool solved the problem.
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 dialogue.
Setup starts while I'm simply trying to use regify
At first, the mechanism of Microsoft Windows tries to re-run the setup (MSI, Installer) automatically, if files or registry keys (created by the setup) have changed or are missing. Thus, please check your AntiVirus logfiles if some components of regify have been classified as dangerous (false alert). If AV software, or other software setups, removed or downgraded components of regify, this may happen.
In some case, a complete uninstall followed by a fresh install of the most recent setup fixed the issues. As this is a Windows issue and not directly related to regify, we sadly can not give you any further assistance on this.
If you're an IT professional and if you're able reproduce the problem, you may activate MSI debugging to identify the missing component.
I'm not able to uninstall because of a missing MSI file/dependency
Such problems happen if Windows is having a corrupted installer configuration, independently of regify. As this is a common problem on Windows, Microsoft offers a tool to solve such issues. Please try to solve the issue with this tool.
As this is a Windows issue and not directly related to regify, we sadly can not give further assistance. Google for "uninstall missing msi file" will give you a lot of possible solutions and tools to solve such issues, too.
You also may try to activate MSI debugging for further investigation.
Start extended debug logging
Beginning version V4.0 and newer, the regify client uses an extra structure in his regify_client.ini file.
- Windows: %APPDATA%\regify\regify_client.ini
- MacOS: ~/.regify/regify_client.ini
- Linux: ~/.regify/regify_client.ini
Follow this guide:
- Close any regify client!
- Open the ini file (see locations above).
- Locate the section with [GUI] and update this entry:
debugLevel = 5
- Save settings file and close the editor.
- Try the things you need to log.
- Close any error messages and the regify client!
- To deactivate debugging, please remove the line with "debugLevel" or set debugLevel = 0.
If the file does not exist or you need to get debug information before the file was created (PLS or Proxy problems), please create the file and simply insert the content from above.
Debugging in client 4.0 or earlier creates two debug-log files in the systems temp-directory: regify_client.log and regify_client_sdk.log.
In order to find problems, regify support will need both files from you.
An alternative way to activate debugging is to call the regify client using the comandline parameters -v and -l.
regify_client.exe -v -l "c:\temp\mylog.txt"
The example above is for Windows.