Skip to main content
  • EN

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?

I've had the exact same issues, but a reboot of the FME Server machine seemed to fix it in my case.

I've had the exact same issues, but a reboot of the FME Server machine seemed to fix it in my case.

@david_r, I did twice reboot both server and the publishing PC, no luck.

 

 

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

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.

 

@david_r For the connection, "authenticate" works fine, "Next" gives the above error.

 

Yeah, that's exactly the same thing I had...

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?

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?
@jlutherthomas, I tried http://phoupgisapw108:80/fmeserver and http://phoupgisapw108:80, none of them works. I don't see any errors in fmeserver.log file. Here is the interesting part - I rebooted the server machine, then launched FME desktop 2017.1 on my PC, open an 2017.1 workbench (the same one as in 2018.1, but a backup). I have no problem connecting and publishing to the server, using either the old 2017.1 connection or the new 2018.1 connection. But I still get the same error when connecting and publishing from 2018.1 desktop.

 

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?
@jlutherthomas, I need to open a support ticket for this. We only have one FME server machine and it is a production server, and we can't wait too long.

 

What 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.

 

@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.

Sounds like it could be a DNS issue. Can you connect to the web gui using the server name in your browser?
Sounds like it could be a DNS issue. Can you connect to the web gui using the server name in your browser?
Yes, I used the server name i web UI, and connections, and never used IP until now.

 

 

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.

Reply


Community Stats

30,159
Posts
114,480
Replies
37,806
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.