DXL error help

I open a module and I keep getting this DXL error and I am not able to figure out how to clear it or get rid of it. Any help?

-E- DXL: <Line:1> could not open include file (addins/kitchen/triggers/paranums.dxl) (No such file or directory)
-I- DXL: all done with 1 error and 0 warnings
lkdoyle - Wed Feb 11 12:56:44 EST 2009

Re: DXL error help
Ron_Lewis - Wed Feb 11 13:14:14 EST 2009

You may need to install the kitchen scripts.

Until you can do that creat a folder structure under your doors directory with a path to addins/kitchen/triggers.

Then create a blank file there named paranums.dxl

This quick solution is a poor workaround till you can install the kitchen scripts.

Re: DXL error help
mcnairk - Wed Feb 11 13:30:47 EST 2009

You are probably encountering one of the problems of triggers. They get set up and then the required dxl gets deleted, moved, or renamed. Often the reason for the trigger is forgotten. DOORS does not provide tools to manage them properly. If you don't know what the trigger does and there are no ill effects you could just delete it. You can display and/or delete the trigger using Delete Persistent Triggers.dxl which you can download from http://galactic-solutions.com/GalacticDownloads.htm. Triggers are the devils work and should be banned!

Ken
NAV CANADA

Re: DXL error help
lkdoyle - Wed Feb 11 13:46:18 EST 2009

mcnairk - Wed Feb 11 13:30:47 EST 2009
You are probably encountering one of the problems of triggers. They get set up and then the required dxl gets deleted, moved, or renamed. Often the reason for the trigger is forgotten. DOORS does not provide tools to manage them properly. If you don't know what the trigger does and there are no ill effects you could just delete it. You can display and/or delete the trigger using Delete Persistent Triggers.dxl which you can download from http://galactic-solutions.com/GalacticDownloads.htm. Triggers are the devils work and should be banned!

Ken
NAV CANADA

This was the answer, it worked. THANK YOU SO MUCH!!!!!! I think the trigger got set by accident.

Re: DXL error help
lkdoyle - Wed Feb 11 13:54:20 EST 2009

lkdoyle - Wed Feb 11 13:46:18 EST 2009
This was the answer, it worked. THANK YOU SO MUCH!!!!!! I think the trigger got set by accident.

The delete triggers is the solution.

Re: DXL error help
llandale - Tue Feb 24 15:44:21 EST 2009

Yes in this case its a rouge unwanted trigger, but it can also be AttrDXL, LayoutDXL, or AutoDeclare correctly turned off when the original DXL was incorrectly written with it turned on.

This highlights the serious fault of such embedded DXL using #include statements, as the file may later be deleted or other folks using the module may not have access to that network location; or in this silly case the silly trigger is pointing to the local client, pretty much guaranteeing all other users get the error.

Louie

Re: DXL error help
twm - Thu Nov 01 17:12:19 EDT 2012

llandale - Tue Feb 24 15:44:21 EST 2009
Yes in this case its a rouge unwanted trigger, but it can also be AttrDXL, LayoutDXL, or AutoDeclare correctly turned off when the original DXL was incorrectly written with it turned on.

This highlights the serious fault of such embedded DXL using #include statements, as the file may later be deleted or other folks using the module may not have access to that network location; or in this silly case the silly trigger is pointing to the local client, pretty much guaranteeing all other users get the error.

Louie

here's my problem. I created a trigger and just after execution my system crashed and I can't recall the name I used to initiate the trigger. Now I can't delete it. Additionally the recommend dxl script for identifying and deleting a trigger does not find the trigger, so I can't delete it. Is there another way?

Re: DXL error help
llandale - Fri Nov 02 16:55:13 EDT 2012

twm - Thu Nov 01 17:12:19 EDT 2012
here's my problem. I created a trigger and just after execution my system crashed and I can't recall the name I used to initiate the trigger. Now I can't delete it. Additionally the recommend dxl script for identifying and deleting a trigger does not find the trigger, so I can't delete it. Is there another way?

Well, here is a start:


Triggg trg 

for trg in database 

do 
{  

if (confirm(
"delete database trigger: [" name(trg) 
"]")) delete(trg) 
} 

if (!

null current Project) 
{  

for trg in (current Project) 

do 
{  

if (confirm(
"delete prjoect " name(current Project) 
" trigger: [" name(trg) 
"]\")) delete(trg) 
} 
} 

if (!

null current Module) 
{  

for trg in (current Module) 

do 
{  

if (confirm(
"delete Mod " fullName(current Module) 
" trigger: [" name(trg) 
"]")) delete(trg) 
} 
}

There may be a nested project problem with this.

-Louie