A certain Lotus Notes "RTVScan" Error has nothing to do with Symantec software

book

Article ID: 156515

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

It has been brought to our attention, that when launching Notes 8.0.2 or 8.5 (Standard or Basic), users intermittently receive one of the following errors:

"0x1B1 - Version mismatch between executable and preexisting shared memory versions! EXITING. You may need to stop RTVSCAN or reboot."

or

"RTVSCAN is operational and may be holding out memory"

 

 

Cause

The IBM Technote, confirms that this error can occur whether you have a Symantec product installed or not.  

- http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21386749

Problem
When launching Notes 8.0.2 or 8.5 (Standard or Basic), users intermittently receive one of the following errors:

"RTVSCAN is operational and may be holding out memory"

- or -

"0x1B1 - Version mismatch between executable and preexisting shared memory versions! EXITING. You may need to stop RTVSCAN or reboot."

Diagnosing the problem
RTVSCAN.exe is a Symantec executable, but this error occurs regardless of whether the user has Symantec installed on the machine or not

Resolving the problem
This issue is fixed in 8.0.2 Fix Pack 2 and 8.5 Fix Pack 1.
 

 

Resolution

This issue is not a Symantec problem, so continue with troubleshooting other lines of equiry you may have.

 

Last update from IBM Tech support when they were queried on this (Mon 21/05/2012)

"The issue seems to be linked to the shared memory handling but is not linked to your software so an update request has been made for the technote in question.

Install the latest version of Lotus Notes, which is 8.5.3 FP1 so if there is still an issue it will be investigated further when customer reports the issue to us."

Also, there is another technote which adds further clarity to the error message and how to troubleshoot it. 

http://www-304.ibm.com/support/docview.wss?uid=swg21410634

 


Applies To

Lotus Notes 8.x

SEP maybe installed, but after testing, it turns out that this error appears even if none of Symantec's software is installed.

Attachments