WLS 6.0 error 404, 400

Hi, I have just installed the wls 6.0 sp1. I am unable to run servlets, however jsp files are running fine. when i try to access a servlet i get error 404.any help would be appreciated.

          Azhar <[email protected]> wrote:
          >Hi, I have just installed the wls 6.0 sp1. I am unable
          >to run servlets, however jsp files are running fine.
          >when i try to access a servlet i get error 404.any help
          >would be appreciated.
          Have you set up the servlet mapping in web.xml?
          <web-app>
          <servlet>
          <servlet-name>Main</servlet-name>
          <display-name>Main</display-name>
          <description>Main Servlet</description>
          <servlet-class>MyPackage.Main</servlet-class>
          </servlet>
          <servlet-mapping>
          <servlet-name>Main</servlet-name>
          <url-pattern>/Main</url-pattern>
          </servlet-mapping>
          </web-app>
          Steffen

Similar Messages

Error 404 not found for PAPIWS Console deployed in WLS

Hi, All,
I created 07-papiws-wls103-XAFDIDS.ear in OBPM 10.3.1 Admin Center, and deploy it to WLS 10.3 successfully.
The problem is when I try to access PAPIWS console by http://192.168.48.1:8901/papiws/PapiWebService, Error 404 not found reported.
Any ideas? Thanks in advanced.
Best Regards,
Bill

Let's start by clearing up some confusion.
PORTS
In version 11.1.1.x here are how the common ports are defined by default:
1. HTTP Server - 8888
2. WLS_FORMS - 9001
3. WLS_REPORTS - 9002
4. WLS Admin Server - 7001
So, if you understand how ports work in general, you should see that there are two ways to run a form. You can either go through HTTP Server or call WLS_FORMS directly. This means that both of the following would work, although one would be a direct path and the other would route the request through the HTTP Server:
<li>http://ie1fdtfc5zl1s:9001/forms/frmservlet?config=frmdemo
<li>http://ie1fdtfc5zl1s:8888/forms/frmservlet?config=frmdemo
Port 7001, will always be the Admin Server port by default for the Classic domain. By default, the only thing you can do from here is access EM or WLS Console.
As for the tns issue, by default, both the Builder and runtime will expect to find tnsnames.ora in the Instance Home \config so be sure you are adding the correct entries to the correct file.
You can hard code a path to the file which you prefer be used by setting TNS_ADMIN in default.env (e.g. TNS_ADMIN=C:\Oracle\mytnsdirectory). This will apply only to running forms and not the Builder.
Also, here is something which often is confusing to many people.... just because you launched your form from the Builder does not mean that the running form has anything to do with the Builder at that point. In other words, when you click on the RunForm button in the builder all you are doing is passing a url to a browser. The browser and the form are not using any of the Builder's settings except those which may have been passed in the URL (e.g. username/password). ALL running forms are considered "runtime". This means all of the environment configuration information for a running form will need to be set in default.env. The Builder, on the other hand will rely on the System variable, Windows Registry (or shell if on Unix).

DADs on WLS 11g (version 10.3.6.0) do not work (Error 404--Not Found)

Actually we use Application Server 10g (version 10.1.2.3.0) for different Forms 10g Applications (roundabout 1000 Forms) and want to change to Forms 11g and Weblogic Server 11g (version 10.3.6.0). A Test-Application on the Weblogic Server works fine, but DAD’s do not work at all.
In Enterprise Manager 10g i can configure DADs within the GUI of the Enterprise Manager, where i can see, if a connection could be established or not.
In Enterprise Manager 11g Fusion Middleware Control this doesn't seem to exist anymore, so i tried to configure the DADs manually, but something has to be wrong or missing, because there is no connection to the database and the following error appears:
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
I added several DAD’s to /opt/oracle/product/Middleware/asinst_1/config/OHS/ohs1/mod_plsql/dads.conf like this:
<Location /pls/jd-download-dev>
SetHandler pls_handler
Order allow,deny
Allow from All
AllowOverride None
PlsqlDatabaseUsername w_web_user_download
PlsqlDatabasePassword @BWKChfgPacV6yQL40lIKZqXUUA9wC4cmAw==
PlsqlDatabaseConnectString jddev TNSFormat
PlsqlNLSLanguage German_Germany.WE8ISO8859P1
PlsqlAuthenticationMode Basic
PlsqlDefaultPage w_anwendung.p_web_show_document
PlsqlAlwaysDescribeProcedure Off
PlsqlErrorStyle DebugStyle
</Location>
The passwords were obfuscated with dadTool.pl and the http-Server restarted with /opt/oracle/product/Middleware/asinst_1/bin/opmnctl restartproc process-type=OHS
The files /opt/oracle/product/Middleware/asinst_1/config/OHS/ohs1/mod_plsql.cache.conf and /opt/oracle/product/Middleware/asinst_1/config/OHS/ohs1/moduleconf.plsql.conf were left unchanged.
Our Test-Application generates the following link
'http://172.106.2.7:9001/pls/jddevdev/B_ARCHIVE.P_ARCHIVE_VIEW?docfid=200'
that seems to be ok, because when i replace IP and port with our old IAS it works fine, but the WebLogic Server generates the above mentioned error.
To get some more information i searched an error_log in /opt/oracle/product/Middleware/asinst_1/diagnostics/logs/OHS/ohs1 but there isn’t any.
I used the following Documentation for configuring the DADs which is for HTTP Server 11g Release 1 (version 11.1.1), because I could not find one for version 10.3.6.0:
http://docs.oracle.com/cd/E23943_01/web.1111/e10144/under_mods.htm#i1055269
So probably there are differences between configuring version 10.3.6.0 and version 11.1.1 and so something is wrong configured or missing...
Thank you in advance for your help
Udo

