Skip to Content
Product Information
Author's profile photo Joerg Wolf

SAP S/4HANA 1709 (SP00 & FPS01) Fully-Activated Appliance: Hints & Known Issues

This blog covers latest information and known issues for the SAP S/4HANA 1709 (SP00 & FPS01) Fully-Activated Appliance. If not indicated otherwise, the issues will occur in client 100 or across all clients.

The overview blog for this appliance can be found under

Update July 2021:
This appliance will soon be revoked from SAP Cloud Appliance Library since the underlying Linux release (SLES 12) will go out of maintenance and the solution can not be ported to the more recent SLES 15.
If you are in need of the SAP S/4HANA 1709 Fully-Activated Appliance, you can still obtain the appliance image for installation on your own hardware (see SAP Note 2041140).

Overview of fixes in the appliance from 1709 SP00 to 1709 FPS01

The following issues have been fixed in the SAP S/4HANA 1709 FPS01 fully-activated appliance compared to the SP00 version.

  • Cross Topics > Access via SAP Analysis, Eclipse ABAP, …
    • Needed settings have been entered
  • Fiori launchpad > User Assistance not visible
    • The Web Dispatcher proxy parameters (which contained an SAP-internal proxy in SP00) have been cleansed. SAP employees: Usage from the SAP-internal CAL network requires the re-entering of SAP proxy settings.
  • Fiori launchpad > Client 200/300/400 access
    • Client 100 has been removed from the RFC destination LOCAL_HTTP

Cross Topics

Initial system performance after instance creation

When you create an instance, the initial system performance will be slow, especially within the Fiori Launchpad (some minutes of response time for the logon / first tiles, potentially a time-out). Also, the first click on a Fiori tile will be significantly slower. This is due to initial caching in the system and will become faster if you continue working.  

Note to SAP administrators: SGEN has been performed to pre-compile ABAP coding.


Supported hosting providers for the SAP S/4HANA 1709 Fully Activated Appliance

Currently, Amazon Web Services (AWS), MS Azure, Google Cloud Platform (GCP) and SAP Monsoon (only SAP-internal for 1709 SP00) are supported cloud providers for the SAP S/4HANA 1709 Fully Activated Appliance.


Access via SAP Analysis for MS Office, Eclipse ABAP perspective, and other RFC-based channels (SP00 only)

When trying to open a connection from SAP Analysis for MS Office to SAP S/4HANA (using a local entry in your SAP Logon), you get the error message:

LOCATION    SAP-Gateway on host vhcals4hci.dummy.nodomain / sapgw00
ERROR       reject connection request from […]
MODULE /bas/[…]/gwr3cpic.c


  1. Open transaction SMGW > Goto > Expert Functions > External security > Maintain ACL files> > switch to tab prxyinfo
  2. Add a standard line to the PRXYINFO tab as follows to allow all traffic regardless of network.:
  3. Save > Activate Globally

Please also ensure that the ports 3300 and 30215 are opened for your instance. These ports are open by default but you can check/change this in the instance details of your CAL instance ( > Instances > [Click on your instance] > Virtual Machines > Access Points)


Fiori Launchpad

The Fiori User Assistance icon (question mark icon on top right) is not visible

The reason for this could be two things:

  1. Wrong proxy setting in the Web Dispatcher configuration.
    This is wrongly configured in the SAP S/4HANA 1709 SP00 fully-activated appliance, so fix this first. Resolution needs access to the Linux backend system of the appliance (via PuTTY/ssh) and takes ~10-15 minutes.
    This has been fixed in the FPS01 version of the appliance.Note to SAP employees: if you have deployed a 1709 SP00 version of the appliance in the SAP-internal CAL network, you don’t have to touch this setting, proceed directly with step 2 below.
    If you are using the 1709 FPS01 version of the appliance, you will have to re-enter the two parameters into the Web Dispatcher configuration (see below), since otherwise you won’t have access to the user assistance content.
  2. Invalidated certificate for the server that contains the help content.
    If the corrected proxy setting does not take effect, apply this fix. Resolution is browser-based and takes ~5 minutes.
