This issue occurs due to a software defect in Pulse Desktop client 5.2R7 and 5.3R1 that prevents a connection from initiating due to a task that is unable to complete in the background. This issue occurs when any one of the following conditions are met:
- A user manually deletes a connection from the Pulse client connection list.
- Pulse is configured with existing connections and the connection set is updated using a pulsepreconfig file that deletes a connection from the connstore.dat file and replaces it with a different connection. (A connection is deleted if the existing connection GUID value is different from the connection GUID value being pushed to the client.)
- A user connects to a PCS device and the connection GUID does not match the GUID in the client's connstore.dat file for that connection.
When connection GUID's do not match the following behavior will occur:
- Pulse client will make a connection to the PCS device.
- PCS device will send the connection set details to the client.
- Pulse client will evaluate all connection GUID's received from the PCS device.
- Pulse client will delete all connection GUID's that exist in the local connstore.dat file, but do not exist in the response from the PCS device. If the current connection being used is deleted, this will cause the Pulse client to immediately move to a Disconnected state.
When the end user attempts to connect again, the status of the connection will remain at Connect Requested