1. Go to the Nationwide box and select Maritime
2. Click on Get Data and uncheck the items not to import
3. Click Import
ProScan: Official Software Thread
1. Go to the Nationwide box and select Maritime
2. Click on Get Data and uncheck the items not to import
3. Click Import
Does that give the international also? I had to pick a country in order for the database selection to show up.
Thanks Bob for your help
Select the Country first. What country? I see Canada & UK has Nationwide systems listed. Australia no
Last edited:
I did answer them in a previous reply with the exception of the event viewer. Please let me know what else you would like me to answer.
I found this in the event viewer.
Faulting application name: ProScan.exe, version: 12.6.0.0, time stamp: 0x59fd906c
Faulting module name: KERNEL32.dll, version: 6.1.7601.23915, time stamp: 0x59b94aba
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x1c6c
Faulting application start time: 0x01d36ab0d8fce190
Faulting application path: C:\Program Files (x86)\ProScan\ProScan.exe
Faulting module path: C:\Windows\syswow64\KERNEL32.dll
Report Id: a565011c-d6ea-11e7-a705-bc5ff4547cb7
Did you try the following?
1. Try elevating ProScan to Admin. Rerun and see what happens. I doubt this will work but when I google searched this, It fixed it for one person that was getting this type of error with another program.
2. Retest without the Web Server running to confirm it's specific to the Web Server.
3. Check that your Windows Updates are up to date.
What I have don so far -
Raised ProScan to Admin , Windows are up to date, and Web server On. With this combination the software crashed after about 8 hours.
Current setup - Proscan running in admin, Widows are up to date, Web Server OFF. With this configuration Proscan is approaching 18 hours and no crash yet.
So I suspect there must me something related to the webserver function causing it to crash.
Ok, thanks. I've had 5 or 6 reports of this problem in the last 12 years. Last report by a user advised a graphics driver was out of date causing the problem.
Can you try one thing. Change an option "Program Icon". It's located in the Options - General tab. Set it to "Normal" for at test.
Other then that, I don't think anything can be done in ProScan other then don't show graphics. It's a problem deep inside the OS at the Kernel level dealing with the memory management and hardware. I think the problem is related to the graphics card so perhaps double check you have the lastest version of the graphics driver.
Just checked. It is already set to normal.
I will check on the graphics card drivers next. Thanks!
I will check on the graphics card drivers next. Thanks!
Can you also uncheck the option "Show Activity Color On Program Icon" and see what happens
OK will do that next. Currently attempting to check the driver version and update if necessary.
I have the latest drivers already. Now unchecking the "Show Activity Color On Program Icon" selection.
I will let it run and see if it crashes during the day.
Thanks!
I will let it run and see if it crashes during the day.
Thanks!
Bob,
Since we were discussing the graphics interface and drivers I put in an Nvidia PCI graphics card and got off the on board Intel that was being used initially. This is a better graphics interface if it has anything to do with the software crashing at all. I will monitor going forward.
Since we were discussing the graphics interface and drivers I put in an Nvidia PCI graphics card and got off the on board Intel that was being used initially. This is a better graphics interface if it has anything to do with the software crashing at all. I will monitor going forward.
Okay, let me know what happens.
Yes I will. Thanks!
I started scanning a new 800mhz trunked system in my area and use ProScan for the remote scanner, logging, and programming. After figuring out which Talk Group IDs were what I entered them into my program. But when I write the program to the scanner it gives me this error...which is the first TG in the list. It errors every time.
Talk Group Channel Error - 501, SystemName = BOZEMAN TRUNKED, GroupName = BZN TGID, ChannelName = Bozeman PD, Code = ABP,ERR
I did a couple searches and couldn't find anything. Thanks much, this program is awesome!
Talk Group Channel Error - 501, SystemName = BOZEMAN TRUNKED, GroupName = BZN TGID, ChannelName = Bozeman PD, Code = ABP,ERR
I did a couple searches and couldn't find anything. Thanks much, this program is awesome!
I don't know at this point. Can you email me the database file so I can upload it and see what's happening.
Bob,
Even with the upgraded graphics card, the software crashed. Here is the code again. Can you decipher it as the program writer?
Problem signature:
Problem Event Name: BEX
Application Name: ProScan.exe
Application Version: 12.6.0.0
Application Timestamp: 59fd906c
Fault Module Name: KERNEL32.dll
Fault Module Version: 6.1.7601.23915
Fault Module Timestamp: 59b94aba
Exception Offset: 00000000
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 2bba
Additional Information 2: 2bba7f1a734eb5a6f84844ca89c1212a
Additional Information 3: ef31
Additional Information 4: ef31141e9d3bb2fb7abec2e3e8b369cf
Only decipher info are KERNEL32.dll which is the OS kernel and BEX which is buffer overflow exemption. It could be a memory leak, memory conflict, hardware conflict, etc.. The problem could be a zillion things related to my code or 3rd party such as Microsoft. It could be a common control such as the grids, or GDI+(graphics), file I/O, dot net framework namespaces, Win API's. Doing a google search "KERNEL32.dll BEX" shows it's a relatively common problem. Many users have posted this same problem with iTunes, Chrome, Edge, and the list goes on and on.
High level programs to low level API's could take a hundred or thousand calls to a particular function so it's kind of like spaghetti and I think it's really impossible to troubleshoot especially if I can't duplicate the problem. ProScan has a catch all exemption (or error) trapping/catching/handling but it doesn't work on older dll's that don't throw exemptions.
I'm not sure how common this is with ProScan. In the last 12 years or so, I received 4 or 5 reports of this type of problem. Your testing is greatly appreciated.
One thing I can think of is email me so I can send a special debug version that may produce additional hints of where the problem lies
Just emailed you Bob. Thanks!
