Syclo : Error in connecting Work Manager Client with Agentry Server

[Former Member]

Hi,

Can somebody please shed some light on work manager client-server connections? I have downloaded the "SAP_WORK_MANAGER_BY_SYCLO_5.2" package from market place and set up the Work Manager server. It can successfully connect to the SAP back-end. Environment variables are correctly set too. However, I'm failing to connect to the Work Manager server from the Work Manager clients. I have tried from the Win32 & Android clients both.

For Win32 client, the error I'm getting is:

For Android, I can't even see the server instance, although it's running (it shows up while attempting to connect from Win32). Error:

When I attempt to connect from Work Manager client to the server, it asks for username/password and for Android client it asks for Agentry user id and password. Aren't these username/password of the server where my Work Manager (Agentry) server is installed?

Also, the "Agentry Development Server" which has been set to run as a service runs with Administrative privileges.

I followed this: http://wiki.scn.sap.com/wiki/display/SAPMOB/Agentry+error+Client+Receiving+RFC+ERROR+LOGON+FAILURE+i...

It didn't help. Please let me know where I'm going wrong?

Tags edited by: Michael Appleby

[bill_froelich · Accepted solution]

I would also like to point out that the Work Manager 6.0 product has been released and I would strongly recommend using that as your starting point rather than the 5.2 version you are currently working with.  It will better position you to move forward as the product team releases new versions of the applciation and platform.

--Bill

[Former Member · Accepted solution]

I shall keep that in mind, Bill. Thanks a lot.

[syam_yalamati · Accepted solution]

Hi Sreyan,

    You can verify whether the personnel number properly assigned to mobile user or not by using Info Type table PA0105 and by passing Communication Type  = 0001 and ID/Number = <SAPUserID> and make sure record is available in this table.

Regards

Syam

[Former Member · Accepted solution]

Hi Syam,

There are no records against 0001/ABAPDEV in the PA0105 table.

[Former Member · Accepted solution]

Hi Sreyan,

"No personnel ID is found" Definitely the configuration issue.

You have done everything right so far only thing is you have not done HR configuration for this user(Login User).

Following things you need to do

1. create a pernr in SAP backend(IF alreday created use same)

2. Create record for communication in PA30 using infotype as 0105 and subtype as 0001.

3. then assign Syclo login user(SAP User) in UserID field.

3. This pernr you need to assign to Work orders.

You can take help form HR team to get this done.

Hope it helps.

Regards,

Abhishek Wajge

[Former Member · Accepted solution]

As mentioned previously the error you have is that you have not maintained a 0105 infotype for the personnel number.

Simply go to transaction PA30 enter your personnel number -> select system address -> change -> enter your SAP username into the System ID field. This is the vaildation that is failing.

If the data is maintained there check BAPI BAPI_USER_GET_DETAILS make sure you have authorisation to run this - as this is what gets the data for the personnel number check for which you are seeing an error..

Thanks

Stu

[Former Member · Accepted solution]

Hi Syam,

I think I was able to solve the issue. Thanks for the PA0105 hint.

Record for ABAPDEV existed in PA0001 table and had a personnel id of 10 but was missing from the PA0105 table.

So I went to PA30 transaction

1) There gave an active employee no. (personnel id) [Mine was 10 for ABAPDEV]

2) Entered Infotype as 0105 and Subtype 0001

3) Entered ID value as ABAPDEV

4) Pressed F5 to create

Entry was created in PA0105 for 0001/ABAPDEV. ABAPDEV got correctly assigned to its personnel id/number.

Now, I can login to Work Manager client using the SAP credentials.

Thank you experts!!

[Former Member]

Can you post the Agentry Startup.log file?

[Former Member]

Hi Steeve,

Here's the Startup log.

10:20:16 03/13/2014: Starting server (64-bit Windows)

10:20:16 03/13/2014: Administration client command port is 49156, status port is 49157

10:20:16 03/13/2014: Reading system ini file.

10:20:16 03/13/2014: ID: SMART Work Manager for SAP Server v5.2.0.0, Name: ???, Location: ???

10:20:16 03/13/2014: Starting log file.

10:20:16 03/13/2014: Loading message groups.

10:20:16 03/13/2014: Starting threads.

10:20:16 03/13/2014:    1 initial threads.  Threads will auto-scale.

10:20:16 03/13/2014: Starting Server: Agentry v6.0.14.0

