Skip to main content
Question

Backup is not working after upgrade to Server 2017.1

clemensb
Contributor
Forum|alt.badge.img+5

Hi,

we upgraded our Server from 2016 to 2017.1

I created a Schedule to create a backup once a week, this job failes. When i open the job there is a notification "no log files exists" so i cannot check why this job failed.

So i tried to make a manual backup. It started the process but it never finishs. It doesn't matter if i choose Backup To Download or to a ressource. After i start the backup there is this notification:

If i want to check the logs in from Backup & Restore i get:

Are there any other logs where i can check whats the problem?

There are no other Problems and the Server works fine.

Thanks for your help!

4 replies

david_r
Celebrity
  • david_rCelebrity
  • November 16, 2017

First thing: Double-check the Server Username and Server Password parameters in the scheduled task.

If that's not it, you should check the FME Server system logs. Look under Resources/Logs in the GUI, in particular the following

  • service/current/rest.log
  • engine/current/fmeprocessmonitorengine.log
  • core/current/fmeserver.log
clemensb
Contributor
Forum|alt.badge.img+5
  • clemensbContributor
  • Author
  • Contributor
  • November 16, 2017
david_r wrote:

First thing: Double-check the Server Username and Server Password parameters in the scheduled task.

If that's not it, you should check the FME Server system logs. Look under Resources/Logs in the GUI, in particular the following

  • service/current/rest.log
  • engine/current/fmeprocessmonitorengine.log
  • core/current/fmeserver.log
Thank you. There was indeed a Typo in the Password (facepalm) would be great if there would be a notification or something, that tells you that.

 

 

But the manual Backup still feezes, but since the automated works its not so tragic.

 

 

 

boubcher
Contributor
Forum|alt.badge.img+11
  • boubcherContributor
  • Contributor
  • January 12, 2018

it's not working for me I did check the credential and all ok

attached is the Job log file

please any idea what may cause this

logfilebackup.txt

clemensb
Contributor
Forum|alt.badge.img+5
  • clemensbContributor
  • Author
  • Contributor
  • January 15, 2018

It seems there is a Problem, @boubcher reminded me. First i thought there was a typo, because afterwards the backup succeeded, but now i get the error again. Most Times the automated Backup doesnt work. I got the same Error in the log and the credentials are ok.

Reply


Helpful Members This Week

Community Stats

31,402
Posts
119,078
Replies
39,019
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

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