[WebDNA] [BULK] Windows XP Pro Success!

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 100765
interpreted = N
texte = This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C917D4.070910B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable OK Gang - I was able to get WebDNA running on my Windows XP Pro box! = Very special thanks to Terry Nair & Stuart Tremain for keeping me going = during this process. =20 The "secret" was this: First, WebDNA does NOT like spaces in the path name for the $WebCat.dll file. I had my web root in: D:\My Documents\Inetpub\wwwroot =20 That was the problem with all subsequent attempts to install WebDNA = because that folder was "remembered" between installs. =20 So, here's what I believe to be the proper install procedure: =20 1) Run the Windows Installer - The installer asks for 2 folder paths. The first is where to install = the "WebCatalog" folder. THis should be the root of your default website. = In my case, this was: D:\My Documents\Inetpub\wwwroot in default IIS installations, it's usually: C:\Inetpub\wwwroot =20 The second folder is where to install the WebCatalogEngine folder (this = is where the ISAPI filter: $WebCat.dll is installed). Make sure this = folder path does NOT have any spaces in it! I originally installed this folder to: D:\My Documents\Inetpub\Scripts However, this caused all types of problems. The folder that worked was = to install it to: C:\Inetpub\Scripts Note that this folder does not have any spaces in it. =20 Additionally, The installer has some verbiage about installing the = Engine in a folder designated to run "scripts". The truth is that this folder = must be configured in IIS 5.1 as an "Application" folder. You can make this designation AFTER the install if you don't already have a folder = designated as an "Application". =20 After the installer has run, it defaults to running the WebDNA html = page. BEFORE you do this, you should check several things in IIS. =20 2) "Web Sites" Configuration. =20 - Open IIS Manager. - Rt-Click the "Web Sites" folder and select "properties" - Under the "ISAPI Filters" tab, you should see "WebCatalog" with a = "high" priority. Make sure this is the LAST high priority filter. Click on = this filter and select "Edit" and make sure the executable to set to the = correct path to $WebCat.dll file (remember - no spaces!) - Next Click on the "Home Directory" tab and click the "Configuration" button. The first tab on the next screen is "mappings". When you ran = the installer in step 1, you should see the default extensions (.db & .tpl) mapped to the $WebCat.dll file. Again, confirm that these settings are mapped correctly with no spaces! Now, I think these mappings are used whenever you create a NEW website, but do not effect the settings of an existing website (like your default website), so there's more to do... =20 3) Default Web Site configuration. - Open IIS manager and open the "Web Sites" folder in the treeview - Rt-Click on the Default Website and select "properties" - Click on the "ISAPI Filters" tab and it should be empty - Click on the "Home Directory" tab and click the "Configuration" = button. - Under the Mappings" tab, make sure that at a minimum .tpl and .db extensions are mapped to the $WebCat.dll file and that the path to the = .dll file is correct and DOES NOT CONTAIN any spaces. =20 4) Make sure "Scripts" folder is defined as a Virtual Folder in IIS - Open IIS Manager, then open the "Web Sites" folder, then open the = "Default Web Site" folder - Under the Default Website Folder, make sure the "Scripts" folder where = you installed the WebCatalogEngine folder is listed as a virtual directory. = If it is not, then add it. - Also, if this folder is shown as an Application folder, then you must check the mappings to be certain that .tpl & .db are mapped correctly. = If the folder is NOT an application folder, then the folder should get it's mappings from the "Default Web Site" mappings. =20 5) Make sure Web Catalog is defined as a Virtual Folder in IIS - Open IIS Manager, then open the "Web Sites" folder, then open the = "Default Web Site" folder - Under the Default Website Folder, make sure the "Web Catalog" folder = is listed as a virtual directory. If it is not, then add it. - Also, if this folder is shown as an Application folder, then you must check the mappings to be certain that .tpl & .db are mapped correctly. = If the folder is NOT an application folder, then the folder should get it's mappings from the "Default Web Site" mappings. =20 OK, this is how I was able to get the Windows XP Pro IIS to run the = WebDNA program. For users with default folder locations, it should not be as difficult as it was for me. As mentioned, I think my whole problem = stemmed from having a space in my folder path and then each subsequent install = had remnants of that space somewhere in all of the IIS settings. Following = the process above helped me get the configuration running. =20 Again - thanks to all on the List Server that tried to help me out. =20 Sincerely, =20 JD Ready jdready@risedev.com RISE Development Group, Inc. 303.925.0047 Phone 720.226.0740 Fax 866.321.0944 Toll-Free =20 ------=_NextPart_000_0000_01C917D4.070910B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
OK = Gang - I was able=20 to get WebDNA running on my Windows XP Pro box!  Very special = thanks to=20 Terry Nair & Stuart Tremain for keeping me going during this=20 process.
 
