Connection error - timeout.

Eg. client error texts:

• Can't connect to gctp.cpr.dk:443 (Operation timed out)”, "Unable to connect to the remote server" (timeout)

• Unable to connect to the remote server

• A connection attempt failed because the connected party did not properly respond after a period of time..

• Http 403 error when calling the webservice https://gctp.cpr.dk:443/cpr-online-gctp/gctp

1. Verify that the GCTP request is not blocked by a firewall on the client side. For verification telnet command can be used - “telnet gctp.cpr.dk 443”

2. If the GCTP service request is not blocked on the client side then the reason can be that the firewall on the server side (CPR) is blocking. For verification a ticket can be made in https://cpr.dk/csd . Remember to state the outgoing IP address. Identification of outgoing IP address pls. refer to Identifying your outgoing IP-address

Connection error - TLS protocol/chipers.

Eg. client error text:

• The underlying connection was closed: Could not establish secure channel for SSL/TLS.

• The request was aborted: Could not create SSL/TLS secure channel

1. Verify that valid TLS protocol and chipers are used in the connection to the GCTP service - https://gctp.cpr.dk:443/cpr-online-gctp/gctp. Valid TLS protocol and chipers described in https://cprservicedesk.atlassian.net/l/c/nNDgD3eZ

GCTP login failure

The response value in the XML element<Kvit> contains value in the range 9xx.

Eg. response: <root xmlns="http://www.cpr.dk"><Gctp v="1.0"><Sik><Kvit r="returKode" t="" v="908"/></Sik></Gctp></root>

Look up errorcode in https://cprservicedesk.atlassian.net/l/c/6buy7Bzq bilag 5

Rules for valid passwords listed in https://cprservicedesk.atlassian.net/l/c/gvrrt2tz