Common Sap Gui Problems and Solutions

Common SAPGUI Problems and Solutions for Level Two Support
Last Saved: 2/24/2012 9:54:00 PM Printed On: 02/27/12 4:13 AM Version Number: 1.0
Prepared By: SAP Basis Team
Common SAPGUI Problems and Solutions

TABLE OF CONTENTS
1.0 1.1 1.2 2.0
OBJECTIVE ............................................................................................................................................. 4 PURPOSE ................................................................................................................................................. 4 AUDIENCE ............................................................................................................................................... 4 INTRODUCTION .................................................................................................................................... 5
2.1 DESKTOP SERVICES FILE CHANGED OR DAMAGED .................................................................................... 6 2.1.1 Symptoms ........................................................................................................................................ 6 2.1.2 Solution........................................................................................................................................... 6 2.1.3 Explanation ..................................................................................................................................... 7 2.2 INCORRECT SAP R/3 HOST NAME OR ADDRESS ........................................................................................ 8 2.2.1 Symptoms ........................................................................................................................................ 8 2.2.2 Solution........................................................................................................................................... 8 2.3 LOGON GROUP CONFIGURATION PROBLEM ............................................................................................. 10 2.3.1 Symptoms ...................................................................................................................................... 10 2.3.2 Solution......................................................................................................................................... 10 2.4 INCORRECT R/3 SYSTEM NUMBER .......................................................................................................... 11 2.4.1 Symptoms ...................................................................................................................................... 11 2.4.2 Solution......................................................................................................................................... 11 2.4.3 Explanation ................................................................................................................................... 11 2.5 SLOW SAPGUI PERFORMANCE ON WIDE AREA NETWORKS .................................................................... 13 2.5.1 Symptoms ...................................................................................................................................... 13 2.5.2 Solution......................................................................................................................................... 13 2.5.3 Explanation ................................................................................................................................... 14 2.5.4 Installation Setup........................................................................................................................... 14 2.6 DESKTOP RESOURCES AND SAPGUI ...................................................................................................... 15 2.6.1 Symptoms ...................................................................................................................................... 15 2.6.2 Solution......................................................................................................................................... 15 2.7 PASSWORD IS IN THE EXCEPTION T ABLE.............................................................................................. 17 2.7.1 Symptom ....................................................................................................................................... 17 2.7.2 Solution......................................................................................................................................... 17 2.7.3 Explanation ................................................................................................................................... 17 2.8 DETERMINING THE VERSION OF SAPGUI YOU ARE USING ..................................................................... 18 2.9 USING SAPSWEEP TO UNINSTALL OLD VERSIONS OF SAPGUI................................................................ 20 2.10 NETWORK CONNECTION PROBLEMS ....................................................................................................... 21 2.10.1 Verifying Basic TCP/IP Network Connectivity................................................................................ 21 2.10.2 SAP Network Interface Layer......................................................................................................... 21 2.11 EXAMPLES OF NETWORK PROBLEMS ...................................................................................................... 23 2.11.1 Symptoms ...................................................................................................................................... 23 2.11.2 Solution......................................................................................................................................... 23 3.0 APPENDIX ............................................................................................................................................. 24 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 Sample Desktop Services File (C:\Windows\services) ..................................................................... 24 Example of a Successful niping t Test....................................................................................... 30 Services File Repair Script sap_services.bat .............................................................................. 31 Services File Repair File sap_dp_gw_.add ................................................................................ 32 Services File Repair File sap_ms.add ........................................................................................ 36
CSC/Nortel Networks Confidential Page 2 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx
Last Saved 2/24/2012 9:54:00 PM
Common SAPGUI Problems and Solutions Revision History

Date Author Comments
PERIODIC REVIEW OF DOCUMENT SAP Basis team will review this document quarterly to keep the content up to date and comply with Corporate Security policy and standards
Last Saved 2/24/2012 9:54:00 PM
1.0 Objective
The objective of this document is to describe commonly encountered problems with the network and SAPGUI, and suggest solutions.
1.1
Purpose
The purpose of this document is to describe common network problems and SAPGUI problems in sufficient detail to allow the Basis analyst or support technician to quickly find solutions and get the user back on line.
1.2
Audience
This document is intended for experienced Basis administrators and support technicians who are familiar with TCP/IP networking, SAPGUI, and network tools like niping. It is also useful to second and third level support in handling the most common problems.
Last Saved 2/24/2012 9:54:00 PM
2.0 Introduction
This document describes most common problems that may be encountered when attempting to connect to an SAP R/3 server and log on as an SAP user. Fixes, work-arounds, and referrals are provided to help you overcome these common problems:

Desktop services file changed or damaged Incorrect SAP server host name or IP address Incorrect SAP System Number Slow SAPGUI Performance Desktop Resources and SAPGUI Password is in the Exception Table, too easy to guess, not secure Determining Which Version of the SAPGUI You Are Using Network connection problems
Last Saved 2/24/2012 9:54:00 PM
2.1
Desktop Services File Changed or Damaged
2.1.1 Symptoms
There are two possible error messages for this problem. If you are logging in using a Logon Group like Atlas, FDC Operations, or GOH-Workgroup2, you will receive this load balancing error 88 message:
If you are logging directly into a particular SAP server, you will see this service unknown error:
The error window usually appears very quickly when you attempt to log into an R/3 system: This means that SAPGUI cannot find an entry in your desktop services file. (This message is also a symptom of not reaching the R/3 server, but that message has a slower response time.)
2.1.2 Solution
Locate the users desktop services file:

For Windows 95 and Windows 98 systems, the file path is C:\Windows\services For Windows NT and Windows 2000, the file path is C:\Windows\System32\Drivers\Etc\services
Examine the services file, looking for the SAP port definitions. There should be entries for ports sapdp00 through sapdp99, sapgw00 through sapgw99, and messge server entries like sapmsHP1, sapmsPRD, sapmsPE1, etc. Compare the contents of the services file to the sample file in the Appendix below. You will probably find that the SAP service entries beginning with sapdp00 are missing.
Last Saved 2/24/2012 9:54:00 PM