Hi Raj,
it is a Sparc Solaris 10
and yes that's my enviorment.
After some more tests it's seems it's not a real bug but no realy nice working solution.
Eclipse uses for all instances the same secure storage, where OEPE also saves the password.
And if I look right the pasword was saved without the user context, so if you use an other user he takes the same password from the old user.
and I doesn't know how do OEPE check the connection in reality or only reply the last failed login message.
After deleting the complete secure storage and test it again with the juno version it works well.

"Error 404: file not found"displayed when trying to run a process on server

Iam trying to run a "weblogic integration-process application" on server to test the application. Iam using weblogic workshop 9.2.
It is giving me the below error:
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address
File iam trying to run is RequestQuote.java
The file is in Tutorial_process_application_web/src/requestquote/
In the browser it is opening the below link:
http://localhost:7051/Tutorial_Process_Application_Web/requestquote/RequestQuote.java
I tried adding "src" in between but still same error is coming. I tried running just http://localhost:7051/, it is opening the weblogic integration window.
I have pasted the web.xml and all other configuration files below. Please let me know what changes i have to make to get the testing window.
Thanks,
Vishu.
web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>
Tutorial_Process_Application_Web</display-name>
<listener>
<listener-class>com.bea.wli.management.WliWebAppListener</listener-class>
</listener>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
<welcome-file>default.html</welcome-file>
<welcome-file>default.htm</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>
</web-app>
weblogic.xml
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
<wls:context-root>Tutorial_Process_Application_Web</wls:context-root>
<wls:library-ref>
<wls:library-name>struts-1.2</wls:library-name>
<wls:specification-version>1.2</wls:specification-version>
<wls:implementation-version>1.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>jstl</wls:library-name>
<wls:specification-version>1.1</wls:specification-version>
<wls:implementation-version>1.1.2</wls:implementation-version>
</wls:library-ref>
<wls:url-match-map>weblogic.servlet.utils.SimpleApacheURLMatchMap</wls:url-match-map>
</wls:weblogic-web-app>
application.xml
<?xml version="1.0" encoding="UTF-8"?>
<application id="Application_ID" version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
<display-name>
Tutorial_Process_Application_Ear</display-name>
<module id="WebModule_1180909671484">
<web>
<web-uri>Tutorial_Process_Application_Web.war</web-uri>
<context-root>Tutorial_Process_Application_Web</context-root>
</web>
</module>
<module>
<ejb>Tutorial_Process_Application_Web_WLI_ProjectBeans</ejb>
</module>
<module>
<ejb>Tutorial_Process_Application_Web_WLI_ComponentBeans</ejb>
</module>
</application>
weblogic-application.xml
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_1_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-application.xsd">
<wls:ejb>
<wls:start-mdbs-with-application>false</wls:start-mdbs-with-application>
</wls:ejb>
<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
<wls:classloader-structure>
<wls:classloader-structure>
<wls:module-ref>
<wls:module-uri>Tutorial_Process_Application_Web.war</wls:module-uri>
</wls:module-ref>
<wls:classloader-structure>
<wls:module-ref>
<wls:module-uri>Tutorial_Process_Application_Web_WLI_ProjectBeans</wls:module-uri>
</wls:module-ref>
</wls:classloader-structure>
<wls:classloader-structure>
<wls:module-ref>
<wls:module-uri>Tutorial_Process_Application_Web_WLI_ComponentBeans</wls:module-uri>
</wls:module-ref>
</wls:classloader-structure>
</wls:classloader-structure>
</wls:classloader-structure>
<wls:listener>
<wls:listener-class>com.bea.wli.management.WLIAppListener</wls:listener-class>
</wls:listener>
<wls:library-ref>
<wls:library-name>beehive-controls-1.0</wls:library-name>
<wls:specification-version>1.0</wls:specification-version>
<wls:implementation-version>1.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wls-commonslogging-bridge</wls:library-name>
<wls:specification-version>1.0</wls:specification-version>
<wls:implementation-version>1.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>weblogic-controls-1.0</wls:library-name>
<wls:specification-version>1.0</wls:specification-version>
<wls:implementation-version>1.0</wls:implementation-version>
</wls:library-ref>
</wls:weblogic-application>
Edited by gvishu at 06/04/2007 9:39 AM

sorry i didnt mention the weblogic workshop version, it is weblogic workshop 9.2.
Thanks,
vishu

Error 404 -- NOT FOUND when running a form in form 11g

Hi All,
I got this problem when I run the forms using internet explorer.
I work on Forms 11g which uses weblogic 10.3 for web deployment of the forms.
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
Can any one tell me where it went wrong.
Thanks

