09-19-2024 01:33 AM
The devices with issue are cRIO-9066.
I have tried:
Any more ideas, before formatting the PC?
09-19-2024 07:17 AM - edited 09-19-2024 07:17 AM
Hi Anders,
Ensure you have all the required softwares and drivers on your computer for programming with a cRIO:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019PTeSAM&l=en-US
Regards,
Raphaël.
09-19-2024 09:20 AM
The picture posted seems to show the offending items on TARGET:MyComputer. Since, MyComputer is NOT a RIO Device the RIO items will not work there and the Project Explorer is simply pointing out that it expects a RIO Target.
Somebody removed the RIO Device from the project.
09-19-2024 09:37 AM
Everything is installed, I have checked.
And we are also using same NI Package to install all computers, the 5 other computers are working without problems.
09-19-2024 09:39 AM
Thanks for the suggestions.
Same project is working on other PC.
The cRIO are under "Project" and not under "MyComputer"
09-19-2024 09:44 AM - edited 09-19-2024 09:46 AM
Does the cRIO 9066 show up in NI MAX? It's pretty hard to decipher a redacted picture 😉
What information is available from the warning?
09-19-2024 01:42 PM
Yes the cRIOs are shown in MAX.
It says the warning is because of missing software or license. But it is exactly same software and license as the other PCs.
So now I think it's an issues with the registry database, and the easiest solution right now is a format and reinstall, but I would like to know is there is a fix, maybe also if I encounters the problem again.
I have also looked for logfiler for more info, but I can't find it in LabVIEW log file locations I know.
09-19-2024 02:03 PM - edited 09-19-2024 02:12 PM
@AndersSekanina wrote:
Yes the cRIOs are shown in MAX.
It says the warning is because of missing software or license. But it is exactly same software and license as the other PCs.
So now I think it's an issues with the registry database, and the easiest solution right now is a format and reinstall, but I would like to know is there is a fix, maybe also if I encounters the problem again.
I have also looked for logfiler for more info, but I can't find it in LabVIEW log file locations I know.
When I saw that in the past I often tracked down that the offending install was done without respect for the "Please close all other applications prior to...." prompt or, forgetting to reboot the OS to complete the installation process. You might want to just wipe the darn <I COULD USE 4 LETTER WORDS OTHER THAN DARN> machine and start again given 5 other machines are working.
Then, adjust your IQ (installation qualification) procedure documents to reflect changes. Sometimes you cannot identify why but, User Interactions during installation are the most common problem.
Computers and computer programs generally just do the same thing over and over as they are programmed to to. Users....meh....Not so much!
Of course, you should never troubleshoot the general case!
09-20-2024 01:39 AM
Hi Jay
I think I have not expressed me clear enough, the PC had run for 8 months without problem, then one day it got the issue. So the issue did not occur during the installation process.
It is okay, if there is no answer to it other than format and reinstall, but if there were I believe this is the right place to ask.
And if you don't have the answer it is OK not to answer 😉
09-20-2024 09:19 AM
@AndersSekanina wrote:
Hi Jay
I think I have not expressed me clear enough, the PC had run for 8 months without problem, then one day it got the issue. So the issue did not occur during the installation process.
It is okay, if there is no answer to it other than format and reinstall, but if there were I believe this is the right place to ask.
And if you don't have the answer it is OK not to answer 😉
So, something changed! I can't tell you what happened-- I was not informed.