Toad World® Forums

Instable TDM

Hello TDM community,

I am using TDM 3.6.6.7 under Vista. This version is very instable, almost impossible to work with it. After some minutes of work (random time, random action) the application is not responding anymore. Is this problem only on my system or it is a know problem ?

IKrischer

Hi Ilja,

TDM should work on Vista normally. We did a full set of tests on Vista and found no problem.

TDM uses Microsoft scripting engine that is a standard part of Windows operating systems. Please make sure your access is not restricted (full privileges, no conflicts with antiviral software etc.).

I would recommend to try to temporarily disable antiviral software and try to do what you did earlier.

Regards,

Vaclav

hello Vaclav,

access is not resitrcted, and the problem occurs when trying to open a window, for example when double clicking on an attribute. most of the times it works, but sometimes the window is not opening and the appliction is not answering anymore. before the new version I never had that problem.

ikrischer

Hi,

thank you. I would like to eliminate possible problems with models. Can you close all models and try to create a new one, please? If you feel the problem appears when working on specific model, can you send it to modeling@quest.com, please?

Please have a look at the following article:
http://blogs.inside.quest.com/modeling/2010/10/25/how-to-test-and-repair-your-model/

Regards,

Vaclav

I have the problem on different models, I can start the test but no window appears after I startet the test. nothing happens…

ikrischer

Hi,

please click Tools | Message Explorer to open Log. It should be docked at bottom and warnings and errors should be written there also when a problem appears in a model you try to open. The Log/Message Explorer is relatively important part of TDM and I recommend to keep it docked at bottom (you can use splitter button to collapse it down).

Thanks!

Vaclav

ok, I can see errors, repaired it, start the test again, no errors. hope that was the problem thanks for you help.

ikrischer

Hi Ilja,

Good. Thank you. If you are OK with sending us the model to modeling@quest.com , we may try to find out what was wrong and how to avoid similar situations.

Regards,

Vaclav

I am having EXACTLY the same issue and it is happening on several computers and Operating Systems - XP and Windows 7. We noticed that the problem showed up when we upgraded to the version 3.6 - 3.5 worked just fine.

It is also happening with ANY model - including sample model that came with TDM.

The only way to “clear” the problem is to reboot! After reboot the TDM will work for a while until it will just stop responding usually after double click to open a property window.

Please HELP!!!

Gene.

Hi gfichtenholz_031,

there are two possible reasons of your issue.

  1. Either it may be caused by insufficient user rights and therefore try running TDM on some Admin account or with Admin rights, or

  2. your computers might be running some security software like antivirus, firewall or antispyware, which prevents TDM from accessing neccessary files or directories and thus it causes the hangs and freezes.

Please, let us know if any of above applies or if you have any other hints.

Thank you.

Regards,
Lukas

I am having the same problem with Data Modeler 3.6 on Windows 7-64. Have run as admin and disabled anti-virus with no change in behavior. Frankly, I question whether the program would work at all if either of these were an issue.

Have there been any developments in solving this issue, as it is seriously disrupting my work.

Thanks.

-Wil Gerken

Hi Wil,

I am sorry for the problems with hangs. We have had altogether 4 cases of hangs we are unable to trace so far, but next week we are going to release a special Beta with improved eureka log just for this purpose, just to get any information from TDM, as we haven’t managed to reproduce the issue. Test are always run in full range on all the supported platforms, but no problems were had been noticed before releasing TDM 3.6.
We hope the logs from the Beta next week will tell us some information to be able to go further in solving this issue.

When the Beta is out, I will be back here to ask you for what we will need from you to help us solve this nasty behavior of TDM.

Thank you very much for your patience.

Regards,
Lukas and R&D Team

Appreciate that you’re working on it, Lucas.

Further trials with the program have yielded error dumps from Win7. The first stated that “Control PcGeneral has no parent window”. An example of subsequent errors is as follows:

EurekaLog 6.0.14

Application:

