So far, we've been unable to bring the Mid Tier up using Jakarta on our new 64-bit W2003 Enterprise server. We've been working with Support for a week now, they're pointing to Jakarta as the problem. Here's what we've tried so far:
- successfully loaded ARS 7.1 p002 on MS Windows Server 2003 Enterprise Edition, 64-bit to D:/Program Files, received no errors. - ran the command that enables 32-bit mode: cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1 - found the ARSList post re: D:/Program Files vs. D:/Program Files (x86) but according to Support, the Mid Tier is registered as a 32-bit application so Windows knows how to deal with it. - ran the command that installs the 32-bit version of asp.net to clear the ISAPI filter error: %SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i - downloaded fresh copies of Tomcat and Jakarta directly overriding those provided during the Remedy install. Tried both 32-bit and 64-bit versions of Jakarta. - Mid Tier simply won't come up under IIS using Jakarta Redirector. We turned on logging, the debug log shows: jk_isapi_plugin.c (1417): [/arsys] is not a servlet url. - Able to use Mid Tier under Tomcat without issue, but we must use IIS. - Loaded ServletExec, Mid Tier works under this as well so it may an option, albeit an expensive one. If anyone has run into a similar problem, any insights would be most appreciated. Thanks. - Don _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
