Hi guys, I use XML publishing to sync some data between two remote FM servers: The urls are not imported directly via import records but the url is called via WebAssistant and the result is saved to disk and imported from there. I use WebAssistant for better control/time-outs etc. in favor of other techniques. The solution worked seamlessly for some month with two FM11. The solution was migrated to FM12 and now the odd part: via a FM12 client (12.03) everything works as expected via server script, I receive an error (111) Connection refused via WebAssiant, but if the same url is called via ScriptMaster's GetUrlAsText() everything works as expected. even the new Insert from URL is working seamlessly. Any ideas? WebAssistant 1.57 FM Server #1 MAC 10.7.5 / 12.02 Adv FM Server #2 MAC 10.6.8 / 12.02 Adv FM Clients 12.03 / 12.03 Adv Best, Alexander

WebAssistant strange feedback: FM12 client / FM12 server

January 21, 201312 yr

Hi guys,

I use XML publishing to sync some data between two remote FM servers:

The urls are not imported directly via import records but the url is called via

WebAssistant and the result is saved to disk and imported from there.

I use WebAssistant for better control/time-outs etc. in favor of other techniques.

The solution worked seamlessly for some month with two FM11.

The solution was migrated to FM12 and now the odd part:

via a FM12 client (12.03) everything works as expected
via server script, I receive an error (111) Connection refused via WebAssiant,
- but if the same url is called via ScriptMaster's GetUrlAsText() everything works as expected.
- even the new Insert from URL is working seamlessly.

Any ideas?

WebAssistant 1.57

FM Server #1 MAC 10.7.5 / 12.02 Adv

FM Server #2 MAC 10.6.8 / 12.02 Adv

FM Clients 12.03 / 12.03 Adv

Best,

Alexander

Solved by Will Slaughter

January 29, 201312 yr

Go to solution

2 weeks later...

January 29, 201312 yr

Solution

For anyone who is also having this problem, it ended up most likely being an issue with the specific .fmplugin file that was installed. I sent Alexander another copy of the plugin with some updated logging capabilities (will be in the next release as well) and the problem went away completely. Just re-downloading the plugin from 360Works.com and reinstalling should solve any problems of this sort.

Cheers!