ErrorCodes

From regify WIKI
Revision as of 17:58, 8 March 2012 by Regify (talk | contribs) (Created page with '== regify error codes == This is a short list with all possible error codes for client software that uses the '''regify Client-SDK'''. This numbers are not valid for the regify …')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

regify error codes

This is a short list with all possible error codes for client software that uses the regify Client-SDK. This numbers are not valid for the regify Provider-SDK!


SERVICE RELATED

1 invalid session

2 missing parameter (transmission or protocol error). Maybe you use an old version?

3 wrong connection (remember, you need SSL)

4 client sdk version to old. Please use a more recent sdk version (customer should actualize, too)

5 Your regify provider does not support the regify provider lookup service.

10 username and/or password invalid

11 user uses an invalid identity-file or user/identity-file does not match

12 too many recipients (max. 500 recipients per call)

13 transaction limit for this month is reached (contact your regify provider to rise limit)

14 transaction limit for this month is reached (you are a "regimail private" member)

20 transaction not found (wrong hash code, recipient or transmission error)

21 delivery denied. Recipient-user has to be authenticated (set by sender)

22 delivery denied. Sender-user has to be authenticated (set by recipient)

23 clearing denied delivery because of an invalid identity sender identity (sender manipulated?)

24 clearing denied delivery because the sender (or sender-provider) denied roaming

25 invalid recipient (new with clearing-update) This extends error 20 about a know transaction, but invalid recipient.

30 identity-file can not be delivered (no identity-file available)

40 premium-membership is expired (please contact your regify provider to extend)

41 you need to be authenticated to use the override functions

42 wrong identity-file password (wrong unlock-code)

43 user is not allowed to send regibill transactions

44 user is not allowed to send regipay transactions

45 one of the email addresses is locked for usage with regipay (your own regipay blacklist-domain)

55 the PLS server has returned an error

56 currently, your regify® provider is under maintenance. Please try later.

57 currently, the regify® clearing service is under maintenance. Please try later.

58 can not connect to regify provider (check firewall and internet connection)

59 internal protocol error

FUNCTIONS RELATED AND OTHERS

60 file not found

61 no regify file decrypted (use regifyDecryptContainer() function first)

62 header not found

63 FileID not allowed

64 parameter need to be set

65 can not load identity-file

66 need to be connected to use this function

67 you need to call regifyComposeContainer() at first

68 out of memory

69 can not open file (check the rights and maybe the regify_log.txt)

70 can not write to user home directory (check the rights and maybe the regify_log.txt)

71 wrong parameter length (check the length of keys or values)

72 one or more email addresses are not valid (check log file for more information)

73 failed to copy to destination

74 no valid regibill digest found

75 missing regify system dependencies (check needed .dll / .so)

76 you need to be connected using an individual identity-file

77 invalid parameter

78 the given document is already a regibill document.

79 multiple recipients are not supported

80 this message uses an unsupported encryption or compression method. Please use a newer version of this library/software.

98 user abort

99 internal error without description