ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 116 of 238

Not logged in

Find | Login | Help

Full | Summary | Threaded | Collapse | Expand

1899 Entries

Goto page Previous 1, 2, 3 ... 115, 116, 117 ... 236, 237, 238 Next

Fail to connect to SMTP server on WinXP but works on Win2K, posted by David Spindler on Sat Mar 6 19:59:58 2010

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by David Spindler on Sat Mar 6 20:06:24 2010

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I have been running Elog for years on a Win2K machine with no email problems. I have been forced to move it to a WinXP machine and I always get this message under WinXP: "Error sending Email via "netsvr10.prod.company.com": Cannot connect to server"

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

28-Oct-2009 18:28:38 [609144@199.82.127.9] {Generals} NEW entry #0
28-Oct-2009 18:28:38 [609144@199.82.127.9] {Generals} Email from <christophermeyer@fedex.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
28-Oct-2009 18:28:42 [609144@199.82.127.9] {Generals} 220 netsvr10.prod.company.com -- Server ESMTP (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit))

Here is an entry from today's elog.log under WinXP that does not work.

06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} NEW entry #0
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} Email from <david.spindler@company.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} READ entry #1612

We use an SMTP server without authentication.

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by David Spindler on Sat Mar 6 20:16:52 2010

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} NEW entry #0
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} Email from <david.spindler@company.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} READ entry #1612

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

06-Mar-2010 10:31:43 [117361@199.81.166.149] {Gbld} READ entry #1691
06-Mar-2010 10:39:10 [117361@199.81.166.149] {Gbld} NEW entry #0
06-Mar-2010 10:39:11 [117361@199.81.166.149] {Gbld} Email from <david.spindler@company.com> to david.spindler@company.com, SMTP host smtp.mail.company.com

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by Stefan Ritt on Thu Mar 11 15:47:21 2010

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

The only idea I have is that your Windows firewall prevents outgoing network traffic on port 25 (SMTP). You should put an exception into the firewall rule. You can try that by opening a DOS box and entering

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by David Spindler on Fri Mar 12 19:30:53 2010

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by David Spindler on Wed Mar 17 21:34:53 2010

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

My apologies. I just realized that my first answer to you was lost. I turned the firewall completely off with no luck. I also tried the telnet and it worked. So, it does not appear to be the firewall. I tried the VM's afterwards. Another puzzle is that the Win2K VM works on a WinXP host. It seems like it is only the WinXP elog that fails. I have tried to obtain some our company's IT help with no luck.

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by soren poulsen on Wed Mar 17 22:39:59 2010

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

Just an idea: could you try specifying an IP address for your SMTP server instead of smtp.mail.company.com ?

I would also try to make a manual SMTP session to see if that works.

Otherwise, next step would be to create a VM installed with Wireshark to record the network traffic that ELOG generates when it makes the SMTP connection.

Soren

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by David Spindler on Thu Mar 18 20:08:03 2010

soren poulsen wrote:

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

Just an idea: could you try specifying an IP address for your SMTP server instead of smtp.mail.company.com ?

I would also try to make a manual SMTP session to see if that works.

Otherwise, next step would be to create a VM installed with Wireshark to record the network traffic that ELOG generates when it makes the SMTP connection.

Soren

Thanks, I will give it a try.

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by David Spindler on Thu Mar 18 20:34:41 2010

David Spindler wrote:

soren poulsen wrote:

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

Just an idea: could you try specifying an IP address for your SMTP server instead of smtp.mail.company.com ?

I would also try to make a manual SMTP session to see if that works.

Otherwise, next step would be to create a VM installed with Wireshark to record the network traffic that ELOG generates when it makes the SMTP connection.

Soren

Thanks, I will give it a try.

I cannot send an email from elog using an IP address.

I can send an email manually through SMTP.

I will have to locate a copy of wireshark and set up a VM. I cannot access any site that has it from here.

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by soren poulsen on Fri Mar 19 13:45:13 2010

David Spindler wrote:

soren poulsen wrote:

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

Just an idea: could you try specifying an IP address for your SMTP server instead of smtp.mail.company.com ?

I would also try to make a manual SMTP session to see if that works.

Otherwise, next step would be to create a VM installed with Wireshark to record the network traffic that ELOG generates when it makes the SMTP connection.

Soren

Thanks, I will give it a try.

