Error occured during the last teamwork operation

[jamesMorris]

We already spent a lot of time in previous threads.

Anyway, since we did not encounter this issue for almost a year, I am ready for a fresh start. 

No bad feelings from my end. Let's see if we can solve this issue. 

The issue occurred again today in our BIMcloud/Teamwork environment. I have opened a support case so that the underlying cause can be investigated.

[jamesMorris]

I noticed additional behaviour:

I also told them that I have very big news, since I noticed something new!

User M. gets the error. 

But the changes from user M. were transferred to bimserver. User G. can see them! This is astonishing!

The second thing that I found very interesting: you won't see that on the bimserver! You only see that user M received, but not that he (successfully) sent changes. 

[jamesMorris]

09. october 15:10 

IDC mailed me that I should check free space and contact my admin. 

I wrote back 09. oct 15:39:

The server has free disk space available.
The issue does not affect just one user. At present, it only affects one project. However, as mentioned previously, several users are affected, each working on completely different computers and laptops.
I can rule out a network issue, as both users are connected via LAN cable.

[jamesMorris]

deleted

[Patrick M]

I have found that the warning is sometimes benign, sometimes catastrophic. I also have found that even when a user gets this warning, and the bimcloud reports that changes were sent, when they reload, they will not see some/all/most of their work done since the previous successful change. So you can't necessarily trust the activity log in the bimcloud. It recognizes a data cache was sent to the cloud, but does not confirm that it was received by the cloud data cache.

[Patrick M]

this warning is pretty nearly the reason I dread starting my day every morning. Its always uncertain if this will pop up at all, or if I'll get 30+ people notifying me they got this (or similar) warnings.

[Tamas Gaspar]

Hi @jamesMorris,

Thank you for starting this as a separate topic. We followed up with the relevant support team regarding this case. Saving the affected project as a PLN file and re-sharing it as a Teamwork project resolved the immediate issue and enabled the team to continue working.

Because the project was restored before the original condition could be fully examined, the root cause could not be confirmed in this instance. If the issue occurs again, please contact your support channel as soon as possible and, where feasible, collect the relevant diagnostic information before recovery steps are taken. This gives the support team the best opportunity to investigate the underlying cause, and we will do our best to support the investigation.

Kind regards,

Tamas

[jamesMorris]

Ok, next time that happens, what should I do?

Please describe it in concrete steps. One by one.

Because it isn't fully true what you wrote above. It wasn't that we resaved is a PLN because we wanted to continue work. This was actually a case where we would have had the chance to investigate it, since there is no time pressure (that is pretty rare). 

No the reason that we saved is as PLN, is that because IDC did not respond to my e-mail from 09. october 15:39. Still hasn't to this day btw.

I find it pretty odd, that you first delete some of my post, and than also delete your own in from @Gordana Radonic. 

Please don't just delete stuff. This forum does not even show it, so for an outsider it is very hard to follow this thread if you do. This is a severe limitation if this forum software, so we have to adapt to it IMHO. 

So again, next time I contact IDC, what will differ? May I remind you, that we play that game now for almost tree years. Did you talk to them? Opened up a way for internal communication?