Updated to GVM11, now Scans don't start

GVM versions

gsa: Greenbone Security Assistant 9.0
gvm: Greenbone Vulnerability Manager 9.0.0
Manager DB revision 221
Copyright © 2010-2017 Greenbone Networks GmbH
License GPLv2+: GNU GPL version 2 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
openvas-scanner: OSP Server for openvas: 1.0.0
OSP: 1.2
OSPd: 2.0.0

Copyright © 2014, 2015, 2018, 2019 Greenbone Networks GmbH
License GPLv2+: GNU GPL version 2 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
gvm-libs: 11.0.0

Environment

Operating system: Ubuntu 18.04.3
Kernel: Linux 4.15.0-1054-aws #56-Ubuntu SMP Thu Nov 7 16:15:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Installation method / source: mrazafi ppa

Hello, I know that I installed all the GVM Parts from the mrazafi ppa, however i can’t figure this problem out:

When I start a Scan after a few seconds it returns with Status Error.

The gvmd.log File then contains these Lines:

event task:MESSAGE:2019-11-21 13h38.59 CET:30635: Status of task (1dad0592-a2b0-434d-93e5-204bd4e738f8) has changed to Requested
event task:MESSAGE:2019-11-21 13h38.59 CET:30635: Task (1dad0592-a2b0-434d-93e5-204bd4e738f8) has been requested to start by admin
md manage:WARNING:2019-11-21 13h39.12 CET:30638: OSP start_scan e3314edf-3126-4660-b9fb-a90d6f80d9e5: Invalid data
event task:MESSAGE:2019-11-21 13h39.12 CET:30638: Status of task (1dad0592-a2b0-434d-93e5-204bd4e738f8) has changed to Done
event alert:MESSAGE:2019-11-21 13h39.12 CET:30638: The alert Ticket - Systems was triggered (Event: Task status changed to ‘Done’, Condition: Always)
md manage:WARNING:2019-11-21 13h39.12 CET:30638: report_content_for_alert: Could not find report format ‘6c248850-1f62-11e1-b082-406186ea4fc5’ for Email

The Install was already converted from openvas9 sqlite to openvas9 postgres, then updated to gvm10, and now to gvm11.

Can anyone tell me, what is wrong here? Also, if you need any other Infos, just ask, and I will add them.

Looks like the key to your problem is here:

Secondarily, there is also an invalid report format: