Hi Johannes Purer ,

We are aware of this issue, unfortunately it can't be reproduced on all machines.

We'd need more details, please can you confirm the following:

1. What steps do you take until you get the error?

2. Does the error occur with all files or specific project? 

3. What is your Windows regional settings and region format? 

Would you mind sharing your files so we can test?

Thank you,

Oana

Hi,

I do have further input to this issue.

After I have repaired Studio, re-installed Post-Edit-Compare, I was able to run one report successfully. With the second report, I had the same issue then again.

I have tried to run Post Edit Compare on another computer, where PEC was not installed before. Windows 10 and Studio 2021. And there I do get the same error at the first try. "Die Eingabezeichenfolge hat das falsche Format" (The input string has the wrong format).

I ran the report with different files, again the same result.

The error does not appear right away, it seems that the comparison itself runs successfully through all files, only in the step where the report is created, it crashes.

So the following questions come up for me:

Do only I have these issues with this app?

Why does it run sometimes, and then this error comes and it does not work anymore?

Why does that apply to different files?

It must be some kind of error in the computer or Studio settings, which causes these results.

Any help on this would be appreciated, I have to deliver a Post-Editing-Distance report to the client, but can't.

Thanks,

Johannes

Hi,

I do have further input to this issue.

After I have repaired Studio, re-installed Post-Edit-Compare, I was able to run one report successfully. With the second report, I had the same issue then again.

I have tried to run Post Edit Compare on another computer, where PEC was not installed before. Windows 10 and Studio 2021. And there I do get the same error at the first try. "Die Eingabezeichenfolge hat das falsche Format" (The input string has the wrong format).

I ran the report with different files, again the same result.

The error does not appear right away, it seems that the comparison itself runs successfully through all files, only in the step where the report is created, it crashes.

So the following questions come up for me:

Do only I have these issues with this app?

Why does it run sometimes, and then this error comes and it does not work anymore?

Why does that apply to different files?

It must be some kind of error in the computer or Studio settings, which causes these results.

Any help on this would be appreciated, I have to deliver a Post-Editing-Distance report to the client, but can't.

Thanks,

Johannes

Hi Johannes Purer ,

Thank you for those details. We managed to reproduce the error and we have it under Development (internal reference SDLCOM-5950), so soon we should have a fix in place.

Until then, we also found a workaround, and that is switching your Windows to English as regional settings and region format.

We also try to address the TERp issue regarding Java path.

Regards,

Oana

Hi Oana,

many thanks for your reply and taking care of this issue. So this is an issue with the German Windows operating system.

I will switch to the English version on my second computer, hope that works.

Regards,

Johannes

Quick update, switching the settings in Windows works, I could produce the reports.

Many thanks,

Johannes

HI Johannes Purer ,

I've sent you a PM with hopefully a fix for the issue.

Please let me know if that solves the "Input was not in a correct string" error

Thank you,

Oana

Oana Nagy 

Hi Oana,

sorry for the late reply.

Thanks a lot for the fix, I had now time to do a quick check. The fix seems to work, the report is now also generated on my German Windows OS.

There is only one issue, when starting Plunet, I now get this message (non-signed plug in found). Can I avoid that?

Thanks,

Johannes