How To Fix WF808 - Calling presentation server was not Windows (NT)

SAP Error Message - Details

• Message type: E = Error

• Message class: WF - Workflow: messages

• Message number: 808

• Message text: Calling presentation server was not Windows (NT)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message WF808 - Calling presentation server was not Windows (NT) ?

  SAP Error Message:
  
  WF808 Calling presentation server was not Windows (NT)
  
  Cause:
  This error occurs when a workflow or a related SAP process tries to call or interact with a presentation server (frontend) that is expected to be running on a Windows NT (or compatible Windows) operating system, but the actual presentation server is not Windows NT or is not recognized as such.
  In other words, the workflow or SAP GUI expects the frontend system to be a Windows machine (typically for certain GUI or scripting operations), but the system it tries to communicate with is either:
  
  A non-Windows OS (e.g., Unix, Linux, Mac), or  
  The system identification or environment does not match Windows NT, or  
  The frontend is not properly registered or configured as a Windows presentation server.
  
  This can happen in scenarios involving SAP Business Workflow, where the workflow tries to start a task or send a message that requires interaction with the user's frontend system.
  
  Typical Scenarios:
  
  Workflow tasks that require frontend interaction (e.g., dialog steps, user confirmations).
  SAP GUI scripting or frontend automation expecting Windows environment.
  Remote function calls or RFCs that assume Windows frontend.
  Using SAP GUI on non-Windows platforms without proper configuration.
  
  
  Solution:
  
  
  Check the Frontend OS:
  
  Verify that the user's frontend system is indeed running Windows NT or a compatible Windows OS.
  If the user is on a non-Windows platform (Linux, Mac), some workflow functions expecting Windows frontend may not work.
  
  
  
  Adjust Workflow or Application Logic:
  
  Modify the workflow or application logic to handle non-Windows frontends or avoid calls that require Windows-specific frontend features.
  Use platform-independent methods or redesign the workflow steps.
  
  
  
  SAP GUI and Scripting Configuration:
  
  Ensure SAP GUI is properly installed and configured on the Windows frontend.
  Check that SAP GUI scripting is enabled if the workflow depends on it.
  For non-Windows platforms, check if SAP GUI for Java or other clients are supported and compatible.
  
  
  
  Presentation Server Registration:
  
  Check the registration of the presentation server in SAP.
  Use transaction SICF or SMGW to verify frontend connections.
  Ensure the frontend system is correctly identified and registered as Windows.
  
  
  
  SAP Notes and Patches:
  
  Search for relevant SAP Notes that address this error or related workflow/frontend issues.
  Apply any recommended patches or updates.
  
  
  
  Alternative Approaches:
  
  If the workflow requires Windows frontend features, consider providing Windows-based access for affected users.
  Use web-based frontends or SAP Fiori apps that are platform-independent.
  
  
  
  
  Related Information:
  
  
  SAP Workflow and Frontend Interaction:
  
  Workflows that require user interaction often depend on the frontend system's capabilities. Windows NT was historically the standard platform for SAP GUI, so some workflows assume this environment.
  
  
  SAP GUI for Windows vs. SAP GUI for Java:
  
  SAP GUI for Windows supports scripting and certain features that may not be available or behave differently on SAP GUI for Java or other platforms.
  
  
  Transaction Codes:  
  
  SWI1 (Workflow Logs) to check workflow errors.  
  SMGW (Gateway Monitor) to check frontend connections.  
  SICF (Maintain Services) to check HTTP services if web frontends are involved.
  
  
  
  SAP Notes:
  
  Search the SAP Support Portal for notes related to message WF808 or frontend OS compatibility.
  
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  Workflow expects Windows NT frontend, but actual frontend is not Windows or not recognized.
  
  
  Solution
  Verify frontend OS, adjust workflow logic, ensure SAP GUI and scripting are properly configured, register frontend correctly, consider platform compatibility.
  
  
  Related Info
  SAP GUI platform differences, workflow frontend interaction, SAP Notes for patches.
  
  
  
  
  If you provide more context (e.g., workflow type, frontend OS, SAP GUI version), I can help tailor the solution further.