1.1 Start Date : Fri, 3 Jun 2011 15:39:57 -0800
1.2 Name/Description: TDM.exe - (Toad Data Modeler)
1.3 Version Number : 3.6.6.7
1.4 Parameters :
1.5 Compilation Date: Thu, 26 Aug 2010 02:57:40 -0800
1.6 Up Time : 12 minutes, 20 seconds

Exception:

2.1 Date : Fri, 3 Jun 2011 15:52:18 -0800
2.2 Address : 00496362
2.3 Module Name : TDM.exe - (Toad Data Modeler)
2.4 Module Version: 3.6.6.7
2.5 Type : EAccessViolation
2.6 Message : Access violation at address 00496362 in module ‘TDM.exe’. Read of address 3239384A.
2.7 ID : 6252
2.8 Count : 1
2.9 Status : New
2.10 Note :

User:

3.1 ID : wagerken
3.2 Name : Microsoft
3.3 Email :
3.4 Company : Microsoft
3.5 Privileges: SeIncreaseQuotaPrivilege - OFF
SeSecurityPrivilege - OFF
SeTakeOwnershipPrivilege - OFF
SeLoadDriverPrivilege - OFF
SeSystemProfilePrivilege - OFF
SeSystemtimePrivilege - OFF
SeProfileSingleProcessPrivilege - OFF
SeIncreaseBasePriorityPrivilege - OFF
SeCreatePagefilePrivilege - OFF
SeBackupPrivilege - OFF
SeRestorePrivilege - OFF
SeShutdownPrivilege - OFF
SeDebugPrivilege - OFF
SeSystemEnvironmentPrivilege - OFF
SeChangeNotifyPrivilege - ON
SeRemoteShutdownPrivilege - OFF
SeUndockPrivilege - OFF
SeManageVolumePrivilege - OFF
SeImpersonatePrivilege - ON
SeCreateGlobalPrivilege - ON
SeIncreaseWorkingSetPrivilege - OFF
SeTimeZonePrivilege - OFF
SeCreateSymbolicLinkPrivilege - OFF

Active Controls:

4.1 Form Class : Tf_Main.UnicodeClass
4.2 Form Text : Toad Data Modeler [C:\HSS\Projects\AUAS\Schema\AUAS.txp]
4.3 Control Class: TPERDesigner2.UnicodeClass
4.4 Control Text :

Computer:

5.1 Name : HSSANCFMI172652
5.2 Total Memory : 3966 Mb
5.3 Free Memory : 1181 Mb
5.4 Total Disk : 232.83 Gb
5.5 Free Disk : 159.23 Gb
5.6 System Up Time: 6 days, 18 hours, 2 minutes, 42 seconds
5.7 Processor : Intel® Core™2 Duo CPU E8400 @ 3.00GHz
5.8 Display Mode : 1920 x 1200, 32 bit
5.9 Display DPI : 96
5.10 Video Card : RADEON X600 Series (Microsoft Corporation - WDDM) (driver 8.56.1.16 - RAM 256 MB)
5.11 Printer : HP LaserJet 5100 PCL 5 (driver 6.1.7601.17514)

Operating System:

6.1 Type : Microsoft Windows Vista (64 bit)
6.2 Build # : 7601
6.3 Update : Service Pack 1
6.4 Language: English
6.5 Charset : 0

Network:

7.1 IP Address: 146.063.151.159
7.2 Submask : 255.255.255.128
7.3 Gateway : 146.063.151.129
7.4 DNS 1 : 146.063.174.085
7.5 DNS 2 : 146.063.177.031
7.6 DHCP : OFF

Call Stack Information:

|Address |Module |Unit |Class |Procedure/Method |Line |

