![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Mysterious Error Messages Topic Summary: Has anyone seen this behaviour before? Created On: 12-May-2006 20:33 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: I found the problem. It appears there was a trigger set in a canned script from the Kitchen scripts ('Triggers'-->'Display default link module in status bar'). Basically, the level of the trigger, as a default, was set to 'all' which translates to 'throughout the database' for those of us who have admin rights, when we only wanted it confined to the current module/user. The result was that when a module is opened and/or an object is selected, the error pops up until all are cleared for the module. It's actually a little more complicated than that, but for the sake of brevity, I'll leave it at that. Through researching the DXL forum and DXL manual, I figured out the issue, ran the 'Edit triggers...' script (from the Kitchen scripts) to find out where they were applied, wrote a quick script and cleared them, and now all is right with the world again. Thanks for the tips! Kim | |
![]() |
|
Don't know if it's due to internal network/system upgrades or ???, but error messages such as 'incorrect context for function call' and 'Module does not have a window' are running rampant throughout the database, yet no one claims to be running any new scripts.
Any ideas? |
|
![]() |
|
![]() |
|
Are there any triggers running on your database?
Has someone written and tested a script on a PC with Autodeclare on and forgotten to declare a variable, when everyone else has it turned off? Regards, Ewen Miller QinetiQ |
|
![]() |
|
![]() |
|
Thanks for the advice, Ewen - we're checking into it. One question came up... could installation of the Kitchen scripts in any way have anything to do with this?
|
|
![]() |
|
![]() |
|
DXL Error messages do not run rampant. DXL is run only when specifically invoked. Thus, there must be some event associated with these error messages.
You'd know if you got the messages after running a specific script, such as from a menu. I therefore strongly suspect you are getting these error messages when you open a module. DXL runs when a module is opened in only (I believe) the following ways: [1] There is some sort of module-open trigger defined [2] the module has a DXL Attribute defined in it [3] the default loaded view has a DXL Layout defined. Lets presume you get these errors when you open some module. [3] Notice the name of the view; change the view, then change it back; did you get the errors again? [2] Run Tools > Refresh DXL Attributes; did you get the errors again? [1] You have no mechanism for searching for Triggers, other than if the previous two tests failed. I don't really recognize the errors you are getting, but my intuition about these things is real good, so here goes: [1] the first looks like a function is being passed to another function as a paramater; yet the sub-function is expecting some variable. You may get this if a function or variable is defined with the same name as some restricted word, such as "length". [2] I cannot think of a case now but I'm sure there are some functions that require a visible module, yet the module in question is being opened invisibly. Linked partners are opened invisibly. There may thus be a trigger or attr dxl defined in a link module associated with this (visible) formal module. Its also possible that somehow your DXL environment was modified; some script running "eval_" or "evalTop_", and redefined how standard routines behave, such as "length". There are other's here who know a lot more about that than I. I don't know anything about the Kitchen scripts, but would be surprised to find that deploying them also sets triggers or changes the DXL environment. Do other clients get these errors? Do other modules trigger these errors? You should be getting a DXL window that at least dumps the line number of the failure, even if it doesn't dump the offending file. - Louie |
|
![]() |
|
![]() |
|
I found the problem. It appears there was a trigger set in a canned script from the Kitchen scripts ('Triggers'-->'Display default link module in status bar'). Basically, the level of the trigger, as a default, was set to 'all' which translates to 'throughout the database' for those of us who have admin rights, when we only wanted it confined to the current module/user. The result was that when a module is opened and/or an object is selected, the error pops up until all are cleared for the module. It's actually a little more complicated than that, but for the sake of brevity, I'll leave it at that.
Through researching the DXL forum and DXL manual, I figured out the issue, ran the 'Edit triggers...' script (from the Kitchen scripts) to find out where they were applied, wrote a quick script and cleared them, and now all is right with the world again. Thanks for the tips! Kim |
|
![]() |
Telelogic DOORS
» Administration
»
Mysterious Error Messages
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.