Connection to the Server failed

This message is displayed whenever the Swift MEAP™ client is unable to contact the Swift MEAP™ server URL registered with iEnterprises.  This means:

1. The client was able to connect to the Swift MEAP™ Activation server
2. The Swift MEAP™ Server address was returned to the device.
3. When the client attempted to send login details to the server address received, the client was unable to open the URL.

A user will experience this when they enter an activation user id, the client connects to the iEnterprises Activation server and the Activation Server returns a Swift MEAP™ Server address.  The client is unable to connect to the Swift MEAP™ Server and therefore cannot validate credentials.

Possible causes and investigation

No internet connection

The device has no internet connection - please check that the device has an active internet connection. 

If the client was able to connect to the activation server and retrieve details, this is unlikely to be the cause as the client required a connection to get the details.  It could indicate a temporary internet outage, which is outside of our control. 

Activation URL is incorrect

Please check the client logs and the Swift MEAP™ server address that was returned to the client.  Please search the logs for: ActivationResponse

A sample line from a log file with the Activation Response is as follows:

2014-08-21 09:41:26.422 disconnectedmobilesales[11154:707] -[ActivationViewController activateUsingReturnData:] [Line 1154] Response = <?xml version="1.0" encoding="UTF-8"?>
<ActivationResponse><Status>0</Status><Description></Description><Protocol>https</Protocol><ServerName>swiftmeap.ienterprises.com</ServerName><Port>443</Port><Context>SwiftMEAP</Context><ConnectionMode>BIS</ConnectionMode></ActivationResponse>

The  <Protocol>, <ServerName>, <Port> and <Context> can be used to check the address that the client will connect to.  In the example above, this is: https://swiftmeap.ienterprises.com:443/SwiftMEAP

The client will use this address for all communication with the Swift MEAP™ Server so it is critical this is correct.  In a Split Port server, the client uses the "Service" port to communicate with clients, please check that the address matches the public URL you intend to communicate over. 

The client cannot connect to the server URL

This occurs if the client was returned an address from the activation server, but could not connect to the address identified.  It is possible that if you have an internet connection and the server registration details have been checked, that you have another networking issue.  In the example above, we identified the server address as: https://swiftmeap.ienterprises.com:443/SwiftMEAP

Please check the request / response sent to the server after activation (as detailed above).  When we attempt to connect, this is captured in the logs as: MEURLConnection

Sample from the logs with connection attempt:

2014-08-21 09:41:32.482 disconnectedmobilesales[11154:707] -[MEURLConnection initWithURL:delegate:AndPostXml:] [Line 57] xmlData p = <?xml version="1.0" encoding="UTF-8"?>
<DeviceRequest><Name>test</Name><Pwd>#####</Pwd><ActivationEmailId>dorian@swiftmeaptest.com</ActivationEmailId><ApplicationIdentifier>com.oraclecorp.internal.ent2.disconnectedmobilesales</ApplicationIdentifier><CustomerEmail>dorian@swiftmeaptest.com</CustomerEmail><Pin>BA39FD7C-264F-4750-9F10-5A60C1BB7BDF</Pin><Language>1</Language><CommunicationMode>BIS</CommunicationMode><Version>v2</Version><CompatibilityVersion>2</CompatibilityVersion></DeviceRequest>
2014-08-21 09:41:33.370 disconnectedmobilesales[11154:707] -[MEURLConnection connection:didFailWithError:] [Line 141] didFailWithError __ Error Domain=NSURLErrorDomain Code=-1005 "The network connection was lost." UserInfo=0x17dabb20 {NSErrorFailingURLStringKey=https://swiftmeap.ienterprises.com:443/SwiftMEAP/CRMRecords, NSErrorFailingURLKey=https://swiftmeap.ienterprises.com:443/SwiftMEAP/CRMRecords, NSLocalizedDescription=The network connection was lost., NSUnderlyingError=0x17daf6e0 "The network connection was lost."}

Searching for MEURLConnection, we can see a didFailWithError response.  This clearly shows the URL that the device attempted to connect to in the NSErrorFailingURLStringKey.

Open a browser on the device, enter the URL that we attempted to connect to (example shown was): https://swiftmeap.ienterprises.com:443/SwiftMEAP/CRMRecords

This will discover if the device has network connectivity to the server.  You should see 'EmptyBisResponse' displayed, if you get any kind of error, such as 404 or server not found, the device cannot connect to the specified URL.