can't open attachment from outlook

Discussion in 'ESET NOD32 Antivirus' started by ogsi, Dec 8, 2009.

Thread Status:
Not open for further replies.
  1. ogsi

    ogsi Registered Member

    Joined:
    Mar 16, 2007
    Posts:
    28
    Office 2003 on WinXP SP2 with NOD32 anti virus 4.0.474
    this user receive 2 excel attachments on a daily basis. one contain a macro.
    few days ago he started poping an error (see attachment) when opening the one with the macro. the 2nd attachment open just fine
    I've sent the email to another client (non outlook) and the macro file open fine.
    I followed this: http://support.microsoft.com/kb/305982 but both folder and reg key already in place.
    knowing that it is not the file (which open out of outlook), not the local excel or outlook (the 2nd file in the same email open just fine) I suspect the NOD32 scanning on outlook to be the reason
    any ideas?
     

    Attached Files:

  2. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
    can it be opened if the attachment is saved locally?
     
  3. ogsi

    ogsi Registered Member

    Joined:
    Mar 16, 2007
    Posts:
    28
    no.
    it cannot be saved locally or open directly from the email
    when the same file is opened via non-outlook email client I can open directly or save locally
     
  4. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    Hello,

    If you disable Outlook integration on the client, will it allow you to save the file? This will determine if the ESET email integration could be causing the problem.
     
  5. ogsi

    ogsi Registered Member

    Joined:
    Mar 16, 2007
    Posts:
    28
    it is still won't open after the email client is disabled
     
  6. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    If the registry is already set to the new temp directory, you will need to create a new folder and set the registry to point to that one. Since disabling Outlook integration did not remedy the issue, there seems to be an issue with something else.
     
Thread Status:
Not open for further replies.