Installation worked but Web Server forwarding is not working MirrorSync 2.0.3

[Niche IT]

Hi,

 

Using a Windows 2008 R2 Server and at the end of the installation stage the following message was displayed...

 

"Installation worked but Web Server forwarding is not working. You will need to access MirrorSync at the direct connect URL: http://127.0.0.1:42424/MirrorSync"

 

I had this problem with v1.5 and worked around it by changing some configuration settings in IIS. However, these don't seem to work the same way with v2.

 

Installation on another server that appears to be identical went without a problem and is running fine but there must be something different about this one.

 

Any ideas?

 

Thanks

Andrew

[Jesse Barnum]

There is a file at C:Program Files360WorksInternalLogs with the word 'stderr' in the title, and the date you ran the installation. Could you get that file and send it to [email protected]? I should be able to figure out from that log what's going wrong.

[Donald Clark]

Hi Jesse,

I just installed on Mac Mini running 10.9.5 and FM server 14 and got this error:  "Installation worked but Web Server forwarding is not working. You will need to access MirrorSync at the direct connect URL:http://127.0.0.1:42424/MirrorSync".

Do you have any ideas about how to fix it?

Thanks,

Don Clark

 

[Caleb360Works]

Donald,

Restarting the FileMaker apache process should do the trick. I would recommend using the FMSAdmin command to do this. You run this command from the Mac OSX Terminal.

fmsadmin restart httpserver

This should get the web forwarding to reflect and you should be able to access MirrorSync on http:/127.0.0.1/MirrorSync at that point.

[Charles Delfs]

I am having this same issue but my server is stand alone and does not have FMS installed (an AWS instance)   Any Suggestions? 

Is application routing or something else needed?