Missing SAP port definitions can be reapplied to the services file using the repair script sap_services.bat, available on the following servers. Click on an entry to execute the script. System FDC, HPOCS, Goh-Fast FDC, HPOCS, Goh-Fast FDC, HPOCS, Goh-Fast FDC, HPOCS, Goh-Fast Atlas Atlas Atlas Atlas Region Bellerica MASS USA North Ryde Australia Val Bonne France Santa Clara CA USA Europe North America Brazil Mexico Command Link
\\bl_corp1\corp_sw\pc\sap_gui\SAP_GUI_46D\sap_services.bat
\\Znryp001\share\sap_gui_46d\sap_services.bat
\\Valbonne1\Software\SAPInstall\SAP_GUI_46D\sap_services.bat \\sc_corp1\corp_sw\pc\sap_gui\SAP_GUI_46D\sap_services.bat
\\Znsgd034\atlasemea\sap_services.bat \\ZCARC003\GROUPS\AtlasGlobalHR\GlobalHRSupport\sap_servic es.bat \\Zbrgc5\atlasbrs\sap_services.bat \\Zgard1\atlasmex\sap_services.bat
Missing SAP port definitions can also be restored manually, by copying the entries from another system, or entering them into the services file using an editor, e.g. Notepad.
Note: For Windows NT and Windows 2000 desktops, the services file is under the control of the Administrative User. You will need administrator privileges to make changes to the file. Use the Install Privilege Tool to grant administrative privileges.
2.1.3 Explanation
If you are installing or configuring new network devices, like PCMCIA network adapter cards or modem cards, the installation or upgrade program may replace the IP services file. This often happens to people who use a docking station with a network card when in their local office, but switch to a PCMCIA network card when they are working at other Nortel Networks sites. Unfortunately, switching from one network interface to the other runs a network configuration program that replaces the users services file with its own version. Any special port definitions that were added to the default file are lost. The repair script sap_services.bat appends the SAP port definitions to the services file. The list of ports includes message server entries for all known SAP systems. Existing services file entries belonging to other applications are not lost.
Last Saved 2/24/2012 9:54:00 PM
2.2
Incorrect SAP R/3 Host Name or Address
2.2.1 Symptoms
You receive this error message when attempting to log into SAP R/3:
This means that the Domain Name Server cannot find the host server you are asking for. A similar message results if you ask for an IP address that is not available.
2.2.2 Solution
First, make sure you have spelled the host server name correctly, or entered the IP address correctly. If the host name or IP address is being issued from a logon icon that you have used before, then it is probably correct, and the host itself is unreachable. You can test whether the host is reachable using the ICMP Echo command, usually called ping. Open a DOS window and enter ping followed by the host name or IP address. If you do no receive an echo reply from the host, the disconnect may be caused at any point on the network between the desktop and the server. Start by pinging other hosts you know about to see if they reply. If they do not reply to their host name, try using their IP address, if you know it. If none reply, try pinging your own desktops IP address. If that fails, there is a network stack problem, and you need to call NT4HELP to get the network software reinstalled and/or reconfigured. If you find that host servers reply to their IP address, but not to their host names, then you have a Domain Name Server (DNS) problem, which may be due to a configuration error on your desktop, or that the DNS server is unreachable. In either case, you probably need to call NT4HELP to get the problem fixed. Similarly, if you request an R/3 server by host name and you get a very slow initial response, this may be due to the DNS server having to look up the hosts IP address. The DNS server may be very busy, or it may have to refer the question to a lot of its fellow DNS servers before it finds one that knows the answer. If this is a chronic problem, try using the IP address instead, so the DNS does not have to look it up. The only disadvantage of using the IP address directly is that sometimes IP addresses are changed by the network administrators, whereas host names usually remain the same for the working life of the server. However, IP addresses for the SAP servers are not changed very often, and the quicker response for each login you do is definitely worth the trouble of having to change the IP address once or twice.
System Atlas Development Atlas Training
Hostname maple.us.nortel.com cypress.us.nortel.com
Last Saved 2/24/2012 9:54:00 PM

System Atlas Fix Atlas Testing Atlas Production FDC Development FDC Unit Test FDC System Test FDC Production Goh-Fast Development Goh-Fast Testing Goh-Fast Testing 2 Goh-Fast Conversion Goh-Fast Production HPOCS Development HPOCS Training HPOCS Fix HPOCS Production Hostname mulberry.us.nortel.com aspen.us.nortel.com sequoia.us.nortel.com sapdv3.corpwest.baynetworks.com saput3.corpwest.baynetworks.com jumanji.corpwest.baynetworks.com sapprd.corpwest.baynetworks.com sapde1.corpwest.baynetworks.com sapqe1.corpwest.baynetworks.com sapqe2.us.nortel.com sapce1.corpwest.baynetworks.com sappe1.corpwest.baynetworks.com sapmd1.us.nortel.com sapmd1.us.nortel.com samf1.us.nortel.com sapmp1.us.nortel.com
Last Saved 2/24/2012 9:54:00 PM
2.3
Logon Group Configuration Problem
2.3.1 Symptoms
The user attempts to access any SAP System via the logon group Atlas, GOH-WorkGroup1, GOH-WorkGroup2, Customer Admin, EMEA, Financial Admin, Human Resources, Ireland, Operations, Public or and receives a network timeout error. There might be a problem with the configuration with the logon groups. To see if users are using Logon Groups: Go to Saplogon select one of the SAP systems and click on Properties. The Application Server field is the Logon Group name and should be greyed out. The Note: Saplogon-pad will not have the Properties option.
2.3.2 Solution
This may be because the IP address setting in the server Attributes tab in SMLG is incorrect, or more likely, the IP address setting is missing. If there is no IP address attribute, the message server will assigning its default address for the application server. Unfortunately, the default subnet could be private, so the user cannot access the server by that route. Please route case to Basis Team to re-configure the Logon Groups. Note: This problem can appear to be intermittent if only one server is misconfigured and the rest are correct.
Last Saved 2/24/2012 9:54:00 PM
2.4
Incorrect R/3 System Number
2.4.1 Symptoms
You are attempting to log into an SAP R/3 system that you have not used before. You set up an entry in SAPlogon, specifying the host name or IP address, and an R/3 system number of 01. You then attempt to log on using the new entry. After a delay, you receive the following error message:
2.4.2 Solution
Check your configuration information for the R/3 system. You will probably find that the system number is not 01, but 49, or some other number. Also, you must specify a two-digit system number, complete with leading zero, for numbers under 10. The repair file sap_ms.add in the Appendix lists the message server entries for all currently active SAP systems. You can derive the system number from the entry by taking the last two digits from the port number. For example, the message server port entry for HP1 is:
sapmsHP1 3642/tcp
That means that the system number for HP1 is 42. Similarly, the system number for PE1 is 28, MD1 is 87, etc.
2.4.3 Explanation
This error message usually means that you have reached a UNIX host, but the SAP R/3 dispatcher has not picked up your connection. This may be because the dispatcher is only accepting calls for a different system number, e.g. 49, or that SAP R/3 is not running on this system (it is down, or not installed). Missing SAP system number definitions can be reapplied to the services file using the repair script sap_ms.add, available on the following servers. Click on an entry to execute the script. System FDC, HPOCS, Goh-Fast FDC, HPOCS, Goh-Fast Region Bellerica MASS USA North Ryde Australia Command Link
\\bl_corp1\corp_sw\pc\sap_gui\SAP_GUI_46D\sap_ms.add
\\Znryp001\share\sap_gui_46d\sap_ms.add
Last Saved 2/24/2012 9:54:00 PM

