Intel® Business Client Software Development
Support for Intel® vPro™ software development and technologies associated with Intel vPro platforms.
1381 Discussions

EventManagerService.SubscribeForGeneralAlert : Invalid parameter

gennadiy
Beginner
495 Views
AMT has version 5.0. I try to work with EventManagerServicefunction SubscribeForGeneralAlert.
I created and send string to AMT computer





1


192.168.1.22







and I got error "Failed to parse the request, Detail=Invalid parameter"
Where is my mistake?

0 Kudos
5 Replies
Andrew_S_Intel2
Employee
495 Views
Quoting - gennadiy
AMT has version 5.0. I try to work with EventManagerServicefunction SubscribeForGeneralAlert.
I created and send string to AMT computer





1


192.168.1.22







and I got error "Failed to parse the request, Detail=Invalid parameter"
Where is my mistake?


Do you have an event filter setup with an AlertSubscriptionPolicyID entry that matches the policyID you passed in?
0 Kudos
gennadiy
Beginner
495 Views

Do you have an event filter setup with an AlertSubscriptionPolicyID entry that matches the policyID you passed in?
Yes. I added pictute.
0 Kudos
gennadiy
Beginner
495 Views
Quoting - gennadiy
Yes. I added pictute.
On a picture it is visible that AlertSubscriptionPolicyID is equal policyID. It means not the reason of occurrence of an error. There can be a reason is in syntax Web service?
0 Kudos
Gael_H_Intel
Moderator
495 Views
Quoting - gennadiy
On a picture it is visible that AlertSubscriptionPolicyID is equal policyID. It means not the reason of occurrence of an error. There can be a reason is in syntax Web service?


Well, in looking at the SoapUI generated request it looks like you have everything that you need. One thing I notice is that in the Network Interface Guide, the IPv4Address appears to be a string and the example they give is in quotes. Maybe you need to add quotes to your Soap code?

I also notice that the name spaces in the Envelope are not the same ones you are using. Not sure if that is causing you problems either. You have also have a namespace in the body, where the wsdl file has all the name spaces in the Envelope line.

From the WSDL file:
http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://schemas.intel.com/platform/client/EventManager/2004/01" xmlns:ns1="http://schemas.intel.com/platform/client/Common/2006/01">

Your Code:





--The wholeWSDL file:
http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://schemas.intel.com/platform/client/EventManager/2004/01" xmlns:ns1="http://schemas.intel.com/platform/client/Common/2006/01">




?




?
?
?


?


?


?


?
?


?






0 Kudos
gennadiy
Beginner
495 Views


Well, in looking at the SoapUI generated request it looks like you have everything that you need. One thing I notice is that in the Network Interface Guide, the IPv4Address appears to be a string and the example they give is in quotes. Maybe you need to add quotes to your Soap code?

I also notice that the name spaces in the Envelope are not the same ones you are using. Not sure if that is causing you problems either. You have also have a namespace in the body, where the wsdl file has all the name spaces in the Envelope line.

From the WSDL file:
http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://schemas.intel.com/platform/client/EventManager/2004/01" xmlns:ns1="http://schemas.intel.com/platform/client/Common/2006/01">

Your Code:





--The wholeWSDL file:
http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://schemas.intel.com/platform/client/EventManager/2004/01" xmlns:ns1="http://schemas.intel.com/platform/client/Common/2006/01">




?




?
?
?


?


?


?


?
?


?






Hi Gael,
Thank you. I found my mistake.
0 Kudos
Reply