Skip to Content
0
Former Member
Jun 18, 2014 at 12:27 PM

Error while communicating with server - No endpoint listening

975 Views

Hi experts

I have come across a user with a machine which is having problems connecting to our BPC environment. The same user can successfully connect via other machines so a security issue is ruled out.

When trying to launch the EPM add-in from the web front-end interface, we are hit with the message 'Error while communicating with server'.

The EPM log reads:

FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2

RECORD_SEPARATOR:35

COLUMN_SEPARATOR:124

COLUMNS:Time|Severity|Category|Method|User|DSRRootContextID|DSRTransactionID|DSRConnectionID|DSRCounter|Thread|Text

SEVERITY_MAP:DEBUG|Debug|INFO|Information|VERBOSE|Verbose|WARNING|Warning|ERROR|Error|FATAL|Fatal

HEADER_END

2014-06-18 13:21:03,745|ERROR|BPCProxy|FPMXLClient.BPCProxy.Common.Wcf.InterceptorChannelFactory`1+InterceptorRequestChannel.Request||||||1|There was no endpoint listening at https://.../sap/bpc/session?method=Get that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.#

2014-06-18 13:21:03,752|ERROR|BPCProxy|FPMXLClient.BPCProxy.Common.Wcf.InterceptorChannelFactory`1+InterceptorRequestChannel.Request||||||1|There was no endpoint listening at https://.../sap/bpc/session?method=Logout that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.#

2014-06-18 13:21:03,754|ERROR|BPCProxy|FPMXLClient.BPCProxy.Session.SessionServiceHelper.Logoff||||||1|There was no endpoint listening at https://.../sap/bpc/session?method=Logout that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.#

2014-06-18 13:21:03,772|ERROR|BPC10Connection|FPMXLClient.Connection.RESTConnection.Connect||||||1|There was no endpoint listening at https://.../sap/bpc/session?method=Get that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.#

Does anyone have any ideas ?

Thanks

Ian