cancel
Showing results for 
Search instead for 
Did you mean: 

Error while communicating with server - No endpoint listening

Former Member
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

Thanks for your help Roberto, however, we solved the problem by re-installing MS Excel.

Ian

Answers (1)

Answers (1)

former_member186498
Active Contributor
0 Kudos

Hi Ian,

verify if in this machine the connection type is wrong or not, maybe you have first installed connection type for MS version instead of NW version.

If so you cannot modify it so you have to delete the incorrect connection and create a new one.

Regards

     Roberto

Former Member
0 Kudos

Hi Roberto

Thanks for the reply.

This is definitely a netweaver installation.

The only thing which I can see that is slightly different is that the machine has a 64 bit operating system.  However, I am not using the 64 bit version of Internet Explorer.

Ian

former_member186498
Active Contributor
0 Kudos

Hi Ian,

I found this thread http://scn.sap.com/thread/3541687 where it seems an office issue ...

Regards

     Roberto