Problem Messages 

When you create problem messages for the Business Client (component BC-WD-CLT-BUS), in addition to describing the steps up to when the error occurred, the following information will make it easier to find the cause of the error, to process the error and to find a solution.

NWBC Version Information

In a problem message for the Business Client you should first provide information about the version of the NWBCClient.exe file.

You can find the version of the NWBC in the following ways:

●      From the help menu in the Business Client

●      In the trace and log files

●      In the Windows Explorer

Attach the version information to your customer message.

Version in the Local NWBC Client

In the Business Client choose Help ® About and note down the version of the client.

Example of the version number:

Version in the Trace/Log File

When you create a trace or log file, you can find the version number at the start of the file under the heading, Version.

Example of the version number:

Version in the exe File

If the Business Client will not even start, you can still get the version information from the Windows Explorer.

In the Windows Explorer go to directory \Program Files\SAP\FrontEnd\SAPgui. Select the NWBCClient.exe file and from the context choose Properties and then Version.

Example of the version number:

SAP GUI Version Number

To find out which SAP GUI is running in your Business Client, from the Start menu choose All Programs ® SAP Front End ® SAP Logon. In your SAP logon dialog box open the context menu by choosing the icon on the top left, and choose About SAP Logon. The version number is displayed.

Example of the version number:

To get detailed version information, choose Save Version Information and save the file.

Attach the version information to your customer message.

Configuration

Make sure that you have made the necessary Configuration Settings.

The fully configured NWBCClient.ini file is one of the main prerequisites to ensure the NWBC runs smoothly and correctly. This file is in the MyDocuments directory of the user on whose machine the Business Client is running. Each user has his or her own NWBCClient.ini file.

Example of the NWBCClient.ini file:

C:\Documents and Settings\<UserID>\My Documents

You can find more information under Parameters in the ini File.

Attach the NWBCClient.ini file of the user who has the problem to the customer message.

Tracing and Logging

Traces contain information that helps developers identify errors in the source code. Logs on the other hand contain information about high level functions such as EPCM and OBN. For more information, see Tracing and Logging.

Attach the trace file to your customer message.

Tools

For problems related to client server communication, or navigation and OBN problems, an analysis of the network traffic between the client and server is useful. We recommend the freeware tool, Fiddler, for this: http://www.fiddlertool.com. Fiddler is an HTTP debugging proxy, which as soon as the normal application has started, listens to the entire HTTP network traffic, and displays it in a simple and readable format. No complicated configuration is required - you just have to run the tool. To write the recorded network traffic to a file, you simply have to select all the sessions and choose File  ®  Save  ®  Session(s)  ®  As ZIP.

Attach the file to your customer message.

Types of Problem

Different type of problems may occur during the different phases of Business Client operation.

Types of Problem

Operation Phase	Problem
Start	Connection to the back end: Incorrect connection parameter in the NWBC configuration (protocol, host, port, path, client) or invalid proxy configuration, authentication problems (incorrect user or password), incorrect back end configuration (for example, HTTPS not activated)
	Retrieval of data from back end: back end not responding, or issuing an error message.
	Interpretation of data from the back end: Data is not in the expected format, version incompatibilities
Navigation output	Navigation is not in the expected sequence
	Navigation entry is missing, incorrect navigation entries present (incorrect role configuration)
User opens new sessions	Problems with opening sessions could be due to: Invalid URL for the navigation entry, host not available, host not responding to the TCP port, and so on.
	SAP GUI is not running in the canvas area, or error messages are displayed
User is working in the canvas area	Problem opening session: An invalid URL is configured for the navigation entry, or the host is not available, or the host is not available for the TCP port.
	SAP GUI is not running in the canvas area, or an error message is displayed (installation error)
Closing sessions	Sessions that are closed in the NWBC are not released in the back end
General	NWBC terminates

We recommend you reproduce the problem at a high trace level, for example, HEX, in order to get more information. For more information about problems working in the canvas area, the log level DEBUG is also required.