Troubleshooting Send/receive error messages in Teamwork

by GRAPHISOFT and Greg Kmethy · updated: 11.04.2010

General Troubleshooting Steps when you can not Send / Receive Changes

General troubleshooting steps for any case, when you have a Send/receive problem that others working on the same file don’t:

  1. Always save a PLN first, to avoid data loss.
  2. Send changes (if possible). If you have a problem during Send and receive, try just sending, then just receiving changes, in two separate runs.
  3. Use the “Reload project from Server” command from the Teamwork/Project menu. This will overwrite your “local copy” with a fresh copy from the server. If above does not work, then:
  4. Use the “Leave Teamwork Project” command from the Teamwork/Project menu. This will completely delete your local cached copy of the project.
  5. Re-join project

If none of these help, or you suspect that the issue is somehow related to Libraries, you can use the Teamwork/Project/”Local Data Manager” command to delete the local copies of libraries. They will be automatically downloaded again at the next receive changes.

If none of these help:

  1. get everybody send their changes,
  2. then save out a PLN, and re-share the PLN as a new Teamwork project.

But before you do that, please create a “Support Package” using the Help menu/”Create Support Package” command, and get in touch with your local tech support. Give Graphisoft a chance to fix the problem.

 

Error Messages and their meaning

All of the possible Send/receive errors in Teamwork can be categorized into either of these three types of errors:

  • Send errors – when the client’s local data (aka. “local cache”) can not be sent to the server. This typically affects only the one client who is trying to send the data, and she/he is probably the only one suffering data loss.
  • Receive errors – when the changes from the server can not be merged with the client’s local data. This can be either caused by an unresolvable conflict between the server data and the local data – in which case only one team mate is affected – or might be caused by a server database error, in which case multiple users might be affected
  • Database errors – when the server data itself has corrupt elements, affecting all the team mates. The first symptom of a database error is a receive error.

Send Errors

Send Failed! Invalid elements were found…

  • SendFailed.jpg

What happened?
When you issue a “Send” or “send and receive” command, first ARCHICAD checks your local data (that you are about to send) to make sure no bad data or corrupt information is sent to the server. This proofing algorithm finds invalid elements in your local project data, so to prevent corrupting the server data, ARCHICAD will prevent you from sending changes.

Solution
You will not be able to send your changes, so you will need to reload the project from the server, losing your local project data. To prevent data loss, you can (and should) save your local project data as a PLN file before reloading from server.

  • Click the “Save as…” button and save a solo project (PLN) file
  • Launch a second copy of ARCHICAD, and re-open the Teamwork file
  • Click Teamwork/ Project/ Reload Project from Server command
  • Copy/paste elements from the PLN back to the Teamwork project.
  • Try sending again

Troubleshooting:
Help GRAPHISOFT fix this problem – The best way to do so is creating a SupportPackage from the client machine right after the problem occurred, and sending it to TechSupport .

Unsuccessful Teamwork operation! Server returns error code!

  • ServerReturnError.png

What happened?
When you issue a “Send” or “send and receive” command, first ARCHICAD checks your local data (that you are about to send) to make sure no bad data or corrupt information is sent to the server. The data passes this check but still, the server refuses to accept this. This usually happens when there are somehow modified elements in your local cache that you don’t actually own.
Note: This error message may also occur when the BIM Server can not write the project data to the “Project” folder on the BIM server, possibly because the hard drive space is insufficient.

Solution:
You will not be able to send your changes, so you will need to reload the project from the server, losing your local project data. To prevent data loss, you can (and should) save your local project data as a PLN file before reloading from server. After saving out a PLN, you should “reload project from server” and then manually copy/paste elements from the PLN back to the Teamwork project.

Troubleshooting:
Help GRAPHISOFT fix this problem – The best way to do so is creating a SupportPackage from the client machine right after the problem occurred, and sending it to TechSupport .


Receive Errors