Let's start by clearing up some confusion.
PORTS
In version 11.1.1.x here are how the common ports are defined by default:
1. HTTP Server - 8888
2. WLS_FORMS - 9001
3. WLS_REPORTS - 9002
4. WLS Admin Server - 7001
So, if you understand how ports work in general, you should see that there are two ways to run a form. You can either go through HTTP Server or call WLS_FORMS directly. This means that both of the following would work, although one would be a direct path and the other would route the request through the HTTP Server:
<li>http://ie1fdtfc5zl1s:9001/forms/frmservlet?config=frmdemo
<li>http://ie1fdtfc5zl1s:8888/forms/frmservlet?config=frmdemo
Port 7001, will always be the Admin Server port by default for the Classic domain. By default, the only thing you can do from here is access EM or WLS Console.
As for the tns issue, by default, both the Builder and runtime will expect to find tnsnames.ora in the Instance Home \config so be sure you are adding the correct entries to the correct file.
You can hard code a path to the file which you prefer be used by setting TNS_ADMIN in default.env (e.g. TNS_ADMIN=C:\Oracle\mytnsdirectory). This will apply only to running forms and not the Builder.
Also, here is something which often is confusing to many people.... just because you launched your form from the Builder does not mean that the running form has anything to do with the Builder at that point. In other words, when you click on the RunForm button in the builder all you are doing is passing a url to a browser. The browser and the form are not using any of the Builder's settings except those which may have been passed in the URL (e.g. username/password). ALL running forms are considered "runtime". This means all of the environment configuration information for a running form will need to be set in default.env. The Builder, on the other hand will rely on the System variable, Windows Registry (or shell if on Unix).

Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED

Hi experts,
I have a big issue in production server,
the Queues are stuking in smq2 " command to tRFC/qRFC: execute LUW again"
if i am reprocess or press F6 it is going manually.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><html><head><title>Application Server Error</title> <style type="text/css"> body { font-family: arial, sans-serif;} </style> </head> <BODY text="#172972" link="#808080" vlink="#808080" alink="#8e236b" bgcolor=white leftmargin="0" topmargin="0" marginheight="0" marginwidth="0"> <table height="61" width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td background="http://xidist:8000/sap/public/icman/img/bluebar_tile.gif" height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP NetWeaver Application Server </font></td><td width=75% align="right" nowrap><font face=arial size="-1" color="white"><a href="http://help.sap.com/">Help </font></td><td width=5% nowrap></font></td> </tr></table> </td><td rowspan=2 width=122 height=61 valign=top><img src= "http://xidist:8000/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://xidist:8000/sap/public/icman/img/graybar_tile.jpg" height="31"> </td></tr> </table> <br><br> <table width=800> <tr><td width=50 nowrap> </td><td> <H2><b>404 Resource not found</b></H2><br>Partner not reached<br><br><hr> <table border="0"> <tr><td>Error:</td><td>-20</td></tr> <tr><td>Version:</td><td>7000</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Wed May 14 15:50:24 2014 </td></tr> <tr><td>Module:</td><td>icxxconn.c</td></tr> <tr><td>Line:</td><td>2341</td></tr> <tr><td>Server:</td><td>xidist_GXI_00</td></tr> <tr><td>Error Tag:</td><td>{004654a1}</td></tr> <tr><td>Detail:</td><td>Connection request from (110/28816/0) to host: xidist, service: 50000 failed (NIESERV_USED) EX-T110, U28816, 001 PIAFUSER, 10.1.57.50, 15:50:24, M0, W1, , 1/0</td></tr> </table> <p></p> </td></tr></table> <table><tr><td width=50 nowrap></td> <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2009, SAP AG</a></FONT> </td></tr></table> </body></html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Regards,
Kiran polani

Dear Sriram Ramani,
in ths case some scenarios are working good. proxy to soap, idoc to soap and jdbc to proxy, proxy to jdbc all are working with out error.
but my problem is in Soap to RFC case..
for all RFC communication channels are working but some time it is throwing RFC_COMMUNICATION_ERROR and messages are stucks in smq2 with retry.
when i check with retry error with in sxmb_moni log showing ICM_HTTP_CONNECTION_FAILED with error code 400.
not for all signals for few signals for some time..
Why it is happening i can't understand.
in repository it is saying Repsitory object hmi failed and address already in use.
is there any problem with loading IR objects.
Please suggest me good suggestion for this type of issue what can do for this to resolve.
Regards,
Kiran Polani

Cannot sign in to Elements 9 Get error message 400-photoshop services unavailable

Cannot sign into Elements 9. Get Error message 400-photoshop services unavailable

They're not available because photoshop.com is dead and gone, and any photos there are moved to revel, which you can't access through PSE versions prior to PSE 11. You should have received a bunch of emails about this back when it was happening.
http://barbarabrundage.com/2013/09/16/pse-8-9-10-cant-sign-in-error-404/

On signing in, get error message 400. How do I fix this?

Problem signing in to Photoshop Elements 9. Get error message 400. Also can't create new user ID. Help!

There is no longer anything to sign in to.
See this for the reason and solution:
http://barbarabrundage.com/2013/09/16/pse-8-9-10-cant-sign-in-error-404/

I currently own Photoshop Elements 9 and receive an error message "400" when logging in

I need to log into Photoshop Elements 9 but I receive an error message of "400". Do I just need to purchase a later version of photoshop? I need to retrieve my pictures.

http://barbarabrundage.com/2013/09/16/pse-8-9-10-cant-sign-in-error-404/

Error 404 when using the app

For my app that is built using JDeveloper 11.1.1.3.0, I have a .jspx which has 3 page fragments (.jsff) built into it. I see the following error message whenever any buttons, including the out of the box, Search button, are clicked:
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
I see this error message only when I deploy the EAR to DEV and TEST environments and I don't see this error on my local env, where I am deploying the EAR to Integrated WLS.
WebLogic server logs don't give me any more info than:
"Multiple forms detected on viewId: /SpecPages/CSTHistory.jspx. Rich client currently has some limitations in dealing with multiple forms."
I didn't modify the page authorization (jazn-data.xml) for this .JSPX or the three .JSFF's I use so I am not sure why this error is popping up.

