logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

error since update 9.0.82 intstall
km2e
#1 Posted : Sunday, January 24, 2016 1:54:27 PM(UTC)
Rank: Member

Groups: Registered
Posts: 19
Location: Hudson, NY

Thanks: 8 times
Was thanked: 1 time(s) in 1 post(s)
dennis,

since installing the 9.0.82 update, i receive the two error messages. "Command contains unrecognized phrase/keyword. and "object global is not found." these messages cause logic to stop functioning. how would i remove the update and go back to 9.0.81 or earlier?

kevin
km2e
File Attachment(s):
error logic 1.pdf (147kb) downloaded 32 time(s).
error logic.pdf (155kb) downloaded 33 time(s).
Sponsor
Note: We receive a commission from Amazon when you purchase via this link. It does not affect your cost. Thank you!
WN4AZY
#2 Posted : Sunday, January 24, 2016 7:50:18 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,061
Man
Location: Auburn, GA

Thanks: 974 times
Was thanked: 485 time(s) in 400 post(s)

Thanks for your note. Sorry for the problem.

What is the first error you get? What are you doing in LOGic when this happens?

Thanks,

Dennis WN4AZY
OZ4CG
#3 Posted : Monday, January 25, 2016 11:31:33 AM(UTC)
Carsten Gjessing

Rank: Advanced Member

Groups: Registered
Posts: 49
Man
Location: Denmark

Thanks: 17 times
Was thanked: 14 time(s) in 14 post(s)
Hi, Dennis!
Since I downloaded 9.0.82, I get this start-up-error: "Error 1426 "OLE error code 0x80004005: unspecified error." has occurred in program. LOGICAPP.MODE_CHANGE, line 31." But when I click Yes to continue, the program opens normally. So it does not bother me, but I think you might know!
Another problem comes when I have downloaded LoTW-QSL's, and as usual will send a mail to the LoTW-database. Then I get this error: "You have not downloaded any QSO's from LoTW. Nothing to email." And that is not true.. Hi! This error does not bother me as well, but I think you might know this also...
Best 73 from a satisfied LOGic9-user...
Carsten / OZ4CG
File Attachment(s):
Start-up error 2016-01-14 17.24.13.png (16kb) downloaded 26 time(s).
LoTW-error 2016-01-21 20.20.00.png (20kb) downloaded 26 time(s).
1 user thanked OZ4CG for this useful post.
WN4AZY on 1/25/2016(UTC)
km2e
#5 Posted : Monday, January 25, 2016 4:32:44 PM(UTC)
Rank: Member

Groups: Registered
Posts: 19
Location: Hudson, NY

Thanks: 8 times
Was thanked: 1 time(s) in 1 post(s)
Dennis,

Seems like if I just open logic and don't try and connect to the cluster via telnet 1 then the programs runs ok. When I attempt to connect to the cluster via telnet then the message;
"Command contains unrecognized phrase/keyword" pops up and locks up the program. I then must close logic and reopen to have any access, until I try and connect to the cluster at which time the program again locks up.

Kevin
km2e

1 user thanked km2e for this useful post.
WN4AZY on 1/25/2016(UTC)
WN4AZY
#6 Posted : Monday, January 25, 2016 7:37:16 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,061
Man
Location: Auburn, GA

Thanks: 974 times
Was thanked: 485 time(s) in 400 post(s)
Kevin:

Great detective work! We did change how the login works.

What telnet host are you trying to connect to? Did you do your own prompt/response or scripting?

Tnx & 73,

Dennis WN4AZY
km2e
#7 Posted : Monday, January 25, 2016 8:03:25 PM(UTC)
Rank: Member

Groups: Registered
Posts: 19
Location: Hudson, NY

Thanks: 8 times
Was thanked: 1 time(s) in 1 post(s)
Dennis,

I only stay logged in for a few seconds, then I get the error message. It appears that the only screens affected are the telnet and spotlog. The rest of the program seems to work good. I usually use dxc.w1nr.net or w3lpl. I can't stay logged into any of them. I use the prompt/response.

What should I do to correct the login issues.

Kevin
km2e
WN4AZY
#8 Posted : Monday, January 25, 2016 8:45:29 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,061
Man
Location: Auburn, GA

Thanks: 974 times
Was thanked: 485 time(s) in 400 post(s)
Carsten:

I found the problem with LoTW and email to BBCyber. It will be fixed shortly.

The OLE error is caused by logicserver.exe, which allows LOGic to communicate with third-party programs. You can try renaming logicserver.exe to logicserver.exex. It is located in the LOGic install folder c:\program files (x86)\logic typically. This will prevent LOGic from loading the server when you start LOGic, and should bypass that error.

If you run into problems after renaming it, we will have to look at whatever you have LOGic interfaced to.

Let me know.

Tnx & 73,

Dennis WN4AZY

1 user thanked WN4AZY for this useful post.
OZ4CG on 1/27/2016(UTC)
WN4AZY
#11 Posted : Wednesday, January 27, 2016 10:46:15 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,061
Man
Location: Auburn, GA

Thanks: 974 times
Was thanked: 485 time(s) in 400 post(s)
Please post screen shots of your setups for these two hosts.

I found W1NR already in LOGic. The prompt had changed so the SH/FDX no longer worked, but I couldn't reproduce the error. Attached is a screen shot of the proper setup.

You mentioned the spot log. Maybe the spot log is the real issue. Close Telnet, and try getting spots from DXScape. I'm thinking that the expressions for Alerts or Prefilter got messed up somehow.

Call me if you want and I can log in and take a look, or tell me a good time to call you (evenings, days...) I'm thinking that this is coincidental to the .82 update.

Tnx & 73,

Dennis WN4AZY
File Attachment(s):
capture.jpg (62kb) downloaded 36 time(s).
1 user thanked WN4AZY for this useful post.
km2e on 1/31/2016(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF 1.9.5.5 | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.036 seconds.