All, Just figured this wonderful little guy out. It turns out there is a problem with SMS and Apache Tomcat running on the Default Web Site Port 80 in IIS. Here's what we were doing and the issues/fixes/etc. that we ran into. We wanted to install the Mid-Tier 7.1 on the same server where we had SMS running. We wanted to do this so we don't have to go buy our own separate server (cost reduction). Also, IIS is already installed there so why not use that. Well the box already had SMS installed on it and SMS was using the default Web Site Port 80 in IIS. When we installed Mid-Tier 7.1 Patch 5 with Apache Tomcat and Jakarta, we installed it under the same Default Web Site Port 80 in IIS. As it turns out there was a conflict with SMS and Apache Tomcat trying to use the same Port. Whenever an individual tried to access the web page it would cause an error on the server: "IIS Worker Process encountered a Problem and needed to close" Essentially there was a problem with ntdll.dll crashing. This in turn would cause both SMS and the Mid-Tier to stop working correctly.
FIX: We created a separate website in IIS and specified a different Port # for that web site. >From that point we added the Jakarta ISAPI filter to that new website, and we >created the Jakarta virtual directory. After that we removed the Jakarta ISAPI filter in the Default Web Site to stop it from breaking SMS. We tested this and it all looks to be working. Mid-Tier 7.1 Patch 5 IIS 6 Apache Tomcat/Jakarta Java 1.6 Patch 3 Matt P. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
