"Error -88302 An internal error occurred" when attempting to test PCI-6221

[Phased]

Good day. I have a NI 68 pin PCI-6221 that is I cannot reset or query. I currently recieve and error of -88302 An internal Error has occurred. We are going to the card in another computer tomorrow. Does anyone have any ideas about this issue?

[Phased]

I also tried renaming the Data folder within the MAX directory. This is occurring in Measurment and Automation Explorer.

[John_P1]

Hi Phased,

Welcome to the NI forums!  I have a few follow-up questions for you that will help us troubleshoot the issue:

1. Are you trying to run the self test from an account with Administrative access?  If not, please follow the steps in this KnowledgeBase to see if that resolves your issue.
2. After renaming the Data folder did you restart your computer?  If the problem was a MAX database corruption, then you should restart your computer after renaming the Data folder to ensure that no corrupt data is cached.
3. What happens when you try the 6221 in another computer?
4. What version of DAQmx are you using?  I would try to repair DAQmx (through Add/Remove Programs), and if this does not work I would download and install DAQmx 8.8 if you have not done so already.

Let me know the answer to each of these questions (or if one of the suggestions resolves your issue) and we will go from there.  Thanks for posting!

-John 

[Phased]

Hi John. We've tried accessing the card as both a local admin and standard user of the system. We have not yet tried swapping the card into another box as a result of technical ability on the remote site. We will have a technician there either tomorrow or the day after to try that if needed. We've tried Daq 8.0 and 8.8 with with the results. And yes, I did reboot after renaming the Data folder.

[Phased]

Oh yes, and we;ve tried this on and off our domain.

[Phased]

Ok. We managed to remotely reimage the system and it's working now. Many issues popped up out of nowhere that made that descission. All is well now.

[John_P1]

Thanks for the update--there must have been a corrupt file or installation that was fixed by the reimaging.  I'm not sure which file it was, but if you run into the problem in the future you could try repairing the DAQmx driver before resorting to reimaging the system.  Glad to hear that everything is now functioning, thanks again for the reply!

-John 

[John_P1]

As a follow-up for anybody who happens to come by this thread, I had a customer who recently ran into this issue and fixed the problem by updating his DAQmx.  The user in this post also seems to have resolved his issue in the same manner.

Again, I think the problem is a software corruption, so updating the driver (or repairing/reinstalling) should be a good alternative to completely re-imaging the system.  Here is a link to our software download page where you can find the latest DAQmx driver.

-John

Message Edited by John P on 07-13-2009 10:52 PM