Unsolved
3 Posts
0
3931
Dell Command | Integration Suite 5.0 Not retrieving Warranty
The Latest Dell Command Integration suite is not retrieving warranty data. I had this configured and working earlier this year, but am unable to retrieve new warranty data.
I continue to get this error in the log:
: Date: 20181112095633
WARRCLI-M01: *** DellWarranty-CLI Starting ***
DC-VICM01: Retrieving permissions for database SCCM
DC-GSTF01: Retrieving tags from configuration manager database SCCM
SS-GCMS01: Getting service tags from from configuration manager DB SCCM.
DC-GSTF02: Number of serviceTags found in configuration manager: 6415
DC-VCST01: Retrieving permissions for database DellWarranty
DC-DWRE04: Error retrieving warranty data
Error (System.ArgumentNullException) at DC-DWRE04:
Value cannot be null.
Parameter name: source
Everything appears to be working until this point, and I'm guessing this is an error on Dell's side. Any help would be appreciated.
Thank you.
Kekataag
2 Posts
0
November 13th, 2018 03:00
Getting the exact same error, started about a week ago
Damon5334
2 Posts
0
November 13th, 2018 07:00
rmacgregor
2 Posts
0
November 13th, 2018 11:00
i am receiving the same issue
Pitt Tech 1
3 Posts
0
November 14th, 2018 06:00
I'm thinking maybe Dell is working on this because my error changed to:
: Date: 20181114095535
WARRCLI-M01: *** DellWarranty-CLI Starting ***
DC-VICM01: Retrieving permissions for database SCCM
DC-GSTF01: Retrieving tags from configuration manager database SCCM
SS-GCMS01: Getting service tags from from configuration manager DB SCCM.
DC-GSTF02: Number of serviceTags found in configuration manager: 6445
DC-VCST01: Retrieving permissions for database DellWarranty
DC-DWRE04: Error retrieving warranty data
Error (System.AggregateException) at DC-DWRE04:
One or more errors occurred.
Inner Error: (System.Net.Http.HttpRequestException)
An error occurred while sending the request.
Inner Error: (System.Net.WebException)
The underlying connection was closed: An unexpected error occurred on a receive.
Inner Error: (System.IO.IOException)
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Inner Error: (System.Net.Sockets.SocketException)
An existing connection was forcibly closed by the remote host
An error occurred while sending the request.: DC-DWRE05
The underlying connection was closed: An unexpected error occurred on a receive.: DC-DWRE06
If anyone at Dell could confirm, I'd greatly appreciate it!
Tbonewiz
2 Posts
1
November 15th, 2018 08:00
All -
I have a case open with the REC team, which was moved to the Enterprise team. I'm just waiting for a reply back. It does appear to be a Dell issue with the API from what we can see on our side.
EDIT: Quick update for anyone interested. Here is the reply from my tech:
I’ll be available at noon . Yes, as I’m understanding so far this is needing an API fix on our end and already being addressed. I’m working on getting your case to the right escalation team but just use me as point-of-contact until I get an engineer assigned.
Nick
Tbonewiz
2 Posts
1
November 16th, 2018 08:00
RESOLVED:
I received good news from my support technician!!! They fixed the back-end issue! I ran a test and it appears to be working as intended now. For anyone else actively watching this thread. Please test and report back on your findings too!
Dell Customer Communication
Good morning Travis,
The Engineer indicated that they resolved the issue this morning. Can you give it a try and let us know?
rmacgregor
2 Posts
0
November 16th, 2018 10:00
this appears to be trying to run but i am receiving this log, mind you have just tried setting this up recently so it may be the syntax
DellWarranty-CLI.exe /Ics="Data Source=x.x.x.x;Database=cm_xxx;Integrated Security=true;" /E="C:\temp\dellwarranty.csv"
: Date: 20181116103219
WARRCLI-M01: *** DellWarranty-CLI Starting ***
DC-VICM01: Retrieving permissions for database cm_xxx
DC-GSTF01: Retrieving tags from configuration manager database cm_xxx
SS-GCMS01: Getting service tags from from configuration manager DB cm_xxx.
DC-GSTF02: Number of serviceTags found in configuration manager: 22316
DC-DWRE04: Error retrieving warranty data
Error (System.ArgumentNullException) at DC-DWRE04:
Value cannot be null.
Parameter name: source
Pitt Tech 1
3 Posts
0
November 16th, 2018 10:00
It appears to be resolved for me as well!
Damon5334
2 Posts
0
November 16th, 2018 11:00
You're not alone. I'm also getting a similar error:
: Date: 20181116125102
WARRCLI-M01: *** DellWarranty-CLI Starting ***
DC-VICM01: Retrieving permissions for database CM_XXX
DC-GSTF01: Retrieving tags from configuration manager database CM_XXX
SS-GCMS01: Getting service tags from from configuration manager DB CM_XXX.
DC-GSTF02: Number of serviceTags found in configuration manager: 10362
DC-AWRD02: Failure in AssetWarrantyResponseToDcwAsset Null Refference was passed to assetWarrantyResponse.ProductHeaderData.
DC-AWRD02: Failure in AssetWarrantyResponseToDcwAsset Null Refference was passed to assetWarrantyResponse.ProductHeaderData.
DC-AWRD02: Failure in AssetWarrantyResponseToDcwAsset Null Refference was passed to assetWarrantyResponse.ProductHeaderData.
DC-DWRE04: Error retrieving warranty data
Error (System.ArgumentNullException) at DC-DWRE04:
Value cannot be null.
Parameter name: source
WrighC04
1 Message
0
November 27th, 2018 09:00
We've got the same issue, does anyone from Tech Support check these forums or do we need to log a fault? : Date: 20181127050055
WARRCLI-M01: *** DellWarranty-CLI Starting ***
DC-VICM01: Retrieving permissions for database CM_XXX DC-GSTF01:
Retrieving tags from configuration manager database CM_XX SS-GCMS01:
Getting service tags from from configuration manager DB CM_XXX DC-GSTF02:
Number of serviceTags found in configuration manager: 12803
DC-DWRE04: Error retrieving warranty data Error (System.ArgumentNullException) at DC-DWRE04:
Value cannot be null.
Parameter name: source
Kekataag
2 Posts
0
November 28th, 2018 05:00
OK so it worked fine on the 23rd of November and now it's giving errors again so it seems that whatever they did it was a temporary fix.