I cannot send an email from elog using an IP address.

I can send an email manually through SMTP.

I will have to locate a copy of wireshark and set up a VM. I cannot access any site that has it from here.

We will get there. What is the output of "ipconfig /all" of the Win2K and WinXP machines respectively ?

Maxbe the DNS suffix is missing on XP ?

Soren

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by David Spindler on Fri Mar 19 15:56:38 2010

soren poulsen wrote:

David Spindler wrote:

soren poulsen wrote:

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

Just an idea: could you try specifying an IP address for your SMTP server instead of smtp.mail.company.com ?

I would also try to make a manual SMTP session to see if that works.

Otherwise, next step would be to create a VM installed with Wireshark to record the network traffic that ELOG generates when it makes the SMTP connection.

Soren

Thanks, I will give it a try.

I cannot send an email from elog using an IP address.

I can send an email manually through SMTP.

I will have to locate a copy of wireshark and set up a VM. I cannot access any site that has it from here.

We will get there. What is the output of "ipconfig /all" of the Win2K and WinXP machines respectively ?

Maxbe the DNS suffix is missing on XP ?

Soren

Here are the IPCONFIG /ALL pastes:

#1>>>WinXP not running VM:

ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : AOC-117361-W1
        Primary Dns Suffix . . . . . . . : corp.ds.companyname.com
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : corp.ds.companyname.com
                                            ds.companyname.com
                                            companyname.com

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Cont
roller
        Physical Address. . . . . . . . . : 00-11-43-18-D3-7B
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : ##9.81.166.149
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : ##9.81.166.1
        DNS Servers . . . . . . . . . . . : ##9.81.11.53
                                            ##9.81.7.54

************************************************************************
#2>>>VM Win2K fail to send emails:
ipconfig /All

Windows 2000 IP Configuration

        Host Name . . . . . . . . . . . . : jc_vm_w2k
        Primary DNS Suffix . . . . . . . :
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : corp.ds.companyname.com

Ethernet adapter Local Area Connection 2:

        Connection-specific DNS Suffix . : corp.ds.companyname.com
        Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

        Physical Address. . . . . . . . . : 00-0C-29-28-24-8F
        DHCP Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : ##9.81.163.127
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : ##9.81.163.1
        DHCP Server . . . . . . . . . . . : ##6.18.71.214
        DNS Servers . . . . . . . . . . . : ##9.81.10.150
                                            ##6.18.71.3
                                            ##9.82.243.70
        Lease Obtained. . . . . . . . . . : Friday, March 19, 2010 8:24:21 AM
        Lease Expires . . . . . . . . . . : Friday, March 19, 2010 12:24:21 PM

*************************************************************************
#3>>>VM Win2K with successful emails:
C:\>ipconfig /all

Windows 2000 IP Configuration

        Host Name . . . . . . . . . . . . : win2k-vm
        Primary DNS Suffix . . . . . . . :
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : corp.ds.companyname.com

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix . : corp.ds.companyname.com
        Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

        Physical Address. . . . . . . . . : 00-0C-29-1A-40-F3
        DHCP Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : ##9.81.163.127
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : ##9.81.163.1
        DHCP Server . . . . . . . . . . . : ##6.18.71.214
        DNS Servers . . . . . . . . . . . : ##9.81.10.150
                                            ##6.18.71.3
                                            ##9.82.243.70
        Lease Obtained. . . . . . . . . . : Friday, March 19, 2010 8:32:26 AM
        Lease Expires . . . . . . . . . . : Friday, March 19, 2010 12:32:26 PM

#1 was the output from the WinXP PC running Elog with no successful emails.

#2 was the output from the Win2K VM running on the #1 PC, also with no successful emails.

#3 was the output from another Win2K VM running on the #1 PC that successfully emails.

The difference between the 2 VM's is that #2 has the latest VMWare tools installed and #3 does not. This is running under VMWare Player 3.

The DNS suffix is present on the host PC but neither of the VM's, yet one of the VM's works.

BTW, thanks for your time in examining this issue.

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by David Spindler on Fri Mar 19 20:18:17 2010

David Spindler wrote:

soren poulsen wrote:

David Spindler wrote:

soren poulsen wrote:

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

Just an idea: could you try specifying an IP address for your SMTP server instead of smtp.mail.company.com ?

I would also try to make a manual SMTP session to see if that works.

