Failed to write out model changes. Reason: No connection to service.

Tekla Structures
Not version-specific
Tekla Structures
Sharing operation failed
Service could not be reached
realm or server address could be wrong
No connection to service
Failed to write out model changes
Environment
Not environment-specific

Question:
We have got some cases where customers have a message like "Sharing operation failed. Service could not be reached - realm or server address could be wrong" when opening the shared models

Image
TMS_Service_could_not_be_reached.png


or a error message like "Failed to write out model changes. Reason: No connection to service. Check that you have internet connection."  when using Tekla Model Sharing:

Image
TMS_no_connection_to_service.png


If you check the log file, error might be something like this:
2019-06-12 18:10:50 UTC: [ERROR]
TS Facade: Connect (cloud) returned error:
Connect failed in phase1: OperationFailed (1)
FileNotFoundException: Could not load file or assembly 'System.Net.Http, Version=4.1.1.3, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
   at Trimble.ServiceHub.Client.HttpGateway..ctor(Uri baseAddress, String clientName, String clientVersion)
   at Trimble.ServiceHub.Client.ModelSharingServiceGateway.<ConnectAsync>d__17.MoveNext()
TeklaStructuresFacade 3.12.50.0 failed to connect cloud service using service url https://tmss-eu.teklamodelsharing.com from W111.
Check service documentation for connection requirements.
(ErrorCode: ServiceUnreachable)

 
Answer: 

We found that in some cases this is related to the outdated .NET library since some customers do not receive latest windows updates and all is managed by domain admin. If something like this occurs using Tekla Structures 2019 or later, we suggest to install .NET Framework 4.7.2.

 


Was this helpful?