Running Thread: ID=5692; Priority=-2; Class=; [Main]
004EBC12
004EE834
004EE818
004EE841
004EE83C
004EC1D3
004EC170
0051D4D9
0069E6BB
004EBF44
75970D48
75970D32
0051D13C
75972175
00D6C10E
004E9248
004E90C0
004EC2C7
004EC170
00D69F0A
0109203E
0051D4D9
0069E6BB
004EBF44
75970D32
0051D13C
75970D48
75969A55
006DA008
006BE8D5
004EA62D
004EA5A0
004F05DD
004EA62D
004EA5A0
00D6F7D6
0111A39A
0111A2C8
00F38D57
00F38CB8
007A6154
004E9248
004E90C0
004EC2C7
004EC170
0051D4D9
0069E6BB
004EBF44
75970D32
0051D13C
75970D48
75967BC5
75967BBB
011763C8
0117621C
01178F5E
763633C8
--------------------------------------------------------------------------------------------------------------
Running Thread: ID=6220; Priority=0; Class=TExplorerNotifierThread
--------------------------------------------------------------------------------------------------------------
769D0862
7636199E
76364233
76364220
0072E079
763633C8
--------------------------------------------------------------------------------------------------------------
Calling Thread: ID=5692; Priority=-2; Class=; [Main]
--------------------------------------------------------------------------------------------------------------
0072DF9D
0072DEFC
0072DD45
0072DD0C
0072E106
0072E0D0
0072E175
0072DE15
0072DE00
0072DD05
0072DD00
00F6171D
00F5E947
01139EFF
01139AFC
011762E3
0117621C
01178F5E
763633C8
--------------------------------------------------------------------------------------------------------------
Running Thread: ID=6544; Priority=0; Class=TExplorerNotifierThread
--------------------------------------------------------------------------------------------------------------
769D0862
7636199E
76364233
76364220
0072E079
763633C8
--------------------------------------------------------------------------------------------------------------
Calling Thread: ID=5692; Priority=-2; Class=; [Main]
--------------------------------------------------------------------------------------------------------------
0072DF9D
0072DEFC
0072DD45
0072DD0C
0072E106
0072E0D0
0072E1A1
0072DE15
0072DE00
0072DD05
0072DD00
00F6171D
00F5E947
01139EFF
01139AFC
011762E3
0117621C
01178F5E
763633C8
--------------------------------------------------------------------------------------------------------------
Running Thread: ID=6704; Priority=0; Class=TExplorerNotifierThread
--------------------------------------------------------------------------------------------------------------
769D0862
7636445A
76361450
7636199E
76364233
76364220
0072E079
763633C8
--------------------------------------------------------------------------------------------------------------
Calling Thread: ID=5692; Priority=-2; Class=; [Main]
--------------------------------------------------------------------------------------------------------------
0072DF9D
0072DEFC
0072DD45
0072DD0C
0072E106
0072E0D0
01135C0C
0072DE15
0072DE00
0072DD05
0072DD00
0112D8A5
01134122
0113406C
01139FFF
01139AFC
011762E3
0117621C
01178F5E
763633C8
--------------------------------------------------------------------------------------------------------------
Running Thread: ID=1272; Priority=0; Class=TWorkerThread
--------------------------------------------------------------------------------------------------------------
769D077E
7636118F
76361151
76361143
76361136
763633C8
--------------------------------------------------------------------------------------------------------------
Calling Thread: ID=5692; Priority=-2; Class=; [Main]
--------------------------------------------------------------------------------------------------------------
00FFFFFB
004E7215
004E71E8
004EA76D
004EA748
7637D9E0
75971151
75971160
005313FD
0053135C
01119ECA
01119E6C
0109A979
0109A95C
006E2F8E
006E2F78
00C9062A
00C90614
00CA89A6
0108F9A3
0108F744
00D6B919
0068A57B
0068A94C
0068A890
01090EEF
01090E68
00D6901C
764E3E59
00533430
76361450
00531480
0053135C
01119ECA
01119E6C
01090BEC
01090BB0
00D69A66
0117636A
0117621C
01178F5E
763633C8

Modules Information:

|Handle |Name |Description |Version |Size |Modified |Path |