10:20:16 03/13/2014: Event: 0, 2, System Startup

10:20:16 03/13/2014: Loading 1 front ends

10:20:16 03/13/2014: Loading front end from angelvine.dll

10:20:16 03/13/2014: ANGEL Front End: reading init files.

10:20:16 03/13/2014: Event: 17, 14, ANGEL Front End v6.0.14.0

10:20:16 03/13/2014: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.

10:20:17 03/13/2014: Event: 0, 2, Key pair loaded successfully.

10:20:17 03/13/2014: Starting Server Agent.

10:20:17 03/13/2014: Agentry: Starting threads.

10:20:17 03/13/2014:    1 initial threads.  Threads will auto-scale.

10:20:17 03/13/2014: Agentry: Adding messages.

10:20:17 03/13/2014: Event: 1, 4, Agentry v6.0.14.0

10:20:17 03/13/2014: Loading 1 agents

10:20:17 03/13/2014: Loading agent from ag3.dll

10:20:17 03/13/2014: Starting Server

10:20:17 03/13/2014: Server: reading ini file

10:20:18 03/13/2014: Initializing 1-Java from ag3javabe.dll

10:20:18 03/13/2014: SystemConnection-1: Reading configuration information.

10:20:18 03/13/2014: SystemConnection-1: Setting name to 'Java Back End'.

10:20:18 03/13/2014: Java Back End: Initialized.

10:20:20 03/13/2014: Java Back End: Java Virtual Machine loaded.

10:20:36 03/13/2014: Java Back End: Java Back End AJAPI version 5.0, release 6.0.14.0

10:20:36 03/13/2014: Java Back End: Initialized.

10:20:36 03/13/2014: Event: 23, 4, Loaded Java Back End (Java v6.0.14.0 (JVM version 1.7.0_51, AJAPI version 5.0 build 6.0.14.0)) from ag3javabe.dll

10:20:36 03/13/2014: Initializing 2-HTTPXML from ag3httpxmlbe.dll

10:20:36 03/13/2014: SystemConnection-2: Reading configuration information.

10:20:36 03/13/2014: SystemConnection-2: Setting name to 'HTTP-XML Back End'.

10:20:36 03/13/2014: HTTP-XML Back End: Initialized.

10:20:36 03/13/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v6.0.14.0) from ag3httpxmlbe.dll

10:20:37 03/13/2014: Event: 20, 150, Loading Development application definitions

10:20:37 03/13/2014: Event: 20, 152, Loading Development application definitions for default localization

10:24:41 03/13/2014: Event: 20, 153, Finished loading Development application definitions for default localization

10:24:41 03/13/2014: Event: 20, 151, Finished loading Development application definitions

10:24:41 03/13/2014: HTTP-XML Back End Back End: Started

10:24:41 03/13/2014: Server: Starting threads.

10:24:41 03/13/2014:    1 initial threads.  Threads will auto-scale.

10:24:41 03/13/2014: Event: 20, 4, Server v6.0.14.0

10:24:41 03/13/2014: Starting front ends

10:24:41 03/13/2014: ANGEL Front End: Starting threads.

10:24:41 03/13/2014:    3 initial threads.  Threads will auto-scale.

10:24:41 03/13/2014: ANGEL Front End: opening listen socket on port 7003

10:24:41 03/13/2014: Event: 17, 10, 0.0.0.0:7003 open

10:24:41 03/13/2014: Event: 17, 16, Threads in thread pool 'ANGEL Front End' expanded to 4. Adding thread 6220

10:24:41 03/13/2014: Event: 17, 10, ANGEL Front End v6.0.14.0

10:24:41 03/13/2014: Event: 0, 0, Old log files moved into Logs-Rolled\2014-03-13-102016

10:24:41 03/13/2014: Event: 0, 23, 0

10:24:41 03/13/2014: Event: 0, 2, Server startup is complete.

10:24:41 03/13/2014: Agentry Service 'Agentry Development Server' startup complete

[agentry_src]

Hi Sreyan,

Can you login into your SAP backend using the same credentials?

Does your application work in ATE or do you see the same error?

Can you show the JavaBE.ini files where the login information resides?

Please increase your log levels in the Agentry Admin Client and show more details of the error with either screenshots or attached files.

Thanks, Mike

SAP Customer Experience Group - CEG

[Former Member]

Hi Michael,

I can login to SAP backend using the credentials mentioned in JavaBE.ini file.

