Random check-out - Inventor 2024

[NigelHay]

Every now & then I get the error message below when working in parts, assemblies or drawings. So far, when I OK the message, I can carry on with whatever I was doing without trouble. My suspicion is that this is caused by a momentary interruption to the server connection, does that sound feasible? All Inventor files are on the server, we do not use Vault.

Inv.2024, Win10 Pro 64bit, all updates automatic.

@NigelHay The posts title was edited to add the Product & Version #.  CGBenner

[CGBenner]

@NigelHay 

Hi, do you have trouble trying to work with the individual file being called out in the warning?  Are they in your Project paths?

[NigelHay]

Chris, no problems generally working with the files. We use the same project path for everything & all files are in the same top level folder on our local server.

[johnsonshiue]

Hi Nigel,

I would try a few things. Make sure all the critical Windows updates, the latest graphics driver, and all the critical PC vendor updates are installed. Use Windows Disk Cleanup to remove all the cached files. When it happens, go to File -> Manage -> Refresh. Does it work better now?

Many thanks!

[NigelHay]

Johnson,

Windows updates are automatic. I use Autodesk access & install updates as soon as they appear. I can clean up the disc but, as this is a random error, it might be a while before I can say if it is better.

[RajSchmidt]

Are these parts by any chance old ones? Created in the context of a legacy project? I am talking about these “Shared workspaces” we hat 15 years ago. There it was possible to “check out” a file which set a flag in the file.

[NigelHay]

Raj, No, this can happen whilst I am creating new parts, assemblies or drawings.

[RajSchmidt]

In that case your suspicion concerning the network might be correct. Do you have the option to work locally for a time?

[NigelHay]

Raj, Not in any serious way. All of our models are located on the server, even down to screws & washers.

[RajSchmidt]

That’s bad. Any other way you can pinpoint the problem? Can you relate the moment the error occurs to any known hiccups in the network? Maybe your IT guys can help you set up some network monitoring?

BTW, I believe that is one of the reasons why modern PDM systems work with a check out mechanism – keeping the actual work files locally. I remember the times of old Compass/Productstream. That used to work directly on network drives and we had problems quite often.

[NigelHay]

Raj, We don't routinely monitor the network. I know that, as we have grown from 1 factory unit to 4 units, the network has been added to with hubs & connections all over the place. It could probably do with being ripped out & replaced but that's not going to happen any time soon.

[RajSchmidt]

Looks like you are out of luck then. I meant to have the monitoring only for a while, for you to locate the problem.

Although, your suggestion of ripping out and renewing the network sound good, too 😉

Honestly, have you thought about using Vault? You could start in a small way with Vault Basic.

[NigelHay]

Raj, We don't use Vault. There are only 3 seats of Inventor here & I can see some advantage with Vault but 1 of the users is a great person & a good engineer but an absolute nightmare when it comes to keeping files in a logical order. I can see Vault being another place where it could all go wrong.

[RajSchmidt]

Well, that’s bad. Leaves only the option I mentioned earlier, about monitoring the network. Sorry about that.

[CGBenner]

@NigelHay 

Hello, do you still need help with this question?

[NigelHay]

Hard to say. I've followed Johnson's suggestions & the issue has not returned so far. If it has not come back in a week or two, I would be prepared to say it is fixed. Always tricky with a randomly occurring event.

[NigelHay]

So, this problem reoccurred yesterday, obviously it is not fixed despite following all of the advice so far.