1) It seems to be caused by any and all attachments. We've tried 2k, 2MB, and 20MB. They all seems to result in the same problem.
2) Yes we run Symantec Anti-Virus. The email scanning portion of it was disabled for I thought it may have been causing the problem.
3) There was 1 other addin (Adobe Acrobat) that was running. I've since disabled / uninstalled them to eliminate them as the culprit.
Quote:
Originally Posted by fsiegel  A few more questions:
1) Is this error caused by all attachments, or just those greater than a given size. [What happens with a 1K attachment?] And if there is a size threshold, what is it?
2) Is there any anti-virus software on the suspect machines that could be causing problems?
3) Are there any Outlook addins (besides ours) on these machines that could be causing problems.
Thanks |
The problem is occuring with every user who has the Outlook connector. It isn't any single user that is having this problem. If they have the outlook connector they can't send attachment outside the local domains.
The timeouts were reset when i upgraded the client to 5.0.3, but I've increased the timeout and the error is still occuring. As far as any patches that were autoinstalled there are none that I can find. The windows autoupdate is enabled, but I didn't find any updates that were installed during the time it worked and when it quit. When i change the timeout for sending Outlook always goes into Offline mode with the message
"The settings for connecting to the Zimbra server may be inforrect. Please verify that they are correct. A common cause of this error is an incorrect value for User Secure Connection. Outlook Will be set to Offline Mode."
The client is *not* using secure mode and the server address is set correctly. The username and password are both correct. If i take Outlook out of offline mode it works fine until it tried to send the message with an attachment again.
Quote:
Originally Posted by fsiegel I'm working on this one. I looked at the latest logs, and I don't believe it's bug 24740. In that one, the server would terminate the connection, and this has been fixed in 5.0.3. But from these logs, it looks like the same old timeout issue that you have always had. It's a 12002 error, not a 12030. I assume that your registry settings are still bumped up?
It seems like a flaky connection. I know it works with the web client, but did you try moving the problem users to another network port? I know that when I was investigating bug 24740, I could only reproduce it from home, with the slower connection speed.
Also, you mentioned that after reinstalling Outlook, it worked again, and then stopped working. Was there some auto update that possibly installed a later Outlook patch?
Thanks |