System FDC, HPOCS, Goh-Fast FDC, HPOCS, Goh-Fast Atlas Atlas Atlas Atlas Region Val Bonne France Santa Clara CA USA Europe North America Brazil Mexico Command Link
\\Valbonne1\Software\SAP-Install\SAP_GUI_46D\sap_ms.add
\\sc_corp1\corp_sw\pc\sap_gui\SAP_GUI_46D\sap_ms.add
\\Znsgd034\atlasemea\sap_ms.add \\ZCARC003\GROUPS\AtlasGlobalHR\GlobalHRSupport\sap_ms.add \\Zbrgc5\atlasbrs\sap_ms.add \\Zgard1\atlasmex\sap_ms.add
Note that if you receive this error immediately after trying to connect, it is more likely to be a problem with the services file on your desktop. See the section Desktop Services File Changed or Damaged above.
Last Saved 2/24/2012 9:54:00 PM
2.5
Slow SAPGUI Performance on Wide Area Networks
2.5.1 Symptoms
It takes more than a minute for SAPGUI to start up and connect to the server. This is most likely to happen in remote locations where network access is slow.
2.5.2 Solution
Since the network is slow, reconfigure SAPGUI to send and receive less data. There are two procedures to follow: 1) Select the old style SAPGUI screen using the SAP Configuration tool. There should be an icon on your desktop called SAP Configuration that looks like this:
Double-click to open it. You will see a small replica of the SAPGUI screen. There is a check box to Use New Visual Design. If the box is checked, click on it to remove the check. Click the Apply button, and close the window. The next time you run SAPGUI, you will see a simplified screen with less animation, which makes less demand on network resources.
Last Saved 2/24/2012 9:54:00 PM

2) Select the low speed connection setting in the SAPlogon screen. Open SAPlogon, select logon entry for the system in question, and click on Properties. Click on the Advanced button to bring up the Advanced Options window shown below. Select the Low Speed Connection check box, and select the OK button to complete the task.
This box should be checked
2.5.3 Explanation
Running the old style SAPGUI screen reduces demand on the desktop by using fewer colours and turning off animation effects. Initial startup runs faster. The Low Speed Connection option reduces demand on network resources by transferring the minimum data required to perform a task. For example, when displaying a large quantity of data, the server sends the data page by page when the user asks for it; it does not read ahead and transfer data in advance. This means that there will be less delay in presenting the first screen of data for a transaction.
2.5.4 Installation Setup

If you are issuing a preconfigured SAPlogon.ini configuration file to your users, you can set the Low Speed Connection option as default. Edit the file, setting the entries as follows:
[LowSpeedConnection] Item1=1 Item2=1
Last Saved 2/24/2012 9:54:00 PM
2.6
Desktop Resources and SAPGUI
SAPGUI makes significant demands on desktop resources, especially RAM, virtual memory, and graphics memory. When these resources run short, a number of symptoms will appear.
2.6.1 Symptoms
The following window pops up when you starting a new SAPGUI session, or performing a task that requires SAPGUI to open a new window:
After a minute, this message is usually followed by:
After SAPGUI startup, resources may be taken up by other applications, and you will receive this warning:
2.6.2 Solution
You may be able to start SAPGUI successfully after you free up some desktop resources by closing other applications. If that does not help, check that you have enough RAM to run SAPGUI. SAP recommends a minimum of 128MB of RAM if you want to run SAPGUI along with other applications. You should also have plenty of spare space on the C:\ drive to accommodate the Windows virtual memory page file (200MB or more free).
Last Saved 2/24/2012 9:54:00 PM

Another suggestion: If the Microsoft Office Shortcut toolbar is active on your desktop, but you do not use it much, you can turn it off to free up memory. The shortcut bar may be located at the left or right of the screen. You can remove it by clicking on the box at the top left, and selecting the Exit option. Click here to see options
A second window will appear to ask whether you want the shortcut bar to be activated each time you restart the system. Select the No button to ensure it is not restarted automatically.
Last Saved 2/24/2012 9:54:00 PM
2.7
Password is in the Exception Table
2.7.1 Symptom
The user is choosing a new password. The system responds with this rather cryptic error message:
2.7.2 Solution
The password chosen is too easy to guess. Select the check mark to accept the message. Make up a more secure password, and try again.
2.7.3 Explanation
The system has a table of passwords that are considered too easy to guess. If a user chooses one of the passwords in the table, the message above is issued. Passwords to avoid are any with NORTEL in them, or peoples first names, or sequences like 12345678 and QWERTY, etc.
Last Saved 2/24/2012 9:54:00 PM
2.8
Determining the Version of SAPGUI You Are Using
Some SAPGUI (and even SAP short dump) problems can be traced back to an out-of-date version of the SAPGUI on the users desktop. Here is how to determine the version of SAPGUI the user has on the desktop: 1) Double click on the SAPlogon icon on your desktop. Left click at the top left hand corner of the SAPLOGON screen and you will be able to see the window menu as shown below.
Click Here
About info
Last Saved 2/24/2012 9:54:00 PM

2) Click on the About Sapgui entry in the window menu. You will see a screen as shown below displaying information about the SAPGUI version you are using. Compare the information displayed on your desktop to that shown here. The current version is SAPGUI 4.6D Final Release, also called Compilation 4.
This is the current version.
3)
Click OK to close the SAPlogon screen.
Last Saved 2/24/2012 9:54:00 PM
2.9
Using SAPsweep to Uninstall Old Versions of SAPGUI
You must always uninstall old versions of SAPGUI before attempting to install a new version. Normally, the uninstall option in the Program menu will effectively remove the old version. The path is: Start p Programs p SAP Frontend p Remove SAP Frontend If the uninstall fails, or you have an older version of SAPGUI that has no uninstall option, the SAPsweep utility can be used to clean up the system before installing the new version. SAPsweep can also be used when an installation fails, leaving an incomplete installation behind. The SAPsweep program can be executed from the following file server location: \\zcarc003\groups\AtlasGlobalHR\GlobalHRSupport\sapsweep.exe Note: SAPsweep consists of two executable files: y sapsweep.exe called by the user y sapregsv.exe called by sapsweep.exe to make a backup copy of the registry If you wish to provide SAPsweep support on an additional file server, both binaries must be copied to the new location.
Last Saved 2/24/2012 9:54:00 PM
2.10 Network Connection Problems

