Sync not happening

Use this Forum to post your “How to …” questions about your use of LongReach. This is not a technical support forum. Both the LongReach Support Team at LANSA and other LongReach customers may answer your questions. LANSA cannot guarantee the accuracy of any information posted by customers.
Post Reply
tonyjensen
Posts: 3
Joined: Fri Dec 09, 2011 1:39 am
Location: Denver, Colorado
Contact:

Sync not happening

Post by tonyjensen » Fri Dec 09, 2011 1:43 am

Yesterday we install LongReach on the iSeries. Last night, I took some time to walk through the app. After creating a folder hierarchy, a couple of text files and an image, I attempted to sync but the sync failed. The same error is happening this morning. The error that pops up is "File Manager. Get folder exception: Connection not allowed".

I am using an iPad with the latest version of iOS connected via VPN to our internal network.

alick
Posts: 67
Joined: Fri Dec 09, 2011 7:52 am

Re: Sync not happening

Post by alick » Fri Dec 09, 2011 8:01 am

File Manager. Get folder exception: Connection not allowed.

This type of error means that LongReach is communicating with the server.

The most common cause, is incorrect User/Password, User profile is disabled.

Edit the '/longreach/jsm/instance/system/httpd.xml' file and enable tracing.

Find the following XML element

<match uri="/service/longreach.jsp" class="com.lansa.mabius.service.HTTPServiceLongReach" trace="false" clienttrace="false">

Change trace="false" to trace="true"

End and start the LONGREACH subsystem to restart the server.

Check out the trace files in the '/longreach/jsm/instance/trace folder'.

More detailed information about the transaction will be available.

The top-level trace folder is the job number of the LONGREACH server job.

Every time you start the LONGREACH server a new job number folder is created.

tonyjensen
Posts: 3
Joined: Fri Dec 09, 2011 1:39 am
Location: Denver, Colorado
Contact:

Re: Sync not happening

Post by tonyjensen » Sat Dec 10, 2011 4:30 am

Thank you, Alick! You pointed me toward the answer. It was a case of user error. I was changing my passwords that day and used the wrong one in the client app. It is syncing now.

Post Reply