Network Management / (OpenView-NNM) Practitioners Forum

Renew subscription on NMMi WS-E

New Member.

Renew subscription on NMMi WS-E



We don't manage to renew subscription on the incident notification service (NMMi WS-E).


The SOAP message that we send seems to respect the rule ( But we receive an error :

"The message is not valid and cannot be processed: Cannot obtain subscription id."


The renew request that we send is :

<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="" xmlns:wsa="" xmlns:wse="">
  <wsa:Action xmlns:wsa=""></wsa:Action>
  <wsa:MessageID xmlns:wsa="">urn:e89ea4ab-d3a6-40e3-bbec-745b9b5028a9</wsa:MessageID>
  <wsa:ReplyTo xmlns:wsa="">
  <wsa:To xmlns:wsa=""></wsa:To>



The renew response that we obtain is :

<env:Envelope xmlns:env=''>
 <env:Header xmlns:wsa=''>
  <env:Fault xmlns:env=''>
   <faultstring>The message is not valid and cannot be processed: Cannot obtain subscription id.</faultstring>



Do you have an idea of what is wrong is our request?


Thank you.

Dave Young
Acclaimed Contributor.

Re: Renew subscription on NMMi WS-E

Hello Otip,


  SDK questions and issues are normally handled by our CPE team.  I passed on your information to them for a quick review and they have suggested to check the system times on the client system and the NNMi host system.  Apparently if they are out of synch by too much then this can lead to the issue you are seeing.


  If this is not the case and you are still having problems then can I suggest you open a case with us so that we can properly track the issue and provide the support you need.


  all the best



HP Support
Viewed the Support tips? Search for "(NNMi) Support Tips" and order by Date to get the list
The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of HP
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.
Tamas Orosz
New Member.

Re: Renew subscription on NMMi WS-E

Hi Otip!


On the last week I got same error message... I think it's a very annoying problem.


The wse:Identifier xml tag has a required attribute: wsa:IsReferenceParameter='true'

and your request will be perfect!


Please read the WS Addressing - W3C Recommendation :) documentation:



Have a nice day!