IBM i NetServer Debug Checklist for Startup Failures

Resolving The Problem

This document provides a listing of known reason codes and items to check when IBM i NetServer fails to start.

Starting IBM i NetServer using System i Navigator:

To start NetServer from System i Navigator, you should do the following:

1.	Open System i Navigator.
2.	Expand My Connections.
3.	Expand the IBM System i connection.
4.	Expand Network.
5.	Expand Servers, and select TCP/IP.
6.	When the list of TCP/IP servers is shown on the right side of the screen, right click on i5/OS NetServer and select Start.

Starting IBM i NetServer using IBM Navigator for i

To start NetServer from IBM Navigator for i, you should do the following:

1.	Open IBM Navigator for i
2.	Expand IBM i Management
3.	Expand Network
4.	Expand Servers, and select TCP/IP Servers
5.	When the list of TCP/IP servers is shown on the right side of the screen, select IBM i NetServer
6.	Expand the Actions drop down menu and select start

Starting IBM i NetServer from an IBM i Command Line (Emulation session):

To start NetServer from the IBM i Command line, you should do the following:

STRTCPSVR SERVER(*NETSVR)


If NetServer starts successfully, the QSYSOPR message queue will contain message CPIB680 - IBM i Support for Windows Network Neighborhood (IBM i NetServer) initialization complete. The QZLSSERVER job will then be active in the QSERVER subsystem and should have an EVTW status. WRKACTJOB SBS(QSERVER) can be used to determine the status of the job.

If NetServer fails to start, the QSYSOPR Message queue (and also in the QHST History log) will contain message CPIB683 IBM i Support for Windows Network Neighborhood (IBM i NetServer) was unable to start. Message CPIB683 will include both a Reason Code and a Return Code that will provide information about why the NetServer did not start.

To locate the CPIB683 message, type one of the following commands on the operating system command line:

DSPMSG QSYSOPR

or

DSPLOG QHST JOB(QZLSSERVER)

Press the Enter key.

For a list of common NetServer startup errors and possible causes, review the chart below.

The Reason Codes and Return Codes in the chart are not necessarily in numerical order.