Otherwise, next step would be to create a VM installed with Wireshark to record the network traffic that ELOG generates when it makes the SMTP connection.

Soren

Thanks, I will give it a try.

I cannot send an email from elog using an IP address.

I can send an email manually through SMTP.

I will have to locate a copy of wireshark and set up a VM. I cannot access any site that has it from here.

We will get there. What is the output of "ipconfig /all" of the Win2K and WinXP machines respectively ?

Maxbe the DNS suffix is missing on XP ?

Soren

Here are the IPCONFIG /ALL pastes:

#1 was the output from the WinXP PC running Elog with no successful emails.

#2 was the output from the Win2K VM running on the #1 PC, also with no successful emails.

#3 was the output from another Win2K VM running on the #1 PC that successfully emails.

The difference between the 2 VM's is that #2 has the latest VMWare tools installed and #3 does not. This is running under VMWare Player 3.

The DNS suffix is present on the host PC but neither of the VM's, yet one of the VM's works.

BTW, thanks for your time in examining this issue.

BINGO!!

I found the trouble. I assumed it was WinXP but I did not notice that the Win2K PCs I used hadSymantec Corporate AV while the WinXP PCs had McAfee AV. McAfee was the culprit.

Thanks very much for all of your help!!!

Re: Fail to connect to SMTP server on WinXP but works on Win2K, posted by David Spindler on Fri Mar 19 20:26:44 2010

David Spindler wrote:

soren poulsen wrote:

David Spindler wrote:

soren poulsen wrote:

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

Just an idea: could you try specifying an IP address for your SMTP server instead of smtp.mail.company.com ?

I would also try to make a manual SMTP session to see if that works.

Otherwise, next step would be to create a VM installed with Wireshark to record the network traffic that ELOG generates when it makes the SMTP connection.

Soren

Thanks, I will give it a try.

I cannot send an email from elog using an IP address.

I can send an email manually through SMTP.

I will have to locate a copy of wireshark and set up a VM. I cannot access any site that has it from here.

We will get there. What is the output of "ipconfig /all" of the Win2K and WinXP machines respectively ?

Maxbe the DNS suffix is missing on XP ?

Soren

Here are the IPCONFIG /ALL pastes:

#1 was the output from the WinXP PC running Elog with no successful emails.

#2 was the output from the Win2K VM running on the #1 PC, also with no successful emails.

#3 was the output from another Win2K VM running on the #1 PC that successfully emails.

The difference between the 2 VM's is that #2 has the latest VMWare tools installed and #3 does not. This is running under VMWare Player 3.

The DNS suffix is present on the host PC but neither of the VM's, yet one of the VM's works.

BTW, thanks for your time in examining this issue.

BINGO!!

I found the trouble. I assumed it was WinXP but I did not notice that the Win2K PCs I used hadSymantec Corporate AV while the WinXP PCs had McAfee AV. McAfee was the culprit.

Thanks very much for all of your help!!!

A little more info in case anybody else runs into this. McAfee defaults to blocking mass mailing worms, or at least our IT department has it doing so. Turn this off and the email from Elog works.

Thread view problem in searches, posted by soren poulsen on Tue Mar 2 14:21:46 2010

Hi,

When I upgrade from build 2278 to 2282 the thread view changes when performing searches: The thread children are not indented and there are no "thread icons" in the search list (e.g. like the read right arrow for replies).

On the forum site I also note that the thread view is not indented when performing searches.

Does anyone have an idea ?

Soren

Re: Thread view problem in searches, posted by soren poulsen on Sat Mar 6 20:53:25 2010

soren poulsen wrote:

Hi,

On the forum site I also note that the thread view is not indented when performing searches.

Does anyone have an idea ?

Soren

This seems to be a bug. I reproduced it with a different browser (Opera) with the default ELOG configuration. When I do Find and select Display Threads I have the message icons but the layout is not correct. Also, all message icons are of the "reply" type even if they are new threads.

This concerns only the latest build 2282.

Soren

Re: Thread view problem in searches, posted by Stefan Ritt on Thu Mar 11 15:44:01 2010

soren poulsen wrote:

Hi,

On the forum site I also note that the thread view is not indented when performing searches.

Does anyone have an idea ?

Soren

This concerns only the latest build 2282.

Soren

That's not a bug, that's a feature

