Input string not in correct format error

[steve.robinson]

This worked for me—thanks.

[jgengler]

Thank you all.
With an assist from @dkienenberger, my machine is working now.

[BrandonParizo]

@StanislavLobodzinski

There seems to be an issue when applying this workarond to 5.1.7. With a working TDP instance, when applying this fix, it appears TDP can no longer find any valid licenses and says that my license has expired. Please see attached picutre. What is your suggestion to get around this?

[StanislavLobodzinski]

@BrandonParizo
This is odd, Toad.exe.config shouldn't have any effect on licenses. Does removing code from workaround make your Toad running again?
Anyway could you please create support ticket here: https://support.quest.com/contact-support and send license information, so we can take a closer look?

Thank you,
Stanislav

[BrandonParizo]

@StanislavLobodzinski Yes, removing code the code that is implemented from the workaround lets TDP run without issue; and the Licenses are back where they need to be.

I will submit a ticket.

[b_rad]

I just started getting this error and cannot open up my old toad query builder files. I am not sure I follow all the responses below. Is this a TOAD problem caused by a Windows patch? What is the solution? Toad patch, or Windows patch?

Brad

[b_rad]

What was the work around?

[Filip.Cevela]

Hi,

currently you have two options. Uninstall latest patch form the MS or follow this workaround described below. Or you need to wait for the next release TDP 5.2.1.

This was cause by the security update of the .NET components with the latest Microsoft update ( 4565633 or KB4565627 based on you Windows version).

@StanislavLobodzinski

we found source of this issue. Workaround untill we release version with fix is to add code below into Toad.exe.config in Program Files directory. It must be placed at the beginning of file, right after configuration tag (line 3).

  <configSections>
    <sectionGroup name="system.data.dataset.serialization" type="System.Data.SerializationSettingsSectionGroup, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
      <section name="allowedTypes" type="System.Data.AllowedTypesSectionHandler, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
    </sectionGroup>
  </configSections>
  
  <system.data.dataset.serialization>
    <allowedTypes>
      <add type="Quest.Toad.QueryBuilder.WhereClauseClass, ToadCore" />
    </allowedTypes>
  </system.data.dataset.serialization>

[b_rad]

Thanks, I will have this along to our support tech.
Brad Bain
Bank of America

[jeanaf]

Hi there,
Does this also apply to patch KB4566516? I'm using 5.0.6.97. Per our patch team "applied on 7/21/2020, 2020-07 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows 10 Version 1809 for x64 (KB4566516)" and I'm getting the same error messagees as well as other end users have reported this issue.
Thank you,Jeana

[StanislavLobodzinski]

Hi Jeana,
yes, this also apply to KB4566516.

[jeanaf]

@Filip.Cevela

KB4565627

@StanislavLobodzinski, Thank you!

[olivier.broliquet]

It worked for me running Toad for data anslysts 3.1.0.638. Thank you very much

[jhughes]

I get the same error. I get automatic updates, so this is a major pain. Is there a workaround beside backing out Windows updates?

[dan]

Have you upgraded to TDP 5.2.1 and you still get the error?

[toddod]

I spend a lot of time building a query against an oracle database. Worked great until I closed toad. Now when I open the .tsm file I get the above message. How can I fix this?
I have other .tsm files that I can open that do not give me this message.

[dan]

Hi,
and have you tried to fix the query builder in Toad? Has anything changed in the connection after you've saved the TSM file?

[dkienenberger]

Hi Dan,

I just installed 5.3.333 (32 bit), and I'm seeing this issue again. I tried to patch it with the same code that was given for 4x and ran into the problem with toad 5x not saving any configurations after that. I'd include the 5x Toad.exe.config but the forum won't allow me to attach .config files.

[Julie_Hyman]

Hi - Dan is no longer with Quest, but I can follow up on this issue. Have you opened a support case for this? I think that is our best approach here since I believe Eng will need to get involved. Let me know!

[rsjames]

Is the work around noted here still valid?