cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Moopere
Engaged Sweeper II
Hello Folks,

Looks like scanning HP warranty on some devices is broken when we're scanning against the HPE database.
See this:

Parsing error: Cannot parse 'https://support.hpe.com/hpsc/wc/public/find?lang=us&rows%5B0%5D.item.countryCode=US&rows%5B0%5D.item.serialNumber=CNB7G7W36J'

If I manually copy the URL above and end up at the HPE site it states that:

"The information you provided does not match our records. Please review your entry again and make any necessary edits or contact HPE for more assistance."


If one uses the HP warranty check site (not HPE):

https://support.hp.com/us-en/checkwarranty

Its happy and doesn't produce any error, just provides the correct warranty details.

Is there a way to add an alternative warranty check URL to lansweeper?

1 ACCEPTED SOLUTION
zaty
Engaged Sweeper
Hi,
i wrote for myself Powershell script to get all HP computers/laptop assets from DB, use Powershell module to get warranty info thru SOAP API and update asset in DB.


You will need these PS1 modules:
https://github.com/dotps1/HPWarranty
https://docs.microsoft.com/en-us/sql/powershell/download-sql-server-ps-module?view=sql-server-ver15


$assets = Invoke-Sqlcmd -ServerInstance servername -Database lansweeperdb -Username lansweeperuser -Password 'password' -Query @"
SELECT a.AssetID, a.AssetName, b.Serialnumber, b.SystemSKU
FROM lansweeperdb.dbo.tblAssets a, lansweeperdb.dbo.tblAssetCustom b
WHERE a.AssetID = b.AssetID AND
a.Assettype = -1 AND
b.Warrantydate is NULL AND
b.Manufacturer in ('HP','Hewlett-Packard');
"@

foreach ($asset in $assets) {
$assetId = $asset.AssetID
$assetName = $asset.AssetName

$warranty = ((Get-HPIncWarrantyEntitlement -SerialNumber $asset.SerialNumber -ProductNumber $asset.SystemSKU).OverallEntitlementEndDate | Measure-Object -Maximum).Maximum
Write-Output "$assetID $assetName $warranty"

Invoke-Sqlcmd -ServerInstance servername -Database lansweeperdb -Username lansweeperuser -Password 'password' -Query @"
UPDATE dbo.tblAssetCustom
SET Warrantydate = '$warranty'
WHERE assetID = $assetId
"@
}

View solution in original post

31 REPLIES 31
nnewton
Engaged Sweeper III
The warranty scanning used to be really good a few years ago, but I think HP started really restricting it. Seems like you can only look up a couple at a time before it starts blocking you.

I've registered for the HP Developers so I can access the warranty using the API, but that doesn't work for servers since the split and now we get this on the warranty API page at HP:

Please note: The beta Warranty API is currently unavailable.
We will resume operations at a later time.
For small numbers of devices, please consider HP Support's manual Warranty Checking web form.


So all-around terrible when looking up HP warranties.

None of this is really LANSweeper's fault, I think they are doing the best they can with what HP is providing.

Luckily we only use HP for our ESX host blades, so manually looking up and populating the warranty dates for 10-20 new machines every year isn't too onerous.
TBMPS
Engaged Sweeper
The use of the HP warranty scan is the primary purpose for my wanting to use Lansweeper. Seemed to have a good following too. Any word on when this might be working again? I am currently running in trial mode, if we can get this feature working, I will definitely be a paid user.
it9
Engaged Sweeper II
Not fixed. Im on the latest version - 7.2.106.48 and still can't see warranty for our HP products...
nnewton
Engaged Sweeper III
I'm on v7.2.105.2 and I have 139 warranty scanning errors in the report, all of them are HP.

Most of them are this error:

Parsing error: Cannot parse 'https://support.hpe.com/hpsc/wc/public/find?lang=us&rows%5B0%5D.item.countryCode=US&rows%5B0%5D.item.serialNumber=<SERIAL>'

I tried one of the URLs in a browser and it returned a warranty page, but after refreshing a few warranties, I started getting this:

Could not open page
The service or information you requested is not available at this time.
Please try again later.

(Error: system-websrv_unavail)

I guess HP have a very strict limit for warranty queries.
Moopere
Engaged Sweeper II
This problem appears to be fixed now? Can anyone confirm?

The warranty scan errors in the lansweeper log are gone and the problematic printers seem to have updated details.
Esben_D
Lansweeper Employee
Lansweeper Employee
I've checked further and there is a known issue with retrieving warranty data from HP devices. The HP API has been down for a while and our fallback method of scraping the website, unfortunately, is non-functional currently as well due to changes at the end of HP. We're currently in contact with HP to try to get a more permanent resolution here, to hopefully set up reliable warranty retrieval via API (as we do for Dell).

Unfortunately, as we're reliant on a 3rd party, slowing down the process, it's difficult to give an estimate on when we can resolve this.
Esben.D wrote:
I've checked further and there is a known issue with retrieving warranty data from HP devices. The HP API has been down for a while and our fallback method of scraping the website, unfortunately, is non-functional currently as well due to changes at the end of HP. We're currently in contact with HP to try to get a more permanent resolution here, to hopefully set up reliable warranty retrieval via API (as we do for Dell).

Unfortunately, as we're reliant on a 3rd party, slowing down the process, it's difficult to give an estimate on when we can resolve this.


Dear Esben,

are there any updates regarding this problem, this function is really important for us.

thanks

Daniel
CWeeks
Engaged Sweeper
Week old install for me. No warranty info. Last version worked fine
DJohnnson
Engaged Sweeper
Just put up a new Lansweeper installation yesterday and I am having the same issue. I installed the update that was released today and am still getting the parsing error.
MRedfern
Engaged Sweeper
We have exactly the same issue, there have been no successful HP warranty scans for us since 24/10/19, 2 days after the last Lansweeper release came out