The attempt to select Lotus Domino databases for backup results in the error 'No data stores can be initialized. The software is most likely installed incorrectly'
|Article:TECH157608|||||Created: 2011-04-07|||||Updated: 2013-03-23|||||Article URL http://www.symantec.com/docs/TECH157608|
When trying to select Lotus Domino databases for backup by expanding the 'Lotus Domino Databases' volume icons the following errors may occur:
'No data stores can be initialized. The software is most likely installed incorrectly'
'The Lotus Domino data stores cannot be initialized because Lotus Domino may have been installed incorrectly. Re-installing Lotus Domino may resolve the issue.'
V-79-57344-39577 - The Lotus Domino data stores cannot be initialized because Lotus Domino may have been installed incorrectly. Re-installing Lotus Domino may resolve the issue.
There are multiple possible causes of this error message related to Domino installation or configuration. These causes are:
1) An upgrade to the Domino server software or a patch installation, can result in older Domino DLLs being left behind that the Backup Exec Domino agent attempts to use.
2) The notes.ini initialization file for Domino server does not exist where indicated by the Lotus Domino registry
3) The Domino Server console is secured
4) The location of the Domino server binaries or data location is not accurately reflected in the Lotus Domino registry
5) A 32 bit installation of Domino server is on a 64 bit server that has remnants of an old 64 bit installation of Domino server in the registry
6) An incorrect entry for the Domino binaries location is in the Windows Path environment variable.
7.) Windows Firewall installation inhibiting the Lotus Agent from opening a named pipe locally on the Domino server preventing Domino Server and the Remote Agent from communicating.
Warning : Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
1) An upgrade to the Domino server software results in older version Domino DLLs being left behind that the Backup Exec Lotus Domino agent attempts to use in communicating with Domino Server.
There are multiple Domino server DLLs that the Backup Exec Domino agent depends on to make an API connection to the Domino server. If the Backup Exec Domino agent tries to use outdated or incorrect-versioned DLLs to make this connection the subject error message may occur. The DLL files are normally read from the Lotus Domino binaries folder which is typically X:\...Lotus\Domino\ but the Windows environment variable 'Path' is also followed in searching for these DLL files.
Example: Lotus Domino is installed in d:\Lotus\Domino and has a copy of NNOTES.DLL located in that folder as expected. The c:\windows\system32 folder also has a copy of NNOTES.DLL that is an earlier version. Since this older file is in the system Path, it may be used by the Backup Exec Remote Agent for the API connection to Domino server and fail. The file in the c:\windows\system32 folder needs to be made unavailable to the Remote Agent.
Locate all copies of the following DLLs on the Domino server and rename those with an extension of 'old' that are not consistent with the installed version of the Domino server:
NOTE: These DLLs are used by beremote.exe during Backup Exec Remote Agent service startup. To confirm what DLLs the Remote Agent is using, a file system monitoring utility such as Microsoft's Process Monitor may be employed. See http://technet.microsoft.com/en-us/sysinternals for these utilities. Monitor the attempt to browse the Lotus Domino databases and watch the locations of each of the DLL files the Remote Agent processes beremote.exe or belnapi.exe read.
IMPORTANT: It is common for the Lotus Notes or the Domino Administrator applications to be present on the Domino server. Some of these same named DLLs may be present for these applications. These files are commonly located in X:\...Lotus\Notes folder. These DLLs should never be renamed.
2) The Lotus Domino initialization file, NOTES.INI is not located in the folder specified in the Lotus Domino registry.
The NOTES.INI file is used in the initialization of the Domino server during startup. It is also used in making a connection between the Backup Exec Remote Agent (beremote.exe) and Domino server. The customary location for this file is in the Domino server binaries location for an un-partitioned Domino server and in the Domino data location for a partitioned Domino server. These locations are specified in the Lotus Domino registry and must be confirmed correct before the Backup Exec Domino agent will connect to Domino server. The following are the locations in the registry for each which should contain and accurate path location.
Un-partitioned Domino Server (single data location, single notes.ini) - HKLM\SOFTWARE\Lotus\Domino\1\Path
Partitioned Domino Server (multiple data locations and notes.ini files) - HKLM\SOFTWARE\Lotus\Domino\1\DataPath and HKLM\SOFTWARE\Lotus\Domino\2\DataPath
3) The Domino console is secured. The Domino console can be set as secure to prevent unauthorized access.
Evidence of this setting is contained in the Notes.ini file with the following line:
SERVER_CONSOLE_PASSWORD=6A624D2C 1F91DE33 BB6289D3 9A282192 (HEX code value will vary)
In order to browse and back up Domino databases, the Domino console must not be secured. This can be turned off within the Server Tools section properties of the Domino server Configuration in Domino Administrator.
4) The location of the Domino server binaries or data is not accurately reflected in the Lotus Domino registry.
The two pointers used are 'DataPath' and 'Path' for the Domino data location and binaries location respectively. Depending on whether the Domino server was installed partitioned (multiple data locations) there may be multiple locations. See Step 2 above for the registry locations of these paths and insure that they accurately reflect the location for Domino server data.
5) A 32 bit installation of Domino server is on a 64 bit server that has remnants of an old 64 bit installation of Domino server in the registry.
A 32 bit Domino Installation creates the registry entries in the following path : HKLM\Software\WoW6432Node\Lotus\Domino but if there are entries for an old 64 bit installation of Domino left in HKLM\SOFTWARE\Lotus\Domino the subject error will be returned. This is caused by the Backup Exec detection process for Domino Server looking in the 64 bit registry location first. In this scenario, an old 64 bit Domino Server installation wasn't removed entirely and the registry remnants caused an attempt to connect to a nonexistent installation of Domino Server.
Remove the registry entry “HKLM\Software\Lotus\Domino” to resolve this Issue
6) As the Backup Exec Remote Agent starts up, detects Domino Server, and makes a connection to Domino, the system path is followed to locate various Domino Server DLLs.
If there is an old or malformed entry for the location of these files that prevents the Remote Agent from finding them, the subject error will be received. The Windows Path can be viewed and edited by going to Computer Properties | Advanced System Settings | Environment Variables | System variables | Path. Look through the path statement to see if the path to the Lotus Domino binaries is present. If so, verify that the path is formed correctly. Below is an example of a system path with the correct location for the Domino Server binaries.
7) Check the firewall policy to make sure it is not blocking the Backup Exec Remote Agent and Lotus Agent executables in the RAWS folder(beremote.exe and belnapi.exe). Try disabling any third party or native Windows Firewall for testing..
"The Lotus Domino data stores cannot be initialized because Lotus Domino may have been installed incorrectly. Re-installing Lotus Domino may resolve the issue."
Article URL http://www.symantec.com/docs/TECH157608