We have been using FME server 2017.1 for about one year now. Yesterday I upgraded it to 2018.1. Everything seems to work fine - workspace runs fine, scheduled jobs work fine, Active Directory users login fine et al. However, I can not publish new workspaces from desktop for both 2017.1 and 2018.1 desktop. The message is "Connecting to 'http://phoupgisapw108' (web connection, user 'admin')... Login failed (Connection Error) - Unable to connect to FME Server." I tried with using the previous connection from 2017.1 and also creating new connection in 2018.1, the same error message. I did the upgrade twice last year from 2016 to 2017.0 and from 2017.0 to 2017.1, never got this issue before. Anything about 2018.1 upgrade that is different?
Question
FME desktop unable to connect to FME server after upgraded to 2018.1
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
I've had the exact same issues, but a reboot of the FME Server machine seemed to fix it in my case.
+11- Supporter
I've had the exact same issues, but a reboot of the FME Server machine seemed to fix it in my case.
Please double check the firewall settings, I've experienced that some of the latest installers didn't properly open the necessary ports. You may even want to temporarily disable the server firewall for testing purposes.
Also, have a look at this article:
https://knowledge.safe.com/articles/60776/fme-server-troubleshooting-connecting-to-fme-serve.html
+11- Supporter
I've had the exact same issues, but a reboot of the FME Server machine seemed to fix it in my case.
@david_r For the connection, "authenticate" works fine, "Next" gives the above error.
+2Hi @ag
Would you be able to look in the fmeserver.log file (or upload it here?) - when I've seen this issue before there should be errors present in that log file.
Also try creating new web connections for different users and see if you always get the error with every user, and maybe include the port in the url. If it's the default put the url in as http://phoupgisapw108:80/fmeserver
Sometimes just keep trying makes it end up working.
When you did the upgrade, are you using a new server/machine for it, or did you do the upgrade on the same machine? Are you using different host names between the 2017 install and the 2018?
+11- Supporter
Hi @ag
Would you be able to look in the fmeserver.log file (or upload it here?) - when I've seen this issue before there should be errors present in that log file.
Also try creating new web connections for different users and see if you always get the error with every user, and maybe include the port in the url. If it's the default put the url in as http://phoupgisapw108:80/fmeserver
Sometimes just keep trying makes it end up working.
When you did the upgrade, are you using a new server/machine for it, or did you do the upgrade on the same machine? Are you using different host names between the 2017 install and the 2018?
+11- Supporter
Hi @ag
Would you be able to look in the fmeserver.log file (or upload it here?) - when I've seen this issue before there should be errors present in that log file.
Also try creating new web connections for different users and see if you always get the error with every user, and maybe include the port in the url. If it's the default put the url in as http://phoupgisapw108:80/fmeserver
Sometimes just keep trying makes it end up working.
When you did the upgrade, are you using a new server/machine for it, or did you do the upgrade on the same machine? Are you using different host names between the 2017 install and the 2018?
+2What build of FME desktop and FME Server are you both using? @ag @david_r
Is active directory used in both instances?
Does this happen with multiple users, from different 2018.1 desktops on different machines?
Do you get the same error messages using the web connection inside FME Server transformers, like the JobSubmitter and Notifier, or is it just the publish wizard?
I'll see if I can reproduce this.
+11- Supporter
@jlutherthomas and @david_r,
Ok, found a workaround. If I use the IP address for the FME server, instead of the server name, it works in 2018.1 desktop connecting and publishing to the FME 2018.1 server.
@jlutherthomas and @david_r,
Ok, found a workaround. If I use the IP address for the FME server, instead of the server name, it works in 2018.1 desktop connecting and publishing to the FME 2018.1 server.
+11- Supporter
Sounds like it could be a DNS issue. Can you connect to the web gui using the server name in your browser?
+13- Supporter
I've had the exact same issues, but a reboot of the FME Server machine seemed to fix it in my case.
I am having this same issue. I am upgrading from 2018.1 to 2019, express install, Windows OS.