Ticket #10 (closed defect: fixed)

Opened 15 years ago

Last modified 15 years ago

Logging enabling not stable

Reported by: michelpons Owned by: ahsanakhtar
Priority: blocker Milestone: Refactoring
Component: COLoggingController Version: 1.08.3
Keywords: Cc: michaelhalloran; ahsanakhtar


While trying to test ticket #8, I am faced with the following issue: I enable COLTT on Aspen Properties Thermo System using COLTT Controller. Then I close the controller. I reopen it and I see that Aspen Properties Thermo System is no longer logged.

Change History

comment:1 Changed 15 years ago by michaelhalloran

  • Owner changed from Michael Halloran to ahsanakhtar
  • Status changed from new to assigned

Assigned to Ahsan.

comment:2 Changed 15 years ago by michaelhalloran


Do you actually get a logfile?

can you check that you have these two keys in your registry after the installation:






InprocServer32\", TRUE);






InprocServer32\", TRUE);

I think if one of these was missing, the controller would show logging enabled even though it was not really enabled, which would mean no logfile but also on restarting the controller the component would be shown as not logged.

Do you have IE 8 installed? It may be that the problem we had before is preventing the installation from working and the logging DLLs are not actually registered.

comment:3 Changed 15 years ago by michelpons

I have seen no log file. In fact, I have discovered the issue when after running a case with a logged PMC, I did not find the log file and reopening the controller, the PMC was not declared as logged.

I have found none of the two registry keys listed.

I have IE8 installed.

comment:4 Changed 15 years ago by ahsanakhtar

  • Status changed from assigned to closed
  • Resolution set to fixed

comment:5 Changed 15 years ago by michelpons

  • Milestone set to Refactoring
Note: See TracTickets for help on using tickets.