Teamwork error on send Archicad 20

[Anonymous]

We have been getting an error come up on Archicad 20 where it won't allow us to send. It isn't like a normal error where clearing the client cache will fix the issue. It seems to be a bim server issue as it will happen simultaneously across multiple machines both within the network and over ip.
We have tried restarting the bimserver in an effort to fix this without success and the only solution is to re-share the project which results in a loss of work. Despite the wording of the error there is no issue with connectivity or licenses. It appears to me that the server file is being corrupted somehow and not allowing the clients to connect.

Is anyone else having this issue?

[Anonymous]

Marton wrote:
Thanks, we received the package, will keep you posted with our findings or if further information is needed.

Support case #: 58189

Marton

Please do keep us all posted. Don't let this issue slip into a private conversation.

This was a crippling error before AC18, got better in AC19 (thank you) and, I hope, will be gone in AC20.

Thank you for joining in on the conversation.

[Anonymous]

Hi All

Looks like it was something to do with the IFC import. GraphiSOFT have a fix for it soon. Deleting the offending IFC object seems to have cured it for us.

[Anonymous]

Steve wrote:
Hi All

Looks like it was something to do with the IFC import. GraphiSOFT have a fix for it soon. Deleting the offending IFC object seems to have cured it for us.

No it does not.

IFC issues are unrelated to this error. The error happens on simple Teamwork projects with no imported IFC or even modules.

As describes in the posts above it has to do with BIMServer's reaction to connection instability issues and consequent project database desynchronization.

[Anonymous]

Anton wrote:

IFC issues are unrelated to this error. The error happens on simple Teamwork projects with no imported IFC or even modules.

As describes in the posts above it has to do with BIMServer's reaction to connection instability issues and consequent project database desynchronization.

Hi Anton

For us it appears it was an error in an IFC type that wasn't allowing synchronization. Once the object was removed on the advice of Graphisoft we went from having the error 4 to 5 times a day to not having an error at all in the past 4 days.

There may be another issue in regards to network stability but in our case this wasn't the problem

Appreciate your input though.

[Anonymous]

Steve wrote:
For us it appears it was an error in an IFC type that wasn't allowing synchronization.

Thank you for coming back with the information, Steve. I hope this issue will be reviewed further by GS, as they solved your problem, but these errors happen on simpler projects with no dependancies at all... I hope it will not stop with your case and will be finally put to rest soon for good.