Home > Return Code > Return Code 3420

Return Code 3420

CPIB683 RC5 RC3448 Start of NetBIOS over TCP/IP failed with return code 3448. Note:  This may affect otherusers. Recovery: Complete recovery for the specified reason code. 5 - Start iSeries NetServer with the reset option using the Start Server (QZLSSTRS) API. iSeries Installation Estimation > PTFs for V4R4 and V4R5 (?) > B. check over here

For complete classification of this Act to the Code, see Short Title note set out under section 951 of Title 21 and Tables. Browse by Topic AS/400 Business Intelligence Career Development Channel Cloud Computing Compliance Consumerization Content Management CRM Data Management Database DataCenter Desktop Management Development Email Administration Hardware IT Strategy Linux Lotus Domino CRPence 2008-02-01 17:48:52 UTC PermalinkRaw Message Was the recovery procedure for RC13 followed as suggested?Regards, Chuck--All comments provided "as is" with no warranties of any kindwhatsoever and may not represent positions, Search form Search About LII Who We Are What We Do Who Pays For This Contact Us Get the law Constitution Supreme Court U.S.

However, remember that the NetServer name must be unique on the network in order for NetServer to start. IBM i NetServer Startup Failure Messages The Reason Codes and Return Codes in the chart are not necessarily in numerical order. iSeries Operations Console Update > C. 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.

And maybe have them > on > hand BEFORE I begin the upgrade? > > 2. WRKOBJLCK QZLSSRV1 *SRVPGM End any job that has a lock on QZLSSRV1. Full details are available here. o TCP/IP must be active.

NetServer fails to start If AS/400 NetServer fails to start and you see the following message in QSYSOPR: Message ID . . . . . . : CPIB683 Severity . . 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. Checking the PC configuration verifiedthe Windows Workgroup name was the same as the NetServer. pop over to these guys Note: This mayaffectother users.

E-mail: Submit Your password has been sent to:[email protected] tech target logo About Us Contact Us FAQ Community Blog TechTarget Corporate Site Terms of Use DMCA Policy Privacy Policy Questions & Answers It > always > gives me an A900 error while its running, because it's just not happy > with > my dumb terminal console. CPIB683 RC4 Unable to obtain lock for service program QZLSSRV1 in library QSYS. To quickly locate the message, on the operating system command line type the following: DSPMSG QSYSOPR or DSPLOG QHST JOB(QZLSSERVER) Press the Enter key.

Error 3420 indicates there is a name conflict on the network. Changing the NetServer name to one that is not being used on the network will allow it to start successfully. Problems caused by having port restrictions configured for the *UDP ports should be resolved by removing restrictions for ports 137-139. Ibm says that this problem is repaired with PTF SI15797.

Following Share this item with your network: Toggle navigation midrange.com Date Prev Date Next Thread Prev Thread Next Indexes Thread Index Author Index Date Index Search List Info Home MIDRANGE-L January check my blog By submitting you agree to receive email from TechTarget and its partners. Checking the PC configuration verified the Windows Workgroup name was the same as the NetServer. We'll email youwhen relevant content isadded and updated.

In V5R1M0, this portion of the code was rewritten to follow the NetBIOS over TCP/IP specification more closely, and this is the reason the problem was exposed with the upgrade to This dump is collected by issuing a CALL QSOMAINT PARM('4' '7'). References: NetServer starting problem From: comp.sys.ibm.as400.misc Prev by Date: Re: UPDATE Re: Problems with SQL SET statements Next by Date: Re: NetServer starting problem Previous by thread: NetServer starting problem Next this content Does anyone know the greenscreen equivalent of the reset and restart for Netserver?Message ID . . . . . . : CPIB683 Severity . . . . . . . :

The trace showed TCP/IP addresses of several PCs on the network that had a group name conflicting with the NetServer name. Our AS400 can see our network devices (ping them with ip or PC name) and also ping www.google.com Telnet is working fine. 0 0 02/25/09--05:33: AS/400 TCP/IP: Port numbers Contact us 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

This is also a timing issue.

  1. CPIB687 RC1 RC3021 NetBIOS over TCP/IP started with errors - return code 3021.
  2. This caused NetBIOS over TCP/IP to lose track of the existing stream pointers and, as a result, could not shut down properly.
  3. The IBM i TCP/IP domain information or the local host information is not correct (CFGTCP Option 12).
  4. Pub.
  5. CALL QZLSENDS PARM(x'00000000') CALL QZLSSTRS PARM('1' x'00000000') If still no success, contact Support for assistance in collecting a TASKINFO dump.
  6. 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.

yes no add cancel HOME | ABOUT US | CATALOG | CONTACT US | ©2017http://www.rssing.com Jump to navigation Cornell University Law SchoolSearch Cornell Toggle navigation Support Us! Did you try the solution the error message recommends? ____________________________________________________________ 5 - Start iSeries NetServer with the reset option using the Start Server (QZLSSTRS) API. Following Follow iSeries error messages Thanks! 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.

In CFGTCP, verify that Domain Host name is correct (Option 12) and the Interface TCP/IP address (Option 1) is correct. I don't use Operations Console. I'm ready to start. have a peek at these guys Next by Author: Re: V5R2 Default # of libraries in LIBLIST Previous by thread: Re: NetServer Configuration Next by thread: Re: NetServer Configuration Index(es): Author Thread Date Return to Archive home

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. We'll email youwhen relevant content isadded and updated. Development might request a LIC trace or TASKINFO dump if the measures above do not correct the problem. Use Option 4 to end all active 445/CIFS ports.

If the problem continues, restart TCP/IP with theEndTCP/IP (ENDTCP) and Start TCP/IP (STRTCP) commands. Expand My Connections. 3.