I'm having problems configuring 3 machine setup with outside web server...

[angelleye]

I'm trying to setup a 3 server test enviornment. My FMSA9 and WPE server's are located on-site and my web server is located off-site.

When I go into the Deployment Configuration and I select 3 machines and then I get to the drop downs where I'm suppose to fill in the domain of my web server and web publishing engine I can't seem to make that work.

The WPE part is working fine but when I put in my web server's domain and hit Lookup I get the following error:

Worker Lookup: Error encountered while doing lookup.

Any information on what's going on here would be greatly appreciated. We do have a firewall here in-house but I've given the FMSA9 Quick Start guide with all of the rules to our fireall admin and he says everything should be good to go. I've also ensured that the same ports are opened on the router where the test web server is located.

Anything you can tell me would be great. Thanks!

[Steven H. Blackwell]

Can you hit the web server from within the LAN using a browser?

Steven

[angelleye]

Yup, I can browse the web sites on the test server without any problem from within the LAN.

[Steven H. Blackwell]

This almost makes me think that the installer did not put the web server module on the web server machine.

Does the log give any clues here?

Steven

[angelleye]

Hey, sorry, I missed your last response some how.

That could have been the problem...I'm actually working with a different web server now. The problem with the previous web server was that I simply couldn't get it to show up in the drop down during the deployment wizard. With the web server I'm working with now it does indeed show up as expected but now I'm having some other problems.

The first time I went through the deployment wizard on this 3 machine config I wound up what seemed to be a working config. See the attached screenshot for the way it looks right now.

The problem I'm having now is that when I send PHP calls to the new test config I'm getting back the following error:

Communication Error: (22) The requested URL returned error: 404 - This can be due to an invalid username or password, or if the FMPHP privilege is not enabled for that user.

Seems like a rather straight forward error, however, I've working on the exact same files with the same users and privilege sets as my current live FMSA machine that is working correctly. The working FMSA is setup as a single machine, however, I'm actually making the calls from the web server that I'm trying to use with the new 3 machine config.

I triple checked that the same un/pw were being used and I also triple checked that the FMPHP extended privilege was added to the privilege set that is being used...again, it's mirroring the working server's files.

At this point I was thinking that maybe it's because of the fact that the WPE machine is using our local domain name instead of a local IP address like the FMSA machine shows.

I'm trying now to go back through the deployment wizard to change it from huscat.dealexpress.local to an actual 192.168.1.* address. I'm able to add it to the drop down and select it but then when I say Next it's getting stuck on the web server part now. It takes awhile and then comes back saying it couldn't connect to the web server. Then when I look at the web server the IIS web site has been stopped and the only way I can get it to turn back on is to reboot the web server.

Any ideas at all what's going on here?

[Steven H. Blackwell]

I wish I did have some idea what was afoot here so I could assist you. The only item I can think of is that there is some kind of miscommuication between IIS and the web server module. Be sure that the web server module is installed on the IIS machine. Also, if you're trying to serve more than one site off the IIS machine that might cause an issue.

Steven

[IdealData]

Have a look here...

http://my.advisor.com/doc/18147

In particular there's an interesting definition of database sessions under CWP

[angelleye]

Ok, I'm back again. As it turns out it doesn't seem that the web server part of FMSA deployment wizard really matters. I can currently hit my single machine server that's working correctly from any web server that I try from even though only the one is actually setup as the web server piece of the 3 machine config.

I still can't get anything but the communication error back from my 3 machine config, though. I am suppose to send my calls to the WPE machine, right? In my scripts when I point directly to my current single machine setup it works fine but then I simply witch to the multi-machine and I get communication error.

The single FM machine and the new FM/WPE separate machines are all located here in our local domain.

I gave the firewall rules to our firewall/router guy and he claims everything is opened up. Again, it works on one machine but not on the other.

From what I can tell I've got all of the settings matching between the FM server that works and the one that doesn't. does this sound like a firewall thing or what???