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)