CPIB683	IBM i Support for Windows Network Neighborhood (IBM i NetServer) was unable to start. CPIB683 always contains a reason code and (or) a return code in the message text, that indicates the cause of the failure. Unexplained Return Codes can be displayed with DSPMSGD CPEnnnn (for example, for RC3021 use DSPMSGD CPE3021). Here are some common Return Codes that might be seen on a CPIB683: RC3028 Message data is not valid. RC3401 Permission denied. RC3406 Operation would have caused the process to be suspended. A resource is temporarily unavailable. RC3409 Operation timed out. RC3418 Possible APAR condition or hardware failure. RC3420 Address already in use. RC3421 Address not available. RC3423 Operation already in progress. RC3435 Cannot reach the destination network. RC3448 The protocol required to support the specified address family is not available at this time. RC3500 Object is a read only object.
CPIB683 RC4	Unable to obtain lock for service program QZLSSRV1 in library QSYS. WRKOBJLCK QZLSSRV1 *SRVPGM End any job that has a lock on QZLSSRV1. If that does not work, try calling the API to end NetServer and then call the API to restart NetServer with a reset. CALL QZLSENDS PARM(x'00000000') CALL QZLSSTRS PARM('1' x'00000000') If still no success, contact Support for assistance in collecting a TASKINFO dump.
CPIB683 RC5 RC1	Start of NetBIOS over TCP/IP failed with return code 1. Try starting NetServer with the reset option. The API to reset and start NetServer is: CALL QZLSSTRS PARM('1' x'00000000') or take the option to Reset and Start from System i Navigator.
CPIB683 RC5 RC3406	This RC indicates a timing problem in which the QSERVER subsystem isn't active (or isn't finished starting) when the NetServer attempts to start. A timing problem can be confirmed by reviewing the QHST History log. The easiest way to do this is to do a DSPLOG OUTPUT(*PRINT) , specifying the beginning and ending Date and Time so that the time span included is that in which the IBM i Start-up program was running (at IPL time or after the system comes up from a Restricted State.) Search the resulting QPDSPLOG Spooled File for the word QSERVER, searching repeatedly until you find the last message indicating that QSERVER if fully active, then make note of the timestamp on that message. If it is after the timestamp on the CPIB683 message, then the problem can probably be corrected by removing the option to start NetServer automatically (from the System i Navigator NetServer Properties) and adding the following to the Start-Up Program, just prior to the DONE: label. DLYJOB DLY(300) STRTCPSVR *NETSVR See Technote N1019476,Changing the IPL Start-Up Program: for an example of the default Start-Up Program.
CPIB683 RC5 RC3409	This return code indicates a timeout. Ensure the TCP/IP interface is active. Refer IBM i Technote N1014374, iSeries NetServer Fails to Start with CPIB683 RC5 RC3409 . For OS V5R4 V5R4M5 V6R1 V6R1M1 V7R1, see APAR MA42411.
CPIB683 RC5 RC3418	Start of NetBIOS over TCP/IP failed with return code 3418. Problems could have been caused by using a Port Scanner on the Network, if TCP Connections are in Close-wait status. A port scanner can cause orphaned TCP/IP connections that need to be cleaned up by ending and restarting TCP/IP. If NETSTAT *CNN is run and there are NetBios jobs found (possibly in closed status), selecting Option 4 to end them may clean up the port and allow NetServer to be started. There were PTFs for this issue at OS V5R1. The problem has not been encountered in newer OS versions, and if it is encountered, IBM Support should be notified so it can be investigated. Problems caused by having port restrictions configured for the *UDP ports should be resolved by removing restrictions for ports 137-139.
CPIB683 RC5 RC3420	Start of NetBIOS over TCP/IP failed with return code 3420. This error indicates there is another computer on the network already using the name configured for the IBM i NetServer. Networking protocols do not allow two devices with the same name on the network. It can be caused by a TCP/IP address conflict in the Domain Name Server (DNS) or WINS Server entries for the IBM i system name or the NetServer name. This error can also occur on IBM i systems with multiple partitions if the NetServers on each partition are configured to use the same name. Or, it can occur at upgrade time. For example, of you did a SAV of the IFS and copied IFS data that included the NetServer configuration files, from one partition to another. Then later, you had both partitions (or both systems) active and tried to start NetServer on both at the same time without having renamed the NetServer on one of the systems. Note: NetServer configuration files are located in the /qibm/userdata/OS400/NetServer directory. Other causes include configuring the NetServer to use the same name as the IBM i or as a Windows Workgroup or Domain having the same name as the NetServer. Try PINGing the NetServer name to see what TCP/IP address is being returned. However, remember that the NetServer name must be unique on the network in order for NetServer to start. If NetServer is active on another IBM i or if the name is assumed by something else on the network, NetServer will fail to start with CPIB683 RC5 RC3420 even if the PING command does not find anything for the name. Changing the NetServer name to one that is not being used on the network will allow it to start successfully. If it is necessary to determine which device is reporting the name conflict, contact your service representative at the Rochester Support Center for assistance.
CPIB683 RC5 RC3448	Start of NetBIOS over TCP/IP failed with return code 3448. TCP/IP is not active, the TCP/IP interface is not defined, or the interface is not active. To determine if the interface is active, use CFGTCP, Option 1. If there is already a valid, active TCP/IP interface for NetServer to use when it starts, verify that there is an IBM i host table entry for the server name that NetServer is using. For OS V7R1, see the following APARS: SE44999 MA40099 MA40025
CPIB683 RC6 RC16	Start of the internal server failed with return code 16. Similar to RC3420. RC16 generally indicates a name conflict between the NetServer name and something else on the network. Refer to the following IBM i Technote: N1010610, NetServer Fails to Start and Issues CPIB683 RC6 RC16
CPIB683 RC6 RC3409	Start of the internal server failed with return code 3409. IBM i NetServer ends normally after being started. If the NetServer name is the same as the NetServer domain name, change one of them. If a search for the TCP/IP address of the IBM i system in Network Places finds the NetServer with a location of Entire Network try changing the NetServer name to something different and restarting NetServer . The Wins Scope ID might not be properly configured in the NetServer Properties. Try setting it to a blank. Also, refer to the following IBM i Technote: N1017510 CPIB683 RC3409 NetServer Does Not Start When WINS Scope ID Is Not Configured Correctly
CPIB683 RC6 RC3420	Start of the internal server failed with return code 3420. To correct the problem: 1. Issue the command NETSTAT *CNN and press the Enter key. 2. Press F13 to sort by Local Port. 3. Page down to port 445/CIFS. 4 . Use Option 4 to end all active 445/CIFS ports. After the port is ended, NetServer can be restarted from System i Navigator or with the following commands: STRTCPSVR *NETSVR or CALL QZLSSTRS PARM('1' x'00000000')
CPIB683 RC6 RC3436	There is not enough buffer space for the requested operation. For OS V5R4 and V5R4M5, see APAR MA35098.
CPIB683 RC5 or RC6 RC3423	Start of the internal server failed with return code 3423. An IBM i NetServer session might be hung on the system and must be ended for NetServer to start successfully. Recycling QZLSFILE jobs followed by starting NetServer with a reset might correct the problem. The following OS/400 or i5/OS command line API calls are recommended for ending and restarting NetServer with the reset option: CALL QZLSENDS PARM(x'00000000') CALL QZLSSTRS PARM('1' x'00000000') Check the QSYS/QPWFSERVER class Default Wait Time parameter. The default is 30 seconds. A smaller value might cause NetServer to fail to start with a RC6 RC3423. This reason code can be caused by other APAR conditions where IBM i NetServer is not ending or starting properly. Development might request a LIC trace or TASKINFO dump if the measures above do not correct the problem. For information on taking the trace and/or dump, refer to the links in the section below called Check the Following Additional Items. Refer to the following IBM i Technote and APARs: N1010611, NetServer Fails to Start with Error CPIB683 RC6 RC3423 For OS V5R4, see APAR MA34146 For OS V5R4M5, V6R1, V6R1M1, and V7R1, see APAR MA39192 For OS V7R1 see APAR MA40754
CPIB683 RC12	This error can be caused by setting the IBM i NetServer code page incorrectly. This can happen when NetServer is configured to use an EBCDIC CCSID rather than an ASCII CCSID. The resolution is to use System i Navigator to configure NetServer, and ensure that the CCSID on the Advanced tab is an ASCII CCSID. The default is 0. Use the Next Start button to change the CCSID, if necessary. If any of the settings are changed, NetServer must be restarted before the changes take effect.
CPIB683 RC13	An incorrect TCP/IP address is configured for the IBM i NetServer name or too many interfaces are configured for the current code level. In CFGTCP, verify that Domain Host name is correct (Option 12) and the Interface TCP/IP address (Option 1) is correct. Verify the name and TCP/IP are correct on the DNS server and/or WINS server. If changes have recently been made on the DNS, check to be sure that a valid IP address is listed there for the NetServer name. In NetServer Properties, try removing the WINS server TCP/IP address and test whether NetServer starts. Historical Information: Check to see how many interfaces are configured. If there are more than 128 interfaces configured on the system, for 'Out of Service' OS versions V5R1 and V5R2 only, see APAR SE12666:
CPIB687	i5/OS Support for Windows Network Neighborhood started, but an error was encountered. The required IBM i Support for Windows Network Neighborhood (IBM i NetServer) job QZLSSERVER started but may not be fully functional. The return code in the message text will indicate the cause of the problem. Unexplained Return Codes can be displayed with DSPMSGD CPEnnnn (for example, for RC3021 use DSPMSGD CPE3021). Here are some common Return Codes that might be seen on a CPIB687: RC3021 The value specified for the argument is not correct. RC3435 Cannot reach the destination network.
CPIB687 RC1 RC3021	NetBIOS over TCP/IP started with errors - return code 3021. The IBM i TCP/IP domain information or the local host information is not correct (CFGTCP Option 12). The IBM i current system name should have an entry in the TCP/IP Host Table entries (CFGTCP, Option 10).
CPIB687 RC1 RC3435	NetBIOS over TCP/IP started with errors - return code 3435. The configured primary and/or secondary WINS server is not accessible or functioning properly. Verify the IBM i NetServer configuration and determine if the WINS addresses are correct. Reconfigure or verify that these system are functioning WINS servers. Help text for the error reads: If the return code specified is 3435, check that your network's Primary WINS server is functioning properly. If your network has a Secondary WINS server configured, check to see that it is functioning properly. As a result of the error, Netserver will be started; however, no Netserver name to IP resolution will be done. No one will be able to connect to the Netserver unless they are on the local network or an LMHOST file is created on the connecting PC (for name to IP resolution). This problem might be caused by an incorrect IP address entry (for this Netserver) on the DNS (Domain Name Server) controller. In this case, the IP address should be corrected and the NetServer restarted to resolve the problem.
CPIB687 RC2 (or) RC4	A Logon Server or Domain Master Browser service already running on &4 conflicts with theIBM i NetServer. NetServer is attempting to start as the Master browser on the network but another Master browser is already active. In the NetServer Properties, change the Logon Server Roll from Server to None.
CPIB689 RC2	Print shares could not be published or updated because of an internal error. These messages do not indicate a problem and will be eliminated in a future release.

