Skip to end of metadata
Go to start of metadata

Keywords

cannot start VAS/VMS, Mobile authnetication server, Mobile processing server

Description

You may notice that the VAS and VMS servers stop immediately after starting them. This means that your mobile servers are not configured properly.

Solution

  1. Check if BES entries are correct and the syntax is proper.
  2. Check if there are port conflicts for VAS and VMS. Resolve if there are any.
  3. Check if the database settings are configured properly, and the database is up and running.
    Note: Ensure that you have run database scripts before configuring your mobile with any database server other than Apache Derby. And also check if you have appropriate rights to update, insert, execute procedures, use indexes on the database schema.
  4. If you are in a scenario where you are able to start VAS but not VMS, then the possible reason could be clustering issues between VAS and VMS servers. This problem might occur if the DNS is not able to resolve fully qualified name for your Host machine. In this case, you must use IP address for the Host.

If you want to monitor your VAS and VMS servers, you can start servers from the windows command line.

To start VAS:

  1. Open command window.
  2. Navigate to C:\Program Files (x86)\SAP BusinessObjects\Mobile 14\server\VAS\bin
  3. Run vtauthd.bat start2.

To start VMS:

  1. Open command window.
  2. Navigate to C:\Program Files (x86)\SAP BusinessObjects\Mobile 14\server\VMSServer\bin
  3. Run vtvmsd.bat start2.

If you want to find the exact cause for why Mobile servers are not starting, check the VAS and VMS log files located at: <SAP_BOBJ_INST_DIR>\SAP BusinessObjects Enterprise XI 4.0\logging

Ensure that you set the logging level to "Fine" while debugging so that the finest information is logged. For information on setting log levels, see the SAP BusinessObjects Mobile Installation and Deployment Guide available at: http://help.sap.com

  • No labels