I copied sapjco3.dll
to
C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.FlightBooking\
The librfc32.dll is in the C:\Windows\SysWOW64\
Don't know how it got there but it must be accessible from anywhere.
Restarted SMP
Text of error changed
19:00:20 02/17/2016: Starting Agentry (64-bit Windows)
19:00:29 02/17/2016: Reading system ini file.
19:00:29 02/17/2016: Starting log file.
19:00:29 02/17/2016: Loading message groups.
19:00:29 02/17/2016: Starting threads.
19:00:29 02/17/2016: 1 initial threads. Threads will auto-scale.
19:00:29 02/17/2016: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.
19:00:29 02/17/2016: Event: 0, 2, Key pair loaded successfully.
19:00:29 02/17/2016: Starting Agentry: Agentry Server Agent v130.7.0.4
19:00:29 02/17/2016: Event: 0, 2, Agentry Startup
19:00:29 02/17/2016: Loading 0 front ends
19:00:29 02/17/2016: Starting Agentry Server Agent
19:00:29 02/17/2016: Agentry Server Agent: Starting threads.
19:00:29 02/17/2016: 1 initial threads. Threads will auto-scale.
19:00:29 02/17/2016: Agentry Server Agent: Adding messages.
19:00:29 02/17/2016: Event: 1, 4, Agentry Server Agent v130.7.0.4
19:00:29 02/17/2016: Loading agent from ag3.dll
19:00:29 02/17/2016: Starting FlightBooking
19:00:29 02/17/2016: FlightBooking: reading config file
19:00:30 02/17/2016: Event: 20, 150, Loading Development application definitions
19:00:31 02/17/2016: Initializing Java-BackendSAPConnection from ag3javabe.dll
19:00:31 02/17/2016: BackendSAPConnection: Reading configuration information.
19:00:31 02/17/2016: BackendSAPConnection: Setting name to 'Java-1'.
19:00:31 02/17/2016: Java-1: Initialized.
19:00:31 02/17/2016: Java-1: Java Virtual Machine already initialized.
19:00:32 02/17/2016: Exception: 19:00:32 02/17/2016 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: serialNumber is null in SERVICE_LOGON section),
19:00:32 02/17/2016: Failed to init Java-1 (Java v130.7.0.4) from ag3javabe.dll
19:00:32 02/17/2016: Event: 20, 152, Loading Development application definitions for default localization
19:00:32 02/17/2016: Event: 20, 151, Finished loading Development application definitions
19:00:32 02/17/2016: FlightBooking: Starting threads.
19:00:32 02/17/2016: 1 initial threads. Threads will auto-scale.
19:00:32 02/17/2016: Loading front end from angelvine
19:00:32 02/17/2016: FlightBooking: loading configuration
19:00:32 02/17/2016: Event: 17, 14, FlightBooking v130.7.0.4
19:00:32 02/17/2016: Event: 20, 4, FlightBooking v130.7.0.4
19:00:32 02/17/2016: Loading agent from ag3.dll
19:00:32 02/17/2016: Starting SAPWM62
19:00:32 02/17/2016: Event: 21, 4, SAPWM62 v130.7.0.4
19:00:32 02/17/2016: Loading agent from ag3.dll
19:00:32 02/17/2016: Starting SAPWM62_NEW
19:00:32 02/17/2016: Event: 22, 4, SAPWM62_NEW v130.7.0.4
19:00:32 02/17/2016: Starting front ends
19:00:32 02/17/2016: Starting front end FlightBooking
19:00:32 02/17/2016: FlightBooking: Opening WebSockets servlet for sub-URL /FlightBooking
19:00:32 02/17/2016: Event: 17, 10, FlightBooking v130.7.0.4
19:00:32 02/17/2016: Event: 0, 0, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2016-02-17-190019
19:00:32 02/17/2016: Event: 0, 23, Agentry startup is complete.
The ag3javabe.dll file is in the
C:\SAP\MobilePlatform3\Server\configuration\org.eclipse.osgi\bundles\213\data\
folder now.
Can I disable othe applocations from loading to see only log for FlightBooking?