Endpoint Protection

 View Only
  • 1.  Client machine getting a Runtime Error

    Posted Nov 12, 2009 09:24 AM
    Program: C:\program files\symantec AntiVirus\Rtvscan.exe

    This application has requested the runtime to terminate it in an unsual way.
    Please contact the application's support team for more information.

    We're currently in the test phase of migrating to SEP and I've installed it on about a dozen machines. With such a small test base I wouldn't expect as many problems as I've encountered.  Particularly with the windows 7 systems and this one XP system. Anyhow, the client system that recieved this message has so on two occasions.  The day after it was installed and now about two weeks later.  It appears for no particular reason.  Client machine is running Windows XP SP 3, SEP 11.0.5.  I've searched for a fix on this one and have come up empty handed.  More importantly than a fix, is there anyway to avoid these types of issues? Before the end of the year we'll be pushing this out building by building on the campus and it'd be nice if we could minimize the amount of issues our support staff sees.


    Side note: Unrelated most likely but this same machine also gave me this error previously: "Symantec AntiVirus 10.1" (C:\program files\symantec Antivirus\vpmsece4.dll) cannot be loaded and has been disabled by Outlook.  Please contact the add-in manufacturer for an update. If no update is available, please uninstall the add-in.  This error was fixed by deleting the extend.dat file and has not recurred.


  • 2.  RE: Client machine getting a Runtime Error

    Posted Nov 12, 2009 09:40 AM
    Have you tried this.

    Error: "Runtime error! Program: C:\Program Files\Symantec Antivirus\rtvscan.exe R6025 pure virtual function call" while running a scan


    http://service1.symantec.com/SUPPORT/ent-security.nsf/2326c6a13572aeb788257363002b62aa/a7ee65aaf2e5c79d65257409000f332f?OpenDocument


  • 3.  RE: Client machine getting a Runtime Error

    Posted Nov 12, 2009 12:32 PM
    I appreciate your response, I will completely remove the install on that machine and try again.

    I may have to call symantec on this to get some answers since we have a service contract. honestly, reinstalling isn't a proper solution. If this happens 1/10 times in our network after pushing the install that could potentially cause us to have to touch 100 machines which is unacceptable. The article you linked me to does not state what causes the error so that prevents me from having any idea of how to prevent it.

    Thanks again