The = "secret" was=20 this:
First, = WebDNA does=20 NOT like spaces in the path name for the $WebCat.dll file.  I had = my web=20 root in:
D:\My=20 Documents\Inetpub\wwwroot
 
That = was the problem=20 with all subsequent attempts to install WebDNA because that folder was=20 "remembered" between installs.
 
So, = here's what I=20 believe to be the proper install procedure:
 
1) Run = the Windows=20 Installer
- The = installer asks=20 for 2 folder paths.  The first is where to install the "WebCatalog" = folder.  THis should be the root of your default website.  In = my case,=20 this was:
D:\My=20 Documents\Inetpub\wwwroot
in = default IIS=20 installations, it's usually:
C:\Inetpub\wwwroot
 
The = second folder is=20 where to install the WebCatalogEngine folder (this is where the ISAPI = filter:=20 $WebCat.dll is installed).  Make sure this folder path does NOT = have any=20 spaces in it!
I = originally=20 installed this folder to:
D:\My=20 Documents\Inetpub\Scripts
However, this caused=20 all types of problems.  The folder that worked was to install it=20 to:
C:\Inetpub\Scripts
Note = that this=20 folder does not have any spaces in it.
 
Additionally, The=20 installer has some verbiage about installing the Engine in a folder = designated=20 to run "scripts".  The truth is that this folder must be configured = in IIS=20 5.1 as an "Application" folder.  You can make this designation = AFTER the=20 install if you don't already have a folder designated as an=20 "Application".
 
After = the installer=20 has run, it defaults to running the WebDNA html page.  BEFORE you = do this,=20 you should check several things in IIS.
 
2) = "Web Sites"=20 Configuration. 
- Open = IIS=20 Manager.
- = Rt-Click the "Web=20 Sites" folder and select "properties"
- = Under the "ISAPI=20 Filters" tab, you should see "WebCatalog" with a "high" priority.  = Make=20 sure this is the LAST high priority filter.  Click on this filter = and=20 select "Edit" and make sure the executable to set to the correct path to = $WebCat.dll file (remember - no spaces!)
- Next = Click on the=20 "Home Directory" tab and click the "Configuration" button.  The = first tab=20 on the next screen is "mappings".  When you ran the installer in = step 1,=20 you should see the default extensions (.db & .tpl) mapped to the = $WebCat.dll=20 file.  Again, confirm that these settings are mapped correctly with = no=20 spaces!  Now, I think these mappings are used whenever you create a = NEW=20 website, but do not effect the settings of an existing website (like = your=20 default website), so there's more to do...
 
3) = Default Web=20 Site configuration.
- Open IIS=20 manager and open the "Web Sites" folder in the = treeview
- = Rt-Click on the=20 Default Website and select "properties"
- = Click on the=20 "ISAPI Filters" tab and it should be empty
- = Click on the "Home=20 Directory" tab and click the "Configuration" button.
- = Under the=20 Mappings" tab, make sure that at a minimum .tpl and .db extensions are = mapped to=20 the $WebCat.dll file and that the path to the .dll file is correct and = DOES NOT=20 CONTAIN any spaces.
 
4) = Make sure=20 "Scripts" folder is defined as a Virtual Folder in = IIS
- Open = IIS Manager,=20 then open the "Web Sites" folder, then open the "Default Web Site"=20 folder
- = Under the Default=20 Website Folder, make sure the "Scripts" folder where you installed the=20 WebCatalogEngine folder is listed as a virtual directory.  If it is = not,=20 then add it.
- = Also, if this=20 folder is shown as an Application folder, then you must check the = mappings to be=20 certain that .tpl & .db are mapped correctly.  If the folder is = NOT an=20 application folder, then the folder should get it's mappings from the = "Default=20 Web Site" mappings.
 