1. Resolution for the wrong proxy setting in Web Dispatcher
  1. Log on to the Linux backend system as root. You will need PuTTY (or another SSH client) and the private key file (.pem) that was generated when you created the instance. Unless you chose to save it on your own computer, the .pem file can be downloaded from the instance details page. For details how to log on with PuTTY, see this page > How to connect to a running instance via the secure shell protocol (SSH).
  2. When logged on to Linux, enter su s4hadm (to change to user s4hadm)
  3. Enter cd /usr/sap/S4H/SYS/profile (to change to the directory with the Web Dispatcher config files)
  4. Enter vi S4H_ASCS01_vhcals4hcs to open the configuration file in the vi text editor
  5. Press E (to edit the file anyway, an older swap version exists as well)
  6. Scroll to the end of the file where you will find the following text block:
    #Configure SAP Web Dispatcher for Context-Sensitive User Assistance
    wdisp/system_3 = SID=ABC, EXTSRV=, SRCURL=/sap/dfa/help/,, SRCSRV=*:*, STANDARD_COOKIE_FILTER=OFF
    wdisp/system_4 = SID=DEF, EXTSRV=,,  SRCURL=/resources/sap/dfa/help/, SRCSRV=*:*, STANDARD_COOKIE_FILTER=OFF
  7. Remove the two occurrences of the PROXY= parameter, i.e. afterwards the two lines should look like this:
    wdisp/system_3 = SID=ABC, EXTSRV=, SRCURL=/sap/dfa/help/, SRCSRV=*:*, STANDARD_COOKIE_FILTER=OFF
    wdisp/system_4 = SID=DEF, EXTSRV=, SRCURL=/resources/sap/dfa/help/, SRCSRV=*:*, STANDARD_COOKIE_FILTER=OFF
  8. Enter [ESC]:wq (to write the file and quit the vi editor)
  9. Lastly, restart the Web Dispatcher. Log on to https://vhcals4hcs.dummy.nodomain:44301/sap/admin/public/default.html with user bpinst and password Welcome1 (for this URL to work, you need to maintain your local hosts file)
  10. In Core System > Monitor > Status, choose Shutdown SAP Web Dispatcher from the drop-down menu and confirm.
  11. Reload the Fiori Launchpad in your browser to check if the question mark icon with the User Assistance is visible. If not, proceed to 2.
2. Resolution for the invalidated certificate of the help content server
  1. Go to with the Chrome browser (other browsers may work differently). An empty white page should appear.
  2. Click the ‘lock icon’ on the left of the URL
  3. Click Certificate > Valid
  4. Go to Details tab
  5. Click “Copy to File”
  6. Select “Next”
  7. Choose “Base-64 encoded X.509 (.CER)”
  8. Browse for the location you want to save it (eg. C:\docs) and type in a file name (eg. ondemand.cer)
  9. Save
  10. Next
  11. Finish
  12. OK
  13. Go to https://vhcals4hcs.dummy.nodomain:44301/sap/admin and login with user BPINST, password Welcome1
  14. Go to Menu > SSL and Trust Configuration > PSE Management
  15. From the Manage PSE pulldown menu (top of the page), select SAPSSLC.pse
  16. Click on import certificate
  17. Open the saved certificate (eg. “ondemand.cer”) from the saved location with notepad
  18. Copy the content of the file between —–BEGIN CERTIFICATE—– and —–END CERTIFICATE—-,including those two lines
  19. Paste this into the “import certificate” form and then click Import
  20. Go to Menu > Core System > Monitor > Click on running drop down menu > Select  Shutdown of SAP Web Dispatcher. Confirm the warning message and select Back.
  21. Refresh the Fiori launchpad page and you should see the ‘question mark icon’ with the context-sensitive Fiori help items (you might need to clear your browser cache as well).


General remark on the Fiori Web Assistant content:

If you click the help icon (question mark) directly on the Fiori launchpad homepage, you will see Guided Tours that are not applicable for the SAP S/4HANA 1709 Fully-Activated appliance, so please ignore them and use the Web Assistant on specific Fiori tiles only.


