|
|
Logbook-Unspecified-error.PNG (61,758 bytes) |
|
|
I'm not able to reproduce this issue. The issue can't be reproduced on my laptop because I don't have a QLM development license for my laptop and the problem described in Matnis 3549 prevents me from using this feature without a QLM license installed. I've tried to repro this issue on my desktop. I see the error about the echo command go by almost immediately afer connecting, but I don't get a message box from the application afterward. I've tried twice, waiting about 20 minutes each time. |
|
|
Do you need a QLM dev license to repro this? I don't have a QLM license on my laptop and the repro is pretty solid there. Which message box are you referring to? The "Unspecified error" one? With an AR Cluster node... those things are pinging me to death. |
|
|
Developers need a QLM license to run a QLM-protected application under a debugger. Applications in the HRD suite are QLM-protected. The Logbook won't connect to a DX Cluster without some (all?) fields in the My Station window set. Since the application won't load the My Station data under the debugger when no QLM license is present, I'm unable to open the DX Cluster and connect on my laptop. Yes, I'm referring to the "HRD Logbook" message box in your screenshot with the error message. No such error messages appear for me after I follow your repro steps. |
|
|
I've asked Soraco for support on this. As I've said before, I have no problem obtaining another QLM Dev license. Last time this came up, I was under the impression that it wasn't needed. As quickly as I can get feedback from Soraco, I can solve this problem. |
|
|
I think there have been email conversations about this problem, and for sure Mantis 3549 is documenting the issue. As I'm not going to be spending much time on this project in the future, the purchase of an additional license for me isn't warranted. Further notes about the issue should be made in Mantis 3549 so that this issue isn't diluted. |
|
|
While I'm sorting out the Soraco response... to verify... You're connected to the K1TTT cluster with the following? Title: K1TTT test Address: dxc.k1ttt.net Port 7373 The only way this error will repro is if the connection is made to an AR Cluster. K1TTT is an AR Cluster. (The "echo #" command is no problem for other types of nodes.) |
|
|
My connection settings match those given in the repro |
|
|
You need to have an active database with WSI enabled |
|
|
With the 6.7.0.245 build, I am unable to repro this. |
|
|
After receiving the 6.7.0.245 beta build, Ferry and I can no longer reproduce this. Closing |
- Anonymous
