SAP BusinessObjects and Antivirus Software

Founder of antivirus software company? Or overworked SAP BusinessObjects administrator? You decide.

I’ve always had a love/hate relationship with SAP BusinessObjects installations and antivirus software. My first experiences with installing XI R2 went badly when antivirus software was still running, frequently resulting in botched WAR file deployments. And who can forget the joy of SAP BusinessObjects Enterprise XI 3.1 SP2 and its crawling installation process? Although the root cause was the Microsoft installer, SAP also advised in KB 1374386 to“disable the antivirus before starting the install so that this does not interfere with the install process”.

While most organizations rely on the big vendors like Symantec or McAfee (the latter company has a more colorful history than the former- hence the photo above), I recently had a situation with Trend Micro antivirus preventing the installation program from running properly. The installer would fail with a “failed to update cache for execution” error. The error can either be triggered by antivirus software (see SAP KB 1781641) although it can also be triggered by the Microsoft User Account Control (UAC) setting (see SAP KB 1671421).

Let’s review some best practices for working with SAP BusinessObjects and antivirus software.

Pre-installation Best Practices

During the kickoff meeting for an installation or upgrade project, determine the vendor and version of the antivirus software in use. Next, identify the person who administers the antivirus software who will assist, if necessary, during the installation process. It’s really important to identify this person, even if everyone in the kickoff meeting begins to stare uncomfortably at their shoes when you pose the question. Determine if the software can either be disabled for the duration of the installation process or if the folder location of the installation can be permanently exempted from scans. Lastly, find out if you can make the necessary changes yourself or if you’ll need to ask a system administrator. With my recent Trend Micro experience, I could see the antivirus software running in the Windows system tray but not any active exemptions. In addition, I had to ask an administrator to make the necessary exemptions from a centralized console that I did not have access to.

Installation Best Practices

Disable the services associated with the antivirus program so they are not running during the installation process. Work with your organization’s system administration team if you’re unable to figure out how to do this. It’s critical that the antivirus program doesn’t interfere with a successful installation of SAP BusinessObjects. The installation will be faster if the antivirus program isn’t analyzing it.

Post-installation Best Practices

Determine what the permanent solution for antivirus software will be after the installation of SAP BusinessObjects. Will the SAP installation folder be exempted from scans? Will specific SAP programs be exempted? Look for a permanent solution for dealing with antivirus software during the project kickoff meeting. If the exemptions are only temporary during the installation process, it is likely that they’ll become a thorn in somebody’s side when it comes time to apply a support pack or patch.

Thus Saith SAP

In many cases, it takes documentation from the vendor to successfully lobby for an exemption to corporate security policies. Here are some relevant knowledge base articles from SAP that you can reference to help your organization work toward a solution.

  • SAP KB 106267 – generic note about SAP and antivirus software, not specific to SAP BusinessObjects
  • SAP KB 1497394 – Which files and directories should be excluded from an antivirus scan for SAP BusinessObjects Business Intelligence Platform products in Windows?
  • SAP KB 1781641 – “Failed to update cache for execution” error occurred while installing SAP BusinessObjects Business Intelligence 4.0.
  • SAP KB 1984459 – Which files and directories should be excluded from an antivirus scan for SAP Data Services

Do you have horror stories of SAP BusinessObjects installations gone bad due to antivirus software? Any best practices that I haven’t mentioned? Please share your thoughts below.

Dallas Marks

Dallas Marks

I am an analytics and cloud architect, author, and trainer. An AWS certified blogger, SAP Mentor Alumni and co-author of the SAP Press book SAP BusinessObjects Web Intelligence: The Comprehensive Guide, I prefer piano keyboards over computer keyboards when not blogging or tweeting.

6 thoughts on “SAP BusinessObjects and Antivirus Software

  1. Hi Dallas,

    I have an identical error generated during SAP BI 4.1 [build] installation. We have Trend Micro Antivirus installed on our servers as well. However, surprisingly, this is the third installation of BI 4.1 on those servers, while the first two were successful with no indication of this issue (despite there were others).


    1. Erik,

      Thanks for sharing. In general, life is better when AV is given exceptions for BusinessObjects. The control freak part of my personality didn’t like Trend Micro, because I had no way of confirming from the server that AV was truly disabled. Good luck with your BI 4.1!


    2. I need to disable antivirus software, but security people don t allow it. My problem is when installing SAP data services SP14. Is there any workaround? I do not know what to do.

      1. I understand. This is where you need to share the relevant SAP KB articles with your manager and have them go talk to their manager. Hope you’re successful!

  2. Dallas,

    I’ve encountered a few BI 4.1 implementations where the symptom was a “File not found in the repository” error message when an instance was scheduled. Turning off AV (and subsequently upgrading it and implementing exclusions resolved this issue for the most part.

    The issue persists for a very specific report however the cause may be capacity as that report runs concurrently with some Lotus Notes reports that consume substantial memory and CPU resources.


    Herb Hess

Comments are closed.