I quickly added one jspx to test if it would help. However, the URL continues to display w/ the .jspx extension. Here is the updated xml file:
<?xml version="1.0" encoding="windows-1252" ?>
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
<view id="csthistory">
<page>/SpecPages/CSTHistory.jspx</page>
</view>
<managed-bean>
<managed-bean-name>login</managed-bean-name>
<managed-bean-class>com.qualcomm.backing.LoginHandler</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
</adfc-config>
I have a total of 6 jspx and most of them have JSFF's and these jspx's are set up as navigation panes.

OIM server running but error 404

hello experts,
I have started OIM server and its in running state in both cmd and weblogic(7001, server status) but while opening it in web console am getting error 404 page not found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
Kindly suggest.
Regards,
Karan

hi
Current staus in deployements tab of oim_server
DMS Application (11.1.1.1.0)     Active     Web Application     5
Nexaweb     Active     Enterprise Application     45
oim (11.1.1.3.0) Failed     Enterprise Application     47
OIMMetadata (11.1.1.3.0)     Failed     Enterprise Application     46
RoleSOD     Active     Enterprise Application     50
spml-xsd     Active     Enterprise Application     49
wsil-wls     Active     Enterprise Application     5
wsm-pm     Failed     Enterprise Application     5
FYI : yesterday I have worked on web console, and it was working fine.
Regards,
Karan

Temporary error (404) Numeric Code: 7

I keep getting a "Temporary Error (404) Numeric Code: 7" when I attempt to open pictures on my gmail account. They open in other web browsers, but not this one. Anyone know what the issue is? It's been doing it for months. I can download a picture, just not view it. Please help!

Hi,
integrated WLS or stand alone WLS ? Is the application successfully deployed? Is security enabled or disabled ? What is the request URL ?
Frank

Error 404 -- Not Found, when a Servlet is invoked from browser

