• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved crontabmng failed: Line (1): System.FormatException: Input string was not in a correct format.

Paul Hermans

Basic Pleskian
Anybody having problems with Scheduled Tasks?

After running a Plesk update via Powershell: plesk installer --select-release-latest --upgrade-installed-components

We get these errors on a clean Windows Server 2019 server:

Code:
...
ERROR: Upgrade step Plesk\Upgrade\Action_UpgradeExtensions failed with error:
The execution of post-install.php has failed with the following message:

The execution of post-install.php has failed with the following message:
ERROR: PleskUtilException: crontabmng failed: Line (1):         System.FormatException: Input string was not in a correct format.
   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at psa.scheduler.device.Parser.GetNumber(Int64 low, String[] names)
   at psa.scheduler.device.Parser.GetRange(Int64 low, Int64 high, String[] names)
   at psa.scheduler.device.Parser.Parse_6_5_FileLine()
   at psa.scheduler.device.PSAScheduler.Load_6_5_File(StreamReader sr)

...

(Error code 1) (Agent.php:196) (DeferredCommand.php:32)
Launching component and product checkers...
Downloading file pool/release/PLESK-WIN_18.0.32_4963/reportupdate.exe: 0%
Downloading file pool/release/PLESK-WIN_18.0.32_4963/reportupdate.exe: 100% was finished.

The changes were applied successfully.

PS C:\Users\Administrator>

We got similar errors on another server from the "Backup task notification"

XML:
<?xml version="1.0"?>
<execution-result local-dump-created="true" export-dump-created="false" status="warnings">
  <object type="Server" name="server.hostname.tld">
    <message severity="warning">
      <description>Unable to back up scheduled tasks. Error: crontabmng failed: Line (1):     System.FormatException: Input string was not in a correct format.&#xD;
   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer&amp; number, NumberFormatInfo info, Boolean parseDecimal)&#xD;
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)&#xD;
   at psa.scheduler.device.Parser.GetNumber(Int64 low, String[] names)&#xD;
   at psa.scheduler.device.Parser.GetRange(Int64 low, Int64 high, String[] names)&#xD;
   at psa.scheduler.device.Parser.Parse_6_5_FileLine()&#xD;
   at psa.scheduler.device.PSAScheduler.Load_6_5_File(StreamReader sr)&#xD;

(Error code 1)</description>
    </message>
  </object>
</execution-result>

The same error appears via Plesk > Scheduled Tasks when editing (or simply click Apply) a task from: "server (user: Plesk Panel)"
This counts for all tasks of this user.
 
This error still exists, running crontabmng from the command line returns the same error:

Code:
PS C:\Program Files (x86)\Plesk\admin\bin> .\crontabmng.exe update
Line (1):       System.FormatException: Input string was not in a correct format.
   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at psa.scheduler.device.Parser.GetNumber(Int64 low, String[] names)
   at psa.scheduler.device.Parser.GetRange(Int64 low, Int64 high, String[] names)
   at psa.scheduler.device.Parser.Parse_6_5_FileLine()
   at psa.scheduler.device.PSAScheduler.Load_6_5_File(StreamReader sr)

PS C:\Program Files (x86)\Plesk\admin\bin> plesk ext wp-toolkit --list
crontabmng failed: Line (1):    System.FormatException: Input string was not in a correct format.
   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at psa.scheduler.device.Parser.GetNumber(Int64 low, String[] names)
   at psa.scheduler.device.Parser.GetRange(Int64 low, Int64 high, String[] names)
   at psa.scheduler.device.Parser.Parse_6_5_FileLine()
   at psa.scheduler.device.PSAScheduler.Load_6_5_File(StreamReader sr)

(Error code 1)

exit status 1

I checked all the Scheduled tasks in de Plesk db and compared with other Plesk servers and they seem alright.
 
This error still exists, running crontabmng from the command line returns the same error:
Do you have another Plesk server with the same version that works correctly? Try to compare files C:\Program Files (x86)\Plesk\Schedules\psaadm
The issue is caused usually by the corrupted mentioned file.
I suggest you contact Plesk Support Team to fix it if you haven't another server to replace this corrupted file.
 
Back
Top