Starts XP Server manually.


xpserver -S XP_Server



  • When you run xpserver in root, xpserver automatically enables secure access on the machine as if you set the xp_cmdshell context configuration parameter to 1, thereby preventing users from accessing the SAP ASE server unless they are also valid users on the machine.

  • XP Server is normally started automatically by the SAP ASE server. Use the manual command to start XP Server only when instructed to do so in an “XP Server Failed to Start” error message.

  • There can be only one XP Server per SAP ASE server. An SAP ASE server running ESPs communicates with a single XP Server, and the ESPs execute synchronously.

  • The -p parameter affects the priority used by the Open Server scheduler. If -p is set to a high number, the scheduler can run XP Server before running the other threads in its run queue. If -p is set to a low number, the scheduler can run XP Server only when there are no other Open Server threads in its run queue. This parameter is unrelated to the application queue priorities within SAP ASE, which are set by sp_bindexeclass.

    See the discussion of multithread programming in the Open Server Server Library/C Reference Manual.

  • If automatic unloading of ESP functions is not set by the -u parameter or by the esp unload dll configuration parameter, unload them at runtime using sp_freedll.

  • Unlike an SAP ASE server and Backup Server, XP Server does not have a runserver file.

  • When configuring an XP Server, the directory service entry name must end with “_XP” in upper case, such as “abcdef_XP” or “ABCDEF_XP.”

See also:
  • Reference Manual: Proceduressp_configure, sp_freedll, xp_cmdshell extended stored procedure


No special permissions are required to run xpserver.

Related concepts
Utility Commands Reference