Work Manager 6 - JCO Version out-of-support

Hi all,
in the comments of JCO 2.1 Table Iterator (for-each-loop) I was made aware, that the JCO version 2.1.8 delivered with the current Work Manager 6.0 is not supported anymore by SAP. Michael Appleby asked me to start a discussion on this in order to give this some more attention. So, here it is...
Regards, Daniel

Daniel,
Currently Work Manager doesn't support SAPJCO 3.0. We have a open request with our Product team to look into this. You can contact support about: SPS-271 - Support for SAPJCO 3.0
Stephen

Similar Messages

Does Dreamweaver Work with Serena Version Manager

Does Dreamweaver Work with Serena Version Manager? If not,
what does everyone use for source control?

Harsh324,
So once you have Serena configured in LabVIEW are you able to right-click in the project and select Show Differences? As mentioned in this tutorial the Graphical Differencing feature is only officially supported by Visual Source Safe and Perforce, however you may be able to get some information from this. I am not familiar with Serena, so it could be possible that it has something similar built in as well.
Please let me know if you get any results by selecting the option from the project. Thanks!
Andy F.
National Instruments

I needed to install a previously purchased CS6 versus on new computer. To do this, I had to download a version from CC. I will not be using CC. How do I activate Photoshop under my license so that it does not stop working when I am out of communication ra

I needed to install a previously purchased CS6 versus on new computer. To do this, I had to download a version from CC. I will not be using CC. How do I activate Photoshop under my license so that it does not stop working when I am out of communication range a month from now?

The CC version will not activate with your perpetual CS6 license. Download the version from here:
http://helpx.adobe.com/x-productkb/policy-pricing/cs6-product-downloads.html
Your number should work with this version.

When is Siri final version out and will it support UK business search?

When is Siri final version out and will it support UK business search?

Sorry, but we're all just fellow users here and have no information as to what Siri will offer in any given country at any point.
Regards.

Am working with trial version of photoshop elements 12. Layer functions remain grayed out when trying to use.

I'm working with trial version of Photoshop Elements 12. Layer functions remain grayed out when trying to use them.

You need to have an image open in the main window.

HT1338 OSX 10.4.11 update quicktime. Browser says out of date. Updater says up-to-date. Is this version no longer supported. How to update QuickTime and Java then?

OSX 10.4.11 Updates to QuickTime and Java.
Browser says out of date. Updater says up-to-date. Is this version no longer supported?
How can I update QuickTime and Java then without upgarding? I wish to keep a back channel to OS9

Mac OS X Tiger was discontinued years ago, and if Software Update doesn't detect any new update, it's because you are running the latest Java and QuickTime version for Tiger.
Apart from that, I see that you have a G5, so the most recent Mac OS X version you can use is Mac OS X Leopard, another version that it's (or it's going to be) discontinued soon. PowerPC support is completely dead now, and if you want the most recent QuickTime and Java versions, you will need a Intel-based Mac with OS X Lion or Mountain Lion, that have got the latest Java 6 versions and they are compatible with Java 7

How to find out Max threads count for Custom Work Manager??

Hi All,
How to find out Max threads count for Custom Work Manager??
I have created 1 WM & targeted it to a cluster of 2 MS. Later I created Max thread Constraint = 300 & assigned that to my WM.
I need to check how many threads maximum were created by my WM after lets say 1 completed day.
The idea behind that is to understand if .. 300 is enough or need to increase the same way as we do it for JDBC datasource like.. Active connections Max count.. etc.
Any Idea?
regards,
Tanmay

Hi Ashish,
Thanks for your response.
The monitoring page that you are suggesting does not indicate the max thread count reached for a particular WM.
For example, If I have Sample WM with 300 Max Thread Constraint, is there a way for me to check how many threads have been used out of 300??
Any pointers in this regard are appreciated.
Thanks,
Tanmay

Every version of firefox 6 won't open, I just get that crash report. Every time this has happened I reinstall firefox 5 which works fine. Anybody out there have a similar problem, any help would be appreciated

every version of firefox 6 won't open, I just get that crash report. Every time this has happened I reinstall firefox 5 which works fine. Anybody out there have a similar problem, any help would be appreciated

