Cbus IP Utility [Archive]

constantcharge

06 Aug 10, 01:14 PM

Hi Guys,

Trying to commision a new black matrix, but having some issue with IPutility 1.1.0.
Im getting a access violation at address 0052A66F in module 'CBusIPUtility.exe'
Read of address 0000000C.
If I Roll back to ver 1.0.0 it works but I cant see the matrix only shows wiser V1 and CNI.

Running windows 7. If that makes a difference :)

Newman

06 Aug 10, 01:21 PM

What were you doing when the exception occurred? Was it during a network scan, or something else?

constantcharge

06 Aug 10, 01:43 PM

I opended up IP utility and it performed scan when status bar got to 100% violation occured.

Have tried on Windows 7 & Vista on 3 pc same problem.

ashleigh

06 Aug 10, 06:52 PM

Can you run it in XP mode on Win7 ?

constantcharge

06 Aug 10, 07:50 PM

I have tried to run in compatibility mode for xp with same result.

If your meaing the winxp mode for windows 7 I believe that it requires Ultimate or Pro edition which I unfortunatly I dont have. :rolleyes:

Guess I may have to install a virtual machine to try, but didnt have time on site.

Previous version runs fine but can someone confirm that the ver 1.0 worked with matrix or not as it didnt pick up the matrix when on site.

ashleigh

06 Aug 10, 10:54 PM

Ver 1.0 will NOT work with matrix switcher. It needs ver 1.1.

It was tested (a lot) during development and worked fine, so why its crashing for you is a mystery. It'll need somebody in office hours to go check whats happening.

Conformist

08 Aug 10, 03:09 PM

yep... just got the same error. This error seems to caused by Wiser! Whilst Wiser is communicating with the CNI, the error occurs. I changed the IP address (in PICED, of the CNI that Wiser is to communicate with) to that of a CNI that doesn't exist and the utility works fine.

Try this (if you need to reconfigure) until a fix can be applied

Cheers

constantcharge

14 Aug 10, 03:17 PM

Thanks yea got it working. I just reset the wiser and did scan while it was still booting up. Guess thats one good thing about the 90sec's it takes to reboot :)

Charlie Crackle

16 Aug 10, 12:50 AM

I just got the same error and there was a wiser on the network. thank for the tips to fix this.

Charles