I'm getting a weird crash every time I open a standalone log and try to display the status bits. I can look at everything else without issue, but if I try to open the status bit panel, or leave it open and load a log the program crashes. I've sent in a bug report when it crashed. This only happens with standalone logs, if I log with the computer there is no issue.
Post an infolog(so I can at least see what software version you are running) as well as the scanner log in question.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
I think the info is what you need, let me know if you need something different.
Seems to open fine for me with the newest public build.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
Huh....What do I need to get that version?
goto your customers page and download it.
Downloaded 2.24.144, everything works fine on my work computer, but not on my home computer.
Happened to me again, this time on the computer that the other file worked on.
Strange, I to got the error when viewing status bits.
Attachment 40075
I also sent the error report.
My Suite Version is 2.24.71
Last edited by planethax; 07-10-2013 at 09:05 AM.
Make sure to update to the newest public build 2.24.144 or newer and try again and send a new error report if it crashes.Originally Posted by planethax
Strange, I to got the error when viewing status bits.
Attachment 40075
I also sent the error report.
My Suite Version is 2.24.71
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
Updated to latest, still get error.
I resent the info.
I also sent the error report
I do not get the error on first log posted but do on the second.
If Status Bit window open when opening log Scanner crashes right away.
If Status Bit window closed I can view and run log.
Clicking Status Bit opens window ok but as soon as you move the mouse it crashes.
I'm still having this problem. Any progress?
Ported TVS1900 OD cogs 10.5psi | ID850 | Vaporworx CTS-V 1:1 | COMP 219/233 .606"/.605" 113+1 | Ported TB | Pacesetter 1 3/4 LT | Solo Mach X3
Same issue here with 2.24.246, i started having this issue probably around .204, don't recall having this issue with .77, but i see somebody had the exact same issue i have with .71, Object reference not set to instance of an object.
This happens with standalone logs only, i installed .246 today, and now it's worst, before .246 i used to connect to the VCM at least one time, like to read a log having the laptop connected to the VCM, and sometimes this was allowing me to open the standalone file, now, no matter what i do, i can't open any standalone log.
Posting one of the logs in question along with the info log, it's frustrating to know something is messed up like this, sometimes it'll open, most of the time it will not. logs taken from the laptop work withot issues, but i can't have the laptop with me 100% of the time.
Please help, and yes, i've been hitting the send error report like crazy, you guys should have a lot of data to fix this by now
Regards,
Last edited by bluegoat06; 10-03-2013 at 08:09 PM.
Lol, with my luck, i was able to open up the file, all i did was to run the vcminflog, and it's working again. Tomorrow i'm sure the issue will come back, please HPT fix this issue, it's so frustrating......
"Object reference not set to instance of an object"
still getting this error when starting a VCM scan. Sent an error report. Any news n how to fix?
For now, open scanner (not log just scanner)
Close Status Bit window, then open log.
You can play log but do NOT open status bit window or you will crash.
Because we are rebuilding the scanner from the ground up in 2.25 we won't be fixing any additional scanner related bugs in 2.24 as it would just hold up 2.25 developement.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
Thanks for response, but I need to clarify. My error occured on first read of VCM, I actually put scan in previous post, but I was actually doing an initial read. Will closing the status bit window correct so I can pull my initial scan?
Reply With Quote