|00380000|olepro32.dll | |6.1.7601.17514 |90112 |2010-11-20 04:20:50|C:\Windows\system32 |
|00400000|TDM.exe |Toad Data Modeler |3.6.6.7 |19673432|2010-08-26 13:03:30|C:\Program Files (x86)\Quest Software\Toad Data Modeler 3\Bin |
|09970000|Odbccp32.dll |ODBC Installer |6.1.7601.17514 |122880 |2010-11-20 04:20:50|C:\Windows\system32 |
|0F000000|csadetoured.dll |Marks process modified by Detours technology. |2.1.0.207 |4096 |2010-07-02 00:12:52|C:\Windows\system32 |
|10100000|csauser.dll |Cisco Security Agent component |6.0.2.145 |419048 |2010-12-03 02:30:40|C:\Windows\system32 |
|14A60000|hhctrl.ocx |Microsoft® HTML Help Control |6.1.7600.16385 |523776 |2009-07-13 17:14:12|C:\Windows\System32

Hi Wil,

thnax a lot for the log, it’s rather a strange one in fact. But the content is not that important as these are only consequent errors, after the main problem had arrived.
Please, are you able to reproduce the original error with “Control PcGeneral has no parent window”? That is what we have to trace, log. When did it happen? Was it upon opening som model? If so, could you send it? Or was it possibly caused by any other activity? And do you have Vista or Win 7 system? The log says Vista, maybe another bug :slight_smile:

Thank you very much.
Anyway, email the log or the model to modeling@quest.com.

Regards,
Lukas

Hey Lukas,

Basically same problem as others - program hangs upon opening of dialog (like edit entity, etc). doesn’t happen first time, might be related to virus software but nothing consistent there either. Happens eventually on every model, large or small. No other activity interspersed.

Using windows 7 64-bit. And yes, noticed that the error reported indicated Vista. Wonder if Win7 did some kind of context switch?

Will see about getting log from error about missing parent window. Have seen it a number of times, not always same control named.

-Wil

Did anybody tried the New Beta 4 - if this fixes the problem with freezes?

Could you please let me know?

Gene.

Well - I have an answer to my own question :frowning: The BETA 4.0.5.10 froze exactly the same way.

Please advise on what logs/settings I need to turn on to produce the log and help you to diagnose this problem.

Gene.
P.S. The BETA seem to work much faster than version 3.6 though -I like it!

Hi Gene,

the BETA with the enhanced log capabilities hasn’t been released yet, most probably the end of this week or the beginning of the next! So heads up, we believe it will give us some key info to solve the hangs finally.
Glad you like the latest Beta!

I’ll be back when the Beta is out. Thank you for patience.

Regards,
Lukas

Hi folks,

for those experiencing the hangs and freezes, the Beta with the enhanced EurekaLog has been just released!

FOLLOW THE INSTRUCTIONS, PLEASE:

This Beta 4.0.9.2 release should be installed only by those users, who have been experiencing serious hangs or freezes while using Toad Data Modeler.

In Beta 4.0.9.2, options for EurekaLog were added. It should now generate a log file when the application gets non-responding. All other features and functionality are identical with the previous release.

By deafault, this logging option is disabled!

Expert Mode must be enabled in Options, tab General!

In case a user experiences any freezes or hangs during regular work with TDM (not considering an extensive AlterScript or Reverse Engineering), then enable option Freeze Activate in Options, tab Expert Mode.

Below Freeze Activate, find the option to set a timeout after which the exception is raised and the log file is generated.

We strongly recommend not to change the timeout bellow the default 120 seconds as some operations take considerably long time in TDM and it might look as non-responding for our purpose.

When TDM becomes non-responding, exception EFrozenApplication is raised. Please, save it and send to our community forum on http://modeling.inside.quest.com. We will investigate the log files in order to solve the misbehavior as soon as possible.

Regards,
Lukas

EurekaLog settings