This section describes how SAPGUI uses the network to connect to the server, and the network services that must be in place before the connection can be made. It is assumed that all users have basic TCP/IP networking software installed on their systems.
2.10.1 Verifying Basic TCP/IP Network Connectivity

The users local desktop support team is responsible for setting up basic network services so the users can connect to email and other applications. The Basis team is responsible for ensuring that the SAP Network Interface (NI) layer runs on top of TCP/IP network, and that the users SAPGUI client can connect via NI to the SAP servers. The general approach in troubleshooting network problems is to start with basic TCP/IP service, and test each additional network layer until the SAPGUI can be connected to the server. The steps are:

check whether other network based applications are running successfully, e.g. email. Check the desktop TCP/IP address allocation using the winipcfg utility. This ensures that the user has received an IP address from the local DHCP server. Go to the Start p Run menu, enter winipcfg, and execute it. The following window will be displayed. Select the network adapter that the user is currently using (PPP is for dial up connections). The IP Address field must contain a valid IP address for the network the user resides on. For internal Nortel networks, the address will start with 47.

If the user travels to another Nortel site, the laptop system may retain an address from the home office location that will not work on this site. Use the Release and Renew buttons to get a new address from the local DHCP server. Use the TCP/IP ping command to see if the users system can be reached using the IP address reported by winipcfg. For example, log into sequoia and run /usr/sbin/ping s 47.130.114.179 to check out the path from HP1 to the users desktop. Similarly, you can run the ping command on the users desktop to see if sequoia is reachable from there. Open a DOS window, and run ping 47.81.128.132. Test TCP/IP with other applications, e.g. email. Once TCP/IP is working, you can concentrate on the SAP Network Interface layer.
2.10.2 SAP Network Interface Layer If the user is receiving errors related to Protocol Family, but basic TCP/IP seems to be working, examine the NI layer for
problems. The utility niping is used to test the NI layer.
Last Saved 2/24/2012 9:54:00 PM

Test whether the desktop is properly configured to support the NI layer. Open a DOS window, change to the directory C:\Program files\sappc\sapgui, and run the command niping t. This should produce a list of NI functional tests, ending with the message *** SELFTEST O.K. ***. There is an example of this test output in the Appendix below.
The next step is to test NI communications end-to-end. Log into sequoia and enter the command niping s to start up the niping test server. Leave it running while you start up the niping client on the users desktop. Enter the command niping c H 47.81.128.132. The niping client and server programs should then be able to talk to each other over the network. Note any error messages issued, and the response time. The users end of this dialog should look like this: Thu May 31 15:17:29 2001 connect to server o.k. Thu May 31 15:17:30 2001 send and receive 10 messages (len 1000) ------- times avg 93000 max 110000 min 50000 bw 21.00 excluding max av2 96250 bw2 20.29 ----usecs usecs usecs kb/sec and min: usecs kb/sec
The server end of the niping test dialog looks like this:
Thu May 31 19:14:25 2001 ready for connect from client ... Thu May 31 19:15:14 2001 connect from host dmclaren-1.ca.nortel.com, client 2 o.k.
Capture any errors you receive to a file for reporting to SAP.
Last Saved 2/24/2012 9:54:00 PM
2.11 Examples of Network Problems

2.11.1 Symptoms
The user is unable to connect to the SAP servers. TCP/IP is working correctly, e.g. email access is working correctly. The following error message is displayed when the user attempts to reach SAP:
Testing with niping t produces the error messages:

Wed May 30 14:47:27 2001 function name parameters return code --------------------------------------------------------------------NiMyHostName (..) rc = 0 ***LOG Q0I=> NiPSocket: WSASocket (10047: WSAEAFNOSUPPORT: Address family not supported by protocol family) [ninti.c 1105] *** ERROR => NiILocalCheck: NiPSocket (rc=-1) [nixxi.c 1758] NiMyAddrVerify (Mauricio_Ortiz, NULL) rc = -16 *** ERROR => NiTSelfTest: NiMyAddrVerify (rc=-16) [nixxtst. 1640]
This suggests that the NI software cannot reach the local (users desktop) host called Mauricio_Ortiz. Note that this host name is 14 characters long. Compare these messages to the successful test in the Appendix below, where the NiMyAddrVerify test worked correctly.
2.11.2 Solution
The users desktop is identified by a host name that is too long. The maximum host name that the SAP network will recognize is 10 characters, e.g. dmclaren_1. The solution is to ask the desktop support team to change the host name to a shorter name, then reinstall SAPGUI.
Last Saved 2/24/2012 9:54:00 PM
3.0 Appendix
3.1.1 Sample Desktop Services File (C:\Windows\services)
# # # # # # # # # Copyright (c) 1993-1995 Microsoft Corp. This file contains port numbers for well-known services as defined by RFC 1060 (Assigned Numbers). Format: <service name> <port number>/<protocol> 7/tcp 7/udp 9/tcp 9/udp 11/tcp 11/tcp 13/tcp 13/udp 15/tcp 17/tcp 17/udp 19/tcp 19/udp 20/tcp 21/tcp 23/tcp 25/tcp 37/tcp 37/udp 39/udp 42/tcp 42/udp 43/tcp 53/tcp 53/udp 53/tcp 53/udp 57/tcp 67/udp 69/udp 77/tcp 79/tcp 87/tcp 95/tcp 101/tcp 102/tcp 103/tcp 103/tcp 104/tcp 105/tcp 109/tcp 109/tcp 110/tcp 111/tcp 111/udp 111/tcp 111/udp 113/tcp 115/tcp 117/tcp 117/tcp 119/tcp 123/udp 137/udp [aliases...] [#<comment>]
echo echo discard discard systat systat daytime daytime netstat qotd qotd chargen chargen ftp-data ftp telnet smtp time time rlp name name whois domain domain nameserver nameserver mtp bootp tftp rje finger link supdup hostnames iso-tsap dictionary x400 x400-snd csnet-ns pop pop2 pop3 portmap portmap sunrpc sunrpc auth sftp path uucp-path nntp ntp nbname
sink null sink null users
quote quote ttytst source ttytst source
mail timserver timserver resource nameserver nameserver nicname nameserver nameserver domain domain
# resource location
# usually to sri-nic # name-domain server # name-domain server # deprecated # boot program server
netrjs ttylink hostname webster # ISO Mail postoffice # Post Office postoffice # usually from sri-nic
authentication
usenet ntpd ntp
# Network News Transfer # network time protocol (exp)
Last Saved 2/24/2012 9:54:00 PM