5) = Make sure Web=20 Catalog is defined as a Virtual Folder in IIS
- Open = IIS Manager,=20 then open the "Web Sites" folder, then open the "Default Web Site"=20 folder
- = Under the Default=20 Website Folder, make sure the "Web Catalog" folder is listed as a = virtual=20 directory.  If it is not, then add it.
- = Also, if this=20 folder is shown as an Application folder, then you must check the = mappings to be=20 certain that .tpl & .db are mapped correctly.  If the folder is = NOT an=20 application folder, then the folder should get it's mappings from the = "Default=20 Web Site" mappings.
 
OK, this is how I was able to get = the=20 Windows XP Pro IIS to run the WebDNA program.  For users with = default=20 folder locations, it should not be as difficult as it was for me.  = As=20 mentioned, I think my whole problem stemmed from having a space in my = folder=20 path and then each subsequent install had remnants of that space = somewhere in=20 all of the IIS settings.  Following the process above helped me get = the=20 configuration running.
 
Again - thanks to all on the List = Server=20 that tried to help me out.
 
Sincerely,
 
JD = Ready
jdready@risedev.com
RISE Development = Group,=20 Inc.
303.925.0047 = Phone
720.226.0740 = Fax
866.321.0944 = Toll-Free
 
------=_NextPart_000_0000_01C917D4.070910B0-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] [BULK] Windows XP Pro Success! (Terry Wilson 2008)
  2. Re: [WebDNA] [BULK] Windows XP Pro Success! (Donovan Brooke 2008)
  3. [WebDNA] [BULK] Windows XP Pro Success! ("JD Ready" 2008)