A serious error has occurred during Receive

  • ReceiveErrorAutosave.png ReceiveError.jpg

What happened?
The received changes from the server could not be merged with your local data project. The server data in this case is OK (unless you get other error messages too), and other users probably can send and receive changes without problem. But your local data can not be synchronized anymore with the server, and you will not be able to send (some) of your changes.

Solution:

  • In case you have not sent changes, and not have reserved/released elements since the last autosave has occurred, you can reload the autosaved copy of your local project data. Only data since the last autosave will be lost. Hit “Reload from Autosave”
  • In case you have sent changes, or have reserver/released elements since the last autosave has occurred, you can only reload the project from the server. Any modification since the last Send will be lost. Hit “Reload from Server”

{i} The above error message might be followed by another error message (discussed below), which indicates server database corruption. See respective explanation below.

Troubleshooting:
Help GRAPHISOFT fix this problem – The best way to do so is creating a SupportPackage from the client machine right after the problem occurred. When creating the Support Package, please select the Custom option and include the server data too. Send the Support Package to TechSupport


Database Errors

Unsuccessful Teamwork Operation! Get content failed!

  • GetContentFailed.png

What happened?
The database on the server includes corrupt data. This data was probably sent by the last user who has sent changes to the BIM server. Then, whoever receives changes first will probably get the “Receive Error” first, then, after “Reloading from server”, this error message too. This indicates that it was not actually just a problem with the receive process, but in fact the server database itself is corrupt. More than likely every user trying to receive will get the same error message.

Solution:
The server database has to be scrapped and rebuilt from either of these sources:

  • Rolling back to a backup using BIM Server Manager
  • Whoever has the most recent version of the project on his/her computer should save out a PLN and re-share it.

Troubleshooting:
Help GRAPHISOFT fix this problem – The best way to do so is exporting a .BIMproject file from the BIM Server Manager right after the problem happened, and sending that to TechSupport .

Invalid elements were found in this project!

  • SaveErrorInvalidElements.png

What happened?
Receiving / Reloading from Server / Signing in the Teamwork project worked, but while saving the local (cache) data, ARCHICAD’s proofing algorithms found invalid elements in the project database. This probably reflects that the server database also contains these invalid elements. An invalid element can be anything: Maybe just a Solid Element Operation between two elements, a dimension, a wall, or it could be a whole section or drawing. The affected elements can be listed in a browser by clicking the magnifier icon. ARCHICAD can “fix” the database by deleting such an element. This means that the resulting database will be “healthy”, but will not be in sync with the server database anymore. You can save this as a PLN

Solution:
Select the Save as button to save out a PLN to avoid data loss. After this re-open the teamwork file, and try to send and receive again. If you get the same error, that proves that the server database is corrupted. If so, you can either re-share the PLN, or roll back to the latest backup using the BimServerManager

Troubleshooting:
Help GRAPHISOFT fix this problem – The best way to do so is exporting a .BIMproject file from the BIM Server Manager right after the problem happened, and sending that to TechSupport .

  • Was this Helpful ?
  • 1   ​0

Subtopics

Receive Fails

Issue Receive in Teamwork fails. Cause Receive might fail if Embedded library structure is too complex, or one foldername is too long If either: Windows user (with shorter name) creates a subfolder in the Embedded Library with as many characters as…

Error message: Server returns error code

Issue If you are working in Teamwork using hotlinks, sometimes the following error-message appears: Error occurred during the last Teamwork operation! Server returns error code! Cause One of the causes of this error message can be the following: A…

Related content

Error message: Server returns error code

Issue If you are working in Teamwork using hotlinks, sometimes the following error-message appears: Error occurred during the last Teamwork operation! Server returns error code! Cause One of the causes of this error message can be the following: A…

Creating a Support Package

What is a Support Package? Creating a Support Package may help the Technical Support Team more efficiently investigate a problem you experience with ArchiCAD. The package captures the current state of your (Teamwork or non-Teamwork) project and includes…