nbdatagram 138/udp nbsession 139/tcp NeWS 144/tcp sgmp 153/udp tcprepo 158/tcp snmp 161/udp snmp-trap 162/udp print-srv 170/tcp vmnet 175/tcp load 315/udp vmnet0 400/tcp sytek 500/udp biff 512/udp exec 512/tcp login 513/tcp who 513/udp shell 514/tcp syslog 514/udp printer 515/tcp talk 517/udp ntalk 518/udp efs 520/tcp route 520/udp timed 525/udp tempo 526/tcp courier 530/tcp conference 531/tcp rvd-control 531/udp netnews 532/tcp netwall 533/udp uucp 540/tcp klogin 543/tcp kshell 544/tcp new-rwho 550/udp remotefs 556/tcp rmonitor 560/udp monitor 561/udp garcon 600/tcp maitrd 601/tcp busboy 602/tcp acctmaster 700/udp acctslave 701/udp acct 702/udp acctlogin 703/udp acctprinter 704/udp elcsd 704/udp acctinfo 705/udp acctslave2 706/udp acctdisk 707/udp kerberos 750/tcp kerberos 750/udp kerberos_master 751/tcp kerberos_master 751/udp passwd_server 752/udp userreg_server 753/udp krb_prop 754/tcp erlogin 888/tcp kpop 1109/tcp phone 1167/udp ingreslock 1524/tcp maze 1666/udp nfs 2049/udp knetd 2053/tcp eklogin 2105/tcp rmt 5555/tcp mtb 5556/tcp man 9535/tcp w 9536/tcp mantst 9537/tcp bnews 10000/tcp rscs0 10000/udp
news sgmp repository snmp snmp
# PCMAIL # network PostScript
comsat whod cmd spooler
# no passwords used # line printer spooler # for LucasFilm
router routed timeserver newdate rpc chat MIT disk readnews uucpd # # # cmd # new-who # rfs_server rfs# rmonitord # # -for emergency broadcasts uucp daemon Kerberos authenticated rlogin and remote shell experimental Brunhoff remote filesystem experimental experimental
# errlog
kdc kdc
# # # # # # # # #
Kerberos authentication--tcp Kerberos authentication--udp Kerberos authentication Kerberos authentication Kerberos passwd server Kerberos userreg server Kerberos slave propagation Login and environment passing Pop with Kerberos
# sun nfs # Kerberos de-multiplexor # Kerberos encrypted rlogin rmtd mtbd # mtb backup # remote man server # remote man server, testing
Last Saved 2/24/2012 9:54:00 PM

queue rscs1 poker rscs2 gateway rscs3 remp rscs4 rscs5 rscs6 rscs7 rscs8 rscs9 rscsa rscsb qmaster qmaster sapdp00 sapdp01 sapdp02 sapdp03 sapdp04 sapdp05 sapdp06 sapdp07 sapdp08 sapdp09 sapdp10 sapdp11 sapdp12 sapdp13 sapdp14 sapdp15 sapdp16 sapdp17 sapdp18 sapdp19 sapdp20 sapdp21 sapdp22 sapdp23 sapdp24 sapdp25 sapdp26 sapdp27 sapdp28 sapdp29 sapdp30 sapdp31 sapdp32 sapdp33 sapdp34 sapdp35 sapdp36 sapdp37 sapdp38 sapdp39 sapdp40 sapdp41 sapdp42 sapdp43 sapdp44 sapdp45 sapdp46 sapdp47 sapdp48 sapdp49 sapdp50 sapdp51 sapdp52 sapdp53 10001/tcp 10001/udp 10002/tcp 10002/udp 10003/tcp 10003/udp 10004/tcp 10004/udp 10005/udp 10006/udp 10007/udp 10008/udp 10009/udp 10010/udp 10011/udp 10012/tcp 10012/udp 3200/tcp 3201/tcp 3202/tcp 3203/tcp 3204/tcp 3205/tcp 3206/tcp 3207/tcp 3208/tcp 3209/tcp 3210/tcp 3211/tcp 3212/tcp 3213/tcp 3214/tcp 3215/tcp 3216/tcp 3217/tcp 3218/tcp 3219/tcp 3220/tcp 3221/tcp 3222/tcp 3223/tcp 3224/tcp 3225/tcp 3226/tcp 3227/tcp 3228/tcp 3229/tcp 3230/tcp 3231/tcp 3232/tcp 3233/tcp 3234/tcp 3235/tcp 3236/tcp 3237/tcp 3238/tcp 3239/tcp 3240/tcp 3241/tcp 3242/tcp 3243/tcp 3244/tcp 3245/tcp 3246/tcp 3247/tcp 3248/tcp 3249/tcp 3250/tcp 3251/tcp 3252/tcp 3253/tcp
Last Saved 2/24/2012 9:54:00 PM

sapdp54 sapdp55 sapdp56 sapdp57 sapdp58 sapdp59 sapdp60 sapdp61 sapdp62 sapdp63 sapdp64 sapdp65 sapdp66 sapdp67 sapdp68 sapdp69 sapdp70 sapdp71 sapdp72 sapdp73 sapdp74 sapdp75 sapdp76 sapdp77 sapdp78 sapdp79 sapdp80 sapdp81 sapdp82 sapdp83 sapdp84 sapdp85 sapdp86 sapdp87 sapdp88 sapdp89 sapdp90 sapdp91 sapdp92 sapdp93 sapdp94 sapdp95 sapdp96 sapdp97 sapdp98 sapdp99 sapgw00 sapgw01 sapgw02 sapgw03 sapgw04 sapgw05 sapgw06 sapgw07 sapgw08 sapgw09 sapgw10 sapgw11 sapgw12 sapgw13 sapgw14 sapgw15 sapgw16 sapgw17 sapgw18 sapgw19 sapgw20 sapgw21 sapgw22 sapgw23 sapgw24 3254/tcp 3255/tcp 3256/tcp 3257/tcp 3258/tcp 3259/tcp 3260/tcp 3261/tcp 3262/tcp 3263/tcp 3264/tcp 3265/tcp 3266/tcp 3267/tcp 3268/tcp 3269/tcp 3270/tcp 3271/tcp 3272/tcp 3273/tcp 3274/tcp 3275/tcp 3276/tcp 3277/tcp 3278/tcp 3279/tcp 3280/tcp 3281/tcp 3282/tcp 3283/tcp 3284/tcp 3285/tcp 3286/tcp 3287/tcp 3288/tcp 3289/tcp 3290/tcp 3291/tcp 3292/tcp 3293/tcp 3294/tcp 3295/tcp 3296/tcp 3297/tcp 3298/tcp 3299/tcp 3300/tcp 3301/tcp 3302/tcp 3303/tcp 3304/tcp 3305/tcp 3306/tcp 3307/tcp 3308/tcp 3309/tcp 3310/tcp 3311/tcp 3312/tcp 3313/tcp 3314/tcp 3315/tcp 3316/tcp 3317/tcp 3318/tcp 3319/tcp 3320/tcp 3321/tcp 3322/tcp 3323/tcp 3324/tcp
Last Saved 2/24/2012 9:54:00 PM

