ErrorCodes - Revision history

Regify: /* Other */

2023-10-10T06:22:08Z

Other

2023-10-10T06:21:32Z

Misc.

2023-10-10T06:21:24Z

Other

2023-10-10T06:21:00Z

Other

2023-10-10T06:19:05Z

regify error codes

2019-10-30T07:26:52Z

2019-01-28T08:53:19Z

Service related

2018-10-24T08:42:59Z

Service related

2018-10-24T08:35:15Z

Service related

2017-07-28T06:34:25Z

Service related

@@ Line 101: / Line 101: @@
 === Other ===
 	The current instance state is invalid for this call.<br>
-: ''(This usually comes up after hardware has changed. Try the 'reset configuration' button in settings and re-enter your credentials.)''<br>
+: ''(This usually comes up after hardware has changed on mobile devices. Try the 'reset configuration' button in settings and re-enter your credentials.)''<br>

@@ Line 85: / Line 85: @@
 === Misc. ===
 	Your regify provider does not support this function. Please contact your regify provider support to find out if this feature will get supported in the future.<br>
-''(This usually comes up if you try to use a feature or product that was not enabled by your regify provider.)''<br>
+: ''(This usually comes up if you try to use a feature or product that was not enabled by your regify provider.)''<br>
 	User aborted<br>
 	Sorry, but an internal server error occurred. Please contact your corresponding program support.<br>

@@ Line 101: / Line 101: @@
 === Other ===
 	The current instance state is invalid for this call.<br>
-''(This usually comes up after hardware has changed. Try the 'reset configuration' button in settings and re-enter your credentials.)''<br>
+: ''(This usually comes up after hardware has changed. Try the 'reset configuration' button in settings and re-enter your credentials.)''<br>

← Older revision		Revision as of 06:21, 10 October 2023
Line 101:		Line 101:
	=== Other ===		=== Other ===
	325 The current instance state is invalid for this call.<br>		325 The current instance state is invalid for this call.<br>
		+	''(This usually comes up after hardware has changed. Try the 'reset configuration' button in settings and re-enter your credentials.)''<br>

@@ Line 3: / Line 3: @@
 This is a short list with all possible error codes for client software that uses the '''regify Client-SDK'''.
-This numbers are <u>not valid for the regify Provider-SDK</u>! For those numbers, please refer to the Provider-SDK documentation.
+'''NOTE:''' This numbers are <u>not valid for the regify Provider-SDK</u>! For those numbers, please refer to [https://manuals.regify.com/docs/provider/current/provider_sdk/#api_error_codes the Provider-SDK documentation].
 === Service related ===
@@ Line 96: / Line 98: @@
 	Your regify provider does not support this authentication method.<br>
 	You do not have enough permissions to complete this operation.<br>

@@ Line 55: / Line 55: @@
 	File not found: xxx<br>
 	No decrypted regify file available<br>
 	Header-information not found<br>
 	FileID not allowed<br>

@@ Line 39: / Line 39: @@
 	This regibox exceeds its size limit.<br>
 	The regibox could not be found.<br>
       A problem occurred while securely accessing the internet (SSL/TLS handshake failed).
 : ''(In all error 52 reports we've had in the past, some content inspection firewall was the cause or some restrictive proxy blocked CRL of SSL certificates. Please ask your administrator about what might be the reason. For proxy servers, he might have a look [[Troubleshoot_Connectivity#General_connectivity_information|here]]. For a content inspection firewall, he either has to whitelist all needed domains (*.regify.com and your regify provider) or to install the needed root CA of your firewall on your machine(s).)''

@@ Line 40: / Line 40: @@
 	The regibox could not be found.<br>
       A problem occurred while securely accessing the internet (SSL/TLS handshake failed).
-: ''(In all error 52 reports we've had in the past, some content inspection firewall was the cause. Please ask your administrator to either whitelist all needed domains (*.regify.com and your regify provider) or ask him to install the needed root CA of your firewall on your machine(s).)''
+: ''(In all error 52 reports we've had in the past, some content inspection firewall was the cause or some restrictive proxy blocked CRL of SSL certificates. Please ask your administrator about what might be the reason. For proxy servers, he might have a look [[Troubleshoot_Connectivity#General_connectivity_information|here]]. For a content inspection firewall, he either has to whitelist all needed domains (*.regify.com and your regify provider) or to install the needed root CA of your firewall on your machine(s).)''
 	Your regify provider currently has regibox in maintenance mode. Please try again later.<br>
 	It is not possible to reset your password more than 10 times per hour. Please wait at least 1 hour before trying again.<br>

@@ Line 21: / Line 21: @@
 	Invalid session file.<br>
 	Invalid e-mail address for communication and notifications. In Outlook, select "Configuration" and turn off the option "Take sending address from Outlook".<br>
-	Invalid login with old password.
+	Invalid login with old password. Please update your local passwords with the new password.<br>
 	Sorry, but this transaction can not be opened. Maybe the file is corrupted or you are not the desired recipient.<br>
 : ''(Please verify the error message text and the given e-mail addresses in there. You need to use a regify account which is assigned to at least one of the recipient e-mail addresses. Maybe someone simply forwarded an encrypted regify message to you but you are not one of the desired recipients for this message. A regify message is always having one or more dedicated e-mail addresses as desired recipients. If you forward an encrypted RGF file, this does not change.)''