empty inbound Error Message

[Former Member]

We have MI. 2.5 SP09 when we do the Synchronization we receive messages We assigned application (WORKFLOW) to all devices and the user XX has al needed authority

Why the application assigned to the user not appear?

We got the following message in the trace file:

[20041204 12:47:19:465] D [MI/Smartsync ] User XX has not been installed on MW, it is not ready for sync :XX

Thanks,

[Former Member]

Thanks for your answer.

But i stell have some difficulties to complete installation guide. For example:

1. When I tried to use MI_MCD transaction for Defining the Installation Sequence, I can not add any component; because when I select the component it inserted incorrectly.

The component version inserted in the #mobile component# field.

2.To enable Installing the SAP MI Client Component From the Internet we use the URL like http://platinum.dha.aramco.com.sa:50200/sap/bc/bsp/sap/me_fw_install/install.htm but when I use it I can not access by the same user that can access to http://platinum.dha.aramco.com.sa:50200/me/WebConsole/login.

The ME_FW_INSTALL application is activated.

Thanks Again

Bakor A. Kamal

[Former Member]

Hello

I have the same problem. When I try to synchronize I get exactly the same error message:

[20041213 09:16:55:832] D [MI/Smartsync ] User has not been installed on MW, it is not ready for sync :XX.

Additionally MI Client says : Received empty inbound container file for user XX.

I successfully uploaded a war file into ABAP stake via WebConsole and assigned it to my user, so there should not be an empty container.

Does anybody know what is going on?

Cheers

marek

[Former Member]

I have seen this message too. It appears when the MI2.5 is not properly configured.

Ensure that all steps in the Install guide are performed. Especially, it is important to check the user roles and authorizations. Check the firewalls as well.

IT IS NOT NECESSARY TO REINSTALL. Just perform all install steps.

[Former Member]

Thanks for your answer.

I performed all steps according to installation guide. I established necessary backgroud jobs in my backend (DP1). I do need any groups becouse my user has all priviliges and authorizations. I made a dp1.props file according to guidelines and it looks like that:

ashost=10.233.112.28

sysnr=00

MI (2.5SP09) client was installed as well without any errors. I set the settings in it and put there my username, clent no.,...,system: DP1.

And I still get the same error. I my opinion everything should be fine, but it is not.

[Former Member]

I think SAP_ALL profile does not include the Mobile Synchronization privileges and functionality authorizations, your users should have anyway the ME_SYNC etc. roles added with the necessary permissions, as given in the instguide.

Anyway, do you have started the <b>me_fw_install</b> service? This is different than the background jobs.

[Former Member]

I've just checked. SAP_ALL include MI priviliges and authorization. So the user I use have all authorizations granted.

I created anyway ME_SYNC role, etc. according to instguide, as you advised, but the result is the same.

The service me_fw_install is running.

What else can be the reason of malfunctionning the MI synchronisation and "empty containers"??

BR marek

[Former Member]

The only other thing that I have met, was problems caused by firewall on the client and/or server side. I can't guess something other.

[Former Member]

Hi.

I haven't sorted it out, but I know a possible reason for this kind of problem.

In misync log file (..\server0\misync.txt) I have found an entry like: "Created jco function template WAF_MW_SYNC_FLOW#[...]JCO$Exception: (127) JCO_ERROR_FIELD_NOT_FOUND: Field SYNCCOUNT not a member of INPUT#".

In my opinion this is a proof for version imcompatibitity. I use ABAP stack 6.20 with MI client 2.5. There should be ABAP stack 6.40.

I'd rather try with installing MI client 2.1 than upgrading ABAP stack. <b>Does anybody know where can I get an installation package of ME client 2.1??</b> I've already checked service.sap.com, but there are only patches.

Regards

marek

[Former Member]

That is definitely a reason.

MI2.5 just doesn't work with earlier than 6.40 versions.