sapgw25 sapgw26 sapgw27 sapgw28 sapgw29 sapgw30 sapgw31 sapgw32 sapgw33 sapgw34 sapgw35 sapgw36 sapgw37 sapgw38 sapgw39 sapgw40 sapgw41 sapgw42 sapgw43 sapgw44 sapgw45 sapgw46 sapgw47 sapgw48 sapgw49 sapgw50 sapgw51 sapgw52 sapgw53 sapgw54 sapgw55 sapgw56 sapgw57 sapgw58 sapgw59 sapgw60 sapgw61 sapgw62 sapgw63 sapgw64 sapgw65 sapgw66 sapgw67 sapgw68 sapgw69 sapgw70 sapgw71 sapgw72 sapgw73 sapgw74 sapgw75 sapgw76 sapgw77 sapgw78 sapgw79 sapgw80 sapgw81 sapgw82 sapgw83 sapgw84 sapgw85 sapgw86 sapgw87 sapgw88 sapgw89 sapgw90 sapgw91 sapgw92 sapgw93 sapgw94 sapgw95 3325/tcp 3326/tcp 3327/tcp 3328/tcp 3329/tcp 3330/tcp 3331/tcp 3332/tcp 3333/tcp 3334/tcp 3335/tcp 3336/tcp 3337/tcp 3338/tcp 3339/tcp 3340/tcp 3341/tcp 3342/tcp 3343/tcp 3344/tcp 3345/tcp 3346/tcp 3347/tcp 3348/tcp 3349/tcp 3350/tcp 3351/tcp 3352/tcp 3353/tcp 3354/tcp 3355/tcp 3356/tcp 3357/tcp 3358/tcp 3359/tcp 3360/tcp 3361/tcp 3362/tcp 3363/tcp 3364/tcp 3365/tcp 3366/tcp 3367/tcp 3368/tcp 3369/tcp 3370/tcp 3371/tcp 3372/tcp 3373/tcp 3374/tcp 3375/tcp 3376/tcp 3377/tcp 3378/tcp 3379/tcp 3380/tcp 3381/tcp 3382/tcp 3383/tcp 3384/tcp 3385/tcp 3386/tcp 3387/tcp 3388/tcp 3389/tcp 3390/tcp 3391/tcp 3392/tcp 3393/tcp 3394/tcp 3395/tcp
Last Saved 2/24/2012 9:54:00 PM

