I have spent the past week trying to sort out a problem with a new configuration of a Dispatcher installation. It is running on IIS 7.0, on a stand-alone server in our Development tier, so it has full access to our single Author and Publisher servers. I have gone through the Configuration page (http://dev.day.com/docs/en/cq/current/deploying/dispatcher/disp_config.html) and the Troubleshooting page (http://helpx.adobe.com/experience-manager/using/dispatcher-faq.html) several times. I have verified that my IIS server has the dispatcher files (the newest ones for 64 bit server) installed in c:\inetpub\Scripts and that they have been edited following the instructions (the dispatcher.any and disp_iis.ini files). The modules have been registered in ISAPI Filters, Handler Mappings, and Configuration editor, and the json mime type has been added. I have triple checked everything. I have even built a temporary server with the Author, Publisher, and IIS server all on one, just to make sure it wasn't an external firewall issue. On the temporary server, I am running the Geometrixx demo site and I can see the pages just fine in the Author mode (http://localhost:4502/content/geometrixx.html) and Publish mode. But when I try to pull it up on Webserver mode (http://localhost/content/geometrixx.html), I get the following error:
Calling GetProcAddress on ISAPI filter "C:\inetpub\Scripts\disp_iis.dll" failed
The only post I see about this refers to registering the disp_iss.dll file, which I have done - and I checked again to make sure.
The only difference I can see is that the documentation talks about a disp_iss.pdb file but that wasn't in the downloaded .zip file (nor in the SSL or x86 versions either). Is that old documentation, or do I need to get that file from somewhere? Or is there another issue at the root of this? I am pulling my hair out, and I have a deadline for a demo site this week. Any help would be appreciated.
Diana W.
Solved! Go to Solution.
Views
Replies
Total Likes
From error seems like disp_iis.dll is included in the ISAPI Filters (Will file a documentation bug). Please remove it. Below is a step-by-step instruction how to configure IIS with dispatcher 4.1.0 or higher posting from my notes. If below steps does not help file an daycare & will help you out through webex.
Views
Replies
Total Likes
Hi Diana,
From your description I have all the info but which dispatcher version you are using is missing. The error "Calling GetProcAddress on ISAPI filter C:\inetpub\Scripts\disp_iis.dll" is given due to an invalid ISAPI filter. Since the dispatcher version 4.1.0, the dispatcher module is no more an ISAPI filter, it is an ISAPI extension and should be used accordingly.
You can follow the steps given below to configure Dispatcher 4.1.0 or higher
You can also refer to the release notes of the dispatcher.
Views
Replies
Total Likes
The version is dispatcher-iis-windows-x64-4.1.4.zip. It contained 5 files: author-dispatcher.any (which we are not using), disp_iis.dll, disp_iis.ini, dispatcher.any, and release-notes.txt. I have them all in the Scripts folder under inetpub, and I have created a Virtual directory link under my website to the Scripts folder.
I have done the Handler Mappings, both with the instructions on the Configuring Dispatcher webpage and the Release-notes.txt file in the download - as a mapped and as a wildcard. I have done it at the website level, then deleted that and did it at the webserver level, then deleted that and put it back at the website (the server has a single website - Default). I have stopped and started the webserver service each time. I have even rebooted the entire server. The last thing I tried was installing the CGI option under Roles on the server, but that didn't help.
The version of AEM we are running is 5.6.1 and it is all brand new installations on VMWare servers running Windows Server 2008r2, fully patched.
Views
Replies
Total Likes
From error seems like disp_iis.dll is included in the ISAPI Filters (Will file a documentation bug). Please remove it. Below is a step-by-step instruction how to configure IIS with dispatcher 4.1.0 or higher posting from my notes. If below steps does not help file an daycare & will help you out through webex.
Views
Replies
Total Likes
Thanks - that got rid of the error message. (Now I am getting a webpage cannot be found, but that is probably a configuration error somewhere.)
Diana
Views
Replies
Total Likes
Thanks for update & good to hear it helped.
Views
Replies
Total Likes
Views
Like
Replies
Views
Likes
Replies