[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 298
  • Last Modified:

ServletExec and IIS: file.java not recognized as servlet!?

I've installed ServletExec on IIS 5.0/Win2k and am having problems getting servlets to run.  First off, this was working; we've had ServletExec, IIS5, and ArcIMS(Map Software) playing nicely, but it appears to be a VERY fragile arrangement.  So today, someone made unknown changes to IIS, trying to affect a misdiagnosed problem with scripting, and now my site which uses ServletExec will not load.  The best description of the problem I can muster, is that when you try to load the TestServlet or Admin servlets, as suggested by New Atlanta, going to http://servername/servlet/admin or TestServlet, instead of executing the file, it prompts to download or open it from it's current location.  Of course if you try to open the file, Win2k doesn't know what the hell it is.  Tried reinstalling ServletExec to no avail.  Permissions are wide open(Everyone Full Access) on New Atlanta\ServletExec ISAPI\ Directory.  Any Ideas?
0
benhanson
Asked:
benhanson
  • 2
1 Solution
 
pssiewCommented:
Try to make the folder where the file is executable from the IIS Console.

I am not familiar with the ServletExec software, but your problem looks like the application's executable file is not made executable in IIS hence when browsed, it is prompts for download.

Check for a .exe file location
0
 
benhansonAuthor Commented:
This was the case.  Actually, the file in question is a .dll, but the Scripts folder in IIS still needed permission to run "Scripts and Executables", so IIS must consider the Java servlets executables.  The actual steps involved:  Open IIS Managager, open properties on <servername>:Default Web Site:Scripts, go to Virtual Directory tab, and change Execute Permissions setting to "Scripts and Executables"  This got me to the point that the example and admin servlets worked, then I was able to work out the remaining ServletExec wierdness, which involved re-entering Serial number, the info was blown away during reinstall(Its in a file, not the registry), re-adding a Virtual Machine:Class Path to ServletExec through the Admin servlet, then re-copying Connector\Servlet\ Files from ArcIMS install directory.  Each of these steps require a restart of IIS, though if they are done all together they would probably only require one restart.  Thanks for the help pssiew.
0
 
pssiewCommented:
No problem Ben. Glad that you managed to solve it.
0

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now