Hi @lopes8
Did you specify a new resource folder when you installed the new FME Server 2018?
You'll need to ensure that FME Server has read write permissions to that folder. This is the account that's running FME Server Core and Engine in Windows Services.
When you say they exist - what do you mean? What do you see?
Before you did the restore, were you able to run the sample workspaces?
Hi @lopes8
Did you specify a new resource folder when you installed the new FME Server 2018?
You'll need to ensure that FME Server has read write permissions to that folder. This is the account that's running FME Server Core and Engine in Windows Services.
When you say they exist - what do you mean? What do you see?
Before you did the restore, were you able to run the sample workspaces?
Hi @jlutherthomas
We did not specify a new Resource folder after installing 2018. We restored the back up and that created all of the Resources that were present in 2017. 2017 had all necessary permissions on the folders referenced within the Resource already, is the account running Core and Engine different in 2018 than it was in 2017?
When I say they exist I mean when you navigate to the Resources tab you see all of the Resources that were present in 2017 listed but when I click on them it says "We cant find what you wanted."
We did not run the sample workspace before performing the restore.
Hi @jlutherthomas
We did not specify a new Resource folder after installing 2018. We restored the back up and that created all of the Resources that were present in 2017. 2017 had all necessary permissions on the folders referenced within the Resource already, is the account running Core and Engine different in 2018 than it was in 2017?
When I say they exist I mean when you navigate to the Resources tab you see all of the Resources that were present in 2017 listed but when I click on them it says "We cant find what you wanted."
We did not run the sample workspace before performing the restore.
This would be the accounts that are running the tomcat (application server), engine and core when you look in Windows Services, scroll to FME and see what account they are running as. That account needs RW permissions on your FME Server Share, or swap to a service account if it isn't already
This would be the accounts that are running the tomcat (application server), engine and core when you look in Windows Services, scroll to FME and see what account they are running as. That account needs RW permissions on your FME Server Share, or swap to a service account if it isn't already
@jlutherthomas
Thanks for the help on this. When you say "FME Server Share" are you referencing a local folder on the machine FME Server is installed or the network locations I am trying to connect to as Resources? All the network locations have the appropriate R/W permissions already from when we were running 2017.
@jlutherthomas
Thanks for the help on this. When you say "FME Server Share" are you referencing a local folder on the machine FME Server is installed or the network locations I am trying to connect to as Resources? All the network locations have the appropriate R/W permissions already from when we were running 2017.
You specify this share on install, so ideally you'd put this in a different place to the 2017 one, and start cleanly (You can also just rename the 2017 share folder, so the 2018 resources are in the same place, but it's a different folder to the 2017).
Because the installer will run as the local user, in the beginning it may struggle putting in everything properly.
With your resources folder, either through web ui or file explorer, can you see the log, engine folders etc and see the items inside them for the 2018 install?
