Skip to main content
Question

Backup is not working after upgrade to Server 2017.1

  • November 16, 2017
  • 4 replies
  • 23 views
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!

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.

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

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.

Community Stats

32,207
Posts
122,305
Replies
39,891
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.