Note: The list above is not comprehensive. Search IBM i Support for message IDs (CPIB68x RCx) because new Technotes are added as new errors and causes are discovered.

Hints: Check System i Navigator's i5/OS NetServer Properties for the Following

o	The NetServer name must be unique on the network. However it can be the same as the System i name (for the system on which it exists).
o	If using the IBM i system name for the NetServer name, uncheck Allow i5/OS NetServer access using the system name.
o	On the Advanced tab, confirm that the Coded Character Set ID is set to 0-Use i5/OS NetServer CCSID or to a valid ASCII CCSID.
o	On the WINS Configuration tab, if the WINS Scope ID in the NetServer configuration is set to @, remove the @ and leave the scope ID blank.

Check the Following Additional Items

o	Operating system release and cumulative tape level.
o	Current IBM i NetServer PTFs are applied. Get the current PTF listing for IBM i NetServer. The following document provides links to lists the latest PTFs that are not on a cumulative PTF package: http://www-01.ibm.com/support/docview.wss?uid=nas8N1021480
o	QSERVER subsystem is active.
o	QSERVER autostart job must be active in the QSERVER subsystem. Check the joblog for errors.
o	Check for QZLSSERVER joblogs for errors (WRKSPLF QPGMR).
o	TCP/IP must be active. Verify that the IBM i current system name viewed from DSPNETA is in the Hosts table (CFGTCP Option 10) and that the Internet address is a TCP interface that is defined and active (CFGTCP Option 1). Network Print also requires that the Loopback interface be active.
o	From an operating system command line, run NETSTAT *CNN. If NetServer is not active, there should not be any NetBIOS nor CIFS jobs under the Local Port column. If there are NetBIOS (ports 137,138,139) or CIFS (port 445) jobs listed, record the state of the job and use Opt 8=Display jobs to check the task the job is on. This information will be useful to your Support Representative.
o	If NetServer did not end cleanly or completely, use the following command line APIs to end, reset, and start it: CALL QZLSENDS PARM(x'00000000') CALL QZLSSTRS PARM('1' x'00000000')
o	Check for any VLOGs with major code 4400 or 4401 (Major Descriptions of Server Message Block or NetBIOS).
o	NBT Dump (dump of the NBT name service) if requested by your Support Representative. This dump is collected by issuing a CALL QSOMAINT PARM('4' '7'). This will generate a VLOG (4401/9904) that contains a dump of the NBT name service.

IBM i NetServer Fails to Start with an IPL, however, it Starts from an Operating System Command Line

If NetServer starts from the operating system command line, but fails from the QSTRUPPGM, there may be a timing problem. QSYSOPR may contain message CPIB683 RC5 RC3448. See the section on RC5 RC3448 above.

Additionally, if there are no QZLSSERVER messages in the history log but the NetServer is set to start with TCP, then the QSERVER subsystem was not started before TCP attempted to start the NetServer. This is also a timing issue. See the section on RC5 RC3406 above for details on resolving.