Known SAP Issue: Error connecting to UI (UI API Server - Server is Down)

During the add-on startup, you can see the following message:

image003.jpg

This error is an SAP Bug (Note: https://launchpad.support.sap.com/#/notes/2875011)

Workaround (from SAP):

End all SAP Business One Client-related processes (SAP Business One.exe and SAPbouiCOM.exe) and restart SAP Business One Client.

If the workaround doesn't fix the issue and it's persistent, please contact SAP support as this is an issue with the SAP environment.

There are a few things we know that can help:

1. Run the client in "Run as administrator" mode. If this helps, then there's something wrong with the permissions on the system as the UI-API cannot run while starting the B1 Client without administrative permissions.

2. The SAP B1 Client components are not registered correctly, or the installation has been corrupted. In that case, please follow our reinstallation guide to install the SAP B1 client properly.

 

 

 

 

 

 

 

 

 

 

Was this article helpful?

1 out of 3 found this helpful

Comments

7 comments

  • Comment author
    JP Mendoza - Ozone IT
    Hi, We seem to be experiencing this error with one of our clients. Is there any answer to this error? what do we have to do to sort this out? Regards JP
    0
  • Comment author
    Yaremi Miranda Lopez
    Hello Jun, unfortunatelly this B1UP error message is generated by SAP, we recommend that you contact SAP directly to solve this issue.
    0
  • Comment author
    Lee Mark
    Jun: we get this error a lot as well, did you find a solution?
    0
  • Comment author
    JP Mendoza - Ozone IT
    • Edited

    Hi Lee What I have done is I deleted the SM_OBS_DLL located on the temp folder and then run SAP B1 to recreate that folder for it to apply the proper security permission. This seemed to have worked for me. Regards JP

    0
  • Comment author
    Rasmus Jensen

    It also seem that finding all "SAP Business One.exe" on the machine (across all users) and killing them with Task Manager resolves the issue in some cases instead of restarting the entire server

    1
  • Comment author
    Michael Herrmann

    Just checking in to see if there are any updates on this issue?

    Regards,

    Mike

    0
  • Comment author
    Gregg Goede

    I too am having a problem with this error while performing a reinstallation. Only one user affected so far.

    Have not restarted server yet. Will also try Jun method

    0

Please sign in to leave a comment.