Please take a look at the JavaBE.ini:

[HOST]

server=<SAP server host name>

;  mobile application name configured in sap like SMART_WORK_MANAGER_51, SMART_CUSTOMER_SERVICE_10, SMART_ISU_WORK_MANAGER_10...etc

APPNAME=SMART_WORK_MANAGER_52

[CONFIG]

;  Used to get the SAP Configutaions from SAP if source=SAP or from JavaBE ini file

;  SAP Configurations are [ENABLE_TABLE], [TABLE_CHECK], [TABLE_REFRESH], [BAPI_WRAPPER],

;  [SAPOBJECT], [CT_SAPOBJECT], [CT_BAPI_WRAPPER], [CT_RETURN_TABLE], [CT_DELETE_TABLE].....etc

source=SAP

[TEST_LOGON]

UID=

UPASSWORD=

UGUID=

SERVERSERIALNUM=

;  Service login user is used to get the SAP Configutaions from SAP if source=SAP

;  Set ENABLED=true if source=SAP or ENABLED=false if source=INI

;  If ENABLED=true, set the UID, UPASSWORD and SERVERSERIALNUM

;  SERVERSERIALNUM is the Agentry server serial number

[SERVICE_LOGON]

ENABLED=true

UID=<SAP backend username>

UPASSWORD=<SAP backend password>

UPASSWORDENCODED=false

SERVERSERIALNUM=AVKNN@NILKGGBTLD

[PUSH_LOGON]

ENABLED=false

UID=

UPASSWORD=

UPASSWORDENCODED=false

SHAREDCONNECTION=10

[CLIENT_NUM]

CLIENT=720

;CLIENT=010

[SYSTEM_NUM]

;SYSNUM=33

SYSNUM=00

[LANGUAGE]

LANG=EN

[LOGGING]

;1=Fatal, 2=Error, 3=Warning, 4=Info, 5=debug, 6=trace

Level=4

[LOGON_METHOD]

;  USER_AUTH if standard UID/Password authentication is used

;  USER_AUTH_GLOBAL if pooled connections using single UID/Password is used

;  USER_AUTH_GROUP if UID/Password authentication with SAP Message Server

;   (load balancing) is used

LOGON_METHOD=USER_AUTH

[GLOBAL_LOGON]

;  referenced when LOGON_METHOD=USER_AUTH_GLOBAL

;  uses a pool of connections to the SAP backend all utilizing a single

;    UID/password

UID=

UPASSWORD=

SHAREDCONNECTION=100

[GROUP_LOGON]

;  referenced when LOGON_METHOD=USER_AUTH_GROUP

;  individual user authentication using an SAP Message Server which distributes

;  client connections among a "group" of SAP application servers based on load

;  balancing criteria

;

;  host name or IP address of SAP Message Server

MESSAGE_SERVER=

GROUP_NAME=

SYSTEM_ID=

CLIENT=

[REQUIRED_BAPI_WRAPPER]

com.syclo.sap.bapi.LoginCheckBAPI=/SYCLO/CORE_SUSR_LOGIN_CHECK

com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT

com.syclo.sap.bapi.RemoteParameterGetBAPI=/SYCLO/CORE_MDW_PARAMETER_GET

com.syclo.sap.bapi.SystemInfoBAPI=/SYCLO/CORE_SYSTINFO_GET

com.syclo.sap.bapi.ChangePasswordBAPI=/SYCLO/CORE_SUSR_CHANGE_PASSWD

com.syclo.sap.bapi.CTConfirmationBAPI=/SYCLO/CORE_OUTB_MSG_STAT_UPD

com.syclo.sap.bapi.DTBAPI=/SYCLO/CORE_DT_GET

com.syclo.sap.bapi.GetEmployeeDataBAPI=/SYCLO/HR_EMPLOYEE_DATA_GET

com.syclo.sap.bapi.GetUserDetailBAPI=/SYCLO/CORE_USER_GET_DETAIL

com.syclo.sap.bapi.GetUserProfileDataBAPI=/SYCLO/CORE_USER_PROFILE_GET

com.syclo.sap.bapi.PushStatusUpdateBAPI=/SYCLO/CORE_PUSH_STAT_UPD

com.syclo.sap.bapi.RemoteObjectCreateBAPI=/SYCLO/CORE_MDW_USR_OBJ_CRT

com.syclo.sap.bapi.RemoteObjectDeleteBAPI=/SYCLO/CORE_MDW_USR_OBJ_DEL

