| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1918
|
Tue Aug 29 15:28:51 2006 |
 | David Spindler | dsspindler@earthlink.net | Question | Windows | 2.6.2-1699 | Email substitution quit working | I have recently upgraded from the 2.6.0-beta (I believe) to 2.6.2-1699. I just found out that on the day I upgraded, email substitution has stopped working. I have checked the discussion area and all the documentation and do not see any clues. The debug_log.txt file shows that the emails are being processed, but the fields are not being substituted correctly.
Thanks, in advance for any help,
David
*********************************************
;***** EMAIL SECTION:
Email All = 494475@emc.work.com, 494476@emc.work.com, $user_email, $Emp#@emc.work.com
Use Email Subject = Facility Maintenance Vehicle Elog Entry
Use Email From = facmx_vehicle_elog@work.com
Use Email Heading = "A new entry has been made on the AOC Vehicle Elogbook. Do NOT reply to this email."
;Set default encoding to 1 for plain text. Elcode and html not usable for EMC2 email. 0 = elcode, 2 = html
Default encoding = 1
MOptions Email To = Aoc Managers, AOC, CTC, WHQ, WTC, Offsite, Facility Management, All
Email "Email To" All = aoc-techs@emc.work.com, ctc-mech@emc.work.com, whq-techs@emc.work.com, wtc-tech@emc.work.com, rttechs@emc.work.com, rtffmteam@emc.work.com
Email "Email To" Aoc Managers= aoc-managers@emc.work.com
Email "Email To" "AOC" = aoc-techs@emc.work.com
Email "Email To" "CTC" = ctc-mech@emc.work.com
;***** EMAIL SECTION:
Email All = 494475@emc.work.com, 494476@emc.work.com, $user_email, $Emp#@emc.work.com
Use Email Subject = Facility Maintenance Vehicle Elog Entry
Use Email From = facmx_vehicle_elog@work.com
Use Email Heading = "A new entry has been made on the AOC Vehicle Elogbook. Do NOT reply to this email."
;Set default encoding to 1 for plain text. Elcode and html not usable for EMC2 email. 0 = elcode, 2 = html
Default encoding = 1
MOptions Email To = Aoc Managers, AOC, CTC, WHQ, WTC, Offsite, Facility Management, All
Email "Email To" All = aoc-techs@emc.work.com, ctc-mech@emc.work.com, whq-techs@emc.work.com, wtc-tech@emc.work.com, rttechs@emc.work.com, rtffmteam@emc.work.com
Email "Email To" Aoc Managers= aoc-managers@emc.workcom
Email "Email To" "AOC" = aoc-techs@emc.work.com
Email "Email To" "CTC" = ctc-mech@emc.work.com |
|
1923
|
Tue Sep 5 15:59:47 2006 |
 | David Spindler | dsspindler@earthlink.net | Question | Windows | 2.6.2-1699 | Re: Email substitution quit working |
| David Spindler wrote: | I have recently upgraded from the 2.6.0-beta (I believe) to 2.6.2-1699. I just found out that on the day I upgraded, email substitution has stopped working. I have checked the discussion area and all the documentation and do not see any clues. The debug_log.txt file shows that the emails are being processed, but the fields are not being substituted correctly.
Thanks, in advance for any help,
David
|
I have not been able to find anything wrong in my config file, so I replaced 2.6.2 with 2.6.1 (apparently that was what I was running last, not the 2.6.0-beta) and my troubles have disappeared.
Anybody have any idea what has happened? |
|
2033
|
Thu Nov 2 18:02:44 2006 |
 | David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.6.2-1734 | Bug? Password file location changed | I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different location.
I have a password file called pwd.txt. It resides in the main elog directory, in my case, c:\elog, along with the elgod.exe and elogd.cfg. Apparently, the new version looks for it in the logbooks directory. I adjusted my path to the file and it works fine.
I am reporting this as a bug because it is my guess that this is not an expected result. I would expect the old elogd.cfg file to work without altering in the newer version.
Thanks, keep up the great work, Stefan. You have a great program.
David Spindler |
|
2034
|
Thu Nov 2 18:10:07 2006 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.6.2-1734 | Re: Bug? Password file location changed |
| David Spindler wrote: | I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different location.
I have a password file called pwd.txt. It resides in the main elog directory, in my case, c:\elog, along with the elgod.exe and elogd.cfg. Apparently, the new version looks for it in the logbooks directory. I adjusted my path to the file and it works fine.
I am reporting this as a bug because it is my guess that this is not an expected result. I would expect the old elogd.cfg file to work without altering in the newer version.
Thanks, keep up the great work, Stefan. You have a great program.
David Spindler |
I also just noticed that the text files I use for presetting the text window also have to be in the logbooks directory. |
|
2039
|
Fri Nov 3 14:40:36 2006 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.6.2-1734 | Re: Bug? Password file location changed |
| Steve Jones wrote: |
| David Spindler wrote: |
| David Spindler wrote: | I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different location.
I have a password file called pwd.txt. It resides in the main elog directory, in my case, c:\elog, along with the elgod.exe and elogd.cfg. Apparently, the new version looks for it in the logbooks directory. I adjusted my path to the file and it works fine.
I am reporting this as a bug because it is my guess that this is not an expected result. I would expect the old elogd.cfg file to work without altering in the newer version.
Thanks, keep up the great work, Stefan. You have a great program.
David Spindler |
I also just noticed that the text files I use for presetting the text window also have to be in the logbooks directory. |
| Quote: | The relocation was a documented change that Stefan made intentionally. Yes, it caught me too  |
|
Thanks. I checked the changelog and the documentation for any such changes but did not see them. I just looked again, and still do not see them. Anyway, I know what to expect, now, and will adjust. Again, thanks! |
|
66571
|
Mon Nov 2 21:23:38 2009 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.7.7 2246 | 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 | I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
Thanks,
David |
|
66596
|
Wed Nov 11 19:45:19 2009 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.7.7 2246 | Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 |
| Stefan Ritt wrote: |
|
| David Spindler wrote: |
|
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
|
I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash.
|
In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:
|
|
66624
|
Fri Nov 20 19:32:22 2009 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.7.7 2246 | Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 |
| David Spindler wrote: |
|
| Stefan Ritt wrote: |
|
| David Spindler wrote: |
|
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
|
I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash.
|
In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:
|
Sorry for the delay.
1: The offending log file.
|
|