Can no longer access cRIO 9024 from labview, just says access denied

[CaveJohnson]

Let me give you some background of whats happening and what I have tried. 

I have a cRIO 9024 that we use to control some equipment remotely. It has been working well for the last couple of years. When we use it we just run the vi from the project, and everything is just in scan mode. Recently I have not been able to connect to it through labview consistently. It still shows up in MAX, but when I try to connect to it it just says "access denied, this target is locked by another vi or distributed system manager". I have formatted it several times and re downloaded the software. It will work for a little bit and I can connect and run VI's but then inevitably it will go into this state that I can't connect. I have even tried connecting to it with a blank project and it will do the same thing eventually. 

I have connected to it via the console out (and have attached some of the output in case that might be useful), and have been able to recreate the error I believe via the console. When I type in the command "tw" which is supposed to print pending task detailed info, it will start to print everything but then at a random point it will "reboot due to system error". It even did this after I had formatted and reinstalled software but before I connected/deployed anything from labview, so I think the issue might be outside of labview. Also I even tried another cRIO 9024 chassis and it did the same thing so I don't think its a hardware issue either. Could there be something wrong with the software I'm downloading to it? or the BIOS? I'm at a bit of a loss.

The only thing that changed I believe before we started having these issues is that out IT guy had me change the static IP to another IP address and after it would reboot it would revert back to that previous IP address. Eventually I formatted and re-downloaded software, and this problem has persisted.

Any suggestions would be appreciated, this has just been a really bizarre problem.

[MichaelBalzer]

My best guess would be an IP address collision on the same network as the cRIO. Is it possible to disconnect the cRIO from the network and then try ping its IP address? If something comes back, there's another device with the same IP floating around on there.

I think the IP address can be manually set in ni-rt.ini if setting through MAX isn't working properly, though I can't find any KB article on it. You might also try setting it with the System Configuration API from LabVIEW.

[skol45uk]

What version of LabVIEW are you on?

[skol45uk]

Are you getting any sort of useful status blinks from the CRIO's physical LEDs?

[CaveJohnson]

I am using 2017, also I have not seen any duplicate ip addresses on the network and I've tried several other static IP's with the same result. There are also no blinking led's.

I am currently downloading updated RIO device drivers just to see.

Sorry for the late reply, I was out of town on vacation last week.

[RavensFan]

Your message has a white square with a  broken document image.  Whatever image you are trying to show is not coming through.  I'm guessing that you have it pointing to an image within a private photo album or an image you deleted.

[CaveJohnson]

It was just something that was part of my signature. I've deleted it now.