Open skoliver1 opened 3 years ago
Same here. Running version 2.6.2, seems that the SOAP URL or ID/Key are now invalid.
https://api-uns-sgw.external.hp.com/gw/hpit/egit/obligation.sa/1.1 $soapWebRequest.Headers.Add('X-HP-SBS-ApplicationId','hpi-obligation-hpsa') $soapWebRequest.Headers.Add('X-HP-SBS-ApplicationKey','ft2VGa2hx9j$')
We are having the same issue!
I get "The remote server returned an error: (404) Not Found." when trying to post the SOAP request manually. All my clients gets Failed to invoke SOAP request.
Does anyone know what changes that can have been made at HP side?
We are having the same issue!
I get "The remote server returned an error: (404) Not Found." when trying to post the SOAP request manually. All my clients gets Failed to invoke SOAP request.
Does anyone know what changes that can have been made at HP side?
In 2019 HP killed off the official API, and then earlier this year they killed the alternative method that this script was using. There is still no public ETA for release of the new warranty lookup, it is a complete mess. There was some talk that the requests are now filtered through AWS but I don't know if anybody has worked out how to work with this yet (if it is even possible at all).
Has there been any update to this or other options?
I'm guessing that HP made a change to their process, because this stopped pulling any data for a few days and now it gives this error on every machine I run this on.
Get-HPIncWarrantyEntitlement : Failed to invoke SOAP request.