This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C917D4.070910B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable OK Gang - I was able to get WebDNA running on my Windows XP Pro box! = Very special thanks to Terry Nair & Stuart Tremain for keeping me going = during this process. =20 The "secret" was this: First, WebDNA does NOT like spaces in the path name for the $WebCat.dll file. I had my web root in: D:\My Documents\Inetpub\wwwroot =20 That was the problem with all subsequent attempts to install WebDNA = because that folder was "remembered" between installs. =20 So, here's what I believe to be the proper install procedure: =20 1) Run the Windows Installer - The installer asks for 2 folder paths. The first is where to install = the "WebCatalog" folder. THis should be the root of your default website. = In my case, this was: D:\My Documents\Inetpub\wwwroot in default IIS installations, it's usually: C:\Inetpub\wwwroot =20 The second folder is where to install the WebCatalogEngine folder (this = is where the ISAPI filter: $WebCat.dll is installed). Make sure this = folder path does NOT have any spaces in it! I originally installed this folder to: D:\My Documents\Inetpub\Scripts However, this caused all types of problems. The folder that worked was = to install it to: C:\Inetpub\Scripts Note that this folder does not have any spaces in it. =20 Additionally, The installer has some verbiage about installing the = Engine in a folder designated to run "scripts". The truth is that this folder = must be configured in IIS 5.1 as an "Application" folder. You can make this designation AFTER the install if you don't already have a folder = designated as an "Application". =20 After the installer has run, it defaults to running the WebDNA html = page. BEFORE you do this, you should check several things in IIS. =20 2) "Web Sites" Configuration. =20 - Open IIS Manager. - Rt-Click the "Web Sites" folder and select "properties" - Under the "ISAPI Filters" tab, you should see "WebCatalog" with a = "high" priority. Make sure this is the LAST high priority filter. Click on = this filter and select "Edit" and make sure the executable to set to the = correct path to $WebCat.dll file (remember - no spaces!) - Next Click on the "Home Directory" tab and click the "Configuration" button. The first tab on the next screen is "mappings". When you ran = the installer in step 1, you should see the default extensions (.db & .tpl) mapped to the $WebCat.dll file. Again, confirm that these settings are mapped correctly with no spaces! Now, I think these mappings are used whenever you create a NEW website, but do not effect the settings of an existing website (like your default website), so there's more to do... =20 3) Default Web Site configuration. - Open IIS manager and open the "Web Sites" folder in the treeview - Rt-Click on the Default Website and select "properties" - Click on the "ISAPI Filters" tab and it should be empty - Click on the "Home Directory" tab and click the "Configuration" = button. - Under the Mappings" tab, make sure that at a minimum .tpl and .db extensions are mapped to the $WebCat.dll file and that the path to the = .dll file is correct and DOES NOT CONTAIN any spaces. =20 4) Make sure "Scripts" folder is defined as a Virtual Folder in IIS - Open IIS Manager, then open the "Web Sites" folder, then open the = "Default Web Site" folder - Under the Default Website Folder, make sure the "Scripts" folder where = you installed the WebCatalogEngine folder is listed as a virtual directory. = If it is not, then add it. - Also, if this folder is shown as an Application folder, then you must check the mappings to be certain that .tpl & .db are mapped correctly. = If the folder is NOT an application folder, then the folder should get it's mappings from the "Default Web Site" mappings. =20 5) Make sure Web Catalog is defined as a Virtual Folder in IIS - Open IIS Manager, then open the "Web Sites" folder, then open the = "Default Web Site" folder - Under the Default Website Folder, make sure the "Web Catalog" folder = is listed as a virtual directory. If it is not, then add it. - Also, if this folder is shown as an Application folder, then you must check the mappings to be certain that .tpl & .db are mapped correctly. = If the folder is NOT an application folder, then the folder should get it's mappings from the "Default Web Site" mappings. =20 OK, this is how I was able to get the Windows XP Pro IIS to run the = WebDNA program. For users with default folder locations, it should not be as difficult as it was for me. As mentioned, I think my whole problem = stemmed from having a space in my folder path and then each subsequent install = had remnants of that space somewhere in all of the IIS settings. Following = the process above helped me get the configuration running. =20 Again - thanks to all on the List Server that tried to help me out. =20 Sincerely, =20 JD Ready jdready@risedev.com RISE Development Group, Inc. 303.925.0047 Phone 720.226.0740 Fax 866.321.0944 Toll-Free =20 ------=_NextPart_000_0000_01C917D4.070910B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
OK = Gang - I was able=20 to get WebDNA running on my Windows XP Pro box!  Very special = thanks to=20 Terry Nair & Stuart Tremain for keeping me going during this=20 process.
 
The = "secret" was=20 this:
First, = WebDNA does=20 NOT like spaces in the path name for the $WebCat.dll file.  I had = my web=20 root in:
D:\My=20 Documents\Inetpub\wwwroot
 
That = was the problem=20 with all subsequent attempts to install WebDNA because that folder was=20 "remembered" between installs.
 
So, = here's what I=20 believe to be the proper install procedure:
 
1) Run = the Windows=20 Installer
- The = installer asks=20 for 2 folder paths.  The first is where to install the "WebCatalog" = folder.  THis should be the root of your default website.  In = my case,=20 this was:
D:\My=20 Documents\Inetpub\wwwroot
in = default IIS=20 installations, it's usually:
C:\Inetpub\wwwroot
 
The = second folder is=20 where to install the WebCatalogEngine folder (this is where the ISAPI = filter:=20 $WebCat.dll is installed).  Make sure this folder path does NOT = have any=20 spaces in it!
I = originally=20 installed this folder to:
D:\My=20 Documents\Inetpub\Scripts
However, this caused=20 all types of problems.  The folder that worked was to install it=20 to:
C:\Inetpub\Scripts
Note = that this=20 folder does not have any spaces in it.
 
Additionally, The=20 installer has some verbiage about installing the Engine in a folder = designated=20 to run "scripts".  The truth is that this folder must be configured = in IIS=20 5.1 as an "Application" folder.  You can make this designation = AFTER the=20 install if you don't already have a folder designated as an=20 "Application".
 
After = the installer=20 has run, it defaults to running the WebDNA html page.  BEFORE you = do this,=20 you should check several things in IIS.
 
