Messages
Reply
Edit
Delete02:00 pm
3SE0U1ESW
| From: | Rick Strahl |
| To: | Brett Baggott |
in 5.60 and later the default installers switch to creating .NET module installations for IIS7/8 installs, so the code to create the virtuals has changed. I can't speak to the 5.20 version stuff, since that's pretty old by now and if there's a problem there it's likely to be a one off error.
I would like to track down what doesn't work in the latest however.
First thing to do is make sure you have the latest. I made a minor update to 5.66 a couple of days after release related to installation/deployment that was related to file copies. So possibly you have the older version. If that still doesn't work. Ping me on Skype and I can take a look.
+++ Rick ---
I am only dealing with 5.66. This is on a fresh install OS and a fresh install of 5.66 (as opposed to an update). I'm still testing the Configure Server Wizard and I'll update this thread once I've done some more testing. However, I've encountered what I believe is another issue.
On another system that I've been using Web Connect on since about 5.2x, I just updated to 5.66. I opened VFP via the Web Connect icon and choosing "Run as Admin". I started the Create New Project wizard and ran through it several times. Every time I choose NOT to create a virtual (i.e. install in root), it threw a "Non fatal error: Virtual" with "Unable to create virtual directory." and then immediately crashed with "Command missing required clause". Every time I entered a virtual to create, it finished normally and fired up the test page. This is the first time I've every tried not entering a virtual but I think there's a bug.
Not trying to find problems, just trying to build some internal docs for creating a production server and setting up a dev box from scratch.
Are you running the 5.66 console? 5.65 had a bug where the module wasn't being copied. This should be fixed iwth the 5.66 console though.
If it didn't copy you can manually copy it into the /bin folder from the Web Connection install directory in the /scripts folder.
+++ Rick ---
I ran into the "Run as Administrator" out of the gate because the Configure Server Wizard couldn't see any of my Sites after selecting the "Advanced IIS Site Selection" option. I re-ran as Admin and was able to see all my Sites to choose from. I did make sure all my Web Server Role services were set as per documentation, including IIS Metabase Compatibility. I'm going to run through it again and see in just a bit and I'll get right back with the results (via Skype if you're on). However, I'm really confused as to why I can't find WebConnectionModule.DLL anywhere under \wconnect. Just going off memory, I thought there was a folder under \wconnect that mimic'd how a deployed server would look (i.e. a Template).
Make sure your use Run As Administrator. Server 2012 runs with UAC so even if you are an Admin you are not in fact running as an admin... (although 5.66 should prompt to elevate rights since it has a manifest to that effect).
Also make absolutely sure that the IIS Metabase compatibility is installed. Without that nothing will work, but you also should see errors. In fact, even if you are not running as a true Administrator you should see errors.
Ping me on Skype - if this really doesn't work I'd like to take a look and see why it doesn't if possible.
+++ Rick ---
I'm intimately acquainted with the process for getting a Web Server up and running Web Connection. However, my normal process is riddled with manually massaged nuances. Recently I was trying to write up some internal documentation for starting with "bare metal" and getting our ecommerce site up and running _on a deployment server_ which naturally involves installing and configuring Web Connection. I was trying to do it by the book as much as possible as to make it as repeatable as possible. Rick's done an amazing job with documentation so I was trying to leverage that as much as possible. So now, to the point.
I tried to use the CONSOLE.EXE to configure the server and it didn't seem to configure the server.
Now let me qualify a bit. This is NOT a development box, this is a production server. I had installed Visual Foxpro and Web Connection 5.66 as well as configuring the very basics of a website in IIS. This is a Windows Server 2012 installation and I selected the options of using the HTTP Handler and installing to the root (not creating a virtual). The process did seem to handle some of the permissions setup and DCOM settings but when I looked in the root of the website there was nothing. No web.config file, no WebConnectionModule.dll, nothing. In fact, I was about to go copy over WebConnectionModule.dll and manually make the web.config to see if that's all that was left and I can't find WebConnectionModule.dll.
Maybe my copy of 5.66 is messed up?
West Wind Technologies
Making waves on the Web