Manual installing elog as service on Windows, posted by Arno Teunisse on Sat Apr 12 16:37:44 2008
|
Hello
Sometimes it can come in handy to start a temporary elog service on the Windows platform. ( Maybe for testing purposes )
You can use the SC.exe utility to do that. If it is not on you're system you may download it from : ftp://ftp.microsoft.com/reskit/win2000/sc.zip
For this you can use the following procedure ( from the dos prompt ) :
sc.exe create AIX-elog binPath= "\"c:\ELOG2.7.3\elogd.exe\" -D -c c:\ELOG2.7.3\security.cfg" DisPlayname= "AIX Elog Security" start= auto
If all went well the system answers :
[SC] CreateService SUCCESS
Please notice the strange way the double quotes are used and the space after the = in the above command.
Now open the windows services ( from the prompt ) : services.msc
In the window that opens you will see the just created service with the DisPlayname you gave in the above command.
You see it is not started. You could click start, but there is an other way.
Now you can start the service from the prompt using the DisPlayname :
net start "AIX elog security"
Press F5 ( refresh ) in the services window and you will see that the service is started.
Or stop the service :
net stop "AIX elog security"
To remove the service ( from the registry ) :
sc.exe delete AIX-elog
The system gives back :
[SC] DeleteService SUCCESS
The other option is to start elogd.exe from the prompt :
elogd.exe -c
This is all for now
|
Re: Message ID and trouble ticketing system, posted by David Pilgram on Fri Mar 7 21:53:28 2008
|
>>Stefan Ritt wrote:
>>
>>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.
>
>----
>
>Great! Thanks Stefan, off to download right now!
>
>Great program, by the way, but don't think you need to be told that yet again!
---
Oh ho!
I've tried this on an existing database, where most entries do not have a ticket #. The previous entry #
(previous in ID sense) is T00550, say. But when I start a new thread, the ticket # is T00001. Is it being put
out by no entry for ticket # in most of the database?
LATER UPDATE.
On a small database (12 entries, with 45 comments in total), this worked as expected if most or all entries have ticket numbers, even if the previous (by id #) had not had a ticket number. (I had to edit every entry to put in ticket numbers).
The only thing I can think of is the number of entries that don't have a ticket #, or a line in the .log file entry saying "Ticket: " but am looking further into this.
(BTW, am posting this way to get around the proxy server problem I have!) |
Re: Message ID and trouble ticketing system, posted by David Pilgram on Fri Mar 7 21:26:18 2008
|
>Stefan Ritt wrote:
>
>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.
----
Great! Thanks Stefan, off to download right now!
Great program, by the way, but don't think you need to be told that yet again! |
Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 20:42:39 2008
|
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. |
|
Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 14:45:02 2008
|
| 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). |
|
Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 14:29:00 2008
|
| 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.
|
|
Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Thu Feb 21 08:04:50 2008
|
| 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-#####
|
|
Re: Message ID and trouble ticketing system, posted by Richard Ecclestone on Fri Feb 15 15:46:38 2008
|
| lance wrote: |
|
| Stefan Ritt wrote: |
|
| lance wrote: |
|
I am trying to create a trouble ticket system however when you do a reply you get a new message ID. I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.
Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.
Has anyone configured a trouble ticket system that I could look at to get some ideas?
|
First of all, ELOG has been designed having shift logbooks in mind, so it probably will never be a perfect trouble ticket system. Nevertheless, there are some options which can help in that respect:
- Use attributes Ticket and Status
- Preset Ticket with a running ticket number via
Preset ticket = TCK-#####
This will increment the 5-digit ticket number whenever you create a new ticket, but will not update it when you do a reply
-
Use Status to determine the status of the whole trouble ticket chain (initial entry plus replies)
Options Status = open, closed
Preset Status = open
-
Once a ticked chain is closed, do the following:
- Go to the threaded list display
- Click on Select
- Select the trouble ticket chain
- Click on Edit
- Now change Status from "Open" to "Closed"
This will then modify the Status of the whole chain from "Open" to "Closed"
|
Stefan,
Thanks for this, I had already implemented the Preset Ticket Nr = TT-##### but I didnt use the threaded and Select to close the ticket, very nice tip thanks. I think this program can be have several uses, and working very well. The trouble ticketing will work for us.
Once again thanks for the very speedy support.
Lance
|
Hi
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?
Cheers Richard |
|