Clients 200/300/400 (or other newly created clients): WebGUI / Web Dynpro apps prompt for separate log-on or access is blocked


If you log on to the Fiori launchpad in a client different than 100 and try to open WebGUI / Web Dynpro apps, you are prompted with a separate log-on screen or are blocked from access with a security certificate message.


You need to remove client 100 from the RFC connection LOCAL_HTTP: tCode SM59 > HTTP Connection to ABAP System > LOCAL_HTTP > Logon & Security > Remove entry 100 in Client field (leave it blank) > Save.


Eclipse / HANA Studio

Message about “Secure Storage Locked” in Eclipse / HANA Studio on remote desktop


When you launch Eclipse on the remote desktop in SAP CAL, you get a “Secure storage locked” error in the systems view tile. Clicking on the Unlock button doesn’t have any effect, and you can not access or create a connection into the HANA database.


On the remote desktop, delete the folder “.eclipse” in the users directory of the logged on user (e.g. C:\Users\Administrator if you are logged on with user Administrator).
Restart HANA Studio / Eclipse afterwards.


Creating a new ABAP package fails in Eclipse


When you try to create a new ABAP package in the Eclipse ABAP perspective, the creation fails with error message “Execution of request “POST /sap/bc/adt/packages” failed: 404 Not Found”.


Implement SAP note 2574380 (might prompt you to implement another depending SAP note), or create the package via SAP GUI (tCode SE80) and access the package in Eclipse afterwards.


“Manage Customer Returns” app (scope item BKP, Advanced Customer Returns)

On the ‘Manage Customer Returns’ app, it’s not possible to select the Return Document number and to activate the ‘Determine Refund’ button. If trying to access the link ‘ Refund Determination’ from the document number, an error ‘ the request Resource not found’ is displayed.
As a workaround, you can use the app “Determine Customer Refund”.


“Display Outbound Delivery” app (scope item 1IU, Customer Consignment)

The “Output Control” button is not active.As a workaround: from the initial screen of the app, select More > Outbound Delivery > Issues Delivery Output


“Manage Debit Memo Requests” app (scope item BDQ, Invoice Correction Process with Debit Memo)

The PDF output for order type CBII Invoice Increase Req. is not possible.
Under investigation.


“Manage Credit Memo Requests” app (scope item BKL, Invoice Correction Process with Credit Memo)

No output possinle for doc type RK Invoice Correct. Request..
Under investigation.


Asset Management

“Change Maintenance Notification” app (scope item BH1, Corrective Maintenance)

