Problems with Version 2.9.0 Service did not start, posted by Michael Dannmeyer on Wed Dec 7 14:18:41 2011
|
Hello,
I tried to update our ELOG installation 2.7.8 to 2.9.0. If I try to start the service i get the error:
Error 193: %1 is not a valid win32 application.
I uninstalled the old version an installed the new one.
Do you have any Idea? The OS is windows 2000 Server.
Best regards
Michael
Could not start the elogd service on local Computer |
Re: Problems with Version 2.9.0 Service did not start, posted by Michael Dannmeyer on Fri Dec 23 14:31:27 2011
|
Grant Jeffcote wrote: |
Stefan Ritt wrote: |
Michael Dannmeyer wrote: |
Hello,
I tried to update our ELOG installation 2.7.8 to 2.9.0. If I try to start the service i get the error:
Error 193: %1 is not a valid win32 application.
I uninstalled the old version an installed the new one.
Do you have any Idea? The OS is windows 2000 Server.
Best regards
Michael
Could not start the elogd service on local Computer
|
Can you start elogd.exe manually in a DOS box? If you get the same error there, the download file might be corrupted and you should try to re-load it again.
Best regards,
Stefan
|
Michael,
I had this problem with the service/elogd.exe not starting on the later versions of ELog and with Stefan's help we tracked it down to some missing Microsoft C runtime library files.
In my case it was a fresh install of Win2k3.
Try installing one the following and see if it helps (mine was solved with the middle option).
http://www.microsoft.com/download/en/details.aspx?id=3387
http://www.microsoft.com/download/en/details.aspx?id=5582
http://www.microsoft.com/download/en/details.aspx?id=5555
Regards
Grant
|
Thanks probelm is solved.
ELOG was installed at a windows 2000 Server. After Grant's Tip I moved it to W2003R2 and installed the midlle option. No it works without any problems.
Regards
Michael |
Problems with Autorization, posted by Michael Dannmeyer on Wed Jun 27 10:42:20 2012
|
Hello,
we used Admin and write passwords. Now this is no longer supported in ELOG 2.9.0 and I tried to change to File or Kerberos Autentication. But nothing worked. I tried the following lines in elog.cfg
[Serverlogbuch]
Authentication = File
Password file = C:\Program Files\ELOG\logbooks\Serverlogbuch\pwd.txt
Self Authentication = 1
So the self Autentication site opens and I can put in all informations. But if I click on save he tries to save the information in the password file and after a time he stops and Internet Explorer says that the page cannot be reached.
The file is not saved. If I remove the 3 lines the logbook opens without any problems.
I tried also kerberos but it didn't work. But there I think some entries in the krb5.ini are wrong.
Would you please help solving the File password problem?
Best Regards
Michael
|
Re: Problems with Autorization, posted by Michael Dannmeyer on Thu Jul 5 11:18:40 2012
|
Andreas Luedeke wrote: |
Michael Dannmeyer wrote: |
Hello,
we used Admin and write passwords. Now this is no longer supported in ELOG 2.9.0 and I tried to change to File or Kerberos Autentication. But nothing worked. I tried the following lines in elog.cfg
[Serverlogbuch]
Authentication = File
Password file = C:\Program Files\ELOG\logbooks\Serverlogbuch\pwd.txt
Self Authentication = 1
So the self Autentication site opens and I can put in all informations. But if I click on save he tries to save the information in the password file and after a time he stops and Internet Explorer says that the page cannot be reached.
The file is not saved. If I remove the 3 lines the logbook opens without any problems.
I tried also kerberos but it didn't work. But there I think some entries in the krb5.ini are wrong.
Would you please help solving the File password problem?
[...] |
Just two hints:
- The file mentioned as "Password file" should be writeable for the "elogd" process. It is needed for both, Kerberos and File authentication. Better not specify the full path, it should assume the file in the logbook directory.
- The command "Self Authentication = 1" does not exist. Maybe you mean "Self register = 1"?
|
Thank you for the answer, but it didn't solve the problem.
- I used Self Register instead of Self Authentication. I deleted the complete path and only used the Filename.
-
The Account which is used to start the Elogd process is local system. System has full right at the logbook directory
Should I use an Admin Account for the elogd process? The error message is always the same (page not reachable) The File is also not created in the logbook dir.
|
Re: Problems with Autorization, posted by Michael Dannmeyer on Fri Jul 13 15:12:07 2012
|
Stefan Ritt wrote: |
Michael Dannmeyer wrote: |
Andreas Luedeke wrote: |
Michael Dannmeyer wrote: |
Hello,
we used Admin and write passwords. Now this is no longer supported in ELOG 2.9.0 and I tried to change to File or Kerberos Autentication. But nothing worked. I tried the following lines in elog.cfg
[Serverlogbuch]
Authentication = File
Password file = C:\Program Files\ELOG\logbooks\Serverlogbuch\pwd.txt
Self Authentication = 1
So the self Autentication site opens and I can put in all informations. But if I click on save he tries to save the information in the password file and after a time he stops and Internet Explorer says that the page cannot be reached.
The file is not saved. If I remove the 3 lines the logbook opens without any problems.
I tried also kerberos but it didn't work. But there I think some entries in the krb5.ini are wrong.
Would you please help solving the File password problem?
[...] |
Just two hints:
- The file mentioned as "Password file" should be writeable for the "elogd" process. It is needed for both, Kerberos and File authentication. Better not specify the full path, it should assume the file in the logbook directory.
- The command "Self Authentication = 1" does not exist. Maybe you mean "Self register = 1"?
|
Thank you for the answer, but it didn't solve the problem.
- I used Self Register instead of Self Authentication. I deleted the complete path and only used the Filename.
-
The Account which is used to start the Elogd process is local system. System has full right at the logbook directory
Should I use an Admin Account for the elogd process? The error message is always the same (page not reachable) The File is also not created in the logbook dir.
|
I once had problems with the local system account, so I used my own account to start the service and that worked. For trial, you can also start the elogd.exe program manually (not as a service) in a DOS box and see if it can create the password file.
|
That worked for me. Used an Account instead of local system and everything is OK. Thanks for your help. |
Limited access to an attribute, posted by Michael Cianci on Mon Jun 15 19:33:39 2015
|
Is there a way to limit access to an attribute "Reviewed by" to only supervisors?
Thank you for your help
Mike |
Limited access to an attribute, posted by Michael Cianci on Mon Jun 15 19:38:58 2015
|
Is there a way to limit access to an attribute "Reviewed by" to only supervisors?
Thank you for your help
Mike |
Password Protect Delete, posted by Michael Cianci on Thu Jul 20 18:38:20 2017
|
We don't use a password file but would like to password protect (Admin only) the DELETE function in the MENU Thank You |