ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
65758
|
Tue Feb 26 03:06:06 2008 |
| Uwe | uweho@web.de | Question | Windows | 2.7.3 | Problem updating from 2.7.2 to 2.7.3 | Hello,
I am trying to update from version V2.7.2-2041 to V2.7.3 but getting the attached error message. OS is Windows 2003. I installed the update on Windows XP without a problem. Does anybody know ho to solve that problem? Thanks!
Uwe
|
Attachment 1: error.JPG
|
|
65759
|
Wed Feb 27 03:46:28 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.3 | Re: Problem updating from 2.7.2 to 2.7.3 |
Uwe wrote: |
Hello,
I am trying to update from version V2.7.2-2041 to V2.7.3 but getting the attached error message. OS is Windows 2003. I installed the update on Windows XP without a problem. Does anybody know ho to solve that problem? Thanks!
|
The shared library msvcr71.dll should be part of the operating system and placed under c:\windows\system32\msvc71.dll. If not it can be downloaded from
http://www.dlldump.com/download-dll-files.php/dllfiles/M/MSVCR71.dll/download.html |
65760
|
Thu Feb 28 01:56:53 2008 |
| Uwe | uweho@web.de | Question | Windows | 2.7.3 | Re: Problem updating from 2.7.2 to 2.7.3 |
Stefan Ritt wrote: |
Uwe wrote: |
Hello,
I am trying to update from version V2.7.2-2041 to V2.7.3 but getting the attached error message. OS is Windows 2003. I installed the update on Windows XP without a problem. Does anybody know ho to solve that problem? Thanks!
|
The shared library msvcr71.dll should be part of the operating system and placed under c:\windows\system32\msvc71.dll. If not it can be downloaded from
http://www.dlldump.com/download-dll-files.php/dllfiles/M/MSVCR71.dll/download.html
|
Thanks, that fixed it... |
65762
|
Sat Mar 1 07:40:18 2008 |
| mike cianci | mike2.cianci@comcast.net | Question | Windows | 2.7.3-2058 | Problem with Email Notification | Sorry to bother you with this, but I am not a programmer and this is probably a simple question but I need some help if someone has the time.
Under Global I have the command - SMTP host = smtp.comcast.net
ELOG responds with - Error sending Email via "smtp.comcast.net": 5.1.0 sender rejected : invalid sender domain
|
65765
|
Sat Mar 1 15:08:07 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.3-2058 | Re: Problem with Email Notification |
mike cianci wrote: |
Sorry to bother you with this, but I am not a programmer and this is probably a simple question but I need some help if someone has the time.
Under Global I have the command - SMTP host = smtp.comcast.net
ELOG responds with - Error sending Email via "smtp.comcast.net": 5.1.0 sender rejected : invalid sender domain
|
Your SMTP server does not accept the email send request from ELOG. That can have many reasons. Most systems are set up so that they do not accept SPAM. To do that, they do various checking of the sender address etc. Maybe you need an "Email from = mike2.cianci@comcast.net" in your config file to have a "real" sender address. Some more information you can get if you start elogd interactively in a DOS box with the "-v" flag, because then you will see all the debugging output of the communication between elogd and your SMTP server. |
65777
|
Fri Mar 7 14:29:00 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | ELOG V2.7. | Re: Message ID and trouble ticketing system |
Stefan Ritt wrote: |
Richard Ecclestone wrote: |
I tried the 'Preset ticket = TCK-#####' method to create unique numbers for our application. This worked very nicely until we replied to a earlier message, if we then create a new message the system creates a sequential number after the last message number we replied to. For example if we have 10 messages. If someone replies to message number #2 then when a new record is created it is then assigned number #3 not #11, thus making a duplicate entry for #3.
Any ideas?
|
Yes. If you want this feature to work also for replies, you have to put following into your config file:
Preset ticket = TCK-#####
Preset on reply ticket = TCK-#####
|
When I was browsing this forum about my previous problem, I found
this thread. A ticket number that applies to all entries in a
thread, but is unique to that thread.
But I have the same problem as Richard Ecclestone reported, and the
"Preset on reply ticket" line from your reply has not had any effect.
It appears that on starting a new thread (which is to have that
ticket number), the ticket number is just incremented by one from
that of the previous (as in previous ID number) entry. This is
fine if each thread is completed before a new one started, but if
there are more than one active thread, which can be progressed
further in any order, new threads are likely to be issued with a
ticket number which has already been issued (see Richards's example).
An alternative source of unique numbers would be the Entry number (as
in "696 Entries", top right of the midas.psi.ch/elogs/Forum page),
which would be the seed for the ticket number on new entry. Not sure
of the syntax for that, or for the replies to have *that* number for
the config file. I know there is a problem if you move a number of
threads away, but the only alternative (that I can think of) is to
store the seed number somewhere, and increment it every time a new
thread is started.
Or have I got something wrong here?
Thanks.
Regards,
David.
|
65778
|
Fri Mar 7 14:45:02 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | ELOG V2.7. | Re: Message ID and trouble ticketing system |
David wrote: |
When I was browsing this forum about my previous problem, I found this thread. A ticket number that applies to all entries in a thread, but is unique to that thread. But I have the same problem as Richard Ecclestone reported, and the "Preset on reply ticket" line from your reply has not had any effect. It appears that on starting a new thread (which is to have that ticket number), the ticket number is just incremented by one from that of the previous (as in previous ID number) entry. This is fine if each thread is completed before a new one started, but if there are more than one active thread, which can be progressed further in any order, new threads are likely to be issued with a ticket number which has already been issued (see Richards's example).
An alternative source of unique numbers would be the Entry number (as in "696 Entries", top right of the midas.psi.ch/elogs/Forum page), which would be the seed for the ticket number on new entry. Not sure of the syntax for that, or for the replies to have *that* number for the config file. I know there is a problem if you move a number of threads away, but the only alternative (that I can think of) is to store the seed number somewhere, and increment it every time a new thread is started.
Or have I got something wrong here? Thanks. Regards, David.
|
I cannot reproduce your problem. Assume we have following config file:
[demo]
Theme = default
Attributes = Ticket, Author, Subject
Preset Ticket = TCK-####
The the first entry gets TCK-0001. Any reply to that stays with TCK-0001. Then I do another "new" entry, which gets TCK-0002. Even if I then do another reply to the first thread, that will just stay with TCK-0001. So avoid using 'Preset on reply Ticket". The post from Richard was different, he wanted a new number also for replies (if I understand correctly). |
65779
|
Fri Mar 7 20:42:39 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | ELOG V2.7. | Re: Message ID and trouble ticketing system | Ok, now I got the point, also Richard had the same problem. Assume we have 10 threads, and thus ticket numbers 1-10. Now we get a reply to #2, which then pops up to the top of the list. A new message increments the top entry of all entries, and then wrongly gives a new #3, instead of #11.
I fixed this in SVN revision 2073, where elogd searches all logbook entries for the largest index, then increments this one by one. The fix will be contained in the next release. |
|