Further information and the link for the new software update ( SIEMENS Update Server with the TIA Administrator, TIA Updater or Corporate Server Configuration Tool ) is available at: https://support.industry.siemens.com/cs/ww/en/view/109749564 

Astonishingly, it needs authorized login before download . This may delay further updates.

Bonjour,

Si malgrès l'installation de la version la plus récente de TIA Administrator, la connection au serveur ne fonctionne pas, voici la solution que j'ai trouvé, en espérant que ça puisse aider:

Clic droit sur le raccourci "TIA Administrator" qui se trouve sur le bureau puis propriétés.

Clic sur "Emplacement du fichier" pour voir la cible.

Dans mon cas, il y avait 2 fichiers qui se ressemblait.

Remplacer la cible TiaAdmin_SYSTEM.html par TiaAdmin_Système.html

Ca fonctionne depuis sans problème.

mopS04

hi together,

as per march 2020 the Siemens-Server doesn´t support TLSv1.0 und TLSv1.1 anymore. This is why out-of-date versions of the TIA Administrator, the TIA Updater or the Corporate Server Configuration Tool can no longer access the server. 

Remedy
In this case you download the next version of the TIA Administrator and install it. The new version should then connect again with the SIEMENS Update Server. Using the newly installed TIA Administrator you can now update your TIA Portal versions. This then also updates the TIA Updater and the Corporate Server Configuration Tool.

Also  see this FAQ:

Why can you not establish a connection to the SIEMENS Update Server with the TIA Administrator, TIA Updater or Corporate Server Configuration Tool?

hope this helps,

regards,

Hi AutoGen_659912,

thanks for sharing your solution 

Please try to write your post in English language. This is an international community and we try to focus on one language. Posting in English will help all users to understand your post.

This is the translation of your solution:

Ok, thanks.

So "Replace the target TiaAdmin_SYSTEM.html by TiaAdmin_Système.html"

I think it's a bug of program installer, in french language. 

Best regards

Romarik

Jen_Moderator

Hi AutoGen_659912,

thanks for sharing your solution 

Please try to write your post in English language. This is an international community and we try to focus on one language. Posting in English will help all users to understand your post.

Best regards,
Jen_Moderator

Actually this is a bug with the system language I guess, because here even that TIA was installed in English language the other shortcut in my folder was named "_SISTEMA" which is portuguese for System, after using this shortcut I was able to acess TIA ADMINISTRATOR.

My frustration levels with TIA Portal Updater and that wretched ‘Cannot connect to the server’ message have been running very high. It falls to me to update all of our copies of TIA Portal to V16 and I had a situation when I had two PCs that would connect to the server and three that would not, at any price. Let’s be clear, the update to TIA Administrator and Automation Licence Manager were not the issue.

On the first one that I tried to run the updater, our anti-virus helpfully reported that it was blocking access to the website, and even gave the url that it was blocking. Our IT provision quickly resolved that, but it didn’t resolve the failure to connect to the server. I spoke to Siemens Technical Support and the material bit of their reply said this:

‘If your network/PC is IT managed, this means it is likely to be IT restrictions causing this issue.

The easiest thing to do is connect via another internet connection that has no VPN or connection to your corporate network to see if it works.’

The first flaw in that is that I had been trying to do some of the updates from home, outside the corporate network. But in any case, I passed that comment on to our IT provision, and set up two PCs for them to remote connect to, one which connected and one that did not. My idea was that they could look at the firewall setup and see if they could see the difference. What he actually did was temporarily disabled the firewall – both ours and Windows – and the anti-virus all together and still Updater would not connect to the server.

Then I got a brand-new laptop that I was to setup for one of our agents. It would need all versions of TIA Portal from V13 to V16. I installed V13 first – the install disk I had was SP1, but I could not find anywhere that I could access disks for SP2. (There are many explanations lying behind all of this that I must resist offering because they are not the point.) Updater refused to connect to the server even after updating Administrator and Licence Manager. By now I was expecting that. So then I installed V14, and it happened to be – and this is centrally important – V14 Sp1 Update 10 that I had an install disk for. Hey presto Updater connected to the server and immediately offered me V13 SP2 Update 4. So I went back to the first PC that had refused to connect – it had vanilla flavoured V14. So I upgraded it to V14 Sp1 Update 10 and hey presto, Updater connected to the server. So then I went to the second PC that would not connect and it was running V14 Sp1 update 7. So I upgraded that to update 10 and it connected too. The final PC that would not connect is currently out on the road with service engineers, so I have not had the chance to sort it out yet.

In any case, I obviously cannot say that it will apply for everyone, but if you are struggling to get Updater to connect to the server even having run the updates to Administrator and Licence Manager, I suggest checking out what version of V14 you are running. If it is less than Sp1 Update 10 then consider upgrading to that version. You can download the update files for that manually from the website.

I can only assume – and I accept that this is pure speculation – that V14 Sp1 Update 10 includes a change to TIA Updater that the update to TIA Administrator and Licence Manager linked to further up this thread does not.

Unless, of course, you know any different…

KenNatton

..
So I upgraded it to V14 Sp1 Update 10 and hey presto, Updater connected to the server. 
..

@KenNatton:
Thank you very much for sharing your experience.
This can be extremely helpful.