You are viewing limited content. For full access, please sign in.

Question

Question

error 784

asked on March 1, 2016

Hi There, It would seem that many answers are posted regarding Error 784 and 781 - however - Ive got something different... we run 2 branches - the branch where the LF server is - works perfectly, next door to us - is a second branch that connects over a wireless connection to the main branch, all connectivity works, all suggested LF ports opened, yet I can not connect from the 2nd location to the primary (where the Repository is being called from) doesn't matter how I try to open LF - by Attaching to repository via the IP, or connecting to it normally... 1 event has been recorded -  (below) does anybody have any ideas of what I can try next please?

thanks a mill - Andre

Fault bucket 50, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: LF.exe
P2: 9.2.0.343
P3: 5425b176
P4: 571e
P5: 257
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Users\Andre_admin\AppData\Local\Temp\WER1216.tmp.appcompat.txt
C:\Users\Andre_admin\AppData\Local\Temp\WER3DA9.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Andre_admin\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_LF.exe_31d9c4a38ff4cea9f94abca7b4e5f6d6435e3d_2f276978

Analysis symbol: 
Rechecking for solution: 0
Report Id: 09a17ea0-df94-11e5-aa7d-d02788e607f0
Report Status: 0

0 0

Replies

replied on March 1, 2016

Some ideas:

- Can you ping the IP of the LF server machine?

- It could be that the LF server is timing out attempting to do a reverse dns lookup on your client machine. Try this KB to disable reverse dns lookup.

- Error 784 can mean there is a firewall blocking the requests.

1 0
replied on March 1, 2016

Yes, can ping the server across the wireless link, can open shares - the networks works fine, good Ping replies from the server .let me try disabling reverse DNS lookups - I'll try today and will send you feedback - thanks for the help! :-)

0 0
replied on March 1, 2016

Can you turn on tracing in the Client?  Go to Help - About and click the Tracing button.  Enable the logs and try to attach.  Then turn off the logs and see if there are any specific messages.

Is Laserfiche on a non-default port?  When you attach have you tried ipaddress:port?

0 0
replied on March 1, 2016

Thanks - let me try this today and I'll get back to you with some results - thanks :-)

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.