Loading ...
Sorry, an error occurred while loading the content.

20947RE: Re: [ARRL-LOTW] HRD to/from LoTW failure

Expand Messages
  • KQ8M
    Nov 6, 2013
    • 0 Attachment

      You will get no support from HRD. They have discontinued support for V5 and earlier. They now only support V6. You may get someone to answer you in the forums but be prepared to get chastised from the powers that be.

       

      73,

      Tim Herrick, KQ8M

      Charter Member North Coast Contesters

      kq8m@...

       

      AR-Cluster V6 kq8m.no-ip.org

      User Ports: 23, 7373  with local skimmer, 7374 without local skimmer

      Server Ports: V6 3607, V4 Active 3605, V4 Passive 3606

       

      From: ARRL-LOTW@yahoogroups.com [mailto:ARRL-LOTW@yahoogroups.com] On Behalf Of w1kf@...
      Sent: Wednesday, November 06, 2013 6:25 PM
      To: ARRL-LOTW@yahoogroups.com
      Subject: RE: Re: [ARRL-LOTW] HRD to/from LoTW failure

       

       

      Thanks, Joe. I'll take  a look at that, and the web address.

       

      73,

      Steve

      W1KF 



      ---In ARRL-LOTW@yahoogroups.com, <lists@...> wrote:

      The "Invalid DateTime LotW" entries appear to be *internal* HRD errors.
      I suggest seeking help from HRD support *not* from LotW support.

      I notice these started happening *after* the change from DST to standard
      time. Again, it would appear to be an *issue internal to HRD* related
      to the computer clock/timezone.

      73,

      ... Joe, W4TV

      On 11/6/2013 4:37 PM, w1kf@... wrote:

      > In my case (HRD 5.24.0.36), TQSL -is- being used to sign the file. I was using 1.14, and only switched to 2.0 when this started happening.
      >
      > Logs generated by HRD, exported as ADIF, then signed and uploaded by TQSL are being corrrectly received in my account.
      >
      > Here is an HRD logfile entry when I try to upload a (duplicate) QSO:
      >
      > Invalid DateTime LOTW Creating C:\Users\Rob\AppData\Local\Temp\LOTWUpload 2013-11-06 163626.ADI...
      > Invalid DateTime LOTW Exported 1 entries to C:\Users\Rob\AppData\Local\Temp\LOTWUpload 2013-11-06 163626.ADI
      > Invalid DateTime LOTW Signing ..: C:\Users\Rob\AppData\Local\Temp\LOTWUpload 2013-11-06 163626.ADI
      > Command ..: "C:\Program Files\TrustedQSL\tqsl.exe" -d -l "Home" -p "helpme??" "C:\Users\Rob\AppData\Local\Temp\LOTWUpload 2013-11-06 163626.ADI" -o "C:\Users\Rob\AppData\Local\Temp\LOTWUpload 2013-11-06 163626.TQ8" -x
      >
      > Invalid DateTime Signing Command = "C:\Program Files\TrustedQSL\tqsl.exe" -d -l "Home" -p "helpme??" "C:\Users\Rob\AppData\Local\Temp\LOTWUpload 2013-11-06 163626.ADI" -o "C:\Users\Rob\AppData\Local\Temp\LOTWUpload 2013-11-06 163626.TQ8" -x
      > Error = TQSL Version 2.0 [v2.0]
      > Error = Signing using Callsign W1KF, DXCC Entity UNITED STATES OF AMERICA
      > Error = C:\Users\Rob\AppData\Local\Temp\LOTWUpload 2013-11-06 163626.ADI: wrote 1 records to C:\Users\Rob\AppData\Local\Temp\LOTWUpload 2013-11-06 163626.TQ8
      > Error = C:\Users\Rob\AppData\Local\Temp\LOTWUpload 2013-11-06 163626.TQ8 is ready to be emailed or uploaded.
      > Error = Note: TQSL assumes that this file will be uploaded to LoTW.
      > Error = Resubmitting these QSOs will cause them to be reported as duplicates.
      > Error = Final Status: Success (0)
      > Error =
      > Invalid DateTime GetHttpConnection URL ............: p1k.arrl.org
      > Internet port ..: 443
      >
      > Invalid DateTime CHttpConnection::OpenRequest Verb ..........: 0
      > Object name ...: /lotwuser/default
      > Referer .......: https://p1k.arrl.org/lotwuser/default
      > Accept types ..: NULL
      > Version .......: NULL
      > Flags .........: 04803000
      >
      > Invalid DateTime LOTW Login Error = The server returned an invalid or unrecognized response
      >
      >
      >
      > Invalid DateTime Reload Loaded 2778/2778 records in 908 miliseconds, 3059.5 records per second
      >
      >
      >
      >
      >
      > ---In ARRL-LOTW@yahoogroups.com, <k1mu@...> wrote:
      >
      > On Wed, Nov 6, 2013 at 2:57 PM, <tdavis@... mailto:tdavis@...> wrote:
      > I person on the HRD group said the following...
      >
      > "I believe the problem is related to a change on the ARRL side of the equation. The redirect that the ARRL does from the old API URL to the new URL doesn't pass the login parameters correctly. I was able to spoof the login from HRD 5 and alter the URL so that the redirect doesn't occur and was able to login without a problem"
      >
      >
      >
      >
      >
      >
      > That's not it. Or, it's not why uploads are failing in any case. When TQSL uploads logs, it does not require any user ID or password.
      >
      >
      > I'll ask again: what do you see when you log in to LoTW and look at your activity? I'm trying to figure out if TQSL is getting invoked to sign the log at all or not.
      >
      > 73,
      > -Rick
      >
      >
      >
      >
      >

    • Show all 41 messages in this topic