No, there is no Dotnet or DLL required. Just start the ELOG server manually by clickin on Start/Programs/ELOG Server/Start ELOG server manually and watch if you can spot any error. One person reported that downloading again the package solved a similar problem.

We are currently having problems with Elog, I never had a problem installing it before but with my last 3 install I can't get it to work. We are running under Windows XP, the installation works perfectly but when I try to use the shortcut pointing to the localhost 8080, I get an error page from Internet Explorer telling me that the server cannot be found. I've rebootied the computer to make sure the server was running but still the same problem. Is there a basic requirement I should look at (Dotnet versionX or specific DLL required)?

Stefan,

I have been running logging and I think I have found the problem however I do not know how to resolve it.

Here is where it is going wrong:

19-May-2009 04:02:48 [] {NSS} MIRROR: ID21268: Local entry submitted

19-May-2009 04:07:34 [] {AMC} MIRROR: send entry #31056

It seems that when it has finished replication on one logbook there is a significant time before the next logbook replication starts. During this time the server is not avalable. I have noticed that the time between ending one logbook and starting the next differs betwee 2 and 5 minutes. Again the server is not available when this happens.

Do you have any idea?

Cheers,

Lance

Hi

Would it be possible to use the "Export to:" function with IE7 on the Forum logbook, and save the logbook.

I can do the export but saving the file with IE7 does not work. Saving the file with Firefox, Chrome, Safari works.

This makes me think that E-log is good and IE7 is bad ?

Soren

Never as far as I know. Try to do logging on your elog server ("Log file = ..."), then you will see all write/delete accesses. So if someone deletes your entries, you will see a trace. 

A few days after I create entries in my logbooks, they are being deleted. Has this happened to anyone before?

We are running elog across two sites and synchronizing every four hours on change only. There are about 100 entries per day of which most are just one line entries. However this is taking up to 9 mins and during the replication process the server gives us an "unavailable" error. We are using a T1 across the sites so bandwidth should not be an issue, I am confused as to why this takes so long.

The issue for us is not how long the sync takes, providing this was happening in the background, and doesnt lock out the server while the replication was taking place. We are operating under a 24 hour call center type environment so the server being available all the time is of paramount importance.

We use version 2.7.2 and I know there have been several changes made since this version. Would changing to the latest version have any impact on this?

Cheers,

Lance

Hi,

A user tried to import a CSV file, which caused e-log to add a field called "date" to the list of attributes (and then crash). This caused the log-book to be blocked until someone (guess who) would go edit the elogd.cfg file and then trigger a reload.

1. suggestion : E-log should not crash in this case

2. suggestion: E-log should not allow invalid attributes to be added via CSV Import, which causes the log-book to be blocked.

For the time being, I will just  "Deny import" (by the way, the doc says it is "Deny CSV import", but I think the syntax is "Deny import". Not really important.

I think this should be quite easy to reproduce.

Thanks a lot

Soren