Server database location differs

Tekla Structures - Not version-specific
Environment
Not environment-specific

Question:
I am getting the following error message when opening a multi-user model, what does it mean and what should I do?

"Tekla Structures - Error
Server database location differs:
Previous location: 'C:/WINDOWS/system32/TeklaStructuresServer/tcpip_srv-app10_1238.db'
Current location: 'C:/Documents and Settings/All Users/Application Data/TeklaStructuresServer/tcpip_localhost_1238.db'
This may cause model corruption.
Please check the server configuration."

Answer:
The "Server database location differs" message means that the server database location written in ".This_is_multiuser_model" file in the model folder is different from the server database location stored in the memory. In this case the location 'C:/WINDOWS/system32/TeklaStructuresServer/tcpip_srv-app10_1238.db' is written in the file, and the location 'C:/Documents and settings/All Users/Application Data/ TeklaStructuresServer/tcpip_localhost_1238.db' is stored in the memory.

This message might be shown, for example, when you have had an old multi-user server (2.3 or previous) and you update the multi-user server software with the following installations, which install the server as a service:

  • Tekla Structures Multiuser Server 2.30s
  • Tekla Structures Multiuser Server 2.301s

The correct way to update the multi-user server software is to make sure that all users have closed multi-user models before doing the installation. If you are sure that this is what is done, you do not have to worry about this message. You just need to close the message with OK and save the multi-user model. Then Tekla Structures writes the new server database name tcpip_localhost_1238.db to the .This_is_multiuser_model file in the model folder. This message is no longer shown when you or other users open this same multi-user model the next time.

If multiuser model was not closed during the installation, there is a risk for errors and model corruption like having two different objects with same ID etc. In this case it is better to find a backup copy of the model and continue with that.
 
Was this helpful?
Submit