• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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