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

Notification

Icon
Error
.81 update
Options View
Previous Topic Next Topic
W5GA
#1 Posted : Friday, January 8, 2016 7:43:06 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 395
Location: Missouri

Thanks: 72 times
Was thanked: 118 time(s) in 105 post(s)
Dennis, now .81 is dying. I've deleted prefix.dbf and reinstalled the update, same result. Logic stops working, and crashes.

73 Doug W5GA
73 Doug W5GA
Back to top
Sponsor
Note: We receive a commission from Amazon when you purchase via this link. It does not affect your cost. Thank you!
Back to top  
K1VC
#2 Posted : Saturday, January 9, 2016 7:52:48 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 294
Location: CT

Thanks: 9 times
Was thanked: 68 time(s) in 61 post(s)
My LOGic v .81 just died. I started to log 4Z/3Z9DX on 40 SSB and I couldn't get past 4Z/3 when LOGic died. I get a bunch of error messages and then a Program Error message and then LOGic closes. I re-installed the .81 update and that didn't help either.

I rebooted the pc several times and re-installed .81 and still nada. I also did a cleaned index and still nada.

I get the following error message:

OLE IDispatch exception code 0 from mscorlib: StartIndex cannot be less than zero.
parameter name startIndex..

Then I get these 3 error messages:

The first few messages are:
GLOBAL in not an object (Cancel/Ignore/Help) I hit IGNORE each time.

...and LOGic shuts down.

Everything was working well up until 7:00 pm EST 9-Jan-2016 until LOGic died.

I installed version .80 and .79 with the same results.

Very confused and frustrating. Scared Confused

Vin
Back to top
 |  Edit by user
ZL4AS
#3 Posted : Saturday, January 9, 2016 9:31:32 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 39
Location: Balclutha, New Zealand

Thanks: 4 times
Was thanked: 4 time(s) in 4 post(s)
I am (was) still running .79 when quite suddenly it failed today.

Error was:
OLE IDispatch exception code 0 from mscorlib: Specified argument was out of range of valid values. Parameter name index

A restart then a total close down and restart was no help (re-indexed each time).

An attempt to reload the .79 update appeared not to happen (probably recognised it was already there).

I'm on Windows 10 but beginning to wish I was not !

Also confused and frustrated. Help please Dennis (when you have time)

73, Cliff ZL4AS
Cliff Gray ZL4AS

QRZ info
Back to top
WWW
W5GA
#4 Posted : Saturday, January 9, 2016 9:50:50 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 395
Location: Missouri

Thanks: 72 times
Was thanked: 118 time(s) in 105 post(s)
I have .79 up and running. Machine is Win7. Uninstalled logic (leave the directory alone!!), reinstalled from CD and applied the .79 update. Working well so far.

73 Doug W5GA
73 Doug W5GA
Back to top
 |  Edit by user
K1VC
#5 Posted : Sunday, January 10, 2016 7:49:05 AM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 294
Location: CT

Thanks: 9 times
Was thanked: 68 time(s) in 61 post(s)
I'm running Win7 as well. I now I have LOGic 9.0.81 working.

The issue for me was when I tried to log 4Z/3Z9DX. LOGic would crash after I started to type 4Z/3 in the Call field. After several uninstalls and re-installs, I was able to deleted the 4Z/3 from the log, entered 3Z9DX/4Z and LOGic plays well with that call.

Not sure why it is but I now have LOGic 9.0.81 running again.

Vin
Back to top
 |  Edit by user
W5GA
#6 Posted : Sunday, January 10, 2016 11:16:25 AM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 395
Location: Missouri

Thanks: 72 times
Was thanked: 118 time(s) in 105 post(s)
That's interesting, Vin. Logic shouldn't care how the call is entered, and in previous iterations it did not.

I was wasn't doing anything at all when .81 died. I had the program open in the background, and all it was doing was receiving spot information from VE7CC. The only thing I had been doing with this particular install is running reports. This isn't the main station PC, it's my laptop, and reports/log extracts to upload to either LoTW or Clublog and watching spots is all this installation is used for.
73 Doug W5GA
Back to top
 |  Edit by user
K1VC
#7 Posted : Sunday, January 10, 2016 12:07:55 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 294
Location: CT

Thanks: 9 times
Was thanked: 68 time(s) in 61 post(s)
I can't explain it. LOGic was running all day yesterday, I logged a few contacts and watching spots on a local node when I logged Dom, 4Z/3Z9DX. All of a sudden, LOGic blew up and I started to get a bunch of error messages.

I've went through too much to fix LOGic so I'll leave it as is and hope Dennis finds a fix. BigGrin
Back to top
WN4AZY
#8 Posted : Sunday, January 10, 2016 7:05:08 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 guys using QRZ.COM per chance?

It was and probably is still causing LOGic to blow up on some calls. However, I can currently log 3Z9DX/4Z with auto callbook lookup on and qrx.com with no problems. If they fixed something, that could explain the seeming randomness.

What is the FIRST error you get?

Tnx & 73,

Dennis WN4AZY

