Re: [WebDNA] Triggers.db wiped completely blank

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 107869
interpreted = N
texte = I had a situation a couple weeks ago where I corrected non-working triggers. It was on a Win2003 / IIS6 server. It had been recently upgraded to WebDNA6.2, but there were signs that the triggers hadn't been firing long before the upgrade. Anyway, I first tried to delete a trigger and realized it wouldn't delete... so upon looking at the the triggers.db file, it was showing incorrect returns (vertical tabs) and one of the triggers had no unique ID value. I manually added the correct returns, deleted the record without an ID, saved, and flushed databases... tried it and still no go... noticed that the "next execute" time was in the past.. so deleted all the triggers using the admin pages, flushed databases, repopulated the triggers, restarted the server, and all works fine now. Anyway, I'm not sure what fixed it there and why it was corrupted in the first place, but I think the gist is that the triggers.db was corrupted, which caused the last record to be entered with unknown results (in this case, no ID, but these kinds of bugs could indeed null data, partially or entirely). Perhaps the server lived on a *nix platform at one time, or perhaps the transfer of the files wrote the file with the wrong returns.. who knows. Note, triggers are not usually touched when upgrading the server unless specified, so this issue was mostly likely there long before the upgrade to WebDNA 6.2. Donovan -- Donovan Brooke Euca Design Center www.euca.us www.keepitturning.co Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Triggers.db wiped completely blank (christophe.billiottet@webdna.us 2011)
  2. Re: [WebDNA] Triggers.db wiped completely blank (Donovan Brooke 2011)
  3. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  4. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  5. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  6. Re: [WebDNA] Triggers.db wiped completely blank (christophe.billiottet@webdna.us 2011)
  7. Re: [WebDNA] Triggers.db wiped completely blank (Govinda 2011)
  8. Re: [WebDNA] Triggers.db wiped completely blank (Daniel Meola 2011)
  9. Re: [WebDNA] Triggers.db wiped completely blank (chris@usinter.net 2011)
  10. Re: [WebDNA] Triggers.db wiped completely blank (Govinda 2011)
  11. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  12. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  13. Re: [WebDNA] Triggers.db wiped completely blank (christophe.billiottet@webdna.us 2011)
  14. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  15. Re: [WebDNA] Triggers.db wiped completely blank (Donovan Brooke 2011)
  16. Re: [WebDNA] Triggers.db wiped completely blank (christophe.billiottet@webdna.us 2011)
  17. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  18. Re: [WebDNA] Triggers.db wiped completely blank (Govinda 2011)
  19. [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
I had a situation a couple weeks ago where I corrected non-working triggers. It was on a Win2003 / IIS6 server. It had been recently upgraded to WebDNA6.2, but there were signs that the triggers hadn't been firing long before the upgrade. Anyway, I first tried to delete a trigger and realized it wouldn't delete... so upon looking at the the triggers.db file, it was showing incorrect returns (vertical tabs) and one of the triggers had no unique ID value. I manually added the correct returns, deleted the record without an ID, saved, and flushed databases... tried it and still no go... noticed that the "next execute" time was in the past.. so deleted all the triggers using the admin pages, flushed databases, repopulated the triggers, restarted the server, and all works fine now. Anyway, I'm not sure what fixed it there and why it was corrupted in the first place, but I think the gist is that the triggers.db was corrupted, which caused the last record to be entered with unknown results (in this case, no ID, but these kinds of bugs could indeed null data, partially or entirely). Perhaps the server lived on a *nix platform at one time, or perhaps the transfer of the files wrote the file with the wrong returns.. who knows. Note, triggers are not usually touched when upgrading the server unless specified, so this issue was mostly likely there long before the upgrade to WebDNA 6.2. Donovan -- Donovan Brooke Euca Design Center www.euca.us www.keepitturning.co Donovan Brooke

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Graphing Modules (2004) [format 40s]text[/format] doesn't work (1997) WebCat2 - Getting to the browser's username/password data (1997) TeaRoom Order fields email account remain empty even thoughthewy are filled. (1997) [ot] ascii values for lf and cr (2001) RE: Credit card processing - UK (1997) PCS Frames (1997) formula's (1998) Using Applescript to process WebCatalog functions (1998) [ShowIf] if the varieable exists (1998) WebCat2b15MacPlugin - [protect] (1997) SandBox and ImageMagick (2003) Emailer (1997) shipCost not working v2.1b4 (1997) Runnaway Trigger (2007) WebCatalog Q & A pages (1997) SQL (2003) [WebDNA] Sublime Text 3 syntax file for WebDNA? (2016) More on the email templates (1997) Weird problems with [SHOWIF]s (1997)