Hi - I purchased Toad Data Modeler a little over a year ago and it was working fine on my machine. Within the past week it started giving error messages and doesn't work now. The application opens but when I try to open a model it gives these errors:
If you are still under support, you are entitled to download a newer version of Toad Data Modeler - version 5.0 just released this week in fact!
If not or if you’d rather not upgrade, I would suggest trying to re-install the product. These types of errors are usually related to another component in the system being upgraded and causing a DLL incompatibility. Re-installing the product in many cases fixes this issue.
I will attempt a re-installation. To save the models that I already have (so they can be used once TDM has been re-installed) do any files other than the .txp files need to be saved?
the JScript.dll error message might be caused by an update of your OS. Toad Data Modeler users Microsoft Scripting Engine, a standard part of Windows. In past, update of Internet Explorer caused changes in OS and affected other applications, including Toad Data Modeler. We will certainly do additional tests and try to find solution.
Did you install new version of IE or did you update your OS?
Hi Vaclav - The only thing that I’m aware of is Notepad++ was updated recently (6/3/13) on the machine in question. Automatic Microsoft updates occur from time to time as well - not sure if those affect anything. IE is set to install new versions automatically but I’m not sure the last time a new one installed itself. IE 10 is what is currently on the machine.
Are there any files other than the .txp files that need to be saved in order to use the models I already have once TDM has been re-installed?
Bad news. I uninstalled the original TDM and reinstalled it from the CD. The application will open but when I try to create a new model the following error message appears:
Now what should be done to try and get it to work?
we did tests on multiple machines, on various operating systems with different versions of IE... and found no issues.
Unfortunately, we are not able to reproduce it.
What version of JScript.dll do you use, please? (Try to find the file on your OS, right click the file and see product version on tab Details)
It is indeed different from the one in your screenshot. The other interesting thing I noticed about this file is the Date Modified date and time. It appears to have been updated recently. It must be one of those files that gets updated automatically, since I'm certain that I did not proactively update it.
Are you able to reproduce the problem with this version of the JScript.dll?
What do you recommend doing at this juncture? Still use a different JScript.dll downloaded from the internet?
thanks for the info. Unfortunately, we do not have this version of JScript.dll at our disposal. If you add it to zip archive and either attach it to this thread or send it to modeling@quest.com, we will test it.
You might also try to revert back to previous version of the file. On your screenshot you can see that the last tab allows you to revert back to previous versions, considering at least one Restore Point exists. If not, then you can try to search jscript.dll in Windows folder and use a copy of older version.
Please backup the file before you overwrite it with older version.
Thank you for sending us details. We tested McAfee several times and found no problems, but will do additional tests.
I do not know how to activate the Restore button, it might be locked by OS or some other prouduct, certainly not by Toad Data Modeler. I tried to search some solution via google search, but didn’t find simple solution.
The same thing has started to happen with me. Out of nowhere my IE has decided to update itself to version 10 (probably by some sys admin remote command) and as soon as that happened Toad stopped working, showing me that same access violation message on jscript.dll.
Judging by the date knot22 posted the problem, I think that it was the same Windows Update that has caused this problem for both of us, since the last big one happened this Tuesday. That, of course, assuming that the Windows Update is the responsible for this mess (if I had to bet, I’d say yes)