Skip to Content
0

Client locked out.. Problem in bapi create /syclo/core_mdw_session1_del in work manger 6.2?

Dec 20, 2016 at 10:05 AM

502

avatar image

Hi All,

I am getting Client locked out error while logging into Work Manager 6.2 from SMP 3.0 server.I have tried removing the ID from cockpit and reset application but still the same problem exists.Only i have the problem and no other user has.

Please find the below image.

Has anyone faced the above problem so that i can fix the issue.

Thanks,

Don Joseph

10 |10000 characters needed characters left characters exceeded
login-error.png

Please find the image for the following error.

Thanks,

Don Joseph

login-error.png (154.6 kB)
0
* Please Login or Register to Answer, Follow or Comment.

9 Answers

Bill Froelich
Dec 20, 2016 at 01:44 PM
0

Have you confirmed your password is correct? Especially if it is just your account. I have seen similar messages when I used the wrong password.

--Bill

Share
10 |10000 characters needed characters left characters exceeded
Don Joseph Dec 22, 2016 at 09:20 AM
0

Hi Bill,

Yes everything is correct password and username.It just that that user cant login in IPAD Agentry and he can successfully login in SAP logon.

Thanks,

Don Joseph

Share
10 |10000 characters needed characters left characters exceeded
Don Joseph Dec 22, 2016 at 04:44 PM
0

Hi All,

This is what i found in logs:

b*****: Problem in BAPI Create (/SYCLO/CORE_MDW_SESSION1_DEL): while trying to invoke the method com.sap.conn.jco.JCoDestination.getDestinationID() of a null object loaded from field com.syclo.sap.jco.JCo3Connection._destination of an object loaded from local variable 'this'.

The error is with this user only and remaining users can connect.

Thanks,

Don Joseph

Share
10 |10000 characters needed characters left characters exceeded
Sudhir Lenka Dec 23, 2016 at 11:55 AM
0

Hi Don,

Please check the following three things.

1.User has the sufficient authorization to use mobile(compare with other user who is able to login successfully).

2. There is no active session in SAP for this user(SM04).

2. User account is not locked in SAP.

Thanks,

Sudhir.

Share
10 |10000 characters needed characters left characters exceeded
Don Joseph Dec 28, 2016 at 07:40 AM
0

Hi Sudir,

1. User has all the authorization.

Note: he was previously able to connect and suddenly after he changed the password and did some successful syncs he got this error.

2.There is no active session in SAP.

Note:Even if we kill the active session for the user the problem still persist

3.The User account is not locked because he can successfully login in SAP logon and not in Agentry IPAD.

Thanks,

Don Joseph

Share
10 |10000 characters needed characters left characters exceeded
Don Joseph Dec 30, 2016 at 09:43 AM
0

Hi Team,

If any of them faced the same issue could you help me on this.

Thanks,

Don Joseph

Share
10 |10000 characters needed characters left characters exceeded
Mark Pe
Jan 06, 2017 at 03:35 PM
0

Don,

One idea is to see if the user was not properly created in the system. The technique to debug this is to study the name of the method that complained "/syclo/core_mdw_session1_del". As a support engineer, one will see that the name of the method is /SYCLO/ + CORE + MDW + SESSION1 + DEL - this means you have a core functionality (SMFND addon) that is trying to use the Middleware to create a Session1 and a delete.

So for this:

The MDW data is saved in the ERP under the "/SYCLO/MDW*" tables. There are a few tables to consider when reviewing the data during transmit. They are the following:

/SYCLO/MDW00

/SYCLO/MDW01

and others.

The trick is to use SAP Transaction SE16 and when you search for the table look for wildcard "/SYCLO/M*" To see all the Middleware tables. The short text of each of the table will give you the names of the table. One technique is to look at all the MDW tables. Read each of the short description to see what the tables are for (ex: MDWX) and each of those middleware tables tracks certain things.

What you will notice is if you browse using SE16 /SYCLO/MDW00 you will see all the USER_GUID and Server_ID.

Most likely you will need to compare your username (that has an issue) to the other working ones to see if you can get a hint on what the issues are. Now after this, if there is a difference, like all other tables, you can modify it but the rule of thumb is that your username needs to be properly setup as a valid mobile user in one of the /SYCLO/ADMIN steps in the manual.

In short, if you properly entered a new mobile user the system should add the contents to the MDW table correctly. There must be some steps during the upgrade that the team misconfigured or forgot a step and this is why this issue is occurring.

Please review the manual. I am pasting the copy from the manual in this response.

~~~~~~~Reference snippet from the main configuration document page 194~~~~~~~~~~

Mobile User Detail - Basic Info When a user is selected in the Search Results table, the fields are populated in the Basic Info section. Click Change to modify editable fields. Click Create in the Search Result section to create a new user through the editable fields. Fields with a red asterisk beside them are mandatory. w

Mobile Application: Name of the mobile application chosen in the Basic Search Parameters section

User GUID: User GUID for the specific mobile application chosen. Each user has a different GUID for each mobile application assigned in SAP.

User Name: User ID chosen from the table in the Search Result section w SAP Personnel Number: User ID number assigned to the user in SAP

Middleware License Number: Server serial number of the middleware server that is running the chosen mobile application

Mobile Add-On for CRM Administration Portal SAP CRM Service Manager

Administration Portal - Administration

Device ID: If a user is assigned to a mobile device connected to the chosen application and the mobile device has an ID, the field is populated.

Device User ID: User ID assigned to the mobile device w Group ID: Allows you to define additional information about a user, such as a crew number or team name. This is a free-text field.

Email Address: Email address of the user. Email are sent through the Push Scenario Definition panel in the Configuration portal. Email are also used in the User Monitor panel under Monitoring in the Administration portal.

HTTP Address: Web address or site links that users can access, such as a Twitter feed w Default Address Type: Select either Email Address or HTTP Address from the drop-down menu for the default email sending method

Source System: Originating SAP system of the user ID. This is useful in multi-backend systems.

Lock Flag: If checked, user is unable to access the mobile application from the mobile device. This is used if a mobile device is lost or stolen and the application data must be made inaccessible.

~~~~~~~~~~~~~~~~end~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This is what I can suggest for now. Hopefully with the hint above you would be able to resolve your issue.

Best Regards,

Mark Pe
SAP Platinum Support Engineer

Share
10 |10000 characters needed characters left characters exceeded
Jeff McDonald May 16, 2017 at 12:16 PM
0

Hi Don - We currently have a similar situation. A single user is getting the error you described, all other users are accessing the mobile app with no issues. Were you able to find a solution?

fyi - I checked /SYCLO/MDW00 but there was no entry in this table for the user who is having issues.

Best Regards - Jeff

Share
10 |10000 characters needed characters left characters exceeded
Ajay Bishnani Jun 20, 2017 at 05:50 PM
0

Hello,

Please check the below Note

https://launchpad.support.sap.com/#/notes/2488922/E

Regards,

Ajay Bishnani

Share
10 |10000 characters needed characters left characters exceeded