weblink setup ( again)

[Mike]

I have a weblink developer application that I am trying to install on
a new windows 2008 R2 64 bit server using Cache 2012. I am having
problems with what I think are permissions settings for access to the
mgwsm32.dll. When I try to access mgwms32.dll through the browser,
rather than executing the .dll the browser is trying to download
the .dll. What am I doing wrong.

Thanks,

Mike

[kevin furze]

I had a similar problem with nph-mgwsic.exe (the executable for EWD / m-apache)
I finally worked out that the MGWSI service was set to "manual-start" in services whereas it should have been set to "automatic-start"

I'm not saing for one moment, that I know what I'm talking about with weblink, but the "downloading" not "executing" is a similar problem that I was having.
perhaps, and its only a perhaps, you may have a similar problem.

I am of course, totally prepared to be told "you haven't got a clue what your'e talking about"

[Mike]

THanks for the response Kevin. I will check the services, but I think
this is a handler mapping issue. For some reason, the server is not
executing the mgwms32.dll. I have been trying to set up a handler
mapping but nothing I have tried works. Looks like I'm going to have
to pay an expert to fix it....

[Tony]

Hello Mike - I presume you are using IIS 7.5 (if you are using Windows Server 2008 R2); I have installed Weblink on this platform, see below for some of the steps I followed from notes I made at the time.  /Tony

# Directory structure

D:\[path]\CacheSys\Weblink\ (or whatever structure you prefer)

    mgwms32.dll - runtime/systems management executable

    mgw.ini - configuration file

    mgw.log - logging file

...\inetpub\wwwroot\ (your web site files)

    css\

    images\

    other\

    mgwx.js (located in distribution)

Note: there is no need to create a 'scripts' folder here, as handler mapping will take care of that.

# Directory permissions

Add 'IIS_IUSRS' group to the following directories, with 'read' permissions.  You will also need to allow write permissions for the individual 'mgw.ini' and 'mgw.log' files.

D:\[path]\CacheSys\

...\inetpub\wwwroot\

# Application pool

Create new application pool called 'CacheSys' and modify the following attributes.

1. Prevent worker process idle timeout (Idle Time-Out=0)

- Weblink native module manages connection pools.

2. Prevent worker process recycling (Regular Time Interval=0)

- Periodic recycling of worker processes is not required.

3. Allow worker process to run 32-bit applications (Enable 32-Bit Applications=True)

- The Weblink module is ‘mgwms32.dll’, which is a 32-bit application.

# Web site

Change anonymous authentication credentials to use the application pool identity instead of a specific user (e.g. 'IUSR').

# Register Weblink native module

Before the Weblink ('mgwms32.dll') module can be used it must be 'registered' with IIS.  This is done in the 'Internet Information Services (IIS) Manager' control panel.

First, open the 'Internet Services Manager' window and select base container, for example 'SERVER (Administrator)'.  In the middle panel, double-click the 'Modules' icon.  Now select the 'Configure Native Modules' in the actions pane and register the Weblink module.  The name should be 'Caché Weblink' and the path to where the 'DLL' file is located.

In the left-hand panel expand the top level to reveal the 'Web Sites' section.  In the middle panel, double-click the 'Handler Mappings' icon, select the 'Add Module Mapping' action and complete the dialogue.  The request path should be '*.dll', the module the one you have just created and the name 'Weblink_dll'.

# Weblink system management

Connect to the Weblink system management pages, using the appropriate link, see example below.

http://localhost/scripts/mgwms32.dll

[Mike]

Thanks Tony....I will try these instructions and see if I can get
things working.

[Mike]

Tony,

Following your instructions, I have gotten past the part where the
browser is trying to download the dll. It now tells me that the
service is unavailable.

One question that I have regarding your instructions is in the
section:

># Web site
>Change anonymous authentication credentials to use the application pool
>identity instead of a specific user (e.g. 'IUSR').

When changing the anonymous authentication credentials, the only
option besides a specific user is a select button for application pool
identity. Is there some setting with allows me to specify the
application pool to use?

On Mar 19, 7:29 am, Tony <tou...@spuddy.mew.co.uk> wrote:

[Tony]

Hello Mike

I inadvertently missed out a vital step in my instructions, so well spotted and my apologies.  You do actually need to create a 'scripts' directory in the root of your web site, even though you don't actually need anything inside it.  The section in question should read as follows.  You don't need to specify the application pool identity in the first step.

# Web site

Change anonymous authentication credentials to use the application pool identity instead of a specific user (e.g. 'IUSR').

Convert the '\scripts\' virtual directory to an application and assign the 'CacheSys' application pool to it.

The new version of IIS takes a while to get used to and I found file permissions particularly problematic.  If you do encounter problems I have used the 'Process Monitor' utility to help resolve these issues.  You can downloaded this from the Windows Sysinternals site, see link below.

http://technet.microsoft.com/en-gb/sysinternals/bb896645.aspx

Please feel free to post again if you encounter any further problems, because it does take a while to configure IIS and get working.

Tony

[Mike]

an update to all....

I had the server provider reload the system with the 32 bit version of
Windows 2008. I was then able to get WLD running on the new server.
Thank you everyone for all the help and advise you gave me.

Mike