But honestly, this feature was requested recently and implemented. See https://midas.psi.ch/elogs/Forum/66670. So when searching, the thread organization is broken up and messages are treated independently. If you want to see the thread for a certain entry in you search result page, click on that entry and you will see the full thread above the entry.

Re: Thread view problem in searches, posted by soren poulsen on Sun Mar 14 21:04:44 2010

Stefan Ritt wrote:

soren poulsen wrote:

Hi,

On the forum site I also note that the thread view is not indented when performing searches.

Does anyone have an idea ?

Soren

This concerns only the latest build 2282.

Soren

That's not a bug, that's a feature

That sounds fine but I think there is a problem with rendering under Opera. I enclose a screen shot: There is too much white space in the lines, it seems $

The problem only appears in Find

Soren

Re: Thread view problem in searches, posted by Stefan Ritt on Mon Mar 15 08:23:45 2010

soren poulsen wrote:

That sounds fine but I think there is a problem with rendering under Opera. I enclose a screen shot: There is too much white space in the lines, it seems $

The problem only appears in Find

I just tried myself with V10.50, and things work fine, even in the find page:

Can you try on the forum, just to check if it's specific to your configuration?

Re: Thread view problem in searches, posted by soren poulsen on Mon Mar 15 18:35:26 2010

Stefan Ritt wrote:

soren poulsen wrote:

That sounds fine but I think there is a problem with rendering under Opera. I enclose a screen shot: There is too much white space in the lines, it seems $

The problem only appears in Find

I just tried myself with V10.50, and things work fine, even in the find page:

Can you try on the forum, just to check if it's specific to your configuration?

Thanks. The Forum is fine. The problem is - apparently - specific to my installation. The white space origins in long sequences of "&nbsp" (repeated); in the lines in Find.

Let me re-install with the latest version and see if I can solve it like that.

Soren

Re: Thread view problem in searches, posted by soren poulsen on Mon Mar 15 18:58:06 2010

soren poulsen wrote:

Stefan Ritt wrote:

soren poulsen wrote:

That sounds fine but I think there is a problem with rendering under Opera. I enclose a screen shot: There is too much white space in the lines, it seems $

The problem only appears in Find

I just tried myself with V10.50, and things work fine, even in the find page:

Can you try on the forum, just to check if it's specific to your configuration?

Thanks. The Forum is fine. The problem is - apparently - specific to my installation. The white space origins in long sequences of "&nbsp" (repeated); in the lines in Find.

Let me re-install with the latest version and see if I can solve it like that.

Soren

I have re-installed the latest, fastest, smartest, brightest version. And it all works perfectly! Thanks a lot for your help.

Soren

Re: Thread view problem in searches, posted by soren poulsen on Tue Mar 16 11:58:55 2010

soren poulsen wrote:

Stefan Ritt wrote:

soren poulsen wrote:

That sounds fine but I think there is a problem with rendering under Opera. I enclose a screen shot: There is too much white space in the lines, it seems $

The problem only appears in Find

I just tried myself with V10.50, and things work fine, even in the find page:

Can you try on the forum, just to check if it's specific to your configuration?

Thanks. The Forum is fine. The problem is - apparently - specific to my installation. The white space origins in long sequences of "&nbsp" (repeated); in the lines in Find.

Let me re-install with the latest version and see if I can solve it like that.

Soren

I have re-installed the latest, fastest, smartest, brightest version. And it all works perfectly! Thanks a lot for your help.

Soren

Everything is fine. But my users do not like that the threads are broken into individual entries and not shown as full threads as before. So I am stuck with the "old" version. This is probably asking for too much but would it be difficult to have a flag to specify if you want to benefit from the new behaviour or keep pre-2282 behaviour (with its inconvenience which led to the presentation change). It could even be a compile tag flag, if it just me (well, my users) who is asking for this.

Soren

Invalid URL for groups beneath top groups in overview page, posted by Bertram Metz on Mon Mar 15 09:29:11 2010

Hi,

I'm trying to implement top groups and started with the sample configuration shown in the 'Syntax of elogd.cfg' chapter of the documentation. But now I'm facing a problem with the links in the logbook selection page.

Here's my group configuration:

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1

The selection page for the top groups is displayed correctly, but the URL for the groups beneath the top group is incorrect. The URL for the Linux PCs group for instance is http://localhost:8080/engineering/engineering/ . The URLs for the logbooks within the Linux PCs groups is correct (e.g. http://localhost:8080/Debian/)