I had this issue. I went to c:\program files (x86)\Mozilla Firefox\
I renamed my plugins folder to plugins.old.
It recreated the Plugins folder and all was good again. I have since reinstalled the plugins I've been prompted to install.

Upgrading work manager 5.3 to 6.1 with out SMP 3.0

Hello Experts,
As per the blogs and posts, work manager 6.0 is designed for SMP 2.3 and work manager 6.1 for SMP 3.0.Can we use work manager 6.1(with its additional features)without SMP 3.0 similar to work manager 5.3.Can we have standalone work manager 6.1 server or we need to install complete SMP 3.0 runtime .
Please suggest can we upgrade work manager 5.3 to 6.1 without SMP 3.0 to have standalone Agentry server for work manager 6.1(Like standalone server for work manager 5.3)
Thanks in advance
Thanks & Regards,
Sravanthi Polu

Hi Bill,
Thanks for your reply.What about the customization's done in Work Manager 5.3, will they have impact when we upgrade from 5.3 to 6.1 on SMP 3.0.What is the better approach to retain the custom logic if we go for upgrade(SMP 3.0).As per my knowledge if we go for 6.1 on SMP 3.0, then custom logic need to be implemented again, so considering customization's as higher priority, can we migrate existing Work Manager 5.3(With custom logic(Editor,Java,ECC Changes)) to SMP 3.0.If we migrate custom logic would be retained,but can we make use of the new features in SMP 3.0 like open ui,client branding .... etc.
Please help in this regard.
Thanks in advance.
Regards,
Sravanthi

Work Manager 6.1 and SMP 3.0 with Agentry new features

Hi,
I know that Work Manager 6.1 is expected to be released by the end of June but I can't find any information about the product.
Since I'm starting a new project initially thought for Work Manager 6.0 but running in SMP 3.0, I would like to know the list of new features of 6.1 version.
At the same time I would like to know if the use of SMP 3.0 brings to the Agentry applications improvements regarding error handling, logging and administration in general since that was a bit poor in the previous versions.
The only thing I found regarding 6.1 version is this PDF where new functionalities regarding localization of assets in a map are added. I hope there is more than that.
Thank you for your help.

I guess the following thread answers my questions (except regarding SMP 3.0 logging, administrating and error handling with Agentry): http://scn.sap.com/message/15086739
I copy&paste the basic things to know:
More news during/after Sapphire
New features:
Based on SMP 3.0 using websockets for communication
GIS (ESRI) integration via Open UI
Visual Enterprise 3D integration via Open UI
SAP JCO 3 Support
Crew Management
WRP Customer Service
UX Improvements

Error when trying to re-mount a VHDx (the version does not support this version of the file format)

Hi,
I have a vhdx on a NAS that I use for server backup. I created the VHDx via disk management, mounted it and assigned drive letter X. I now created a script that gets triggered upon startup via task scheduler to remount the VHD. If I try to mount it however,
it tells me this:
No matter what I try, I can't mount it. Double clicking just says this:
Eventviewer spits out error 137: The default transaction resource manager on volume X: encountered a non-retryable error and could not start. The data contains the error code.
How do I trouble shoot this? oO Originally I had created the VHD as expanding, where now I recreated it at it's full size of 900GB. Maybe that will make a difference.
Thanks for the help
Cheers
Maike

Hi Maike,
Do you mean that you can mount the VHDX via disk management but cannot mount it via a script? If so, please provide the diskpart’s mount commands in the script.
In the meantime, check if destination partition is NTFS formatted.
Problem with Attach VHD function: The version does not support this version of the file format
http://www.paulauskis.lt/2010/03/problem-with-attach-vhd-function.html
Please Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]
Hi Mandy,
I can not mount it after a reboot. So I create the VHDx via disc management and attach it afterwards without problem. After the server reboots and the attached VHDx dropps, I can't remount it. Gives me the errors I posted above.
As I had mentioned above, I recreated the VHDx at it's full size this time, rather than expanding. That worked just fine and I can remount after reboot.
So I consider this dealt with ;)
Thanks anyway!

How to publish Work Manager 6.0 on SMP3.0 ?