Obviously, I have not been able to configure my WebLogic Server 5.1.0 to run
          even the simplest servlet.
          I painstakenly went through all the steps that are listed in the WebLogic
          Server 5.1.0 documentation on the Web to enable servlets, but obviously, I
          have missed a step somewhere.
          I have modified the weblogic.properties file as per all the instrustions,
          but the server simply won't recognize any servlets, not even the SqlServlet
          that came with the server as an example.
          It would require more than 1 exchange of posts to resolve it for me, and I
          am wondering if one of you is willing to work with me on this until I have
          managed to configure the server to make a servlet work on it.
          The server does function as a Web server as I can run the index.html
          document by entering the URL: http://localhost:7001/index.html
          I am pasting the contents of weblogic.properties file below to get the
          person who is willing to help me started.
          The machine I have is a Pentium III with Windows 2000 Professional on it.
          It's a home machine and the WebLogic server is the freely downloadable
          version. I am using it to prepare for a potential contract work.
          I have managed to modify setEnv.cmd file and have managed to compile the
          SqlServlet.java, which is an example servlet. Neither this particular
          servlet nor a HelloWorld type of very basic servlet I have written are
          recognized by the server.
          As you can see from my weblogic.properties file (pasted at the end of this
          post), the SqlServlet has been registered. I have also uncommented the lines
          to allow for the following type of URL:
          http://localhost:7001/servlet/myServlet
          Thanks!
          Anjum Jaleel
          CONTENTS OF MY weblogic.properties file
          # THE WEBLOGIC PROPERTIES FILE
          # This file, which conforms to the java.util.Properties file
          # definition, configures your WebLogic products. You cannot run
          # WebLogic Server without setting required configuration properties in this
          # file. Required properties are marked and appear first in the file.
          # Details on each entry and important information about configuration
          # and security are documented on our website. Please go to:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # for full instructions on how to edit this file.
          # You do not need to include properties in this file unless you want to
          # change the default, embedded property. Some properties on the
          # AdminProps page are not listed here because the default property
          # is being used. You can change the default by adding the property and
          # its value to this file.
          # You cannot set weblogic.system.home in this file, since the WebLogic
          Server
          # must know where home is in order to retrieve this file. You can
          # change WebLogic home on the command line when you start the
          # WebLogic Server.
          # CLUSTER USERS: Note that the (shared) per-cluster properties file should
          # contain most all of the properties in this file. The only properties
          # that potentially belong in a per-server properties file for a server
          # running in a cluster are the registration (startup class) of pinned
          # RMI objects, and a few tuning properties that may be different for
          # servers in the cluster, depending upon hardware and memory. If you use
          # a per-server properties file, please REMOVE all properties except those
          # that are specifically required in the per-server properties file. You
          # can find specific notes on clusters by searching through this file for
          # "CLUSTER USERS".
          # The way this file is organized:
          # Core properties (includes REQUIRED and RECOMMENDED)
          # Core system properties
          # Core security-related properties
          # Core security-related properties for SSL
          # Core HTTPD administrative properties
          # Optional properties
          # Administrator properties
          # System properties
          # System startup files
          # System shutdown files
          # Security-related properties for Workspaces
          # Jolt for WebLogic properties
          # WebLogic Enterprise Connectivity properties
          # WebLogic File properties
          # WebLogic JMS demo properties
          # WebLogic RMI demo properties
          # WebLogic EJB demo properties
          # WebLogic XML demo properties
          # WebLogic ZAC demo properties
          # HTTPD administrative properties
          # WebLogic JDBC driver properties
          # WebLogic JDBC connection pool management
          # WebLogic demo connection pool
          # WebLogic HTTP Servlet properties
          # Proxy servlet registration
          # Classpath servlet registration
          # File servlet registration
          # ServerSideInclude servlet registration
          # PageCompileServlet (used by JHTML)
          # JSPServlet (used by JSP)
          # ServletServlet registration
          # Servlet reload properties
          # Servlet ACLs
          # WebLogic JSP properties
          # WebLogic JHTML properties
          # WebLogic RMI over IIOP properties
          # User-written and demo servlet registrations
          # CORE PROPERTIES
          # You should set these before you start the WebLogic Server the first time.
          # If you need more instructions on individual properties in this
          # section, check the same section in the Optional Properties, where
          # we've left the long explanations. Or, better yet, go to our
          # website and read all about properties, at:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # CORE SYSTEM PROPERTIES
          # TCP/IP port number at which the WebLogic Server listens for connections
          weblogic.system.listenPort=7001
          # CORE SECURITY-RELATED PROPERTIES
          # Read important information about security at:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # REQUIRED: The system password MUST be set in order to start the
          # WebLogic Server. This password is case-sensitive, at least 8 characters.
          # The username for the privileged user is ALWAYS "system".
          # This username and password also includes httpd access (see
          # HTTPD properties below).
          weblogic.password.system=lovkako1
          # RECOMMEND Set to 'everyone' if HTTPD is enabled
          weblogic.allow.execute.weblogic.servlet=everyone
          # Set individual ACLs to restrict access to HTTP-related resources,
          # such as the Administration servlets.
          # To make your own servlets generally available, follow this
          # pattern (provide a weblogic.allow.execute) for your packages and
          # set ACLs as appropriate.
          # CORE SECURITY-RELATED PROPERTIES FOR SSL
          # Read important information about SSL at:
          # http://www.weblogic.com/docs51/classdocs/API_secure.html
          # Enable SSL
          # (default if property not defined is false)
          weblogic.security.ssl.enable=true
          # SSL listen port
          weblogic.system.SSLListenPort=7002
          # Servlets for SSL
          # Authentication servlet for creating tokens for applets
          weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
          ervlet
          # Limits number of unclaimed stored tokens
          weblogic.security.certificateCacheSize=3
          # Capture CA root of client servlet
          weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
          # Certificates for SSL
          # Name of acceptable CA roots
          # For client authentication change value to a valid .pem file
          #weblogic.security.clientRootCA=SecureServerCA.pem
          # Server certificates for SSL
          weblogic.security.certificate.server=democert.pem
          weblogic.security.key.server=demokey.pem
          weblogic.security.certificate.authority=ca.pem
          # registration for certificate generator servlet
          weblogic.httpd.register.Certificate=utils.certificate
          weblogic.allow.execute.weblogic.servlet.Certificate=system
          # CORE HTTPD ADMINISTRATIVE PROPERTIES
          # True permits the HTTPD to run (default)
          # Uncomment this property to disable HTTPD
          weblogic.httpd.enable=true
          # If authentication is required, add username/password for each user
          # who will be included in an ACL, as in this commented-out example:
          #weblogic.password.peter=#8gjsL4*
          # OPTIONAL PROPERTIES
          # These properties affect the behavior of the WebLogic Server.
          # You only need to set these properties if you want
          # to change the default setting, which is the property shown.
          # ADMINISTRATOR PROPERTIES
          # Administrator properties are optional information properties,
          # particularly useful for clusters.
          #weblogic.administrator.location=3355 California Drive, West Hampshire, CA
          94104
          #weblogic.administrator.name=Joe Administrator
          #weblogic.administrator.phone=1 415 555 1234
          # SYSTEM PROPERTIES
          # System properties in this section are set to system defaults
          # Performance pack. The shared library must be accessible from your
          # PATH (NT) or from your shared library path (UNIX; the name of the
          # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
          weblogic.system.nativeIO.enable=true
          # Outputs logging information to the console as well as to the log file
          weblogic.system.enableConsole=true
          # Sets the directory or URL for the WebLogic Admin help pages
          # The help pages are shipped in the "docs/adminhelp" directory, in the
          # default document root in public_html
          weblogic.system.helpPageURL=g:/weblogic/myserver/public_html/docs51/adminhel
          p/
          # If you prefer to access the most recent help pages, you can do so online
          # by commenting out the previous property and uncommenting this one:
          #weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
          # Properties for tuning the server's performance
          # Number of WebLogic Server execute threads.
          weblogic.system.executeThreadCount=15
          # Other optional system properties
          # Limits size of weblogic.log (in K) and versions old log
          weblogic.system.maxLogFileSize=1024
          # Adjust minimum length of password
          weblogic.system.minPasswordLen=8
          # UNIX only: If running on port 80 on UNIX, enable the setUID program
          #weblogic.system.enableSetUID=false
          # UNIX only: Unprivileged user to setUID to after starting up
          # WebLogic Server on port 80
          #weblogic.system.nonPrivUser=nobody
          # CLUSTER-SPECIFIC PROPERTIES
          # Cluster-specific properties in this section are set to system defaults.
          # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
          # in the per-cluster properties file ONLY.
          # Time-to-live (number of hops) for the cluster's multicast messages
          # (default 1, range 1-255).
          #weblogic.cluster.multicastTTL=1
          # Sets the load-balancing algorithm to be used between
          # replicated services if none is specified. If not specified,
          # round-robin is used.
          #weblogic.cluster.defaultLoadAlgorithm=round-robin
          # SERVER-SPECIFIC CLUSTER PROPERTIES
          # Cluster-related properties in this section are set to system defaults.
          # CLUSTER USERS: Note that these server-specific cluster-related properties
          # should be set in the per-server properties file ONLY.
          # Sets the weight of the individual server for the weight-based
          load-balancing.
          # Range is 0 - 100.
          # Larger numbers increase the amount of traffic routed to this server.
          #weblogic.system.weight=100
          # SYSTEM STARTUP FILES - Examples
          # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
          # objects should be registered in the per-server properties file.
          # All other startup classes should be registered in the per-cluster
          # properties file.
          # For more info on writing and using startup file, see the
          # Developers Guide "Writing a WebLogic Client application," at
          # http://www.weblogic.com/docs51/classdocs/API_t3.html
          # Register a startup class by giving it a virtual name and
          # supplying its full pathname.
          #weblogic.system.startupClass.[virtual_name]=[full_pathname]
          # Add arguments for the startup class
          #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
          # This example shows the entry for examples/t3client/StartupQuery.java
          #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
          #weblogic.system.startupArgs.doquery=\
          # query=select * from emp,\
          # db=jdbc:weblogic:pool:demoPool
          # SYSTEM SHUTDOWN FILES - Examples
          # For more info on writing and using shutdown file, see the
          # Developers Guide "Writing a WebLogic Client application," at
          # http://www.weblogic.com/docs51/classdocs/API_t3.html
          # Register a shutdown class by giving it a virtual name and
          # supplying its full pathname.
          #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
          # Add arguments for the shutdown class
          #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
          # This example shows the entry for examples/t3client/ShutdownTest.java
          #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
          #weblogic.system.shutdownArgs.ShutdownTest=\
          # outfile=c:/temp/shutdown.log
          # SECURITY-RELATED PROPERTIES FOR WORKSPACES
          # For backward compatibility, the following entries disable Access
          # Control on Workspaces
          weblogic.allow.read.weblogic.workspace=everyone
          weblogic.allow.write.weblogic.workspace=everyone
          # JOLT FOR WEBLOGIC PROPERTIES
          # These properties configure a BEA Jolt connection pool for use with
          # the simpapp and bankapp examples, and register a servlet for use with
          # with the simpapp example. The default server address provided here
          # points to a public TUXEDO server that is hosted by BEA for use with
          # this example.
          # Servlet registration for simpapp example:
          #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
          t
          # Pool creation and cleanup
          # note this example is set up to work with the public
          # demo TUXEDO server available from BEA's website:
          #weblogic.system.startupClass.demojoltpoolStart=\
          # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
          #weblogic.system.startupArgs.demojoltpoolStart=\
          # poolname=demojoltpool,\
          # appaddrlist=//beademo1.beasys.com:8000,\
          # failoverlist=//beademo1.beasys.com:8000,\
          # minpoolsize=1,\
          # maxpoolsize=3
          #weblogic.system.shutdownClass.demojoltpoolStop=\
          # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
          #weblogic.system.shutdownArgs.demojoltpoolStop=\
          # poolname=demojoltpool
          # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
          # The registrations enable a BEA IIOP connection pool and
          # register servlets for use with the simpapp and university examples.
          # Configure for your environment and uncomment to use.
          # Uncommenting these properties requires WebLogic Enterprise Connectivity
          # and an operating WebLogic Enterprise Server.
          # Servlet registration for simpapp servlet example
          #weblogic.httpd.register.SimpappServlet=\
          # examples.wlec.servlets.simpapp.SimpappServlet
          #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
          # Servlet registration for simpapp EJB example
          # (You'll need to add the wlec_ejb_simpapp.jar to the
          # weblogic.ejb.deploy property in this file.)
          #weblogic.httpd.register.ejbSimpappServlet=\
          # examples.wlec.ejb.simpapp.ejbSimpappServlet
          #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
          # Pool creation and cleanup for the simpapp example
          #weblogic.CORBA.connectionPool.simplepool=\
          # appaddrlist=//wlehost:2468,\
          # failoverlist=//wlehost:2468,\
          # minpoolsize=2,\
          # maxpoolsize=3,\
          # username=wleuser,\
          # userrole=developer,\
          # domainname=simpapp
          # Servlet registration for university Servlet example:
          #weblogic.httpd.register.UniversityServlet=\
          # examples.wlec.servlets.university.UniversityServlet
          #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
          # Pool creation and cleanup for the University example:
          #weblogic.CORBA.connectionPool.Univpool=\
          # appaddrlist=//wlehost:2498,\
          # failoverlist=//wlehost:2498,\
          # minpoolsize=2,\
          # maxpoolsize=3,\
          # username=wleuser,\
          # userrole=developer,\
          # apppassword=wlepassword,\
          # domainname=university
          # WEBLOGIC FILE PROPERTIES
          # Maps a volume name to a path, for client file read/write
          #weblogic.io.fileSystem.[volumeName]=[fullPathName]
          # WEBLOGIC JMS DEMO PROPERTIES
          # CLUSTER USERS: Note that ALL JMS deployment should be done in the
          # per-cluster properties file ONLY.
          # You set up a JDBC connection pool if you want persistent messages
          # (including durable subscriptions). To use JMS and EJBs in the same
          # transaction, both must use the same JDBC connection pool. Uncomment
          # the following property to use the default JDBC connection pool
          # 'demo', which is defined in the Demo connection pool section of this file.
          #weblogic.jms.connectionPool=demoPool
          # The JMS Webshare example demonstrates how the ClientID for a
          # durable subscriber is configured in the connection factory:
          #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
          #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
          #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
          #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
          # The JMS trader example shows how to use JMS with an EJB. In addition
          # to uncommenting the following properties, you must also set up and
          # deploy the EJB example examples.ejb.basic.statelessSession.Trader in
          # ejb_basic_statelessSession.jar to try out this JMS example:
          #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
          #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
          #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
          #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
          # Registers the underlying servlet
          #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
          # These properties are used with the ServerReceive JMS example,
          # which demonstrates how to establish a JMS message consumer
          # in a startup class:
          #weblogic.system.startupClass.serverReceive=\
          # examples.jms.startup.ServerReceive
          #weblogic.system.startupArgs.serverReceive=\
          # connectionFactory=javax.jms.TopicConnectionFactory,\
          # topic=javax.jms.exampleTopic
          # These properties are used with the PoolReceive JMS example,
          # which demonstrates how to establish a pool of JMS message consumers
          # in a startup class:
          #weblogic.system.startupClass.poolReceive=\
          # examples.jms.startup.PoolReceive
          #weblogic.system.startupArgs.poolReceive=\
          # connectionFactory=javax.jms.TopicConnectionFactory,\
          # topic=javax.jms.exampleTopic
          #weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
          # WEBLOGIC RMI DEMO PROPERTIES
          # CLUSTER USERS: Note that pinned RMI objects should be registered
          # in the per-server properties file ONLY. All other RMI startup
          # classes should be registered in the per-cluster properties file.
          # Remote classes registered at startup after the pattern:
          #weblogic.system.startupClass.[virtualName]=[fullPackageName]
          # These examples can be compiled to see RMI in action. Uncomment to use:
          #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
          #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
          #weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
          # WEBLOGIC EJB DEMO PROPERTIES
          # CLUSTER USERS: Note that ALL EJB deployment should be done in the
          # per-cluster properties file ONLY.
          # See WebLogic Demo Connection Pool below for a connection pool
          # to use with these examples.
          # Deploys EJBeans. Uncomment the appropriate lines below and
          # modify DBMS-related info and paths to match your particular installation:
          #weblogic.ejb.deploy=\
          # g:/weblogic/myserver/ejb_basic_beanManaged.jar, \
          # g:/weblogic/myserver/ejb_basic_containerManaged.jar, \
          # g:/weblogic/myserver/ejb_basic_statefulSession.jar, \
          # g:/weblogic/myserver/ejb_basic_statelessSession.jar, \
          # g:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
          # g:/weblogic/myserver/ejb_extensions_readMostly.jar, \
          # g:/weblogic/myserver/ejb_subclass.jar, \
          # g:/weblogic/myserver/jolt_ejb_bankapp.jar
          # Servlet used by the EJB basic beanManaged example
          # Uncomment to use:
          #weblogic.httpd.register.beanManaged=\
          # examples.ejb.basic.beanManaged.Servlet
          # Add a list of users (set the password with
          weblogic.password.[username]=XXX)
          # to set an ACL for this servlet:
          #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
          #weblogic.password.user1=user1Password
          #weblogic.password.user2=user2Password
          # WEBLOGIC XML DEMO PROPERTIES
          # These properties are required to run the XML examples.
          # Uncomment to use.
          # CLUSTER USERS: Note that ALL servlets should be set up
          # in the per-cluster properties file ONLY.
          #weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
          # BizTalk example properties
          #weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
          #weblogic.jms.queue.tradeError=biztalk.jms.tradeError
          #weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
          dapter
          #weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
          # WEBLOGIC ZAC DEMO PROPERTIES
          # These registrations enable the ZAC Publish Wizard.
          weblogic.zac.enable=true
          # Set the publish root for a WebLogic Server. Edit and
          # uncomment to use.
          #weblogic.zac.publishRoot=g:/weblogic/zac
          # Set an ACL for each package you publish. The [name] is
          # the "Package name" you assign in the ZAC Publish Wizard.
          # Publish a package, edit this property, and uncomment to use.
          #weblogic.allow.read.weblogic.zac.[name]=[user list]
          #weblogic.allow.write.weblogic.zac.[name]=system
          # HTTPD ADMINISTRATIVE PROPERTIES
          # Enables logging of HTTPD info in common log format and
          # sets the log file name (default is "access.log" in "myserver")
          weblogic.httpd.enableLogFile=true
          weblogic.httpd.logFileName=access.log
          # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
          weblogic.httpd.enableEvents=false
          # Enables HTTP sessions
          weblogic.httpd.session.enable=true
          # Sets an optional cookie name. The default name is "WebLogicSession".
          # Prior to version 4.0, the default was "TengahSession". To make
          # this backward compatible with cookies generated from previous
          # installations, you should set this property to "TengahSession".
          # Uncomment this line and set this to any string of your choice,
          # or comment out this property to use the default.
          #weblogic.httpd.session.cookie.name=WebLogicSession
          # MIME types
          weblogic.httpd.mimeType.text/html=html,htm
          weblogic.httpd.mimeType.image/gif=gif
          weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
          weblogic.httpd.mimeType.application/pdf=pdf
          weblogic.httpd.mimeType.application/zip=zip
          weblogic.httpd.mimeType.application/x-java-vm=class
          weblogic.httpd.mimeType.application/x-java-archive=jar
          weblogic.httpd.mimeType.application/x-java-serialized-object=ser
          weblogic.httpd.mimeType.application/octet-stream=exe
          weblogic.httpd.mimeType.text/vnd.wap.wml=wml
          weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
          weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
          weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
          weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
          # In seconds, the keep-alive for HTTP and HTTPS requests
          weblogic.httpd.http.keepAliveSecs=60
          weblogic.httpd.https.keepAliveSecs=120
          # WEBLOGIC JDBC DRIVER PROPERTIES
          # Enables JDBC driver logging and sets the file name for the log
          # The weblogic.jdbc.logFile is placed in the per-server
          # directory (default is "myserver")
          weblogic.jdbc.enableLogFile=false
          weblogic.jdbc.logFileName=jdbc.log
          # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
          # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
          # in the per-cluster properties file ONLY.
          # For creating JDBC connection pools. This example shows a connection
          # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
          # to use 4 JDBC connections (with a potential for up to 10 connections,
          # incremented by two at a time, with a delay of 1 second between each
          # attempt to connect to the database), to an Oracle database server called
          # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
          # connections are dropped from the pool until only 4 connections remain
          open.
          # Every 10 minutes, any unused connections in the pool are tested and
          # refreshed if they are not viable.
          #weblogic.jdbc.connectionPool.oraclePool=\
          # url=jdbc:weblogic:oracle,\
          # driver=weblogic.jdbc.oci.Driver,\
          # loginDelaySecs=1,\
          # initialCapacity=4,\
          # maxCapacity=10,\
          # capacityIncrement=2,\
          # allowShrinking=true,\
          # shrinkPeriodMins=15,\
          # refreshMinutes=10,\
          # testTable=dual,\
          # props=user=SCOTT;password=tiger;server=DEMO
          # Get more details on each argument for this property in the
          # Administrators Guide on setting properties at:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # Set up ACLs for this connection pool with the following:
          #weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
          # guest,joe,jill
          #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
          # joe,jill
          #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\