Has anybody an idea what's going wrong in y configuration?

Bertram

Re: Invalid URL for groups beneath top groups in overview page, posted by Stefan Ritt on Mon Mar 15 11:21:30 2010

Bertram Metz wrote:

Hi,

Here's my group configuration:

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1

Has anybody an idea what's going wrong in y configuration?

Bertram

Thanks for reporting this bug. I fixed it in the intermediate release 278-4 which is ready for download.

Re: Invalid URL for groups beneath top groups in overview page, posted by Bertram Metz on Mon Mar 15 13:20:17 2010

Stefan Ritt wrote:

Bertram Metz wrote:

Hi,

Here's my group configuration:

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1

Has anybody an idea what's going wrong in y configuration?

Bertram

Thanks for reporting this bug. I fixed it in the intermediate release 278-4 which is ready for download.

Thanks for the quick bug fix.

Bertram

Problem using attribute type , posted by soren poulsen on Wed Feb 17 17:02:38 2010

Hi,

This little logbook has a problem:

------------------------

Attributes = Author, Category, Type, Subject, Number

Type Number = numeric

Options Category = General{1}
{1} Options Type = Routine

------------------------

(it was of course more complicated to start with).

When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.

To avoid the problem, I just comment out the line "Type Number ... "

Is this a bug ?

Thanks for your time

Soren

(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the problem).

Re: Problem using attribute type , posted by soren poulsen on Thu Feb 18 13:21:15 2010

soren poulsen wrote:

Hi,

This little logbook has a problem:

------------------------

Attributes = Author, Category, Type, Subject, Number

Type Number = numeric

Options Category = General{1}
{1} Options Type = Routine

------------------------

(it was of course more complicated to start with).

When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.

To avoid the problem, I just comment out the line "Type Number ... "

Is this a bug ?

Thanks for your time

Soren

(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the problem).

To overcome this problem it is sufficient to switch language from "Language = french" to "Language = english"

It was a mistake not to include the "global" settings in this bug report.

What probably happens is that something in the French translation (accents ?) disturbs the java scripting.

Soren

Re: Problem using attribute type , posted by soren poulsen on Thu Feb 18 15:37:07 2010

soren poulsen wrote:

Hi,

This little logbook has a problem:

------------------------

Attributes = Author, Category, Type, Subject, Number

Type Number = numeric

Options Category = General{1}
{1} Options Type = Routine

------------------------

(it was of course more complicated to start with).

When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.

To avoid the problem, I just comment out the line "Type Number ... "

Is this a bug ?

Thanks for your time

Soren

(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the problem).

To overcome this problem it is sufficient to switch language from "Language = french" to "Language = english"

It was a mistake not to include the "global" settings in this bug report.

What probably happens is that something in the French translation (accents ?) disturbs the java scripting.

Soren

To use "Language = french" it is necessary to remove or substitute the accent character ' with something else in eloglang.french and then the Javascript code works again.

Soren

Re: Problem using attribute type , posted by Stefan Ritt on Fri Mar 12 09:27:25 2010

soren poulsen wrote:

Hi,

This little logbook has a problem:

------------------------

Attributes = Author, Category, Type, Subject, Number

Type Number = numeric

Options Category = General{1}
{1} Options Type = Routine

------------------------

(it was of course more complicated to start with).

When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.

To avoid the problem, I just comment out the line "Type Number ... "

Is this a bug ?

Thanks for your time

Soren

(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the problem).

To overcome this problem it is sufficient to switch language from "Language = french" to "Language = english"

It was a mistake not to include the "global" settings in this bug report.

What probably happens is that something in the French translation (accents ?) disturbs the java scripting.

Soren

To use "Language = french" it is necessary to remove or substitute the accent character ' with something else in eloglang.french and then the Javascript code works again.

Soren

Indeed it was the JavaScript line

