cancel
Showing results for 
Search instead for 
Did you mean: 

SMP SP06: #No endpoint with name SAPXXXX was found#null (Agentry Application)

Former Member
0 Kudos

Hello Expert,

We are using SAP work manager 6.2 on SMP SP06.

We are getting below issue while using the SMP 3.0 SP06 in Production system. Please find the error logs.

2015 08 06 10:50:50#+0800#WARN#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService##anonymous#http-bio-8083-exec-9####null#null#null#warn#Other#iwk.abap#null#bc042910-af7d-474a-a5ef-5cbf98e6a37b#null#1438800650158#null#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService:getEndpoint#No endpoint with name SAPWM was found#null#449#null#1438829450142000#null |

2015 08 06 10:57:07#+0800#WARN#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService##anonymous#http-bio-8083-exec-4####null#null#null#warn#Other#iwk.abap#null#67b54815-fdcc-4b3d-87d5-50e84a6b2b7c#null#1438801027612#null#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService:getEndpoint#No endpoint with name SAPWM was found#null#184#null#1438829827596000#null |

2015 08 06 10:59:49#+0800#WARN#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService##anonymous#http-bio-8083-exec-12####null#null#null#warn#Other#iwk.abap#null#01cae615-55d0-4b0e-8022-c236cf5361c4#null#1438801189066#null#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService:getEndpoint#No endpoint with name SAPWM was found#null#647#null#1438829989050000#null |

We are facing this issue in Production system. Request you to kindly help us if we are missing anything.

Thanks,

Madhur

Accepted Solutions (0)

Answers (2)

Answers (2)

mark_pe
Active Contributor
0 Kudos

Madhur,

Hi. This error "endpoint with name SAPWM was found#null#647#null#" is normally seen in two areas that I can remember.

First error 1:

One has a KBA tied to renaming the end point of the configuration/com*.SAPWM to configuration/com*.application instead. The reason for this is during the upgrade the SMP 3.0 is trying to do the automation of renaming the end point name SAPWM. Due to yours existed already then this error may show.  KBA # 2110369

Second error 2:

2nd problem is tied to mapping the internal names or id within SMP 3.0. Now with this said, the key technique to avoid this issue is to name your Agentry application with the offiicial ID when you create your Agentry node to the key ID of your Agentry application.

To find the key ID name of your agentry application (Like Work Manager), you can either:

1. Open the Agentry Editor and check the official name of it.

2. Or look at the production zip published that you get (ex: SAPWorkMgr620Deployment-143161_7051.zip) and look at the application name in the Application/Production Directory ex: SAPWM-v1-0-0-app.agpz where SAPWM is the official name or official ID.

Make sure when you create your Agentry app from the Management Cockpit (SMP 3.0) - you use the ID correctly (You may reference the link below).

Those two things are the items I know that could resolve issues like that.

Please also look at SMP 3.0 SP09 documentation on publishing. Look at the picture of the ID (Management cockpit).

http://help.sap.com/saphelp_smp309sdk/helpdata/en/7c/1a300370061014b70aff251250df86/content.htm

Hope this helps you out.

Best Regards,

Mark Pe
SAP Platinum Support Engineer (Mobility)

Former Member
0 Kudos

Dear Mike,

I have followed the steps mentioned by you, but i still see the error in logs file:

2015 08 18 15:54:59#+0800#WARN#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService##anonymous#http-bio-8083-exec-9####null#null#null#warn#Other#iwk.abap#null#9b21abea-047d-4a1f-800b-c0a7e24d4694#null#1439855699315#null#com.sap.mobile.platform.server.proxy.configuration.service.AbstractEndpointConfigurationService:getEndpoint#No endpoint with name SAPWM was found#null#662#null#1439884499300000#null |

Thanks,

Madhur

mark_pe
Active Contributor
0 Kudos

Madhur,

When you get the error, what point in the process are you in?

  1. During SMP 3.0 startup?
  2. In the middle of transmit from one of the client?
  3. After startup and idle for a few hours (or in the middle of the day)?

What does this error do to your system? Is it preventing your user from logging in or is it an error you can ignore because it is not doing anything bad to the system?

Other suggestion is to see if this error exist in newer version of SMP 3.0 SPX.

Regards,

Mark Pe
SAP Platinum Support Engineer

Former Member
0 Kudos

Hello Mark,

Please find my response.

1. No we dont see this error at Startup

2. We see this error in the middle of transmit from client

3. sometime in middle of the day

There is no harm to the system but many times it happens that user is not able to login again and he is stuck at transmit window seeing message " Logging client to server ".

We have to manually log him out from SMP Cockpit in order for him to log in again.

We are into production system, do you suggest we should upgrade SP06 to latest.

Thanks,

Madhur

mark_pe
Active Contributor
0 Kudos

Madhur,

Hi. Thanks for answering these questions: "What does this error do to your system? Is it preventing your user from logging in or is it an error you can ignore because it is not doing anything bad to the system?"

Your answer: "There is no harm to the system but many times it happens that user is not able to login again and he is stuck at transmit window seeing message 'Logging client to server '.


We have to manually log him out from SMP Cockpit in order for him to log in again."

We were able to get the real problem. So the problem you are trying to fix is tied to users still not able to connect and you have to log them out.

In this case, try these solutions - these are the 2 known solutions to fix your issue (you may need 1 or both of them).

SAP KBA Articles:

1) 2193329  - SMP 3.0: "Invalid user name or password" that occurs when a Transmit session is restarted after an Error 14 - Agentry

2) 2195429 - Communication Error (14) and SMP 3.0 URL connection states "I am here" - SMP 3 Agentry

Also try to reference (Authentication information below for additional information):

3) Broadcast Resolution: Agentry/SMP 3.0 authentic... | SCN

Let us know if this addresses your issue.

Have a good day.

Mark Pe
SAP Platinum Support Engineer

CRVMANISH
Contributor
0 Kudos

Check if the application deployed gives you URL 'I am here' when you test on browser.

Regards

Manish

Former Member
0 Kudos

Hello Manish,

This error message comes after two or three sync. And then when user tries to log in again he gets message login unsuccessful.

We need to manually disconnect the user from SMP cockpit.

When we checked in logs, we saw above mentioned error.

Thanks,

Madhur Kanungo

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

What version of the client and platform are you using?

--Bill