Problem Resolved!
          I found out that I had 'http' instead of 'httpd' in the statement where I
          registered my servlet, SqlServlet.
          Now, I am having difficulty with hot deployment. The server is returning
          error 404.

I want to add refworks grabit to my tool bar, when I try to install for firefox it won' t let me this is what I get: HTTP Error 404.3 - Not Found The page you a

this is the complete error I get. I just installed firefox so that I can use this feature and now it is useless.
Error Summary
HTTP Error 404.3 - Not Found
The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.
Detailed Error Information
Module StaticFileModule
Notification ExecuteRequestHandler
Handler StaticFile
Error Code 0x80070032
Requested URL http://www.refworks.com:80/refgrabit/install.xpi
Physical Path E:\RefGrabIt\install.xpi
Logon Method Anonymous
Logon User Anonymous
Failed Request Tracing Log Directory C:\inetpub\logs\FailedReqLogFiles
Most likely causes:
It is possible that a handler mapping is missing. By default, the static file handler processes all content.
The feature you are trying to use may not be installed.
The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.)
If ASP.NET is not installed.
Things you can try:
In system.webServer/handlers:
Ensure that the expected handler for the current page is mapped.
Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.
Pay extra attention to typographical errors in the expected handler line.
Please verify that the feature you are trying to use is installed.
Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe.
To set a MIME type, use the following syntax: %SystemRoot%\windows\system32\inetsrv\appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string']
The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.
For example, to add a MIME map for a file which has the extension ".xyz": appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain']
Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them.
Install ASP.NET.
Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
Links and More Information This error occurs when the file extension of the requested URL is for a MIME type that is not configured on the server. You can add a MIME type for the file extension for files that are not dynamic scripting pages, database, or configuration files. Process those file types using a handler. You should not allows direct downloads of dynamic scripting pages, database or configuration files.
View more information »