if (document.form1.Number.value != '- garder les valeurs d'origine -') {

which caused the trouble. The "'" character closed the string '- garder les valeurs d', which caused an exception. I changed it to

if (document.form1.Number.value != "- garder les valeurs d'origine -") {

and now it should work fine.

Re: Problem using attribute type , posted by soren poulsen on Sun Mar 14 20:57:26 2010

Stefan Ritt wrote:

soren poulsen wrote:

Hi,

This little logbook has a problem:

------------------------

Attributes = Author, Category, Type, Subject, Number

Type Number = numeric

Options Category = General{1}
{1} Options Type = Routine

------------------------

(it was of course more complicated to start with).

When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.

To avoid the problem, I just comment out the line "Type Number ... "

Is this a bug ?

Thanks for your time

Soren

(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the problem).

To overcome this problem it is sufficient to switch language from "Language = french" to "Language = english"

It was a mistake not to include the "global" settings in this bug report.

What probably happens is that something in the French translation (accents ?) disturbs the java scripting.

Soren

To use "Language = french" it is necessary to remove or substitute the accent character ' with something else in eloglang.french and then the Javascript code works again.

Soren

Indeed it was the JavaScript line

if (document.form1.Number.value != '- garder les valeurs d'origine -') {

which caused the trouble. The "'" character closed the string '- garder les valeurs d', which caused an exception. I changed it to

if (document.form1.Number.value != "- garder les valeurs d'origine -") {

and now it should work fine.

Thanks a lot for changing that. Now French should work as well.

Soren

eLog crash, posted by Mirza Ehsan on Wed Mar 10 10:36:02 2010

I am using eLog ELOG V2.6.1-1681 which has 7 log books under 8 categories. Out of 7 log books, 2 are daily used. It happened that two weeks back. I modified information on two log books which were not used for quite longtime. Hence using CONFIG, I updated these log books, changing text etc. After that eLog in general started giving error. Any time when we click SUBMIT button in any log book, eLog shows page not found. That submit crashes eLog and as a result elogd service stops. Restarting elogd service, eLog operation comes back and the log which I submitted was actualy saved. Difficulty is that this problem is happening with every single submit action.

I searched forum and learnt that upgrading eLog to newest version 2.7.8 will solve this problem. Upgrade created more problems, I was not able to open any log, authentication was not accepted. I restored that backup and went back to previous version. eLog started working but with submit error.

If any one can help me in fixing this problem

Re: eLog crash, posted by Stefan Ritt on Thu Mar 11 15:36:39 2010

Mirza Ehsan wrote:

If any one can help me in fixing this problem

I propose that you get 2.7.8 working. If the authentication fails, try do do password recovery, or recreated the accounts.

Re: eLog crash, posted by Mirza Ehsan on Sat Mar 13 09:40:37 2010

Stefan Ritt wrote:

Mirza Ehsan wrote:

If any one can help me in fixing this problem

I propose that you get 2.7.8 working. If the authentication fails, try do do password recovery, or recreated the accounts.

Thanks for the reply. I found problem with existing version. I opened log book group without opening log book details in configuration, that is why at submitting or opening elog was not able to find log book for that group and was getting lost.

Regarding moving to 2.7.8, I want to know that in this new version file location for pwd and log books will remain same or are changed. If changed then I have to change location manually. Also how I can perform password recovery.

Last 3 days of log entries, posted by Paul O'Shaughnessy on Wed Feb 10 15:27:43 2010

Is it possible to create a drop down menu for the last 3 days of log entries. Currently we have the last day, month, 3 month, etc.

Reason being, after a weekend most people would like to view the log entries for the last three days. Can anyone help me out here?

Re: Last 3 days of log entries, posted by David Pilgram on Mon Feb 22 13:21:14 2010

It is a good point, and surprised that this particular number of days was overlooked.

It only needs four lines added into elogd.c to achieve this.  Even with my notorious 
c coding, I did it first time, but as I'm on linux, not a great help for you.  Indeed, 
any other arbitary number of days could be added in, if you have the sources and means 
to recompile.

I think windows versions are only updated on version number, not svn number, so it will 
require a request to the great man himself(*) to produce a new version for windows.

(*)Hint; Stefan likes the occasional beer.


<p>
<table width="98%" align="center" cellspacing="1" style="border:1px solid #486090;">
<tbody>
<tr>
<td cellpadding="3px" style="background-color:#486090; font-weidht:bold; color:white;">Paul O'Shaughnessy
wrote:</td></tr>
<tr>
<td cellpadding="10px" style="background-color:#FFFFB0;"><p>Is it possible to create a drop down menu for the
last 3 days of log entries. Currently we have the last day, month, 3 month, etc.</p>
<p>Reason being, after a weekend most people would like to view the log entries&nbsp;for the last three days.
Can anyone help me out here?</p></td>
</tr>
</tbody>
</table>
</p><p>�</p>

Re: Last 3 days of log entries, posted by Stefan Ritt on Fri Mar 12 09:16:28 2010

> It is a good point, and surprised that this particular number of days was overlooked.
> 
> It only needs four lines added into elogd.c to achieve this.  Even with my notorious 
> c coding, I did it first time, but as I'm on linux, not a great help for you.  Indeed, 
> any other arbitary number of days could be added in, if you have the sources and means 
> to recompile.

David send me his modification and I put it into the main source code, so it will be contained in the next Windows 
version.

> I think windows versions are only updated on version number, not svn number, so it will 
> require a request to the great man himself(*) to produce a new version for windows.
>
> (*)Hint; Stefan likes the occasional beer.

Yepp ;-)

Re: Last 3 days of log entries, posted by Stefan Ritt on Fri Mar 12 16:18:20 2010

> David send me his modification and I put it into the main source code, so it will be contained in the next Windows 
> version.

I made an interim 2.7.8-3 version which contains the fix and can be downloaded from the web site.

Elogd crashes when closing more than ten entries, posted by Cliff Shaw on Fri Mar 12 08:18:06 2010

Hi Stefan,

I have noticed a problem when closing multiple log entries i.e entries which have more than 10 threads. I use Select -> Click the box that appears next to the thread I wish to close -> Edit.

As soon as I click on Edit the elogd service crashes and Windows displays an error message window. The only work around has been opening up all the threads and individually changing the "Status" to Closed.

Forgive me if this issue has been raised before but I have looked throughout the Forum and could not see anyone experiencing the same problem.

Thanks

Cliff

Re: Elogd crashes when closing more than ten entries, posted by Stefan Ritt on Fri Mar 12 13:54:14 2010

Cliff Shaw wrote:

Hi Stefan,

I have noticed a problem when closing multiple log entries i.e entries which have more than 10 threads. I use Select -> Click the box that appears next to the thread I wish to close -> Edit.

Forgive me if this issue has been raised before but I have looked throughout the Forum and could not see anyone experiencing the same problem.

Unfortunately I cannot reproduce your error. In my test set-up it works fine, so it might be related to your configuration. Can you send me your config file, a zip with the needed logbook entries (xxxxxxa.log files), and a recipe what to click exactly in what order.

Show Attributes, posted by Ulf Helmersson on Wed Feb 24 15:54:40 2010

This programing have stoped working, I guess after last update.

Elog is running on Solaris.

Ulf Helmersson

Options Type = Journal Article{1}, Proceeding Article{2}, Book chapter{3}, Book{4}, Patent{5}

{1} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Abbrivated journal name, Volume, First page, Year, Elsevier format, AIP/APS format, IOP format

{2} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Conference name, Place, Country, First page, Year, Month.Days, Volume, Elsevier format Proceeding

{3} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Book Title, Editors, Publisher, Place, First page, Year, Elsevier format Book chapter

{4} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Publisher, Place, First page, Year, Elsevier format Book, IOP format Book

{5} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Patent number, Year, First page, Elsevier format Patent

Re: Show Attributes, posted by Stefan Ritt on Fri Mar 12 12:59:25 2010

Ulf Helmersson wrote:

This programing have stoped working, I guess after last update.

Elog is running on Solaris.

Ulf Helmersson

Options Type = Journal Article{1}, Proceeding Article{2}, Book chapter{3}, Book{4}, Patent{5}

{1} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Abbrivated journal name, Volume, First page, Year, Elsevier format, AIP/APS format, IOP format

{2} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Conference name, Place, Country, First page, Year, Month.Days, Volume, Elsevier format Proceeding

{3} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Book Title, Editors, Publisher, Place, First page, Year, Elsevier format Book chapter

{4} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Publisher, Place, First page, Year, Elsevier format Book, IOP format Book

{5} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Patent number, Year, First page, Elsevier format Patent

The option

Show Attributes =

has been changed to

Show Attributes Edit =

to distinguish between normal entry display an edit mask. So please adjust your configuration file and everything will be fine again.

Goto page Previous 1, 2, 3 ... 115, 116, 117 ... 236, 237, 238 Next

ELOG V3.1.5-3fb85fa6