2) = "Web Sites"=20 Configuration. 
- Open = IIS=20 Manager.
- = Rt-Click the "Web=20 Sites" folder and select "properties"
- = Under the "ISAPI=20 Filters" tab, you should see "WebCatalog" with a "high" priority.  = Make=20 sure this is the LAST high priority filter.  Click on this filter = and=20 select "Edit" and make sure the executable to set to the correct path to = $WebCat.dll file (remember - no spaces!)
- Next = Click on the=20 "Home Directory" tab and click the "Configuration" button.  The = first tab=20 on the next screen is "mappings".  When you ran the installer in = step 1,=20 you should see the default extensions (.db & .tpl) mapped to the = $WebCat.dll=20 file.  Again, confirm that these settings are mapped correctly with = no=20 spaces!  Now, I think these mappings are used whenever you create a = NEW=20 website, but do not effect the settings of an existing website (like = your=20 default website), so there's more to do...
 
3) = Default Web=20 Site configuration.
- Open IIS=20 manager and open the "Web Sites" folder in the = treeview
- = Rt-Click on the=20 Default Website and select "properties"
- = Click on the=20 "ISAPI Filters" tab and it should be empty
- = Click on the "Home=20 Directory" tab and click the "Configuration" button.
- = Under the=20 Mappings" tab, make sure that at a minimum .tpl and .db extensions are = mapped to=20 the $WebCat.dll file and that the path to the .dll file is correct and = DOES NOT=20 CONTAIN any spaces.
 
4) = Make sure=20 "Scripts" folder is defined as a Virtual Folder in = IIS
- Open = IIS Manager,=20 then open the "Web Sites" folder, then open the "Default Web Site"=20 folder
- = Under the Default=20 Website Folder, make sure the "Scripts" folder where you installed the=20 WebCatalogEngine folder is listed as a virtual directory.  If it is = not,=20 then add it.
- = Also, if this=20 folder is shown as an Application folder, then you must check the = mappings to be=20 certain that .tpl & .db are mapped correctly.  If the folder is = NOT an=20 application folder, then the folder should get it's mappings from the = "Default=20 Web Site" mappings.
 
5) = Make sure Web=20 Catalog is defined as a Virtual Folder in IIS
- Open = IIS Manager,=20 then open the "Web Sites" folder, then open the "Default Web Site"=20 folder
- = Under the Default=20 Website Folder, make sure the "Web Catalog" folder is listed as a = virtual=20 directory.  If it is not, then add it.
- = Also, if this=20 folder is shown as an Application folder, then you must check the = mappings to be=20 certain that .tpl & .db are mapped correctly.  If the folder is = NOT an=20 application folder, then the folder should get it's mappings from the = "Default=20 Web Site" mappings.
 
OK, this is how I was able to get = the=20 Windows XP Pro IIS to run the WebDNA program.  For users with = default=20 folder locations, it should not be as difficult as it was for me.  = As=20 mentioned, I think my whole problem stemmed from having a space in my = folder=20 path and then each subsequent install had remnants of that space = somewhere in=20 all of the IIS settings.  Following the process above helped me get = the=20 configuration running.
 
Again - thanks to all on the List = Server=20 that tried to help me out.
 
Sincerely,
 
JD = Ready
jdready@risedev.com
RISE Development = Group,=20 Inc.
303.925.0047 = Phone
720.226.0740 = Fax
866.321.0944 = Toll-Free
 
------=_NextPart_000_0000_01C917D4.070910B0-- "JD Ready"

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Closing Databases (take 2) (1998) select multiple 2 more cents (1997) Stopping a [Loop] in mid-stream ... (1997) numeric sorting (2001) SQL speed issues (2001) WebCat2: multiple currency support (1997) Webcat table size. (2001) RE: Webcatalog and CyberSTUD (1998) Any problem with using a g4 with WebCat (2000) WebCatalog NT beta 18 problem (1997) using showpage and showcart commands (1996) [ShowIf] and empty fields (1997) Help name our technology! (1997) AOL (1999) Supressing Error Messages (1998) [cart]= (2004) I'm having trouble using [url][interpret][math] together in lookup (1997) attachment (2000) Help! WebCat2 bug (1997) truncating email part II (1997)