IIS Forword problem from IIS 6.0 to weblogic 12c
I am using IIS 6.0 in windows 2003. I have set the IIS forward to weblogic 12c in 32bits and 64bits windows 2008 R2. But it does not work when call the Action class such as "index.do" , call JSP page is work property. I want to know whether the iisproxy.dll or iisforward.dll is required to upgrade or not. Thank
I am using IIS 6.0 in windows 2003. I have set the IIS forward to weblogic 12c in 32bits and 64bits windows 2008 R2. But it does not work when call the Action class such as "index.do" , call JSP page is work property. I want to know whether the iisproxy.dll or iisforward.dll is required to upgrade or not. Thank
Similar Messages
-
Problem in installing GoldenGate Director on weblogic 12c
hello friends,
we have a server with weblogic 12c and a basic domain namely "base_domain" on it.(i have no earlier experience about weblogic).its path is "D:\Oracle\Middleware_HOME\wlserver_12.1"
i can start its AdminServer and we can login to its console.
now i want to install GoldenGate Director Server.but in installing process when i set Weblogic location it gives me error :
"Please Select a valid weblogic install Directory"
i tried all of these paths :
"D:\Oracle\Middleware_HOME\wlserver_12.1"
"D:\Oracle\Middleware_HOME"
"D:\Oracle"
but the error remains yet.
i installed weblogic on another machine but nothing changed.
another thin is that i checked all places that oracle documents tells that should be updated
i mean :
1 Update the registry.xml file in Weblogic home directory to point to the
correct WebLogic Server home directory.
2 Update all of the scripts under %WLS_SERVER_HOME%/server/bin and %WLS_
SERVER%/common/bin to point to the correct WebLogic Server home directory.
3 Update the .product.properties file under %WLS_SERVER_HOME% to point to the
correct WebLogic Server home directory.
1 & 2 are correct (i think) but i couldn't find third one "product.properties"
please help me.
Whats the problem?
weblogic Servers : Windows Server 2008 64-bit SP2 and Windows Seven Ultimate 64bit
Weblogic version : oepe-indigo-installer-12.1.1.0.1.201203120349-12.1.1-win32
GoldenGate Director : gg-director-serversetup_win_v11_1_1_1_0_001You should specify the middle-ware home direction.
The error normally caused by the wrong version installed, which doesn’t have the correct registry.xml in MW_HOME. I met this problem in the past which is because I installed a dev version of WLS in zip file.
After I install the installable version( I think it is the same version you used: oepe-indigo-installer-12.1.1.0.1.201203120349-12.1.1-win32.exe of WLS, it works fine. -
Error deploying jpa from oepe tutorial example on Weblogic 12c server
I am having the next error trying to deploy jpa in to Weblogic 12c server from the oepe tutorial example at http://www.oracle.com/webfolder/technetwork/tutorials/obe/jdev/obe11jdev/11/eclipse_intro/eclipse_intro.html. The "I---------I" markups are below, "bean.Hello", "hello" and "response.jsp". I've tried to find a solution on the web but nothing. I'll apreciate any help. thanks.
greeting.jsp:1:1: Needed class "bean.Hello" is not found.
^
greeting.jsp:5:44: The bean type "bean.Hello" was not found.
<jsp:useBean id="hello" scope="page" class="bean.Hello"></jsp:useBean>
I----------I
greeting.jsp:6:23: This bean name does not exist.
<jsp:setProperty name="hello" property="*" />
I-----I
greeting.jsp:34:18: Error in "C:\Users\Andres Tobar\workspace\DemoEARWeb\WebContent\pages\response.jsp" at line 13: This bean does not exist.
<%@ include file="response.jsp" %>
I------------II have started again all the tutorial from the begining, trying to not miss any configuration setting even the ones displayed on pictures, finding that the tutorial example now works. I think the first time i have tryed it i missed to activate the anotations facet in project properties because this configuration step is not explained in the tutorial unless you take a close look into the tutorial images. Probably that was the cause of the mentioned error, not so sure, but the tutorial example really works.
-
Problems when deploying web service onto Weblogic 12c
Hello everybody:
Created a web service with MyEclipse 8.5; when deploying onto Weblogic I'm facing this next problem:
Nov 3, 2012 7:44:40 AM com.sun.xml.ws.transport.http.servlet.WSServletDelegate destroy
INFO: WSSERVLET15: JAX-WS servlet destroyed
Nov 3, 2012 7:44:40 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextDestroyed
INFO: WSSERVLET13: JAX-WS context listener destroyed
<Nov 3, 2012 7:44:40 AM CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1351950260963' for task '0'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
... 54 more
weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
... 54 more
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
Truncated. see log file for complete stacktrace
>
<Nov 3, 2012 7:44:40 AM CST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application '_appsdir_WSConsultaTrabajadorCurp_dir'.>
<Nov 3, 2012 7:44:40 AM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application '_appsdir_WSConsultaTrabajadorCurp_dir'.>
<Nov 3, 2012 7:44:40 AM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
... 54 more
:com.sun.xml.ws.policy.PolicyException:[failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
Truncated. see log file for complete stacktrace
It seems it is looking for the file; it is in the specified path so I cannot figure out what's wrong. No reference about the problem found over internet. Same web service deploys without problem on Tomcat, but by requirement, needed to deploy onto Weblogic 10g or above. Any help?
Thanks in advance.how did you configured this ws-policy file?
are you using any @Policy annotations?
Regards,
Sunil P -
Fetch error and jaxb problem in weblogic 12c
Hi,
I have a problem with running my webService in Weblogic 12c. The response of the webService is an entity which has an OneToMany relationship. After executing the service, its response could not be generated. I think there is a problem during MOXy’s unmarshalling operation of response entity (I haven’t had any problem in weblogic 11, because it don’t use MOXy ).
What do you think about this problem and solution?
Regards
Edited by: Elham on May 27, 2012 12:51 AMNote that WebLogic 12c endorses JavaEE6.
Look ups and how JNDI works is explained in the JavaEE6 tutorial: http://docs.oracle.com/javaee/6/tutorial/doc/gipjf.html -
Problems with IIS proxy to cluster
We are using WebLogic 6.1 with two managed servers in a cluster. Our IIS server
is running IIS 4 and is set up to proxy to the cluster by IP addresses. When
one server goes down(as in a hardware failure or shut down), the other server's
queue loads up with unprocessed requests causing our web application to "freeze".
No errors are logged anywhere. The only way to free up the WL server (and stop
the queue from growing) is to reboot both the application server (to clear the
queu)AND the IIS web server(to stop the requests). Is there a known problem with
the WL IIS plug-in DLL that could cause these errant requests? or.. Does this
point to a specific error on our IIS server? or.. Is there a bad setting somewhere
that can be changed to prevent this? Please Advise!
Hello,
From this it looks like you may be able to use PathPrepend to jimmy your URLs:
PathPrepend : String that the plug-in prepends to the beginning of the original URL, after PathTrim is trimmed and before the request is forwarded to WebLogic Server.
I would suggest it may be a good idea to have a seperate webserver for your production domain. In most places I have worked in every platform is configuered with its own resources e.g staging server has its own webserver and db. This affords the people that use those envrionments greater isolation. -
I am using the latest version of the IIS plugin for Weblogic (build: Apr 14 2002
17:53:13)
It seems that the ISAPI Filter (iisforward.dll) does not forward all http POSTs
- however it does seem to work fine for http GET's.
We have configured the plugin (you will see the attached debug dump) to forward
all calls on "/weblogic". If we perform http GET's on such a URL (using IE) everything
works fine - and the call is routed to Weblogic.
When we make a SOAP call using our C++ client, (a http POST) through the IIS plugin
we get a 405 error. If we artificially add the ".wlforward" extension on the context
URL (in our C++ client ) then it is forwarded correctly to weblogic by the Application
Extension (iisproxy.dll) - so the problem lies with the ISAPI filter. Also, if
we remove the ISAPI filter from IIS, we get the same 405 error - which confirms
that the ISAPI filter is not catching the POST's.
More puzzling, however, is that the SOAP requests from our Java SOAP client (using
WLS SOAP) works fine.
The problem must have something to do with the difference in structure of the
POSTS.
Normally, I would attach the logs/config in a zip file - but that seems broken
at the moment. Instead they are all pasted in below.....
-Nick
Successful POST http header:
POST /weblogic/webservice/BondInstrumentService HTTP/1.0
Host: localhost:8080
Connection: Keep-Alive
Content-Length: 1965
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
Authorization: Basic c3lzdGVtOnBhc3N3b3Jk
UNSuccessful POST http header:
POST /weblogic/webservice/BondInstrumentService HTTP/1.0
SOAPAction: ""
Content-Type: text/xml
Connection: close
Content-Length: 1670
IIS 405 Response:
HTTP/1.1 405 Method not allowed
Server: Microsoft-IIS/5.0
Date: Thu, 25 Jul 2002 14:28:52 GMT
Allow: OPTIONS, TRACE, GET, HEAD
Content-Length: 3126
Content-Type: text/html
IIS Plugin Config:
Properties loaded from path: 'D:\Inetpub\WeblogicPlugin\iisproxy.ini'
Query String: '__WebLogicBridgeConfig'
General Server List:
Host: 'localhost' Port: 7001 Status: OK
ConnectRetrySecs: '2'
ConnectTimeoutSecs: '10'
CookieName: 'JSESSIONID'
Debug: '12'
DebugConfigInfo: 'ON'
DefaultFileName: ''
DynamicServerList: 'ON'
ErrorPage: ''
FileCaching: 'ON'
HungServerRecoverSecs: '300'
Idempotent: 'OFF'
KeepAliveEnabled: 'ON'
KeepAliveSecs: '30'
PathPrepend: ''
PathTrim: '/weblogic'
MaxSkips: '10'
MaxPostSize: '-1'
SecureProxy: 'OFF'
WLLogFile: 'D:\Inetpub\WeblogicPlugin\iisPlugin.log'
WLProxySSL: 'OFF'
Runtime statistics:
requests: 1
successful requests: 1
Exception objects created: 0
Exception Objects deleted: 0
URL Objects created: 1
URL Objects deleted: 1
connections recycled: 0
UNKNOWN_ERROR_CODE exceptions: 0
CONNECTION_REFUSED exceptions: 0
CONNECTION_TIMEOUT exceptions: 0
READ_ERROR exceptions: 0
WRITE_ERROR exceptions: 0
READ_TIMEOUT exceptions: 0
WRITE_TIMEOUT exceptions: 0
UNKNOWN_HOST exceptions: 0
NO_RESOURCES exceptions: 0
PROTOCOL_ERROR exceptions: 0
CONFIG_ERROR exceptions: 0
FAILOVER_REQUIRED exceptions: 0
Build date/time: Apr 14 2002 17:53:13Doh. :< I hope you can get someone here from the BEA guys/gals to help out.
I'm outside of my league at this point. Sorry about that. Good luck.
"Nick Minutello" <[email protected]> wrote
in message news:[email protected]...
>
>
Thanks.
Sadly, my IIS configuration is correct. The plugin seems to work fine if Ijust
use my browser (http GET) for either forward-by-extension (*.jsp) orforward-by-path
(/weblogic/*).
However, there seems to be a problem when I use SOAP (http POST). For somereason,
when I use my C++ SOAP client (using WASP), then the ISAPI filter (the onethat
generates the .wlforward on the URL) doesnt modify the URL - hence the403...
If I use my java client.... everything is fine. Comparing the two httppackets,
I dont see anything obviously wrong - but something is making the WLSplugin choke.
>
Cheers,
Nick
"PHenry" <[RemoveBeforeSending][email protected]> wrote:
Howdy. I had a similar problem. I'm not a BEA support person, but maybe
I
might be able to help. If not, at least someone's listening. :>
Did you add the .jsp AND the .wlforward in the path redirection under
your
web app in IIS? I read the instructions thoroughly (or so I thought),
and I
wasn't able to get the POST to work. :< But as I reread the
instructions,
I
had put in the .jsp (is it under Home Directory, Configuration I think?),
and I put in the ISAPI dll, but I didn't put in the .wlforward (in with
the
..jsp). Once I did that, and restarted the box, all was good! :>
That might help. And if not, at least one of the BEA people have one
less
thing to try. Good luck.
"Nick Minutello" <[email protected]>
wrote
in message news:[email protected]...
I am using the latest version of the IIS plugin for Weblogic (build:Apr
14 2002
17:53:13)
It seems that the ISAPI Filter (iisforward.dll) does not forward allhttp
POSTs
- however it does seem to work fine for http GET's.
We have configured the plugin (you will see the attached debug dump)to
forward
all calls on "/weblogic". If we perform http GET's on such a URL (usingIE) everything
works fine - and the call is routed to Weblogic.
When we make a SOAP call using our C++ client, (a http POST) throughthe
IIS plugin
we get a 405 error. If we artificially add the ".wlforward" extensionon
the context
URL (in our C++ client ) then it is forwarded correctly to weblogicby the
Application
Extension (iisproxy.dll) - so the problem lies with the ISAPI filter.Also, if
we remove the ISAPI filter from IIS, we get the same 405 error -which
confirms
that the ISAPI filter is not catching the POST's.
More puzzling, however, is that the SOAP requests from our Java SOAPclient (using
WLS SOAP) works fine.
The problem must have something to do with the difference in structureof
the
POSTS.
Normally, I would attach the logs/config in a zip file - but that seemsbroken
at the moment. Instead they are all pasted in below.....
-Nick
Successful POST http header:
POST /weblogic/webservice/BondInstrumentService HTTP/1.0
Host: localhost:8080
Connection: Keep-Alive
Content-Length: 1965
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
Authorization: Basic c3lzdGVtOnBhc3N3b3Jk
UNSuccessful POST http header:
POST /weblogic/webservice/BondInstrumentService HTTP/1.0
SOAPAction: ""
Content-Type: text/xml
Connection: close
Content-Length: 1670
IIS 405 Response:
HTTP/1.1 405 Method not allowed
Server: Microsoft-IIS/5.0
Date: Thu, 25 Jul 2002 14:28:52 GMT
Allow: OPTIONS, TRACE, GET, HEAD
Content-Length: 3126
Content-Type: text/html
IIS Plugin Config:
Properties loaded from path: 'D:\Inetpub\WeblogicPlugin\iisproxy.ini'
Query String: '__WebLogicBridgeConfig'
General Server List:
Host: 'localhost' Port: 7001 Status: OK
ConnectRetrySecs: '2'
ConnectTimeoutSecs: '10'
CookieName: 'JSESSIONID'
Debug: '12'
DebugConfigInfo: 'ON'
DefaultFileName: ''
DynamicServerList: 'ON'
ErrorPage: ''
FileCaching: 'ON'
HungServerRecoverSecs: '300'
Idempotent: 'OFF'
KeepAliveEnabled: 'ON'
KeepAliveSecs: '30'
PathPrepend: ''
PathTrim: '/weblogic'
MaxSkips: '10'
MaxPostSize: '-1'
SecureProxy: 'OFF'
WLLogFile: 'D:\Inetpub\WeblogicPlugin\iisPlugin.log'
WLProxySSL: 'OFF'
Runtime statistics:
requests: 1
successful requests: 1
Exception objects created: 0
Exception Objects deleted: 0
URL Objects created: 1
URL Objects deleted: 1
connections recycled: 0
UNKNOWN_ERROR_CODE exceptions: 0
CONNECTION_REFUSED exceptions: 0
CONNECTION_TIMEOUT exceptions: 0
READ_ERROR exceptions: 0
WRITE_ERROR exceptions: 0
READ_TIMEOUT exceptions: 0
WRITE_TIMEOUT exceptions: 0
UNKNOWN_HOST exceptions: 0
NO_RESOURCES exceptions: 0
PROTOCOL_ERROR exceptions: 0
CONFIG_ERROR exceptions: 0
FAILOVER_REQUIRED exceptions: 0
Build date/time: Apr 14 2002 17:53:13 -
Strange action from IIS, when call web application
When type http://localhos:8090/sendsms.aspx called smssender.aspx and work fine, when instead localhost write ip address for example
http://192.168.10.10:8090/sendsms.aspx called smssender.aspx but browser write clients IP address in the screen.
No Error, No notification only one string for example:
192.168.10.14
web site hosting in local IIS.
what problem?
Best RegardsHi Paata,
Please post in ASP.NET forums, you could reveive more help from web developers there.
Thanks!
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Accessing VirtualBox host drive from IIS guest OS
Hi there,
I have a setup with Windows 7 as the host OS that is running VirtualBox (4.2.18). The guest I am running is using Windows Server 2012 as the OS. The guest OS has its own domain, completely separate from the host.
For development purposes I want to configure a dev web app that pulls its files from the host and runs them in an IIS process within the guest. How do I proceed?
I really would like to use the VirtualBox's UNC path \\vboxsrv\d_drive but I am getting the following error from IIS:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
One solution as a workaround that I have found is creating a new shared drive, e.g. d$ on the host, add an account (e.g. "virtualbox") on host and guest, and configure this account as the apppool-account and as the connection-account with cleartext
credentials to the physical path of the webapp. This is a lot of work. With this setup I experience delays of 5 seconds, that I guess are due to the authentication that is always taking its time.Hi,
It seems like that the user account you're using for your app pool doesn't have rights to the web site directory, so it can't read config from there. Check the app pool and see what user it is configured to run as. Check the directory and see
if that user has appropriate rights to it. While you're at it, check the event log and see if IIS logged any more detailed diagnostic information there.
Please post in the IIS forum for further analysis:
http://forums.iis.net/
Regards,
Yan Li
Cataleya Li
TechNet Community Support -
Could not browse pages from IIS after re-installation of Oracle client
Hi all,
Unfortunately, I hit a issue today in the morning. I could not browse pages from IIS after I re-installed my oracle client on my machine. Below is the error massage from browser.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Could not load file or assembly 'Oracle.Web, Version=2.111.6.20, Culture=neutral, PublicKeyToken=89b483f429c47342' or one of its dependencies. The system cannot find the file specified.
Source Error:
Line 174: <healthMonitoring>
Line 175: <providers>
Line 176: <add name="OracleWebEventProvider" type="Oracle.Web.Management.OracleWebEventProvider, Oracle.Web, Version=2.111.6.20, Culture=neutral, PublicKeyToken=89b483f429c47342" connectionStringName="OraAspNetConString" buffer="true" bufferMode="OracleNotification" />
Line 177: </providers>
Line 178: </healthMonitoring>
Source File: c:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config Line: 176
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Oracle.Web, Version=2.111.6.20, Culture=neutral, PublicKeyToken=89b483f429c47342' could not be loaded.
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
When I comment a line for OracleWebEventProvider in health monitoring providers in machine.config, it works fine for me. But, Im wondering what went wrong during re-installation and how do I rectify this issue with out a temporary workaround.
Please let me know your suggestions in this regards and thanks for the help in advance.
Regards,
KumarAfter I ran the "uninstaller" on the Oracle CD .. there were services still in existance, however, once I deleted the c:/Oracle folder, they were gone. I also re-booted the pc and double-checked, before I tried re-installing.
Thanks !
Tammy
Hi,
look into services, is there any services is still exist or running with the same name.
or give any other SID which you have given previously.
Yogi
[email protected] -
SP 2010-After adding user from IIS is not found in central admin
Hi Experts,
I am trying to configure my SP 2010 with Form Based Authentication.
After configuring WebSite, STS and Central Admin I added the user from IIS , But not able to found from central admin in Form Authentication.
I checked in database the user is added.
I followed the below blog .
http://jasear.wordpress.com/2012/03/16/sharepoint-2010-setting-up-form-based-authentication-fba-using-asp-net-sql-membership-provider/
Can experts help me how to get the added user to central admin.
Thanks
AshisKI was finally able to get the FBA working. After many failed attempts, I knew there was a configuration issue which was causing the error.
I provided connection string and provider details at 4 places, instead of the 3 mentioned in various blogs around ->
1. Sharepoint Central Admin
2. Sharepoint Web Services
3. SecurityTokenServiceApplication
4. And finally the web application itself.
The connection string for 2nd and 3rd will remain same however, provider details need to be added.
After completing this step, I was able to login using Form Based Authentication without an issue.
AshisK -
No Authentication required, if the req. from IIS
Hello,
I'm using third party authentication tool and it requires, IIS to run as
webserver. So I use IIS +WL6.1.
The authentication will be done, before the request is forwarded to WL.
So I don't want WL to pop-up a login dialog box, when I'm using IIS+WL. But in
my web.xml, I use security-constraint to protect my resource, if I'm using just
WL6.1. How can I tell WL that if the request is from IIS, then don't pop-up the
login box (Basic authentication) and use it only when I'm using just WL.
thanks for your time & help.
VijayHi Utpal,
Thanks. But I've certain concerns.
If the IIS & WL are running in the same box, then I can check with port # &
ip address in combn. But still, I don't want to hardcode the ip address, so I'm
thinking, I can make it as a configurable. In this case, it will be easy to break.
If the administrator,set the port # of WL in the configuration as the port where
IIS runs (either by mistake or intentionally), then in my connection filter, if
I check for this port, it will be ok and let in (which it shouldn't be).
Thanks.
Vijay
"Utpal" <[email protected]> wrote:
we have ConnectionEvent,how can I know whether the requestis from IIS or any other webserverWell, if you know ip address of the box where IIS is running, using
connection
filter you can isolate the requests that come from the IIS, right ?
Based on that decision, you could right the code which handles the request
as you
want.
-utpal -
Hello
Please help me about web.config setting on IIS8.5. I am using first time IIS8.5. We use always IIS 7 or 7.5 max. and I have tried setting of both. But nothing is worked for me.
ThanksHello,
You might also ask in Microsoft's IIS forums:
http://forums.iis.net/
As Microsoft's IIS forums are on a different platform, we cannot move the question for you.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}}) -
Why won't IIS 5.0 let through gzip data to WebLogic?
I have set up a filter in java to handle gzip and deployed to WebLogic. This works great when I call the app server directly. When i try to go through the web server it hangs. It ends up getting to the app server but with 0 bytes of data. I see this with a 500 error in the weblogic access.log.
Does anyone know how to get the gzip data through IIS but not using IIS compression.
All help greatly appreciated,
Thanks.This is a common problem. Something was wrong with the LR 5.5 update process and Adobe put up a Help page showing a process to fix it. When it happened to me I had to do the last solution, of clearing the SLCache folder—on my Windows 8.1 PC.
https://helpx.adobe.com/lightroom/kb/unable-launch-lightroom-55.html -
IIS 6 Metabase and IIS 6 configuration compatibility install
I am trying to install IIS 6 Metabase and IIS 6 configuration compatibility to my Windows 7 ultimate machine. the install fails, and the following log entry is created
Update IIS-Metabase of package IIS-WebServer-Package failed to be turned on. Status: 0x80070bc9.Install the IIS 6.0 Management Compatibility Components in Windows Server 2008 R2 or in Windows Server by using the Server Manager tool
Click Start, click Administrative Tools, and then click Server Manager.
In the navigation pane, expand Roles, right-click Web Server (IIS), and then click Add Role Services.
In the Select Role Services pane, scroll down to IIS 6 Management Compatibility.
Click to select the IIS 6 Metabase Compatibility and IIS 6 Management Console check boxes.
In the Select Role Services pane, click Next, and then click Install at the Confirm Installations Selectionspane.
Click Close to exit the Add Role Services wizard.
Install the IIS 6.0 Management Compatibility Components in Windows 7 or in Windows Vista from Control Panel
Click Start, click Control Panel, click Programs and Features, and then click Turn Windows features on or off.
Open Internet Information Services.
Open Web Management Tools.
Open IIS 6.0 Management Compatibility.
Select the check boxes for IIS 6 Metabase and IIS 6 configuration compatibility and IIS 6 Management Console.
Click OK.
source: http://technet.microsoft.com/en-us/library/bb397374(EXCHG.80).aspx
Maybe you are looking for
-
Next Generation in Monitor or PDA screens...
OK, so I'm sitting here on my iMac, and reading this, and reading that, we do a lot more reading then we used too, and we read more on electronic screens, then plain old school paper and print. SO the financial pundents hammer apple constantly for n
-
Ribbon on document library does not load
I am logged on as a Site Collection Admin and using IE 9.0.8112.16421 on Windows 7 SP1 and when I go to a list, I get "Loading..." and I have closed out, restarted, and tried to log on as a different user, when I do, it WORKS! I set that user to be a
-
Building custom components in jsf 1.2
HI all i am having custom component which has one text field and button together which is extended from a panelgroup component and adding text field and button and child component to this. in jsf1.1 i am not getting any error, but jsf 1.2 i am gettin
-
Engineer question: The limitations of auto-align
I have a question about the capability limitations of auto-align that I'm hoping one of the Photoshop engineers - or perhaps another qualified member of the community - might be able to field. I've been trying, unsuccessfully, to use PS CS5 to precis
-
TWO INVOICE CREATED AGAINST ONE DELIVERY T-CODE VF01
Hi, I got strange scenario that against one delivery containing multiple line items two different invoice created during normal sales process , First invoice with some line item and another invoice contains rest of the item. Both the invoices is of