Distribution, Manufacturing, and Internet Modules

[nbirkes]

I am trying to install the eBM ISAPI plug in on a Windows Server 2008 64bit machine with IIS7. I followed all the steps in the KB article on how to set it up on IIS7 and I am getting an error 500 instead of an error 404 but it's still not working.

The error message I am getting is:

HTTP Error 500.0 - Internal Server Error

There is a problem with the resource you are looking for, so it cannot be displayed.

Then it says the most likely causes are:

 •The path to the ISAPI Filter is incorrect. (Yes, it is)

•IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.(The masisapi is the first mapping and handles all *.pvx requests)

•IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.(This is not the problem)

•IIS was not able to process configuration for the Web site or application.(All web requests are fine other than *.pvx)

•The authenticated user does not have permission to use this DLL. (Possibly, but the permissions seemed fine to me)

Does anyone have experience with this setup? Any help would be more than appreciated! 

[mjpolk]

In IIS7, make sure the isapi web extension has execute rights.

[nbirkes]

Ok, I did that but now I'm getting a 403 error and the mapping is saying that it is disabled. Weird. I am going to look more into it tomorrow but for now it's time to go home.

Thanks for your help for now!!! Hopefully I can get some more info tomorrow. 

[mjpolk]

Here is the ISAPI installation guide. It apears to still apply for ver 4.x.  Run through it and make sure everything is done. If you still have issues let me know.

01/07/2010 15:03       

How to manually install and configure the ISAPI Plug-In for Sage MAS 90 and 200
 Summary:
See details.

 Resolution ID: 403981
How to manually install and configure the ISAPI Plug-In

Entry Type: Informational

Product:
Sage MAS 90 ERP
Sage MAS 200 ERP
Sage MAS 200 ERP - SQL Server Edition

Application: e-Business Manager

Version Reported: 3.71

Subject:

How to manually install and configure the ISAPI Plug-In.

Possible Resolution:

Notes:

• Manually installing and configuring the ISAPI Plug-in is required on Windows Server 2003, and on Sage MAS 90 or 200 4.00.
• Web site 'Execute Permissions' must be set to at least "Scripts Only" to run the ISAPI plug-in.
• The IIS must have at least read permissions to the ISAPI files to avoid errors.
• Sage Software Customer Support is not responsible for assisting with network issues and takes no responsibility for changes made to your network or for errors in these instructions. Consult your network administrator before making changes.

Windows Server 2000 and Server 2003

1. Copy the four  ISAPI files below to a folder on the IIS server. These files are located in ..\Isapi Plug-in\ on the Sage MAS 90 or 200 4.x  installation CD. If Sage MAS 90 or 200 3.7x is installed, contact Sage Software Customer Support to obtain the files.
   • Libeay32.dll
   • Masisapi.dll
   • Openssl.dll
   • Ssleay32.dll
     
2. Register the 'Server Side Include' (SSI) on the IIS Server:
   1. In IIS Manager, right-click the Web site under the 'Web Sites' folder, and select 'Properties' from the menu displayed.
   2. Select the 'Home Directory' tab, and click the 'Configuration' button.
   3. Select the 'Mappings' tab, and click the 'Add' button.
   4. Enter ".PVX" (no quotes) in the 'Extension' field. (This field is not case sensitive.)
   5. Click the 'Browse' button for the 'Executable' field, locate and select MASISAPI.DLL.
   6. Clear the "Verify that file exists" check box.
   7. Click 'OK' to return to the 'Application Configuration' window, and accept all other default settings.
   8. Verify that ".PVX" appears in the 'Application Extensions' panel.
   9. Click 'OK' until the 'Web site Properties' window is closed.
      
      
3. For Windows Server 2003 only - Enable Web Service Extensions on the IIS Server.
   Note: Do not select "All Unknown ISAPI Extensions". Doing so results in a severe security risk on the server.
   1. In IIS Manager, open the 'Web Service Extensions' folder.
   2. Select "Add a new web service extension".
   3. Enter ".PVX" (without quotes) in the 'Extension Name' field.
   4. Click 'Add' to open the 'Add File' window.
   5. Click the 'Path to File' browse button, and locate and select Masisapi.dll. Click 'OK'.
   6. Select the 'Set extension status to Allowed' check box. Click 'OK'.
   7. Verify that ".PVX" appears with a status of "Allowed" in the 'Web Service Extensions' panel.

Windows Server 2008 (32bit and 64bit editions)

1. Copy the four  ISAPI files below to the C:\Inetput\Scripts folder in the IIS server.  The Scripts folder may need to be created if it doesn?t already exist. These files are located in ..\Isapi Plug-in\ on the Sage MAS 90 or 200 4.x  installation CD or Extended Enterprise Solutions DVD .
2. Go to Start \ Control Panel \ Administrative Tools and open the Internet Information Services (IIS) Manager console.
3. Under Connections, select the server that is used for e-Business Manager.  Expand the Sites folder and then select the Web Site where the MASISAPI.DLL will be installed.
4. Double click Handler Mappings.  Under Actions, click Add Module Mapping.
5. Type *.PVX for Request path:.  At the Module: drop-down select IsapiModule.  Enter the path to the MASISAPI.DLL file in the Executable (optional): box.  A typical path will be: C:\Inetpub\Scripts\masisapi.dll.
6. For Name, type PVX.  Accept all the default values under Request Restrictions.
7. Click OK to close the Add Module Mapping screen to complete the installation.

Windows Server 2008 (64bit Editions only)
Enable 32-bit Applications in the Application Pool for the ISAPI Plugin:

1. Right click on Application Pools
2. Select the Application Pool used by the ISAPI Plugin (Typicall DefaultAppPool)
3. Right click and select "Set Application Pool Defaults"
4. Change "Enable 32-Bit Applications" from False to True. Accept your changes.

Related Articles:
How to publish style sheets, java scripts, and images in eBusiness Manager for Sage MAS 90 and 200

[agoldsmith99]

Did you make sure to set :

Windows Server 2008 (64bit Editions only)
Enable 32-bit Applications in the Application Pool for the ISAPI Plugin:

1.     Right click on Application Pools

2.     Select the Application Pool used by the ISAPI Plugin (Typicall DefaultAppPool)

3.     Right click and select "Set Application Pool Defaults"

4.     Change "Enable 32-Bit Applications" from False to True. Accept your changes.

Also check permissions on the scripts folder where all the DLLs are and the webeng folder -- you may have to set permission to EVERYONE Full Control -- I have seen some wierd permissions issues on a server I worked on in the last week that was really locked down and this did the trick -- just like it did in past releases

If you are still stuck -- let me know and I can take a look to see if we can figure it out together.

Angela

[nbirkes]

It's working now. For some reason I originally decided not to include the other DLL's in the directory when I copied over the masisapi.dll but I just copied them all over, re-mapped everything and the __debug.pvx page is working now.

Now I'm getting the "Unable to establish a connection (4)" error but I should be able to figure it out from here, hopefully.

Thanks to everyone for your help!! 

[nbirkes]

I configured the firewall where our MAS server is to allow traffic from the IIS server but I'm still getting the "Unable to establish a connection" error. What is the best way to test for an open connections between the two?

[nbirkes]

I figured it out, I opened the firewall to the wrong IP address, once I changed it to the correct address everything worked just fine.

Thanks again for your help! 

[joecoop]

Ok, I did all of that and it's still not working. I had everything working fine on Server 2003 but once we moved to Server 2008, no good. When I try to go to the _debug.pvx, I get a 404 error. Any ideas?

[agoldsmith99]

You may need to set the permissions on the DLLs as EVERYONE Full Control.