topic Re: TW Operation errors in Teamwork & BIMcloud

TW Operation errors

Lucian Laculeanu — Mon, 08 Apr 2024 21:18:30 GMT

Since I have installed AC27 5003 update, precisely a week ago, a second file became unresponsive on TW operations to BIMcloud.

I am online, I can reserve items in the project, but once I try to release and/or Send/Receive - I get the wonderful announcement below (see image)

I prefer to not be forced to delete projects from the server, save new PLNs, reshare, rejoin and also have others do this because of a software error.

Please investigate and fix if needed. i will do so more at my end.

Also, please do not try to come up with questions like "does your mouse have a fresh battery" and "did you plug in your computer" because I haven't been doing this since this morning...

Re: TW Operation errors

scottjm — Mon, 08 Apr 2024 21:37:04 GMT

The last time I had a similar problem with repeated TW errors it was due to a corrupted element in the file. A railing if I recall.
I had to send a TW support package to my local support and they were able to identify the corrupted element.
Saving as a PLN and doing an open and repair and then resharing has sometimes helped, but not always.
Is it happening for multiple tw files or just the one?

Re: TW Operation errors

Lucian Laculeanu — Mon, 08 Apr 2024 22:30:33 GMT

This is the second one.

First one does not even have a 3D element in it...

This one has only morphs and 3D documents...

Re: TW Operation errors

scottjm — Tue, 09 Apr 2024 03:37:43 GMT

Eessh. In that case it sounds more like the hotfix has possibly corrupted something. I would probably try a complete clean install of 27 include making sure you clean up the user preferences and TWData cache.
Is it happening to other users who’ve also updated to 5003?

Re: TW Operation errors

Lucian Laculeanu — Fri, 12 Apr 2024 15:01:38 GMT

I've concentrated on all user-available methods and disregarded Admin methods.

I don't know if there was a combination of other things I have tried previously, but I was able to regain control by reserving all elements in the project and do an S&R then release.

I am still curious however, why this may happen...

EDIT: One thing that was observed is the tendency for this error to appear when you switch computers, accessing the same project using the same license...