EIZO Colornavigator - Data Access Error

The other day I changed the SSD in one of my Macbooks (retina ...), and restored it from a TimeMachine backup.

Everything was working, except for Eizo Colornavigator 7, which gave me an error:

"Data Access Error - Failed to write data. The data my be corrupted. Uninstall ColorNavigator 7 once and reinstall it"

If for the life of it couldn't figure out what was going on, even using AppCleaner (which normally does a proper cleanup) did not fix it. I removed everything else I could find which had to do with Eizo, and still problem was there.

I then contacted Eizo Support, which told me to reinstall ... dooo.....

But I then just for the fun of it install the latest version again, and look at what it installed, and found "/Library/Application Support/EIZO/tools/ColorNavigator 7/" which have Uninstaller Full.app” and "ColorNavigator 7 Uninstaller.app”.

So the fix is:
# cd  "/Library/Application Support/EIZO/ColorNavigator 7/tools”

# open “ColorNavigator 7 Uninstaller Full.app”



Let it finish, then reinstall and presto it works again.


What hidden file it removes I do not know, maybe that is for another day.

Comments

Charles said…
On Windows 10, unfortunately, I found no alternate "full" uninstaller. What is worse, version 7.0.4, announced by Eizo as a fix for this problem in place of v. 7.0.3, gave me the same problem. While I wait for a response to my message to Eizo tech, I have gone back to version 6.4.24. It did not give me the Data Access Error problem.

CN7 integrates ColorNavigator Network, making the latter redundant. One hypothesis is that the network module and something in Windows 10 collide and crash.
May 10, 2019 at 4:52 AM
Charles said…
More on the problem in a Windows environment: after uninstalling the old version 7, you must also manually delete the \ProgramData\EIZO\ColorNavigator 7 folder, too. Then install the newer release of version 7. That was the advice from Eizo support, and it worked.
May 10, 2019 at 8:05 PM
gregveit said…
Thanks @Charles. Finally got it to work!
August 4, 2019 at 4:10 PM
Post a Comment

Popular posts from this blog

Apple AirPort Express and Digital Jitter..

I'm doing something which I can't really afford, but doing it anyway ... I'm upgrading my Stereo ... I like music, and  believe it should be played at the highest affordable quality. So after getting a new Stereo Amp (Creek Evolution 50A), I got a new Phono Amp. and then started looking for a DAC ... and after reading I do not know how many posts I decided to get an S.M.S.L M8 (from  Amazon  fro €249.99), not too expensive and according to what I can read very good. So I got it hooked it up to my amp, connected my Notebook (Macbook Air 11" / 2011) using USB ... sounded nice, then my Macbook Pro Retina with digital (fiber) in some way better than USB, slightly more air and openness. Then decided to use my old Apple Airport Express ( MB321LL/A  - 802.11n version 1) using it's digital output (I don't like the build in DAC - it's a bit too dark for me), and this is where I started having doubts about my buy. There was drop out, all the time. Right I changed, to
Read more

Kviknet and IPv6

Image
 I decided to switch ISP, mainly due to Hiper (Danish) was using a VLAN for their connection which made pfSense and my APU3 board require a reboot everytime I changed anything. Kviknet has a good reputation (wonder why) in Denmark, they are not cheap and they have the same opening hours as everyone else - meaning until 16:30 and closed during weekends. I sometimes wonder how companies who need 24/7 internet get on with that ... well it's Denmark. Kviknet has an interesting way to do IPv6, your router get and SLAAC assigned IPv6 address on the public side (wan) and you get a ::/48 network from Kviknet to use on your lan.  To some degree it does make sense, you can then configure your lan with static addresses as you see fit, and for dynamic assignment you use RA stateless dhcp *) ... which works for everything.  (I need to get my piHole configured with an static IPv6 so that I can use that ...). pfSense is a pain, I do like it, but they are light years behind their main competitor
Read more

MacOS Ventura: not able to ssh to ruckus switch (diffie-hellman-group1-sha1)

 I upgrade to Ventura and replaced my Intel MacMini with an M2 MacBook Air ... everything was working, then I wanted to ssh to my Ruckus ICX 7150-C12 (08.0.95fT211), and got an error: Unable to negotiate with my-switch port 22: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 Hummm, WTF.... I've seen similar things before when you upgrade FW or OS suddenly ssh will no longer work as a protocol or cipher have been deprecated. As I do not feel like upgrading my switch I had to do something else. I found this on serverfaul t, helped to a part of the way, and then a bit more googling I found the solution, which might be overkill. I ended up adding this in my ~/.ssh/config for the switch: Host my-switch KexAlgorithms=+diffie-hellman-group1-sha1 PubkeyAcceptedKeyTypes ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512 HostkeyAlgorithms +ssh-rsa    And now I can access my switch again. Yes, I know upgrading the firmw
Read more