On the “Change maintenance notification” app, assigning an order to a notification is not possible. As a workaround, use the app “Manage Notification List” to assign orders.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Roland Kramer
      Roland Kramer

      So klein ist die Welt, hallo Jörg …

      Bin gerade dran, S/4 1709 zu installieren, leider gibt es keine Kernel 7.53 DVD die benötigt wird

      Mal sehen, wie weit ich mit der FA Version komme … ?


      Viele Grüsse Roland


      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author

      Hi Roland,

      yes, small world 😉

      One remark:

      the yellow-marked link above is only visible for SAP employees or for customers / partners who have been authorised to download the appliance (see note 2041140 for details).

      Other than that, have fun with the fully-activated appliance.

      Gruesse Joerg

      Author's profile photo Wipro Infotech
      Wipro Infotech

      Can you please link for Installation guide for SAP S/4HANA 1709 Fully activated appliance

      Author's profile photo Claus-Peter Paffrath
      Claus-Peter Paffrath

      Hi Joerg,

      many thanks for your Blogs.

      But I have another Issue: my Colleagues need in Addition several UI Add Ons, eg. UIHR001, UITRV001 for HR Self Services. Now there is a Problem with the Maintenance Planner: due to the Component MSGPMCON 200 the Maintenance Planner assumes, that the Component SAP Insurance FS-PM 5.3 for Netweaver is installed in the System. And therefore no Stack calculation is possible (due to NW 7.40). Clean up in Verification won't correct the Information. In Solution Manager and LMDB the System Information is correct. Any Idea?

      Best Regards


      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author


      Hello Claus-Peter,

      Normally, there's an option to ignore such a mismatch in the Maintenance Planner but if that one doesn't work (or is not even visible), I don't have a quick solution for that one.

      Could you open a question in the community for S/4HANA in that case(  ?



      Author's profile photo Former Member
      Former Member


      I cant connect to either via GUI or remote desktop  PLEASE assist



      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author

      Hello Silas,

      are you mabye behind a corporate firewall ?

      In general, please use the CAL forum and open a new thread for your issue,  describing what you did (and including your CAL user or instance ID).

      Please don’t append your question to existing threads, it’s easier to follow that way.

      Thanks, Joerg

      Author's profile photo Andre Fischer
      Andre Fischer

      I had issues to connect using ADT tools.

      I found the solution in this archived discussion

      A.) Open ports in CAL (from Joerg Wolf )

      Open the respective ports in CAL if not yet done (this is closed by default):

      - Custom TCP, 3300 for access from ABAP in Eclipse to S/4HANA ABAP stack

      - Custom TCP, 30215 for access from HANA Studio / modeling perspective to HANA DB

      Click on the instance in the CAL console to bring up the instance details and then -> Virtual Machine -> Edit (right lower corner) -> Add (access point) -> <add above ports, as IP range choose> -> Add -> Save.



      B.) Change settings in transaction SMGW

      1) Go to SMGW-->Goto-->Expert Functions-->External security-->Maintenance of ACL files-->switch to tab prxyinfo

      2) Add a line to the PRXYINFO tab as follows to allow all traffic regardless of network.

                     P SOURCE=* DEST=*

      3) Go back (F3) --> Save (and on the Popup) -> Activate Globally

      Method found by Former Member in another thread from Former Memberand @Vicente CastelloCannot login with RFC to&amp;nbsp; DEMO / Evaluatio... | SCN


      Author's profile photo kyo choi
      kyo choi

      I have been trying to activate following appliance but I am having issue. My account is developer and I have activated 1610 and I can use it successfully.

      Error message says, “The operation Resume is not allowed for the solution instance “.  Has anyone activated 1709?

      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author

      Hello Kyo,

      I noticed that you posted the same question in the SAP CAL community (see here), and the CAL team is already on it.

      In the future, please use the CAL community as channel for concrete issues (as you did) since comments to blogs are harder to find & track. And cross-posting in different places is always tricky ;-).





      Author's profile photo Hiroshi Iguchi
      Hiroshi Iguchi



      My company has a Fully Activated Appliance system (1610).
      It is currently in use.

      For this reason, we need to change the system ID of HANA and S/4HANA in order to build Fully Activated Appliance 1709 with another instance.
      (The reason is that you can not apply for duplicate hardware keys with the same system ID)

      We are trying to change the system ID when installing Fully Activated Appliance 1709.
      If we change the system ID, please tell me what kind of trouble the system will have.



      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author

      Hello Hiroshi,

      if you have installed it on-premise (i.e. received the appliance via download or Blu-Ray discs), you can change the SID during the installation. The guide is attached to SAP Note 2041140.

      If you use the system via CAL (i.e. hosted), you should have different hardware keys per instance.

      Best, Joerg

      Author's profile photo Hiroshi Iguchi
      Hiroshi Iguchi

      Hiroshi Iguchi May 8, 2018 at 12:53 am


      I appreciate your answer!.

      Do you know “DEMO 21”?
      (It is an online workshop for installing the Fully Activated Appliance by SAP.
      I am participating in this workshop. )

      I recognize that DEMO 21 and Fully Activated Appliance are the same.
      When I build multiple Demo 21s on different servers, can I change the system ID of S / 4 and HANA in the way you instructed?


      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author


      Hello Hiroshi,

      yes DEMO21 is re-using the appliance (a few changes here and there but all in all it's the same image).

      I am not sure if SID renaming is "supported" (in terms of encouraged as a separate activity in DEMO21) since the delivery format of DEMO21 is a bit different to the regular delivery of the appliance, so please check directly in the JAM group of DEMO21.

      Best, Joerg

      Author's profile photo Cornelia Buwaya
      Cornelia Buwaya



      we have deployed a Fully Activated  free trial Appliance (1709). But we can't process any DB changes. WE always get the message Database error 10 at CON

      and a message autentication failed. What can we do to stop this?

      Any idea?

      Thanks a lot.


      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author

      Hello Cornelia,

      If it is the 1709 FPS01 appliance:

      Did you update the HANA DB connection in tCode DBACOCKPIT (please see the Getting Started Guide page 18 on ?

      If this is not the root cause, could you please ask this question in the CAL community ( since it's easier to process & comment in a separate thread.

      Best, Joerg


      Author's profile photo Cornelia Buwaya
      Cornelia Buwaya

      Hello Joerg,

      Thanks a lot. It was exactly the right solution. We didnt update the DB connection.

      Its always better to read carefully....






      Author's profile photo Christopher Adeyoju
      Christopher Adeyoju

      I recently got locked out of the database due to expired license and when i try to connect through Hana studio using the SYSTEM user and password, i'm only able to access the tenant database.

      When i specify multitenant and use the same credentials, it doesn't let me login as the SYSTEM user, however i'm able to log in as the tenant which is not what i need to apply the license.

      How do i access the SYSTEM database in order to apply the license?

      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author

      Hi Christopher,

      the HANA license key can be installed in HANA Studio (Multiple Containers > System DB), and the SYSTEM user with your master PW should work there as well.

      Can you try this on the remote desktop first (to eliminate any port/network issues) ?

      If you use your local Eclipise / HANA Studio, you might need to open additional ports in the CAL Console (Virtual Machines > Access Points).

      Typically, the ports 30201, 30213 and 30214 are relevant (as usual, digit 2&3 denote the instance number which is 02 in our case).

      We didn't open these ports by default to have tighter security from the Internet.

      Here's a helpful documentation:

      Best, Joerg


      Author's profile photo Christopher Adeyoju
      Christopher Adeyoju

      I logged in as HDB SYSTEM and tried, getting the error 

      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author

      Hi Christopher,

      this happens when trying to apply a license in the tenant DB.

      Try the following from the remote desktop:

      Add a new system in the HANA Studio and choose "Multiple Containers > System Database" (see below), in the next screen enter SYSTEM user and your master PW. Then apply the license file as you tried above for the tenant DB.

      If the problem persists, please open a thread in the CAL community ( since it’s easier to process & comment in a separate thread.

      Best, Joerg



      Author's profile photo Frank Di Polo
      Frank Di Polo


      We are trying to access the FIORI Launchpad directly on the remote client of our 1709 Trial CAL system and today it gave us an error on the domain. We have not made any changes on the hosts file of the remote client machine, hence what could be wrong?


      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author

      Hi Frank,

      from the error it looks as if the IP address can not be found.

      Did you specify to use a static IP address for your instance (there's a checkbox in the CAL console of your instance), otherwise you will get new IPs when the instance is suspended.

      Other options to check: does the SAP GUI access works (via SAP Logon) ? If not, the S/4 system may not have come up correctly (try to re-boot the appliance in the CAL console). If it's an SP00 system: License key  expiration also sometimes happens (90 days) ?

      If the problem persists, please open a thread in the CAL community ( since it’s easier to process & comment in a separate thread.

      Best, Joerg

      Author's profile photo Eddy Guo
      Eddy Guo


      We are getting TP_CANNOT_CONNECT_SYSTEM error from Add-on installation (SAINT). I did see the discussion on 1609 article However not able to apply the solution to my case.


      The installation was stopped, since an error occurred during the phase CHECK_REQUIREMENTS,
      which the Add-On Installation Tool is unable to resolve without your input.
      After you have corrected the cause of the error, continue with the import by choosing
      Continue in the queue display.
      The following details help you to analyze the problem:
      – Error in phase: CHECK_REQUIREMENTS
      – Reason for error: TP_CANNOT_CONNECT_SYSTEM
      – Return code: 0200
      – Error message: ERROR: see tp”s stdout (Standard Out may not be
      Notes on phase CHECK_REQUIREMENTS
      In this phase the system checks the various requirements for the add-on installation. The
      following are reasons why this phase may fail:
      – TP_CANNOT_CONNECT_TO_SYSTEM: tp cannot log on to the system database.
      Check the action log (in the menu, choose Goto -> Action Log). You may be able to
      use the detailed tp error message in this log to identify and remove the cause of the error.

      Action Log:

      I1 I2 I3 ED Log Text                                                                                                                            
                Installation/Upgrade of the Add-on   rel.  (16.11.2018, 18:37:04)                                                                   
                Saving the current OCS Queue (16.11.2018, 18:37:49)                                                                                 
                Import of the current OCS Queue (16.11.2018, 18:37:50)                                                                              
              Import of the current OCS Queue (16.11.2018, 19:44:56)                                                                              
                  The import is continued in phase ‘CHECK_REQUIREMENTS’                                                                               
                Import phase ‘PROLOGUE’ (16.11.2018, 19:44:59)                                                                                      
                  Import phase ‘PROLOGUE’ was successfully finished (16.11.2018, 19:44:59)                                                            
              Import phase ‘CHECK_REQUIREMENTS’ (16.11.2018, 19:44:59)                                                                            
                Error during executing the tp command ‘tp CONNECT S4H   …’                                                                        
                Interrupt the import due to an error situation (16.11.2018, 19:44:59)                                                               
                  Display detailed informations concerning the error in phase ‘CHECK_REQUIREMENTS’                                                    
                Abort the import due to an error situation (16.11.2018, 19:46:12)                                                                   


      Best regards,


      Author's profile photo Eddy Guo
      Eddy Guo

      Okay. I fixed this and here's what I did:

      ssh -i <pem file> root@<host ip>
      su s4hadm
      • Verified that /usr/sap/trans/bin was empty initially.
      • I didn’t delete STMS config.
      • One of the Save action I did in SMTS resulted the generation of file/usr/sap/trans/bin/DOMAIN.CFG.
      • The comment in DOMAIN.CFG file inspired me to do STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration.  This generated /usr/sap/trans/bin/TP_DOMAIN_S4H.PFL hence fixed the problem.

      Note 96907 and 2430126 enabled me to stay on the right direction.

      I had to use the method from

      to verify that tp connect is working properly:

      sid-hdb-s4h:s4hadm 25> tp connect S4H pf=./TP_DOMAIN_S4H.PFL
      This is tp version 381.19.67 (release 753, unicode enabled)
      Connection to Database of S4H was successful.
      This is R3trans version 6.26 (release 753 - 19.09.17 - 14:33:00).
      unicode enabled version
      R3trans finished (0000).
      tp finished with return code: 0
        Everything OK

      Content of the DOMAIN.CFG file:

      sid-hdb-s4h:s4hadm 14> cat DOMAIN.CFG
      Transport domain S4H
      System S4H GUOED
      System S4H
      Transport group S4H GUOED
      #Caution !
      #This file was generated by the Transport Management System.
      #Do not change this file using a text editor.
      #If this file was destroyed, it can be regenerated in the TMS.
      #To do this, log on to the domain controller (system S4H) and call
      #Transaction STMS. In the System Overview, you can distribute the TMS
      #configuration. This regenerates the file.
      #STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration
      Author's profile photo Kim Hjorth Poulsen
      Kim Hjorth Poulsen

      Dear Joerg,

      I was very excited to try our access to a HANA system. FAGLL03H was one of the transactions that I was very curious about. Unfortunately the transaction is not working.

      If I execute the transaction I get below error message:
      "An error occurred during database selection: The database returned the SQL code 391. The errortext is: invalidated view: V_GLPOS_N_GL_CT: line 1 col 120 (at pos 119)."

      Looks to me like this is not just a customizing fix.
      Do You know the reason why FAGLL03H is not running?

      Best regards,

      Kim Hjorth Poulsen

      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author

      Hi Kim,

      please check if SAP Note 2697953 resolves your issue (in essence this is about re-generating the DB views in tcode HDBVIEWS).

      I tried this on our S/4HANA 1809 Fully-Activated appliance (successor of the appliance release that you are obviously using), and it fixed the issue there.

      To your question why the tCode is not working from the beginning:

      We simply cannot touch&test every single aspect of S/4HANA within our appliance. But since you are the administrator of your system instance, you can fix&adapt things on your own.

      Best, Joerg

      Author's profile photo Roland Kramer
      Roland Kramer

      Hello Joerg, still under way with your appliance?

      I just posted an update about the FPS03 import in my S/4 1709 system ... S/4HANA 1709 FPS03 – back on the Mothership again … as I found the manual way of installation still more fruitful ... 😉

      Best regards Roland

      Author's profile photo Kim Hjorth Poulsen
      Kim Hjorth Poulsen


      Thanks Joerg. Worked perfectly.

      Author's profile photo Navdeep Singla
      Navdeep Singla



      we have installed S4HANA1709 system using Fully Activated Appliance.

      Initially system was running and we have done functional configuration as well.

      However today system went down suddenly and when we checked the traces we could see that dispatcher went down with below errors.


      rdisp/user_resource_limit/apc: warn=625/reject=1250

      ***LOG Q1K=> MsIAttachEx: compatibility check failed, Kernel not compatible with system [msxxi.c      1645]

      *** ERROR => Compatibility check failed, kernel not compatible with system (see dev_ms for details) [dpMessageSer 1852]

      ********** SERVER SNAPSHOT 1 (Reason: Hard Shutdown) – begin **********

      Server s4hana1709_S4H_00, Fri Feb 15 13:14:11 2019

      When we checked message server trace message service is up and running fine as shown below.

      [Thr 140589005047616] Fri Feb 15 13:06:58:058 2019

      [Thr 140589005047616] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 13244) [msxxserv.c   2787]

      [Thr 140589005047616] SigISetDefaultAction : default handling for signal SIGCHLD

      [Thr 140589005047616] load acl file = /usr/sap/S4H/SYS/global/ms_acl_info

      [Thr 140589005047616] List of entries found in /usr/sap/S4H/SYS/global/ms_acl_info

      [Thr 140589005047616] [001] * [::] (VALID)

      [Thr 140589005047616] MsGetOwnIpAddr: my host addresses are :

      [Thr 140589005047616]   1 : []  (HOSTNAME)

      [Thr 140589005047616]   2 : []  (LOCALHOST)

      [Thr 140589005047616]   3 : []  (NILIST)

      [Thr 140589005047616] MsHttpInit: full qualified hostname = s4hana1709

      [Thr 140589005047616] HTTP logging is switch off

      [Thr 140589005047616] set HTTP state to LISTEN

      [Thr 140589005047616] *** HTTP port 8101 state LISTEN ***

      [Thr 140589005047616] *** I listen to port sapmsS4H (3601) ***

      [Thr 140589005047616] *** I listen to internal port 3901 (3901) ***

      [Thr 140589005047616] *** HTTP port 8101 state LISTEN ***

      [Thr 140589005047616] CUSTOMER KEY: >R0382899352<

      [Thr 140589005047616] compatibility level = 0

      [Thr 140589005047616] build version=753.2017.08.01

      [Thr 140589005047616] read logon groups from previously stored file S4H_msg_server_adtl_storage

      [Thr 140589005047616] Server state ACTIVE


      Present kernel version is 753_REL PL20 .

      Any ideas how to resolve this please?

      Thanks and Regards,


      Author's profile photo Joerg Wolf
      Joerg Wolf
      Blog Post Author

      Hello Navdeep,

      not really from this log.

      I understand you installed the appliance on your own hardware (with a new host name), hence, it should behave like a regular system now where you need to support it.

      Please try looking for SAP Notes on this matter. Potentially a Kernel update might help (since the one used is pretty old).

      Best, Joerg