LabVIEW
VIPM is terrible
Solved!
@cirrusio wrote:
@billko wrote:
You're forgetting one thing. Not everyone is a veteran. Most often, a prompt to post code is a timely one and expedites a solution.
Not forgetting - just reminding others that sometimes (many times) posting code is not an option. In this instance, I just wanted some insight into what the error meant and code was not really necessary. As it turns out, this answer is probably sufficient - "Error codes generated by VIPM are uninformative at best. Good luck!"
I believe in this case, you're probably correct. I'm not sure how the code would be relevant without downloading the entire computer. 😉
But I have seen that code before - it looks like a standard LabVIEW error wrapped in a VIPM handler. I get that error if, for instance, I deleted a VI on the disk and then try to rename a VI to the name of the file I just deleted.