sapgw96 sapgw97 sapgw98 sapgw99 sapmsHP1 3396/tcp 3397/tcp 3398/tcp 3399/tcp 3642/tcp
Last Saved 2/24/2012 9:54:00 PM
Common SAPGUI Problems and Solutions 3.1.2 Example of a Successful niping t Test
niping -t Wed May 30 14:54:03 2001 function name parameters return code --------------------------------------------------------------------NiMyHostName (..) rc = 0 Wed May 30 14:54:04 2001 NiMyAddrVerify (dmclaren-1, NULL) rc = 0 NiServToNo ("0", ..) rc = 0 NiListen (0, ..) rc = 0 NiCloseHandle (1) rc = 0 NiBuf2Listen (NI_FINDSERV, ..) rc = 0 NiRouteToTable (/H/host1/H/host/S/serv, ...) rc = 0 NiHostToAddr (localhost, ..) rc = 0 NiAddrToHost (127.0.0.1) rc = localhost NiHostToAddr (dmclaren-1, ..) rc = 0 NiAddrToHostCanon(47.130.114.179) rc = dmclaren1.ca.nortel.com NiGetHostAddrLis (47.130.114.179) rc = 0 found 1 interfaces [0] 47.130.114.179 NiConnect (dmclaren-1, 65000, 100, ..) rc = 0 NiAccept (1, 100, .., ..) rc = 0 NiWrite (2, EYECATCHER, 11, 100, ..) rc = 0 Ni2Select ([3], [2], 100) rc = 0 NiRead (3, .., .., 100, ..) rc = 0 NiCheck1 (2, 100) rc = 0 NiCheck (2, 100) rc = 0 NiSelect ([2, 3], 100) rc = 0 NiRead ([2, 3], 100) rc = -11 (-11 ok) NiHdlToSock (..) rc = 0 NiSockToHdl (..) rc = 0 NiBufConnect (dmclaren-1, 65000, 100, ..) rc = 0 NiAccept (1, 100, .., ..) rc = 0 NiCheck2 (4, 100, 3, ..) rc = 0 NiCheck2 (4, 100, 3, ..) rc = 0 NiSendHandle (4, 100, 3, ..) rc = 0 NiSelect ([2, 3], 100) rc = 0 NiAccept (5, 100, .., ..) rc = 0 NiSelect ([2, 3], 100) rc = 0 NiRead ([2, 3], 100) rc = -22 (-22 ok) NiWrite (2, EYECATCHER, 11, 100, ..) rc = 0 NiRead (3, .., .., 100, ..) rc = 0 NiDgBind (0, ..) rc = 0 NiDgSend (EYECATCHER, 11, dmclaren-1, 1399, 0) rc = 0 NiDgGetHdl (..) rc = 0 NiSelect ([1], 100) rc = 0 NiDgReceive (.., .., 100) rc = 0 NiDgFreeResrc () rc = 0 NiBufAlloc (&buf, 1234, cU("NI-TEST")) rc = 0 NiBufDup (&buf1, buf) rc = 0 NiBufFree (&buf) NiBufWrap (&buf, data_buf, data_len, data_len, NiT rc = 0 NiBufFree (&buf) NiBufFree (&buf1) --------------------------------------------------------------------*** SELFTEST O.K. ***
Last Saved 2/24/2012 9:54:00 PM
Common SAPGUI Problems and Solutions 3.1.3 Services File Repair Script sap_services.bat
echo off if '%OS%'=='Windows_NT' goto nt4 set os=Windows 95 if exist c:\Windows\SAP_DS_GW.add del c:\Windows\SAP_DS_GW.add copy \\zcarc003\groups\AtlasGlobalHR\GlobalHRSupport\SAP_DS_GW.add c:\Windows\SAP_DS_GW.add if exist c:\Windows\SAP_MS.add del c:\Windows\SAP_MS.add copy \\zcarc003\groups\AtlasGlobalHR\GlobalHRSupport\SAP_MS.add c:\Windows\SAP_MS.add c: cd c:\Windows if exist SAPServicesbackup1 del SAPServicesbackup1 if exist SAPServicesbackup rename SAPServicesbackup SAPServicesbackup1 copy c:\Windows\services c:\Windows\SAPServicesbackup type C:\Windows\SAP_DS_GW.add >> c:\Windows\services type C:\Windows\SAP_MS.add >> c:\Windows\services goto end :nt4 if exist C:\Winnt\system32\drivers\etc\SAP_DS_GW.add del C:\Winnt\system32\drivers\etc\SAP_DS_GW.add copy \\zcarc003\groups\AtlasGlobalHR\GlobalHRSupport\SAP_DS_GW.add C:\Winnt\system32\drivers\etc\SAP_DS_GW.add if exist C:\Winnt\system32\drivers\etc\SAP_MS.add del C:\Winnt\system32\drivers\etc\SAP_MS.add copy \\zcarc003\groups\AtlasGlobalHR\GlobalHRSupport\SAP_MS.add C:\Winnt\system32\drivers\etc\SAP_MS.add C: cd C:\Winnt\system32\drivers\etc if exist SAPServicesbackup1 del SAPServicesbackup1 if exist SAPServicesbackup rename SAPServicesbackup SAPServicesbackup1 copy services SAPServicesbackup type SAP_DS_GW.add >> C:\Winnt\system32\drivers\etc\services type SAP_MS.add >> C:\Winnt\system32\drivers\etc\services :end echo Services file repaired. Exit
Last Saved 2/24/2012 9:54:00 PM
Common SAPGUI Problems and Solutions 3.1.4 Services File Repair File sap_dp_gw_.add
sapdp00 sapdp01 sapdp02 sapdp03 sapdp04 sapdp05 sapdp06 sapdp07 sapdp08 sapdp09 sapdp10 sapdp11 sapdp12 sapdp13 sapdp14 sapdp15 sapdp16 sapdp17 sapdp18 sapdp19 sapdp20 sapdp21 sapdp22 sapdp23 sapdp24 sapdp25 sapdp26 sapdp27 sapdp28 sapdp29 sapdp30 sapdp31 sapdp32 sapdp33 sapdp34 sapdp35 sapdp36 sapdp37 sapdp38 sapdp39 sapdp40 sapdp41 sapdp42 sapdp43 sapdp44 sapdp45 sapdp46 sapdp47 sapdp48 sapdp49 sapdp50 sapdp51 sapdp52 sapdp53 3200/tcp 3201/tcp 3202/tcp 3203/tcp 3204/tcp 3205/tcp 3206/tcp 3207/tcp 3208/tcp 3209/tcp 3210/tcp 3211/tcp 3212/tcp 3213/tcp 3214/tcp 3215/tcp 3216/tcp 3217/tcp 3218/tcp 3219/tcp 3220/tcp 3221/tcp 3222/tcp 3223/tcp 3224/tcp 3225/tcp 3226/tcp 3227/tcp 3228/tcp 3229/tcp 3230/tcp 3231/tcp 3232/tcp 3233/tcp 3234/tcp 3235/tcp 3236/tcp 3237/tcp 3238/tcp 3239/tcp 3240/tcp 3241/tcp 3242/tcp 3243/tcp 3244/tcp 3245/tcp 3246/tcp 3247/tcp 3248/tcp 3249/tcp 3250/tcp 3251/tcp 3252/tcp 3253/tcp Last Saved 2/24/2012 9:54:00 PM

sapdp54 sapdp55 sapdp56 sapdp57 sapdp58 sapdp59 sapdp60 sapdp61 sapdp62 sapdp63 sapdp64 sapdp65 sapdp66 sapdp67 sapdp68 sapdp69 sapdp70 sapdp71 sapdp72 sapdp73 sapdp74 sapdp75 sapdp76 sapdp77 sapdp78 sapdp79 sapdp80 sapdp81 sapdp82 sapdp83 sapdp84 sapdp85 sapdp86 sapdp87 sapdp88 sapdp89 sapdp90 sapdp91 sapdp92 sapdp93 sapdp94 sapdp95 sapdp96 sapdp97 sapdp98 sapdp99 sapgw00 sapgw01 sapgw02 sapgw03 sapgw04 sapgw05 sapgw06 sapgw07 sapgw08 sapgw09 3254/tcp 3255/tcp 3256/tcp 3257/tcp 3258/tcp 3259/tcp 3260/tcp 3261/tcp 3262/tcp 3263/tcp 3264/tcp 3265/tcp 3266/tcp 3267/tcp 3268/tcp 3269/tcp 3270/tcp 3271/tcp 3272/tcp 3273/tcp 3274/tcp 3275/tcp 3276/tcp 3277/tcp 3278/tcp 3279/tcp 3280/tcp 3281/tcp 3282/tcp 3283/tcp 3284/tcp 3285/tcp 3286/tcp 3287/tcp 3288/tcp 3289/tcp 3290/tcp 3291/tcp 3292/tcp 3293/tcp 3294/tcp 3295/tcp 3296/tcp 3297/tcp 3298/tcp 3299/tcp 3300/tcp 3301/tcp 3302/tcp 3303/tcp 3304/tcp 3305/tcp 3306/tcp 3307/tcp 3308/tcp 3309/tcp Last Saved 2/24/2012 9:54:00 PM

sapgw10 sapgw11 sapgw12 sapgw13 sapgw14 sapgw15 sapgw16 sapgw17 sapgw18 sapgw19 sapgw20 sapgw21 sapgw22 sapgw23 sapgw24 sapgw25 sapgw26 sapgw27 sapgw28 sapgw29 sapgw30 sapgw31 sapgw32 sapgw33 sapgw34 sapgw35 sapgw36 sapgw37 sapgw38 sapgw39 sapgw40 sapgw41 sapgw42 sapgw43 sapgw44 sapgw45 sapgw46 sapgw47 sapgw48 sapgw49 sapgw50 sapgw51 sapgw52 sapgw53 sapgw54 sapgw55 sapgw56 sapgw57 sapgw58 sapgw59 sapgw60 sapgw61 sapgw62 sapgw63 sapgw64 sapgw65 3310/tcp 3311/tcp 3312/tcp 3313/tcp 3314/tcp 3315/tcp 3316/tcp 3317/tcp 3318/tcp 3319/tcp 3320/tcp 3321/tcp 3322/tcp 3323/tcp 3324/tcp 3325/tcp 3326/tcp 3327/tcp 3328/tcp 3329/tcp 3330/tcp 3331/tcp 3332/tcp 3333/tcp 3334/tcp 3335/tcp 3336/tcp 3337/tcp 3338/tcp 3339/tcp 3340/tcp 3341/tcp 3342/tcp 3343/tcp 3344/tcp 3345/tcp 3346/tcp 3347/tcp 3348/tcp 3349/tcp 3350/tcp 3351/tcp 3352/tcp 3353/tcp 3354/tcp 3355/tcp 3356/tcp 3357/tcp 3358/tcp 3359/tcp 3360/tcp 3361/tcp 3362/tcp 3363/tcp 3364/tcp 3365/tcp Last Saved 2/24/2012 9:54:00 PM

sapgw66 sapgw67 sapgw68 sapgw69 sapgw70 sapgw71 sapgw72 sapgw73 sapgw74 sapgw75 sapgw76 sapgw77 sapgw78 sapgw79 sapgw80 sapgw81 sapgw82 sapgw83 sapgw84 sapgw85 sapgw86 sapgw87 sapgw88 sapgw89 sapgw90 sapgw91 sapgw92 sapgw93 sapgw94 sapgw95 sapgw96 sapgw97 sapgw98 sapgw99 3366/tcp 3367/tcp 3368/tcp 3369/tcp 3370/tcp 3371/tcp 3372/tcp 3373/tcp 3374/tcp 3375/tcp 3376/tcp 3377/tcp 3378/tcp 3379/tcp 3380/tcp 3381/tcp 3382/tcp 3383/tcp 3384/tcp 3385/tcp 3386/tcp 3387/tcp 3388/tcp 3389/tcp 3390/tcp 3391/tcp 3392/tcp 3393/tcp 3394/tcp 3395/tcp 3396/tcp 3397/tcp 3398/tcp 3399/tcp
Last Saved 2/24/2012 9:54:00 PM
Common SAPGUI Problems and Solutions 3.1.5 Services File Repair File sap_ms.add
sapmsHK1 3600/tcp sapmsHD1 3601/tcp sapmsHD2 3602/tcp sapmsPRD 3603/tcp sapmsTST 3604/tcp sapmsHRP 3605/tcp sapmsDV2 3606/tcp sapmsST2 3607/tcp sapmsUT3 3608/tcp sapmsUT2 3609/tcp sapmsDV3 3610/tcp sapmsARC 3611/tcp sapmsY2K 3612/tcp sapmsST3 3615/tcp sapmsO01 3616/tcp sapmsDE1 3620/tcp sapmsQE1 3621/tcp sapmsCE1 3622/tcp sapmsSE1 3623/tcp sapmsQE2 3624/tcp sapmsTEC 3625/tcp sapmsTE2 3626/tcp sapmsDE2 3627/tcp sapmsPE1 3628/tcp sapmsTE1 3629/tcp sapmsHD3 3630/tcp sapmsHT3 3631/tcp sapmsHQ1 3641/tcp sapmsHP1 3642/tcp sapmsHT1 3643/tcp sapmsHF1 3644/tcp sapmsHC1 3645/tcp sapmsKE1 3650/tcp sapmsDP1 3670/tcp sapmsQP1 3671/tcp sapmsCP1 3672/tcp sapmsPP1 3673/tcp sapmsMP1 3680/tcp sapmsMT1 3683/tcp sapmsMF1 3685/tcp sapmsTE2 3686/tcp sapmsMD1 3687/tcp
Last Saved 2/24/2012 9:54:00 PM

Common Sap Gui Problems and Solutions

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Common Sap Gui Problems and Solutions

Încărcat de

Drepturi de autor:

Formate disponibile

Common SAPGUI Problems and Solutions for Level Two Support

Prepared By: SAP Basis Team

Common SAPGUI Problems and Solutions

1.0 1.1 1.2 2.0

CSC/Nortel Networks Confidential Page 2 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions Revision History

CSC/Nortel Networks Confidential Page 3 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

CSC/Nortel Networks Confidential Page 4 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

CSC/Nortel Networks Confidential Page 5 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

Desktop Services File Changed or Damaged

CSC/Nortel Networks Confidential Page 6 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

\\Znsgd034\atlasemea\sap_services.bat \\ZCARC003\GROUPS\AtlasGlobalHR\GlobalHRSupport\sap_servic es.bat \\Zbrgc5\atlasbrs\sap_services.bat \\Zgard1\atlasmex\sap_services.bat

CSC/Nortel Networks Confidential Page 7 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

Incorrect SAP R/3 Host Name or Address

System Atlas Development Atlas Training

Hostname maple.us.nortel.com cypress.us.nortel.com

CSC/Nortel Networks Confidential Page 8 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

CSC/Nortel Networks Confidential Page 9 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

Logon Group Configuration Problem

CSC/Nortel Networks Confidential Page 10 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

Incorrect R/3 System Number

CSC/Nortel Networks Confidential Page 11 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

\\Znsgd034\atlasemea\sap_ms.add \\ZCARC003\GROUPS\AtlasGlobalHR\GlobalHRSupport\sap_ms.add \\Zbrgc5\atlasbrs\sap_ms.add \\Zgard1\atlasmex\sap_ms.add

CSC/Nortel Networks Confidential Page 12 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

Slow SAPGUI Performance on Wide Area Networks

CSC/Nortel Networks Confidential Page 13 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

This box should be checked

2.5.4 Installation Setup

CSC/Nortel Networks Confidential Page 14 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

Desktop Resources and SAPGUI

After a minute, this message is usually followed by:

CSC/Nortel Networks Confidential Page 15 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

CSC/Nortel Networks Confidential Page 16 of 36 Z:\opt\scribd\conversion\tmp\scratch6292\86053547.docx

Last Saved 2/24/2012 9:54:00 PM

Common SAPGUI Problems and Solutions

Password is in the Exception Table

Common SAPGUI Problems and Solutions