Skip to Content
avatar image
Former Member

Agentry Client | File Writing Issue

Hi Experts,


Problem Faced:

Issue in writing file content on device/ desktop through Agentry Client.

Environment:
Application: SAP Work Manager 6.0
SMP Server: SMP 2.3 SP03

Windows Client: WPF 6.1.3.x & 6.1.4.x

Local Agentry Server: 6.1.0.3

Scenario:

The requirement is to write a file on the device with some content generated during run time.
For the same an External Data property is created for one of the Objects in Agnentry.

Required coding is done in Java to set the Base 64 encoded value to this property.

Once the value is set to this property, the path of the file can be seen if the object is inspected in ATE.
The value itself is observed being set to the property in Java by debugging.

Also, the file WAS getting written on the device/ desktop at the specified path/ location.

But UNFORTUNATELY, this stopped from happening all of a sudden.

Rechecked required Object & property in Agnetry, Java coding.

Tried analyzing by debugging as well but no clues found.

Challenge:

This functionality works fine when application is configured & tested on LOCAL Agentry Server.

But has stopped working when same application is configured & tested on SMP Server connected to same back end.

Earlier it was also working fine on SMP Server as well.

Kindly help by adding your valuable suggestions and comments.

Regards,

Dharmaraj Patil

Message was edited by: Michael Appleby

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Dec 01, 2014 at 05:30 PM

    This is commonly an issue with how the server is running on the SMP server.  In order to send the attached documents to the client the Agentry server needs to be able to write it to a temp file on the Server.  If the SMP Server is running as the system account it may not have access to a temp directory location.

    One suggestion would be to run the SMP server under a specific user account and make sure the TEMP and TMP environment variables are set to valid accessible locations.

    At one time there was also an issue if the TEMP or TMP variables contained other variables in the path name.  The workaround was to set them to a specific path like C:\TEMP for example.

    --Bill 

    Add comment
    10|10000 characters needed characters exceeded