STATUS CODE 25: Backup jobs fail with Status 25 "cannot connect on socket".

Article:TECH45382  |  Created: 2005-01-05  |  Updated: 2010-01-06  |  Article URL http://www.symantec.com/docs/TECH45382
Article Type
Technical Solution


Environment

Issue



STATUS CODE 25: Backup jobs fail with Status 25 "cannot connect on socket".

Error



error connecting to oprd
cannot connect to VMD(70)
network protocol error(39)
cannot connect on socket

Solution



Overview:
Backup jobs fail with Status 25 "cannot connect on socket". Connection errors are also seen when clicking items in the Administration Console.

When clicking "Devices" in the console, the following error may be seen:
Error connecting to oprd on <servername>: cannot connect to VMD(70)

When clicking "Media" in the console, the following error may be seen:
Error connecting to oprd on <servername>: network protocol error(39)

Troubleshooting:
Reviewing the log files will reveal more specific details on the connection errors experienced.  This group of symptoms has been seen in cases where the default port ranges have been changed on a master or media server to a much more constricted setting, causing Veritas NetBackup (tm) to run out of ports to use.  

For example, the default "Server Port Window" is from 1025 to 5000.  If this port window were to be changed to a value from 1025 to 1125, this sort of problem can be seen.  Investigate the port range settings on NetBackup master and media servers, starting with the master server.  

To view the port range settings on a NetBackup server:

1. Launch the NetBackup Administration Console and connect to the master server
2. Expand Host Properties in the left pane and click Master Server or Media Server
3. Double click the actual name of the desired server in the right pane
4. In the Server Properties window, click Port Ranges and view all port range settings

Figure 1 notes the default port settings, as seen on a master server.

Figure 1.
 


Media Server Log Files:  
<Install_path>\volmgr\debug\daemon log
13:10:27.432 [14832.14532] <16> emmlib_initializeEx: (-) Failed to resolve EMM server reference implies that EMM could not be initialized via the PBX component

bptm log
03:55:58.955 [3028.3024] <16> ConnectToServerInterface: failed to connect to desired interface in job manager
03:55:58.955 [3028.3024] <16> initializeJmComm: RequestMultipleResources : ConnectToServerInterface on server [servername] fails [25]

19:30:08.686 [11696.11652] <16> emmlib_initializeEx: (-) Failed to resolve EMM server reference
19:30:13.686 [11696.11652] <16> db_getSTUNIT: (-) Translating EMM_ERROR_CorbaResolveReference(3000005) to 25 in the NetBackup context
19:30:13.686 [11696.11652] <16> db_getSTUNIT: error (25) initializing EMM interface.

19:30:13.749 [11696.11652] <2> db_error_add_to_file: dberrorq.c:midnite = 1132898400
19:30:13.749 [11696.11652] <16> setup_twin_parameters: db_getSTUNITlist() failed: cannot connect on socket (25), cannot continue with copy 1


Resolution:
If port ranges have been constricted for any servers, change the port range settings to a more flexible range, or click the "Defaults" button to recall the default port settings in NetBackup.  Click Ok.  It may be necessary to stop and restart NetBackup services on the server for the changes to take effect.  

For further information on configuring NetBackup port range settings, refer to the VERITAS NetBackup (tm) 6.0 System Administrator's Guide for Windows, Volume 1 (referenced below)

Note: When changing port range settings for a NetBackup server, ensure that firewalls allow communication on the ports that are designated for NetBackup to use.  If port ranges are increased within NetBackup, but the network configuration does not allow the use of those ports, errors will continue to occur.



Supplemental Materials

SourceError Code
Value39
DescriptionNetBackup Error 39: network protocol error

SourceError Code
Value70
DescriptionNetBackup Error 70: cannot connect to VMD

SourceError Code
Value25
DescriptionNetBackup Error 25: cannot connect on socket


Legacy ID



280745


Article URL http://www.symantec.com/docs/TECH45382


Terms of use for this information are found in Legal Notices