Messages
Reply
Edit
Delete02:20 pm
3SF0UPH4U
| From: | Rick Strahl |
| To: | Brett Baggott |
You have to click the Virtual checkbox otherwise nothing gets copied or configured ont he virtual.
The wc.dll is locked is because it's in use - you should stop IIS before running the config. The app optionally asks you whether you want to restart IIS - if IIS isn't live and running then that's enough. If it's running then you'll need to stop it.
IAc, I just tried this here with a completely empty folder and it works without issue.
I created a new folder and created an IIS site for it. No files in there at this point. Then create virtual checked, empty and the path set to the folder.
After it runs I have a bin folder with the Web Connection DLLs and a web.config that only holds the scriptmap mappings.
If an existing application is used in the folder those same files are copied and the web.config updates only the scriptmap section of the existing Web.config file if it exists.
+++ Rick ---
Rick, I just tried the new Console.EXE and either I'm missing something or it's still not working. Let me detail what I've done to make sure I'm not missing something:
1. Installed Windows Server 2012
2. Added Web Server Role with settings as per http://west-wind.com/webconnection/docs/_22f0xkbmq.htm
3. Created basic website, added test homepage, tested site (at least static file delivery)
3. Installed Web Connection 5.66 (that was downloaded 5/17/13 but using your new Console.exe)
4. "Run as Administrator" Console.EXE
5. Select Configure Server
*As a test, I also turned off UAC but that didn't make a difference either
During the Configure Server wizard, if I leave the checkbox empty that's labeled "Create or update Virtual directory", it seems it configures permissions and DCOM but no files are copied. If I check the same checkbox, choose the path to the sites home directory root and leave the field labeled "Virtual:" blank, it does configure permissions and DCOM but I get an error:
"Unable to copy wc.dll to \bin
The file may be in use by the server. Shut down the server and re-run"
If I check the checkbox, enter something in the "Virtual:" field and enter what would be the corresponding filepath in the field labeled "Path:", everything seems to happen as expected and in the root of the site's home directory I have a virtual created as entered and in that folder are 3 files, wc.ini, wc.dll, and webconnectionmodule.dll.
So, it seems to me that leaving the "Virtual:" field blank will not work regardless. One more point. I started thinking that it might be folder permissions because the Home Directory for this site is a folder I created that might not have the _exact_ permissions as the default c:\inetpub\wwwroot. So I tried all of the above but using the "Default Web Site" selection and I got the same results.
On a completely separate issue, I was surprised that even entering something in the "Virtual:" field and having it complete successfully did not do what I expected. I thought the "Configure Server" wizard would be a way to copy everything necessary for a deployment server (i.e. \Admin, \Scripts, web.config, etc.). I realize that during the creation of my project on my development box, most of these things already exist and should work fine if I just XCOPY my development site. It's just that, with web.config in particular, the version on my development box seems to be heavily geared toward development and I'm not sure I'd want to just XCOPY it without some modifications.
Keep in mind that I'm not looking for how to configure all this manually. I know how. What I'm trying to do here is come up with "follow these steps and you can go from bare metal to deployed server" and I was hoping to not have to include a lot of my manual "tweaks".
Brett,
I've attached a copy of an updated Console.exe that removes the option whether to use a virtual or not and cleans up the labels on that UI a bit so it's hopefully clearer on what's actually happening.
The UI for a lot of this stuff is pretty old and although the functionality underneath has drastically changed over the years the UI of the interface hasn't...
This version (and probably also the existing version you have) should work to configure a root web.
+++ 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