- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
AMT has version 5.0. I try to work with EventManagerServicefunction SubscribeForGeneralAlert.
1
192.168.1.22
I created and send string to AMT computer
and I got error "Failed to parse the request, Detail=Invalid parameter"
Where is my mistake?
Link Copied
5 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - gennadiy
AMT has version 5.0. I try to work with EventManagerServicefunction SubscribeForGeneralAlert.
1
192.168.1.22
I created and send string to AMT computer
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Andrew Schiestl (Intel)
Do you have an event filter setup with an AlertSubscriptionPolicyID entry that matches the policyID you passed in?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - gennadiy
Yes. I added pictute.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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:
Your Code:
--The wholeWSDL file:
?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Gael Holmes (Intel)
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:
Your Code:
--The wholeWSDL file:
?
Thank you. I found my mistake.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page