Hi SCN Community,
I'm trying to get the Work Manager 6.0 running on SMP 3.0 (running on Linux). Currently the events.log within the Agentry folder states, that the Agentry Server was started. But If I look into the Threads*.log I see there might be a problem and I'm also not able to connect to the server.
Unfortunately I couldn't find any manual or post where someone described the steps to get a work manager running on SMP 3.0. The SMP 3.0 server manual as well as the SDK manual just describing in general how to publish an application to the SMP 3.0. But for Work Manager, there might be some special things to be done ...
Any help/hints are welcome!
Here what I did so far:
Install SMP 3.0 up to SP02 on Suse SLES 11
Install SAP JCo 2.1.11 (test successful: java -jar /DVD_HANA/jco/sapjco.jar -stdout )
Create a new application in SMP with type Agentry and select security profile default
Install SMP3.0 SDK SP02 (Agentry)
Setup Eclispe 4.2.2 with Agentry Plugin 7.0.2
Import a Work Manager 6.0 from Teamshare
Export Agentry Project as a production version and point to the Agentry.ini which is in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application
Include all jar files to the ZIP file
Import the ZIP file within Agentry application in SMP 3.0
Create JavaBE.ini in folder /opt/SAP/MobilePlatform3/Server which is copied from WM6.0 server
Adjust Agentry.ini in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application (see section config files)
Restart Server
Config files:
Agentry.ini
[Server Administration]
authenticationCertificateStore=AgentryServer.pfx
authenticationCertificateStorePassword=Rzdrj~SwixoAqzmbVxgi
authenticationCertificateStorePasswordEncoded=true
[System Connections]
2=ag3httpxmlbe.dll
1=ag3javabe.dll
[Configuration]
apnsCertificateDirectory=apnsCertificates
apnsCertificatePassword=Rzdrj~SwixoAqzmbVxgi
apnsCertificatePasswordEncoded=True
apnsEnabled=True
applicationGlobalsFile=Globals.ini
applicationStringsFile=ApplicationText.ini
clientStringNamesFile=ClientStringNames.ini
clientStringsFile=ClientText.ini
developmentServer=False
enableFailedTransactionLogging=True
enableOverrideFile=Enables.ini
enableTransactionFailureHandling=False
failedTransactionFilenameFormat=%{userid} %{transaction_name} %{date} %{time}-%{count}.xml
failedTransactionsQueue=FailedTransactionsQueue
gcmEnabled=True
gcmServerAuthorizationKey=Authorization:key=AIzaSyDi0qWQEewdbmNSV_o9QNtSQrlxPnBXtBM
gcmServerLink=https://android.googleapis.com/gcm/send
imagesPath=Application\Development\Images
localizationPath=
localizations=
overrideInfoTableDirectory=OverrideInfoTable
overrideTypesFile=OverrideTypes.ini
postedTransactionDirectory=posted
postedTransactionFile=%{device}.pli
scriptsPath=Application\Development\Scripts
spinDocIniFile=
threadCount=0
transmitConfigurationFile=TransmitConfigurations.ini
trustedCertificateStore=
updateIdleWait=60
updatePeriod=60
urlPath=
[HTTPXML-2]
authenticationCertificateStore=MY
authenticationCertificateStorePassword=
authenticationCertificateStorePasswordEncoded=False
autoDequote=True
baseURL=http://localhost:8282
basicAuthenticationPassword=
basicAuthenticationPasswordEncoded=False
basicAuthenticationUserID=
constantsFile=httpxml_sd.ini
enableAuthentication=False
enablePreviousUserAuthentication=False
httpConnectTimeout=60
httpReceiveTimeout=300
httpResolveTimeout=60
httpSendTimeout=300
listenOn=
name=2
timeZoneName=
timeout=300
trustedCertificateStore=
useSSL=False
xmlNamespaces=
[Java-1]
classPath=./ini4j.jar;./Agentry-v5.jar;./Z_SAPWM-6.0.0.0.jar;./SAPWM-6.0.0.0.jar;./SAPCommon-130881.jar;
constantsFile=
deleteSource=True
enableAuthentication=True
enablePreviousUserAuthentication=True
name=Java-1
outputDirectory=.
performCompile=True
printBusinessLogicStackTrace=False
printStackTrace=False
scriptsPath=
serverClass=com.syclo.agentry.Server
sourceDirectory=.
timeZoneName=
[SpinDoc]
facePath=sql\custom;sql
facepath=sql\custom;sql
[TimeZoneAlias]
Log files:
events.log
02/27/2014 18:51:45, 0,         0,         0, Thr 140352349296384, New files opened events.log, messages.log
02/27/2014 18:51:45, 0,         0,         2, Thr 140352349296384, Agentry Startup
02/27/2014 18:51:45, 0,        17,        14, Thr 140352349296384, WebSockets Front End v7.0.2.151
02/27/2014 18:51:45, 0,         1,         4, Thr 140352349296384, Agentry v7.0.2.151
02/27/2014 18:51:45, 0,        20,       150, Thr 140352200132352, Loading Production application definitions using file "SAPWM-v1-0-0-app"
02/27/2014 18:51:45, 0,        20,       152, Thr 140352200132352, Loading Production application definitions for default localization
02/27/2014 18:52:07, 0,        20,       153, Thr 140352200132352, Finished loading Production application definitions for default localization
02/27/2014 18:52:07, 0,        20,       151, Thr 140352200132352, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
02/27/2014 18:52:08, 0,        24,         4, Thr 140352349296384, Loaded 2 (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
02/27/2014 18:52:08, 0,        23,         4, Thr 140352349296384, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
02/27/2014 18:52:08, 0,        20,         4, Thr 140352349296384, Server v7.0.2.151
02/27/2014 18:52:08, 0,        17,        10, Thr 140352349296384, WebSockets Front End v7.0.2.151
02/27/2014 18:52:08, 0,         0,         0, Thr 140352349296384, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-27-185145
02/27/2014 18:52:08, 0,         0,        23, Thr 140352349296384, Agentry startup is complete.
Thread-140352200132352.log
2014/02/27 18:52:07.310: Opening log file
2014/02/27 18:52:07.310: + Thread=140352200132352
2014/02/27 18:52:07.310:   + Server=Agentry
2014/02/27 18:52:07.310:     + Load Loop=Production
2014/02/27 18:52:07.310:       + AppIniFile=SAPWM-v1-0-0-app
2014/02/27 18:52:07.310:         + Module=PM
2014/02/27 18:52:07.310:           + Service Event=WorkOrderPushHTTPListener
2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkOrderPushHTTPListener'
2014/02/27 18:52:07.310:           + Service Event=WorkorderPushByOperationHTTPListener
2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkorderPushByOperationHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=WorkorderPushBySubOperationHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushBySubOperationHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=BDSDocumentPushHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'BDSDocumentPushHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=DMSDocumentPushHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'DMSDocumentPushHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=WorkorderPushByMRSHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushByMRSHTTPListener'
When trying to connect with the WPF client I get a communication error (14) and nothing is shown in the log files ..
Best Regards,
Michel

Jason,
deleting the service events was helpful regarding the error shown in the Thread log file. After publishing a new version the server seems to start, but has no activity to SAP. I expected at least an initial logon to the SAP system using the service user.
Current log files are:
events.log:
02/28/2014 06:16:36, 0,         0,         0, Thr 140136552040192, New files opened events.log, messages.log
02/28/2014 06:16:36, 0,         0,         2, Thr 140136552040192, Agentry Startup
02/28/2014 06:16:36, 0,        17,        14, Thr 140136552040192, WebSockets Front End v7.0.2.151
02/28/2014 06:16:36, 0,         1,         4, Thr 140136552040192, Agentry v7.0.2.151
02/28/2014 06:16:36, 0,        20,       150, Thr 140136413689600, Loading Production application definitions using file "SAPWM-v1-1-0-app"
02/28/2014 06:16:36, 0,        20,       152, Thr 140136413689600, Loading Production application definitions for default localization
02/28/2014 06:17:06, 0,        20,       153, Thr 140136413689600, Finished loading Production application definitions for default localization
02/28/2014 06:17:06, 0,        20,       151, Thr 140136413689600, Finished loading Production application definitions using file "SAPWM-v1-1-0-app"
02/28/2014 06:17:06, 0,        24,         4, Thr 140136552040192, Loaded HTTP-XML Back End (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
02/28/2014 06:17:06, 0,        23,         4, Thr 140136552040192, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
02/28/2014 06:17:06, 0,        20,         4, Thr 140136552040192, Server v7.0.2.151
02/28/2014 06:17:07, 0,        17,        10, Thr 140136552040192, WebSockets Front End v7.0.2.151
02/28/2014 06:17:07, 0,         0,         0, Thr 140136552040192, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-28-061636
02/28/2014 06:17:07, 0,         0,        23, Thr 140136552040192, Agentry startup is complete.
messages.log is empty and Thread*.log doesn't exist anymore.
Any further idea how to get this up and running?
Best Regards,
Michel

I have tried VERY unsuccessfully to install iphoto 9.2.3 update...it says it has successfully updated - then on opening says: iPhoto cannot be opened because of a problem. Check with the developer to make sure iPhoto works with this version of Mac OS X.

I have tried VERY unsuccessfully to install the new iphoto 9.2.3 update.
I have installed it several times both from the appstore and from Apple Support downloads...it says it has 'successfully updated' - then on opening iphoto, a dialogue box pops up and says:
iPhoto cannot be opened because of a problem.
Check with the developer to make sure iPhoto works with this version of Mac OS X. You may need to reinstall the application. Be sure to install any available updates for the application and Mac OS X.
Click Report to see more detailed information and send a report to Apple.
Insane...I have all my updates including Lion 10.7.3 why does APPLE KEEP SENDING BETAS AS A REAL PRODUCT?
Does anyone know how to copy over a backup from a twinned drive Backup? What files etc.
Thanks tons...

Thanks Terence,
I did get it working finally...and your last advice was what I needed.
I am embarassed that I was an early adopter...SHOULD HAVE KNOWN BETTER and read the problems before creating some for myself.
This was an excercise in frustration, because of the obtuse division between the appstore and Apple Support downloads... it was a bit of a circuitous route...strange that with all the security reciepts and tracking that Apple goes to to prevent piracy... which Steve by his own admission used to build Apple...
Why aren't the server scripts smart enough to say…”HEY DUMMY you can't use this download because you purchased the last iPhoto upgrade from the appstore...and… DON'T WASTE YOUR TIME and precious data BUDGET downloading this gargantuan file which will eat 20% of your expensive 5Gb monthly data allotment!!!…and NOT WORK…only pretend to…and then foul your system….kill your productivity and turn your hair whiter…even worse than LION did.
I am just so antagonized by the inept scripts in recent installations that don't do a diagnostic before allowing installation that is going to corrupt things...I had less effort and frustration when I ran my ATARI with a MAC emulator...rarely lost any productivity to nonsense.
I AM TIRED OF BETAs dressed as products...designed and rushed out for Apple toys that once were tools of the creative trade...COREL...may still have a chance at a comeback if Apple keeps pumping out toys instead of the venerable tools we once adored as income enhancers.

Work Manager 6.1: Uploading pictures or documents error

Hi,
I'm working with SMP 3.0 and Work Manager 6.1 for Android platform
I'm trying to attach a picture and/or a document to a Work Order and to a Notification, but when I start the transmit the following error is displayed in the client:
Sending Document Link Picture Add For Work Order...
Unexpected disconnection from server (11)
'Angel' connection failed
I tried to debug the Java but it didn't reach any break point or "catch", I also checked the SMP 3.0 Agentry logs and there is nothing.
I went through the installation notes and documents and I haven't been able to find out if I missed some configuration. I also checked this nice blog http://scn.sap.com/community/mobile/blog/2014/03/25/troubleshooting-sap-work-manager-60-attach-document-issue with no luck.
Can you help me with this?
Thank you in advance
Tags edited by: Michael Appleby

Short update for this issue. I created a SAP incident regarding it.
It's only failing when attaching pictures in Android (iOS works fine), and it seems due a platform bug documented here: http://code.google.com/p/android/issues/detail?id=17535
But since WM 6.1 is supported for Android 4.0 or higher, I expect some help from SAP if the cause is what I think.

Work Manager 6.0 Push Notification not working

Hi All,
I have configured Standard Work Manager 6.0 application and now I am trying to configure Work Manager 6.0 Push Notification.
I have completed all Post Installation(optional and required) which are mentioned in Standard product document.
I am getting new work order entries in /SYCLO/PSH01 and /SYCLO/PSH02. After that Agentry server is also calling /SYCLO/PM_DOPUSHWORKORDER_GET Function Module and /SMERP/CL_PM_PUSHWORKORDER_DO Class Handler.
I am getting result in final export table(ls_mdo_output_vals) of /SMERP/CL_PM_PUSHWORKORDER_DO.
My problem is still I am neither getting this work order into ATE nor push notification message.
When I went to Syclo Admin panel, status of the push notification is also NEW.
I have configured 8282 port in [HTTPXML-2] section of Agentry,ini and Syclo Config panel outbound trigger.
Kindly let me know what can be an issue?
Regards,
Mohit Verma.
Message was edited by: Michael Appleby

Mohit,
I noticed the following in your Backend-Java.log.
~~~~~~~~error 1~~~~~~~~
2014/06/27 17:37:36.947: Error in initializing the StepHandler from the ini file or SAP configurations (com.syclo.sap.component.serviceorder.stephandler.ServiceOrderRemovePushStepHandler). Please check the JavaBE.ini file. java.lang.ClassNotFoundException: com.syclo.sap.component.serviceorder.stephandler.ServiceOrderRemovePushStepHandler
~~~~~~~~end~~~~~~~~~
<-- Make sure this is corrected. For some reason your java code is not being detected during start up. Check your Java folder in the root directory of your Work Manager 6.0 to see if it can be seen.
Based on history of Support tickets the following SAP Note is mandatory to make Push work:
1. Do mandatory SAP Note: 1954444
2. Please review: 1828657 - Release strategy for the ABAP add-ons SMFND, SMERP, SMISU, and SMCRM (Make sure you installed the correct add-on - look at the spelling in detail)
3. SCN Push threads that may help: http://scn.sap.com/thread/3494003
See if any of the comment above will work for you.
4. After you tried the above and it didn't work for you to try the latest SMP 2.3 SP04 version and let us know. This is for what I can see on the logs.
~~~~~~~~Error 2: Backend-java log~~~~~~~~~
2014/06/27 17:40:35.471:             Getting Java results in the the 'WorkOrderPushForEventSteplet' step (java class com/syclo/sap/component/workorder/steplet/WorkOrderPushForEventSteplet)
2014/06/27 17:40:35.471:             : 1 lines, 0 non-printing characters, 20 total characters
The module is 'PM'
2014/06/27 17:40:35.471:             The root object is 'WorkOrder'
2014/06/27 17:40:35.471:             Trying to read results by calling getReturnData()
2014/06/27 17:40:35.471:             : 1 lines, 0 non-printing characters, 81 total characters
getReturnData() method returned null, falling back to reading _returnData field
2014/06/27 17:40:35.471:             Processing public field _returnData: Ljava/lang/Object;
2014/06/27 17:40:35.471:             _returnData is a single object: 'Ljava/lang/Object;'
2014/06/27 17:40:35.472:             Mapping public fields of Java Class 'java/lang/Object' to Agentry object 'WorkOrder'
2014/06/27 17:40:35.472:             No public field userid found in java/lang/Object for user ID, and not in per-user mode: cannot determine user for data.
~~~~~~~~~end~~~~~~~~~~~~~~~~~~
The log comment above is stating that the push is trying to be sent to the PDA/handheld but it does not know where to send it to. This is proven from your backend setup and when you have no errors in your push retry.
The last line above is still a mystery to me as there are lots of upgrades with patches and SMP 2.3 SP# and with the userid is not found (especially when it states it is not in per-user mode: cannot determine user for data) then the Agentry Server cannot determine where to send the push to.   Hopefully somebody in this thread knows this.
Regards,
Mark Pe
SAP Senior Support Engineer (Mobility)

Work Manager 6 - JCO Version out-of-support

Similar Messages

Maybe you are looking for