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

Notification

Icon
Error

OLE exception code
KA1J
#1 Posted : Tuesday, January 19, 2016 10:27:41 AM(UTC)
Rank: Advanced Member

Groups: Registered, Beta Testers
Posts: 56
Location: Groton, CT

Thanks: 24 times
Was thanked: 5 time(s) in 5 post(s)
V9.0.82

The following has happen frequently lately; I will leave Logic running and return to see what is active as regards the spot log. I will find the error listed below in a small rectangular window Logic uses:

Program error
OLE ldispatch exception code 0 from system: The I/O operation has been aborted because of either a thread exit or an application request

What happens if I then click on ignore is as follows:

Ignore

Function argument value, type, or count is invalid.

Ignore

Function argument value, type, or count is invalid.

Ignore

Function argument value, type, or count is invalid.

Ignore

Function argument value, type, or count is invalid.


I have been getting these OLE exception code messages frequently. Usually logic works fine after hitting ignore several times but sometimes I have to restart Logic to get Spot Log to behave as expected.

Any suggestions?
Thanks & 73,

Gary
KA1J

P.S: I've tried to post this for some time but I was putting < and > outside the word ignore and it was preventing me from posting. Apparently that is a nono phrase in Net 4.0
Sponsor
Note: We receive a commission from Amazon when you purchase via this link. It does not affect your cost. Thank you!
N5VR
#2 Posted : Sunday, January 24, 2016 11:57:27 AM(UTC)
Rank: Member

Groups: Registered
Posts: 22
Location: Austin

Thanks: 4 times
This error drives me crazy. The symptoms are the same as yours but I have always suspected it was related to the rig interface rather than spotting.

Bill N5VR
WN4AZY
#3 Posted : Sunday, January 24, 2016 7:52:03 PM(UTC)
admin

Rank: Administration

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

Thanks: 998 times
Was thanked: 497 time(s) in 412 post(s)
Are you using any non-FTDI USB=>RS232 adapters? What kind of rig?

Tnx & 73,

Dennis WN4AZY
KA1J
#4 Posted : Tuesday, January 26, 2016 5:40:37 PM(UTC)
Rank: Advanced Member

Groups: Registered, Beta Testers
Posts: 56
Location: Groton, CT

Thanks: 24 times
Was thanked: 5 time(s) in 5 post(s)
I'm using the adapter I bought from you, it's a very nice adapter.

73,

Gary
KA1J
WN4AZY
#5 Posted : Thursday, January 28, 2016 5:16:04 PM(UTC)
admin

Rank: Administration

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

Thanks: 998 times
Was thanked: 497 time(s) in 412 post(s)
Ok, try uninstalling the drivers and reinstalling them. Go to the device manager, right-click the device, and select UNINSTALL. Then unplug the device and plug it in again.

Let me know.

Tnx & 73,

Dennis WN4AZY
NA5Q
#6 Posted : Sunday, January 31, 2016 8:53:15 AM(UTC)
Rank: Member

Groups: Registered
Posts: 13
Location: Louisiana

Was thanked: 3 time(s) in 3 post(s)
Dennis,

I am on update 82. Been having problems with Logic giving error code a few versions back and this one. The error message reads

OLE error code 0x80004005: Unspecified error.

Pressing Ignore removes error and I am able to use Logic 9 for a short while, then it returns or I get the message:

"logic.exe has stopped working correctly. Windows will close the program and notify you if a solution is available."

Now I have to close program, on restart it does a clean and then runs sometimes giving me the OLE message above.

This is quite aggravating, because it happens often!

I am using Windows 7 with all latest updates, Logic 9 version 9.0.82, Connected to Com 5 on a Flex SDR 6700 at 9600 baud 2 Stop Bit and POLL Checked.

Roland G. NA5Q
WN4AZY
#7 Posted : Tuesday, February 2, 2016 9:16:25 AM(UTC)
admin

Rank: Administration

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

Thanks: 998 times
Was thanked: 497 time(s) in 412 post(s)
Hi Roland:

Does the error stop appearing if you disable the rig interface?

The Windows event log often gives more information. After the error happens, go to the event viewer. Just type EVENT VIEWER in the Win 7/8/10 search bar. Look under Windows Logs, then Application.

Let me know.

Tnx & 73,

Dennis WN4AZY
Users browsing this topic
Guest (3)
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.031 seconds.