ETA that I checked the callsigns that were known to cause errors, and they are OK for the moment.
http://www.hosenose.com/...defined-break-point.aspx
Back to top
WWW
 |  Edit by user
W5GA
#9 Posted : Sunday, January 10, 2016 7:29:35 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 395
Location: Missouri

Thanks: 72 times
Was thanked: 118 time(s) in 105 post(s)
I do not normally use QRZ, but sometimes. I was not using it when .81 died, nor had I anytime in the recent past. I'd like to say that I hadn't used it at all since installing .81, but don't quote me on that. The first error I received is that Logic quit working. After that, every time I start Logic (even after a clean), it would get almost all the way through the re-indexing process, and then quit working again. In fact, it had finished the re-index, and was just getting ready to display a normal log screen, but never quite got there.

Doug
73 Doug W5GA
Back to top
K1VC
#10 Posted : Sunday, January 10, 2016 8:32:01 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 294
Location: CT

Thanks: 9 times
Was thanked: 68 time(s) in 61 post(s)
Since installing v.81, I have not used callbook look ups when logging. I don't have LOGic look up any calls when I'm logging, I have LOGic setup to automatically log name, QTH and Via.

When I first tried to log 4Z/3Z9DX...LOGic only allowed me to get to 4Z/3, and the first error I got was:

OLE IDispatch exception code 0 from mscorlib: StartIndex cannot be less than zero.
Parameter name startIndex..

After that, LOGic blew up.

I would get to a full screen and then the error windows would start popping up and after several "IGNORE", LOGic would shut down.

I'm too scared to try logging 4Z/3Z9DX for fear of going through the nightmare again. I'll keep it as 3Z9DX/4Z since LOGic is happy.

Vin
Back to top
1 user thanked K1VC for this useful post.
WN4AZY on 1/11/2016(UTC)
WN4AZY
#11 Posted : Monday, January 11, 2016 7:36:46 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)
Quote:
When I first tried to log 4Z/3Z9DX...LOGic only allowed me to get to 4Z/3, and the first error I got was:

OLE IDispatch exception code 0 from mscorlib: StartIndex cannot be less than zero.
Parameter name startIndex..

I can reproduce it now. Fix should be here tomorrow. YOU did most of the work already hihi.

Tnx & 73,

Dennis WN4AZY
Back to top
WWW
WN4AZY
#12 Posted : Monday, January 11, 2016 8:44:32 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)
Back to top
WWW
N5XZ
#13 Posted : Tuesday, January 12, 2016 8:26:47 AM(UTC)
Rank: Advanced Member

Groups: Registered, Beta Testers
Posts: 409
Location: Richmond, TX

Thanks: 35 times
Was thanked: 57 time(s) in 54 post(s)
I'm not going to download it until you guys tell me it;s ok...
73, Allen N5XZ
Back to top
W5GA
#14 Posted : Tuesday, January 12, 2016 9:16:36 AM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 395
Location: Missouri

Thanks: 72 times
Was thanked: 118 time(s) in 105 post(s)
Running .82 as of last night, so far so good.

Doug
73 Doug W5GA
Back to top
1 user thanked W5GA for this useful post.
WN4AZY on 1/13/2016(UTC)
WN4AZY
#15 Posted : Tuesday, January 12, 2016 9:54:16 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)
Pse download it again. The one I posted last night would croak if you logged "/1". I fixed it early this morning. I THINK I tested all possibilities of garbage input hihi.

Tnx/73,

DH
Back to top
WWW
W5GA
#16 Posted : Tuesday, January 12, 2016 9:39:39 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 395
Location: Missouri

Thanks: 72 times
Was thanked: 118 time(s) in 105 post(s)
Got it, thanks Dennis.
73 Doug W5GA
Back to top
K1VC
#17 Posted : Wednesday, January 13, 2016 12:05:23 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 294
Location: CT

Thanks: 9 times
Was thanked: 68 time(s) in 61 post(s)
Just installed v.82. Going to try and change 3Z9DX/4Z to 4Z/3Z9DX...wish me luck BigGrin

It worked !!!!! BigGrin
Back to top
 |  Edit by user
1 user thanked K1VC for this useful post.
WN4AZY on 1/13/2016(UTC)
W5RAE
#18 Posted : Wednesday, January 13, 2016 5:20:54 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 46
Location: Plano, TX

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

Knock on wood, but I have had no issues nor error message since I upgraded to v82.

Thanks for the fixes.

73,
Ron
W5RAE
Back to top
N5XZ
#19 Posted : Thursday, January 14, 2016 11:05:07 AM(UTC)
Rank: Advanced Member

Groups: Registered, Beta Testers
Posts: 409
Location: Richmond, TX

Thanks: 35 times
Was thanked: 57 time(s) in 54 post(s)
Yup. .82 here and no (new) problems.
73, Allen N5XZ
Back to top
W5GA
#20 Posted : Sunday, January 17, 2016 5:17:54 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 395
Location: Missouri

Thanks: 72 times
Was thanked: 118 time(s) in 105 post(s)
All working as it should now with .82

thanks again, Dennis!
73 Doug W5GA
Back to top
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.079 seconds.