Systems Management Forums

Reports - Warranty Information not being populated

Systems Management

Systems Management
Dell Systems Management Solutions: Dell OpenManage, iDRAC, Repository Manager, Microsoft SCCM, Chassis Managment Controller, and more

Reports - Warranty Information not being populated

  • I have a recently installed OME 1.0.1.1253.

    The Warranty Information Report shows my two servers (one entry each for it's iDrac and server). The Service Tag is populated, but not warranty information is being populated.

    Any suggestions ?

  • Thanks for the post.  So this report actually has to connect to the internet to retrieve the warr data.  Does this server have outside internet access?

    thx!

    Rob

  • One more thing, if you need to define a proxy, navigate to the OME preferences and you can define it there.

    thx!

    Rob

  • also: When you click the warranty report do you get a message prompt and what does the message say?

  • Same problem for us. About a hundred servers and warranty does not show up. Instead this message : "There were not any service agreements found for this service tag."

    NOTE: I have noticed a difference between US Dell support Website (and product list) and European Support Website. Is OME designed to retrieve Warranty information on US Website only (Im in Switzerland) ?

    Thanks

  • For information, our OME connects successfully to Internet with our proxy settings.

    Test connection result : "Successfully connected with proxy information"

  • Are you using enahanced security for internet explorer by any chance? In that case you will have to add Dell warranty website (api.dell.com) to the trusted sites.

    You can also try browsing to the following URL from the OME server and check if you see the warranty information. You will have to replace the <servicetag> at the end with the service tag for one of your servers.

    http://lt.dell.com/lt/lt.aspx?CID=72399&LID=1833144&DGC=AF&DGSeg=SLG&DURL=http://www.dell.com/support/troubleshooting/us/en/04/Index?c%3dus%26l%3den%26s%3dbsd%26cs%3d04%26t%3dwarranty%26servicetag%3d<servicetag>

     Example:

    http://lt.dell.com/lt/lt.aspx?CID=72399&LID=1833144&DGC=AF&DGSeg=SLG&DURL=http://www.dell.com/support/troubleshooting/us/en/04/Index?c%3dus%26l%3den%26s%3dbsd%26cs%3d04%26t%3dwarranty%26servicetag%3djbnlbg1

     

  • Hey,

    Thanks for that quick reply.

    I am using Google Chrome but I tried on IE with api.dell.com in Trusted Sites with no success.

    On the OME Server side, I successfully reached the website page with warranty information by replacing the service tag with one of our server (through IE).

    I also tried to view warranty information in OME from the server itself with api.dell.com in Trusted Sites but this does not work too.

    Any ideas ?

    Thanks

  • Thanks for the updates.

    To understand this correctly, you can paste the above URL in the browser on the OME server and can see the warranty status for that server. On the same machine when you right click on the server and select Application Launch->View and Renew warranty, it does not show the warranty information.

    Is this correct?

  • There are two ways OME gets the warranty information. The URL mentioned above gets the warranty information using the right click option on the server.

    Warranty report uses the api.dell.com warranty webservice listed below. Can you also paste the URL below in the browser on OME machine and check if you are getting the data back for your service tag.

    URL:

    https://api.dell.com/support/v2/assetinfo/warranty/tags?svctags=<servicetag>&apikey=XXXXXXXXXXXXXXXXXXXXXXXXXXX

    Example

    api.dell.com/.../tags

  • Thanks for your help.

    Here is what I can do :

    Access warranty information with both links you gave me (lt.dell.com and api.dell.com) with one of our ServiceTag. From my computer's browser and from the server's browser (for both on IE). --> OK

    In OME, right click a server name and select "View and Renew warranty". --> OK

    What I can NOT do :

    Access warranty information for all servers in OME (Reports -> Warranty Information) from my computer and from the server itself (using http://localhost ...)

  • Thanks for the updates.

    Can you check for the OME logs by opening Windows Event Viewer. The logs are located under Application and Services Logs->Dell OpenManage.

    Since all OME solutions generate logs in event viewer, you can clear those logs once, then run the warranty report and check the logs after that. That would help getting to the appropriate log entries.

    Let us know if you see any error messages there.

  • Hey,

    I cleared the log as demanded and then tried to view the warranty report. This error has been logged :

    Log Name: Dell OpenManage
    Source: Essentials
    Date: 04.04.2012 08:08:55
    Event ID: 0
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: XXXXXXXXXX
    Description:
    An exception occurred while executing the update entitlements command.
    System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
    at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
    at System.Net.TlsStream.CallProcessAuthentication(Object state)
    at System.Threading.ExecutionContext.runTryCode(Object userData)
    at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
    at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    at System.Net.ConnectStream.WriteHeaders(Boolean async)
    --- End of inner exception stack trace ---
    at System.Net.HttpWebRequest.GetResponse()
    at Dell.OpenManage.Warranty.AssetService.GetWarrantyInformation(List`1 serviceTags, Guid applicationId) in d:\jenkins\jobs\OME_1.0.1_Build\workspace\bandera_front_end\common\Dell.OpenManage.Warranty\AssetService.cs:line 146
    at Dell.OpenManage.Essentials.Warranty.AssetEntitlements.UpdateEntitlements() in d:\jenkins\jobs\OME_1.0.1_Build\workspace\bandera_front_end\process_logic\Dell.OpenManage.Essentials.Warranty\AssetEntitlements.cs:line 65

    System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
    at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
    at System.Net.TlsStream.CallProcessAuthentication(Object state)
    at System.Threading.ExecutionContext.runTryCode(Object userData)
    at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
    at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    at System.Net.ConnectStream.WriteHeaders(Boolean async)

  • Thanks for the updates.

    It looks like it would be good idea to open a support ticket. Number is 800-945-3355.

    Support can work with you to gather the service tags and other logs as needed to debug this further.

    Regards

    Abhijit

  • Another thing to check would be to see if you have any other application/firewall running which is modifying the traffic in some way or trying to decrypt https traffic. which might cause the certificate error.