com.syclo.sap.bapi.RemoteObjectGetBAPI=/SYCLO/CORE_MDW_SESSION_GET

com.syclo.sap.bapi.RemoteObjectUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD

com.syclo.sap.bapi.RemoteReferenceCreateBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_CRT

com.syclo.sap.bapi.RemoteReferenceDeleteBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_DEL

com.syclo.sap.bapi.RemoteReferenceGetBAPI=/SYCLO/CORE_MDW_SESSION_GET

com.syclo.sap.bapi.RemoteReferenceUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD

com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL

com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL

com.syclo.sap.bapi.RemoteUserUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD

com.syclo.sap.bapi.TransactionCommitBAPI=WFD_TRANSACTION_COMMIT

com.syclo.sap.bapi.SignatureCaptureBAPI=/SYCLO/CS_DOBDSDOCUMENT_CRT

I haven't yet installed ATE and tested out any application. I just want my connections to be perfect, first.

I have a question. Are the credentials used to connect Work Manager client to the server, same as the SAP backend credentials or are they the credentials of the host on which the Work Manager server is installed?

I have tried logging in using the SAP credentials also. But that results in error too.

These credentials are valid for SAP backend and successfully logs onto it and also responds correctly to connectTest.bat. However, I think this error is logical because these are the credentials for SAP backend and not the server where Work Manager server is hosted.

[Former Member]

Hi Michael,

I came across some articles against this problem. If the username/password that I'm using to connect to the Agentry server be the credentials of the SAP backend system, I think the problem lies somewhere else.

The error I'm getting is:

According to the article SCN: Message List - Syclo - Anyone tried installing sap syclo work manager  app? "No personnel id found for user" error occurs if no accounts have been maintained against the user logging in, under PA30. So I checked against the user ABAPDEV (which is my SAP backend login username) in PA30 (Table PA0001 for entries).

As you can see there is already a personnel no. assigned to the user ABAPDEV. So what exactly could be the issue?

Please help. I'm confused here.

[agentry_src]

You are making contact to the backend successfully, but the error being generated is coming from the authorization process in that same backend.  Perhaps there is something wrong with the personnel number itself.

Yes, the credentials for the backend and those listed in the JaveBE.ini file should be the same.

You may want to try it with a different login to see if it is specific to your ID.  I would also recommend installing ATE and doing your testing from there.

Regards, Mike

SAP Customer Experience Group - CEG

[Former Member]

Hi Michael,

I have tried the same using a different user id. The problem still persists. Is there any specific process for creating a personnel number against an user in PA30 for this purpose?

I'll try using ATE. Currently I have no application to test on ATE. Can you point me to a demo or suggest a workaround?

[Former Member]

Same error while logging into ATE using the JaveBE credentials. Any thoughts?

[agentry_src]

Hi Sreyan,

You already have Work Manager, right?  That should be available for ATE to work with.  Not that I expected it work differently givent that either approach should work or not work dependent upon the credentials authorization in the Backend.  For development purposes, you really do not want it running as a Service.  Let me know if the instructions don't mention that.

What did the logs show?

I also see you logging in with the ID Administrator, not ABAPDEV.  Is that what the instructions say to do from the download site?

I suspect that we may need some more experienced help here and I will try to steer some former Syclo folks this way.

Regards, Mike

SAP Customer Experience Group - CEG

[Former Member]

Yes, I do have Work Manager. Right! At first I did try logging in using Administrator, but after your last comment, I have been trying with ABAPDEV and only then did I come across the PA30 solution, which did not work for me.

Logs showed the same, even after increasing trace levels: "No personnel id found for user ABAPDEV".

For development/production purposes, both cases, it was mentioned to run it as a service.

Work Manager client and ATE are both behaving in the same way.

[agentry_src]

I will see if I can steer some other agentry experts this way.

Thanks, Mike

[jason_latko]

Sreyan,

The user/password you need to enter on the Agentry client are definitely the SAP credentials, not your Windows credentials.  I will forward this post to Syam who is a backend expert.  He will have an answer on how to set up the user correctly.

Jason Latko - Senior Product Developer at SAP

[Former Member]

Thank you Michael.

[Former Member]

Thanks Jason.

Yes, I did use the SAP credentials for Agentry client, but to no vain. I did make a mistake of using windows credentials for username/pass but then Michael corrected me and I have been trying with SAP credentials ever since.