This all worked fine till yesterday
It could just be a coincidence that it started failing the day after a leap day.
But perhaps dates, date formats, Unicode vs no Unicode, etc. should be kept in
mind as you search for what’s causing the issue.
Roger S.
Hi Together,
just wanted to give a short Update on this topic as there are some news.
I have been Checking the Date Formats and so on, but with no results.
Then I started testing in the Toad GUI (No command line anymore). I have
successfully generated an INI File from the GUI ( Greg I found the button !!)
but this is also failing. In fact does not seems to depend on the Ini file
itself.
Then I picked up a Simple SQL File, and let it be analysed from Codexpert in the
toad GUI. Worked fine.
Then I have found a small button (like a blue floppy disk) which lets the user
export the results of the codexpert analysis into an HTML file. Pressed it,
getting a popup to select the file destination, and after pressing OK, TADAAA!
Same error as from the Command Line.
So indeed it looks like a problem with the export of codexpert results to
HTML/XML.
Now the Question is, what is Toad calling for the export??
I have also an Eurekalog here, and Stacktrace (but having difficulties to export
this):
EurekaLog 6.0.15
Application:
Hi,
now I also have the ELF File below.
Strange enough, even If I am trying to export to HTML from the GUI, it is still
calling the XML Export.
So Indeed it looks more and more an Issue witht he export.
How to fix that?
EurekaLog 6.0.15
Application:
Hi Together,
just wanted to give a short Update on this topic as there are some news.
I have been Checking the Date Formats and so on, but with no results.
Then I started testing in the Toad GUI (No command line anymore). I have successfully generated an INI File from the GUI ( Greg I found the button !!) but this is also failing. In fact does not seems to depend on the Ini file itself.
Then I picked up a Simple SQL File, and let it be analysed from Codexpert in the toad GUI. Worked fine.
Then I have found a small button (like a blue floppy disk) which lets the user export the results of the codexpert analysis into an HTML file. Pressed it, getting a popup to select the file destination, and after pressing OK, TADAAA!
Same error as from the Command Line.
So indeed it looks like a problem with the export of codexpert results to HTML/XML.
Now the Question is, what is Toad calling for the export??
I have also an Eurekalog here, and Stacktrace (but having difficulties to export this):
EurekaLog 6.0.15
Application:
We’re calling the MSXML api to create both the HTML and XML (the HTML uses XML transforms in that version). It sounds like your computer has been updated to use a version of MSXML that isn’t compatible with that version of Toad. It also may be due to the German installation of Windows you’re using. CodeXpert in v9.7 was not Unicode compatible and often crashed when any Unicode characters were encountered. Since that time CodeXpert (now called Code Analysis) has been totally rewritten and now will work with current operating systems and Unicode environments.
Greg
I had a similar problem with another software product (not-toad) where a Windows
update caused a prior/older version of MSXML to not work – and it broke
the software. In my case I was lucky in that merely going back and re-installing
MSXML 4 and 6 got me back up and working. Have you tried such a thing to see if
the problem is as Greg suspects???
Hi,
I have tried now to reinstall both MSXML4 and MSXML6, by downloading the
versions from Micrososft site.
The 4 was installed, the 6 anyway seems to be skippped as I already have it
installed.
Checking with the Process Monitor anyway seems that toad.exe is just accessing
MSXML6.
Is there a way to tell toad which version of MSXML to use? Or do I need some
special version from MSXML4, or is the latest one from Microsoft ok?
I checked also regarding Unicode, but I have no non-Unicode Charachters either
in the ini files, or in the file paths, so I suppose that should not be the
problem.
regards
manuel
Changing the Server Locale from DE to EN, did the Trick.
Now it seems to work again.
Whatever the reason for that was.
Thanks to everyone for the help.
regards
manuel