Errors concerning legacy tools (4xxx) 1

The errors in this range are organized in secondary groups that can be identified by the second digit as follows:

Code	Description/cause
40xx	The end-user may try again, and has been informed of cause and proposed action by the web page.
41xx	The end-user may try again or contact the bank if the error persists. The error are most often caused by communication problems between internal COI components.
42xx	The end-user should contact the bank. The problem is tied to the runtime environment at the end-user's device.
43xx	The end-user must contact the bank. The problem may only be resolved by the bank that issued the BankID in question.
44xx	Error which must reported to BankID support at Nets. The bank must first verify that the user data are correct and that her runtime environment is correct: Check the order status. Have the end-user try again. The bank should await a response before a new order eventually is submitted. All error codes of the type 44xx that are not described here are by definition "INTERNAL_ERROR".

Code	Description/cause	Action/solution
4000	Incorrect activation code. The user has entered an incorrect activation code, and not the one he has received from the bank.	Have the end-user verify that the correct activation code has been entered. When in doubt about what is the correct code, it may help to describe what the shipment from the bank looks like and when it was sent to the user.
4001	The end-user has not used the same BankID for testing authenticating and signing. The situation occurs during test of BankID as it is possible to choose from different BankIDs in the middle of the test for users registered with more than one BankID. (1^st part of the test if for authorization and the 2^nd part tests signing.)	Have the user perform the test using the same BankID.
4101	Internal error that can be caused by heavy network traffic towards COI.	Have the user try again later. If the error persists, contact BankID support at Nets. It is not possible to estimate the duration of such a situation.
4102	The process of issuing the certificates took too long.	Have the user try again after a short while. If the error persists, contact BankID support at Nets.
4200	The web browser is not among the browsers that are recognized by BankID-tools. Examples of valid browsers are: MS Internet Explorer, Google Chrome, Mozilla Firefox, Opera, Safari.	Have the user upgrade to a valid web browser. A list of tested combinations is described in the release documentation, or contact BankID support at Nets for details.
4201	The web browser is not supported by BankID-tools.	Have the user upgrade to a valid web browser. Possible alternative actions: Describe to the user which web browsers that are supported. (A list of tested combinations is described in the release documentation.) Have the user choose «Test your device» on bankid.no. Supported web browsers (and any combinations with operating systems and browsers) will be shown to the user together with relevant links to do an upgrade.
4202	The web browser has no support for Java. In order to use the legacy BankID Applet the user must use a web browser supporting Java.	Instruct the user: Check whether it is possible to activate Java (in web browser settings). Explain to the user how she may upgrade her web browser to a version supporting Java. Alternatively how to install a Java-plugin to her current browser. Tell about the possibility to utilize the "Test your device" in the left-hand menu at BankID-tools. Relevant links for Java-updates will be displayed if needed.
4203	The Java-environment at the end-user's device is not supported.	Have the user upgrade to a valid web browser or alternatively change the Java-environment. A list of the supported combinations can be found in the latest release documentation. Alternatively the "Test your device" at BankID-tools may be used.
4206	It has been tried to activate a BankID which requires HSM by opening the activation URL in a web browser.	Activate the BankID by using the HAT application.
4301	It is not possible to verify the end-user signature. This could be due to the fact that the client is from an incorrect environment, i.e. that the BankID root certificates in client and server are different, or that the client signature over the "server challenge" is corrupt. The error message may come during identification.	Make sure that a correct client is used (Test system against production) Contact BankID support at Nets if the user has a correct client.
4302	Cannot find end-user or details about the end-user.	If the error occurs during activation, verify that the activation-URL is complete. Verify that the order status is correct. Have the user try again after a while. If the problem continues to occur, contact BankID support at Nets.
4306	The BankID has been suspended by the bank or by BankID support. NB: The validation service does not differentiate between a permanent and a non-permanent suspension. The bank may check the status of a BankID via the banks' order interface.	Depends whether the suspension was made temporarily or permanently, the alternatives are: Non-permanent suspension: Lift the revocation. Revoke permanently. Permanent suspension: Order new BankID.
4307	Incorrect installation code entered too many times.	The BankID cannot be activated. The bank must send a new order with a new OrderID.
4308	Tillatt aktiveringsperiode har passert, og det er ikke mulig å fullføre aktiveringen av BankID. (aktiveringsURL er utgått).	The BankID cannot be activated. The bank must send a new order with a new OrderID.
4312	Invalid request because the HAT-tool was not used.	The HAT-tool must be used.
4318	Invalid/incomplete activation-URL.	Contact the bank. The bank must send a new order with a new OrderID.
4324	The end-user tried to activate a cancelled order. NB: The order was cancelled after the installation code was given to the user.	The BankID cannot be activated. The bank must send a new order with a new OrderID.
4347	The certificate is no longer valid.	The bank has to send a new order with a new OrderID.
4418	Invalid/insufficient activationURL.	Check that the URL is correct or contact the bank for a new activationURL.
4900	The end-user's web browser is not able to execute a signed Applet even though Java is installed and the OS and web browser are supported by BankID. The end-user has clicked a separate link to proceed after having waited for a while.	Verify that the end-user has waited a while before clicking the link. Verify that the end-user has seen a dialog to accept the signed Applet. Have the end-user verify that this dialog is not hidden behind any other windows. Have the end-user restart her web browser and try again. If the problem continues to occur, contact BankID support at Nets.