16452Re: [ARRL-LOTW] Need help withTrusted QSL
- Dec 8, 2012
> The fact that TQSLcert doesn't tell you what's going wrong, alongAnd one among many others that I trust the rebooted tQSL open source
> with requring to use arcane "%AppData" commands to diagnose it is a
> serious oversight in TrustedQSL.
project will address <G>.
... Joe, W4TV
On 12/8/2012 8:42 AM, Rick Murphy/K1MU wrote:
> At 11:04 PM 12/7/2012, barramunda@... wrote:
>> I tried this before. I got the new certificate on email. I
>> double-clicked on the .tq6 certificate file, but got the same result.
>> I even tried uninstalling all TQSL files and started over. Same result,
>> Walt - W2EVU
> Perhaps you missed the second half of the requirement.
> When you issue a certificate request, a file is created ON THAT
> COMPUTER that's needed to complete the issuance process.
> Whe you receive the TQ6 back from LoTW, that file is needed. If you try
> to install the TQ6 on a computer without that file, it won't work. You
> must open the TQ6 on that computer using the same computer login
> account - if not, you can't find that private key and LoTW won't
> recognize the certificate.
> You can see what it's looking for - start Windows Explorer (Windows-E).
> In the address bar, type "%AppData\TrustedQSL\keys" without the quotes
> and enter.
> You should see a file with just your callsign. If it's not there or
> can't be read, TQSLcert can't complete the certificate registration
> The only other case where I've seen this happen was with a computer
> that for some unknown reason wasn't allowing the user to read/write in
> their windows Application Data folder (as above). No private key means
> that you can't finish the registration.
> This is by far the most common question asked here. The fact that
> TQSLcert doesn't tell you what's going wrong, along with requring to
> use arcane "%AppData" commands to diagnose it is a serious oversight in
> Yahoo! Groups Links
- << Previous post in topic Next post in topic >>