That file might have moved to a different location on the server. I think you'll need to check with RefWorks support or your local IT department on why the install page links do not work.

Error 404: SRVE0190E: File not found when trying to access jsp

I am using RAD (new to web dev) for some reason my app is unable to find .jsp's when they are not in the web content folder. I have a predefined package for my jsp's and when I run my servlet I get
Error 404: SRVE0190E: File not found: /WEB-INF/classes/app/view/search.jsp
now if I amend my URL in the servlet to "/search.jsp" and move the jsp to the web content folder, it works. I just don't understand why it cannot find the file when I put it in the package I created and link to it, but finds it just fine in the webcontent folder. Is there some unwritten rule JSP's MUST be in the webcontent folder? Because when i do that, then I have issues with my image links for the GUI (get red X's for all my images regardless of the fact they are linked properly.) Basically if I put my jsps where I want, look fine in design and preview, but the jsp isnt found when executed, if I move them to the web content folder the images no longer work but the jsps run. I am getting rather frustrated. Any help is appreciated.

Clear the cache and the cookies from sites that cause problems.
"Clear the Cache":
*Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"
"Remove Cookies" from sites causing problems:
*Tools > Options > Privacy > Cookies: "Show Cookies"
See also:
*https://support.mozilla.org/kb/Clear+Recent+History
Are you using cleanup software like CCleaner or other software that may corrupt the cache?
You can try to delete the entire cache folder.<br />
You can find the location of the cache folder on the about:cache page (open via the location bar, like a web page).
You can check the <b>browser.cache.disk.enable</b> pref on the <b>about:config</b> page to verify that the disk cache is enabled (should be true).

WLS 6.0 error 404, 400

Similar Messages

Maybe you are looking for