Error Code 003

[Guest]

[visad]

  I have same prob with "error code" CAV003   ON ACSSESS SCANNER INOPERATIVE?

*edited title to reflect question and split post off*

[psych1610]

Hey Visad, welcome to the forums. First, I just wanted to let you know I did split off your post (as you can tell) from where you put it. I did this to try to ensure you could get the best help possible and also because I don't believe your question was similar to the one you were responding to. I believe he was asking more about Windows not recognizing CAVS in the Security Center.. just wanted to give you my reasoning 

As far as your problem it seems to be caused by a variety of issues. Would you mind giving us a few more details?

When it occurs, computer your using CAVS on, anything else you think might be helpful.

Also, a quick search of the forums for "error 003" lists a few posts that might be of assistance to you and might get you a solution quicker than posting here would. If you can't find one though, feel free to keep on asking questions and we'll try to get to the bottom of it.

This is a well documented error though with only a few work arounds and no set in stone solutions (I think).

Once again, welcome.

Dave

[panic]

Error 003 is usually caused by not rebooting after installing CAVS2 BETA. The low level drivers have not been initialised and therefore cannot communicate, causing the 003 error.

If you have rebooted since the install, please try the following;

1. Uninstall CAVS2 Beta
2. Reboot
3. Reinstall CAVS2 Beta
4. Reboot
5. Check that the CAS2 Beta services and drivers are running.

hope this helps,
Ewen :-)

[Tags:]