Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
10 replies Latest Post - ‏2012-06-21T12:45:20Z by SystemAdmin
SystemAdmin
SystemAdmin
30895 Posts
ACCEPTED ANSWER

Pinned topic Error after installing Fixpack 7.0.0.2

‏2012-06-18T19:42:45Z |
I can successfully install FP7002 on my local version of Portal. The install wizard reports that everything was installed successfully, but then when I restart I get this:
Error 404: javax.servlet.UnavailableException: Initialization of one or more services failed.

Here are the errors from the logs:
...
6/18/12 15:01:53:464 EDT 00000013 ServerCache I DYNA1071I: The cache provider "default" is being used.
6/18/12 15:01:53:636 EDT 00000013 DefaultStateM E com.ibm.wps.state.services.DefaultStateManagerService defaultActionProtectionServiceHome() JNDI lookup failed!
javax.naming.NameNotFoundException: The object or context engine does not exist.; Remaining name: 'engine/ActionProtectionService'
at com.ibm.wps.jndi.portal.GenericPortalJNDIContext.lookup(GenericPortalJNDIContext.java:333)
at com.ibm.wps.jndi.portal.GenericPortalJNDIContext.lookup(GenericPortalJNDIContext.java:346)
at com.ibm.wps.jndi.portal.RootPortalJNDIContext.lookupObject(RootPortalJNDIContext.java:155)
at com.ibm.wps.jndi.portal.PortalContext.lookup(PortalContext.java:72)
at com.ibm.wps.jndi.portal.PortalContext.lookup(PortalContext.java:77)
at javax.naming.InitialContext.lookup(InitialContext.java:436)
at com.ibm.wps.state.services.DefaultStateManagerService.defaultActionProtectionServiceHome(DefaultStateManagerService.java:291)
at com.ibm.wps.state.services.JndiStateManagerService.<init>(JndiStateManagerService.java:131)
at com.ibm.wps.services.state.WPStateManagerService.newService(WPStateManagerService.java:128)
at com.ibm.wps.services.state.WPStateManagerService.init(WPStateManagerService.java:115)
at com.ibm.wps.services.Service.init(Service.java:107)
at com.ibm.wps.services.Service.init(Service.java:83)
at com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:363)
at com.ibm.wps.services.ServiceManager.initInternal(ServiceManager.java:261)
at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:173)
at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:115)
at com.ibm.wps.engine.Servlet.init(Servlet.java:252)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:358)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:169)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1809)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:98)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:1038)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:959)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:638)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:436)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:304)
at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:732)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:617)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:376)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1127)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1319)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:610)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:944)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:740)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2051)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:385)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:328)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$300(CompositionUnitMgrImpl.java:113)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:895)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)

6/18/12 15:01:53:667 EDT 00000013 ExtensionPoin I CWXRS0034I: Extension com.ibm.wps.resolver.proxy.PortletAjaxProxyServiceHome connected with Extension Point com.ibm.portal.resolver.proxy.PortletAjaxProxyServiceHome
...
6/18/12 15:01:59:985 EDT 00000013 ServerCache I DYNA1071I: The cache provider "default" is being used.
6/18/12 15:02:00:297 EDT 00000013 Servlet E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.
javax.naming.NameNotFoundException: The object or context engine does not exist.; Remaining name: 'engine/ActionProtectionService'
at com.ibm.wps.jndi.portal.GenericPortalJNDIContext.lookup(GenericPortalJNDIContext.java:333)
at com.ibm.wps.jndi.portal.GenericPortalJNDIContext.lookup(GenericPortalJNDIContext.java:346)
at com.ibm.wps.jndi.portal.RootPortalJNDIContext.lookupObject(RootPortalJNDIContext.java:155)
at com.ibm.wps.jndi.portal.PortalContext.lookup(PortalContext.java:72)
at com.ibm.wps.jndi.portal.PortalContext.lookup(PortalContext.java:77)
at javax.naming.InitialContext.lookup(InitialContext.java:436)
at com.ibm.wps.resolver.service.PocServiceDependencies.<init>(PocServiceDependencies.java:89)
at com.ibm.wps.resolver.service.PortalPocBootstrapServiceDependencies.<init>(PortalPocBootstrapServiceDependencies.java:146)
at com.ibm.wps.resolver.service.PortalPocBootstrapService.init(PortalPocBootstrapService.java:264)
at com.ibm.wps.services.Service.init(Service.java:107)
at com.ibm.wps.resolver.service.PortalPocBootstrapService.init(PortalPocBootstrapService.java:344)
at com.ibm.wps.services.Service.init(Service.java:83)
at com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:363)
at com.ibm.wps.services.ServiceManager.initInternal(ServiceManager.java:261)
at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:173)
at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:115)
at com.ibm.wps.engine.Servlet.init(Servlet.java:252)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:358)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:169)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1809)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:98)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:1038)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:959)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:638)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:436)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:304)
at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:732)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:617)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:376)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1127)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1319)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:610)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:944)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:740)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2051)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:385)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:328)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$300(CompositionUnitMgrImpl.java:113)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:895)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)

6/18/12 15:02:00:344 EDT 00000013 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\IBM\WebSphere\wp_profile\logs\ffdc\WebSphere_Portal_138a138a_12.06.18_15.02.00.3139024422779108355508.txt com.ibm.ws.webcontainer.servlet.ServletInstance.init 259
6/18/12 15:02:00:344 EDT 00000013 extension W com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor createServletWrapper Servlet portal is currently unavailable: Initialization of one or more services failed.
6/18/12 15:02:00:344 EDT 00000013 servlet I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: wps [/wps] federation: Initialization successful.
...
6/18/12 15:02:28:783 EDT 00000013 ExtensionPoin I CWXRS0034I: Extension com.ibm.wps.proxy.connectionFactories connected with Extension Point com.ibm.mm.proxy.common.httpURLConnectionFilterFactory
6/18/12 15:02:28:892 EDT 00000013 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\IBM\WebSphere\wp_profile\logs\ffdc\WebSphere_Portal_138a138a_12.06.18_15.02.28.8614746261708322035038.txt com.ibm.ws.webcontainer.servlet.ServletInstance.init 172
6/18/12 15:02:28:892 EDT 00000013 servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0100E: Uncaught init() exception created by servlet UserProfileRESTServlet in application UserProfileRESTServlet: javax.servlet.ServletException: javax.naming.NameNotFoundException: The object or context resolver does not exist.; Remaining name: 'resolver/PocService'
at com.ibm.portal.rest.userprofile.UserProfileRESTServlet.initIOHandlerImpl(UserProfileRESTServlet.java:211)
at com.ibm.portal.rest.userprofile.UserProfileRESTServlet.init(UserProfileRESTServlet.java:174)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at com.ibm.portal.rest.userprofile.UserProfileRESTServlet.init(UserProfileRESTServlet.java:167)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:358)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:169)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1809)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:98)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:1038)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:959)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:638)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:436)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:304)
at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:732)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:617)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:376)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1127)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1319)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:610)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:944)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:740)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2051)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:385)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:328)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$300(CompositionUnitMgrImpl.java:113)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:895)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Caused by: javax.naming.NameNotFoundException: The object or context resolver does not exist.; Remaining name: 'resolver/PocService'
at com.ibm.wps.jndi.portal.GenericPortalJNDIContext.lookup(GenericPortalJNDIContext.java:333)
at com.ibm.wps.jndi.portal.GenericPortalJNDIContext.lookup(GenericPortalJNDIContext.java:346)
at com.ibm.wps.jndi.portal.RootPortalJNDIContext.lookupObject(RootPortalJNDIContext.java:155)
at com.ibm.wps.jndi.portal.PortalContext.lookup(PortalContext.java:72)
at com.ibm.wps.jndi.portal.PortalContext.lookup(PortalContext.java:77)
at javax.naming.InitialContext.lookup(InitialContext.java:436)
at com.ibm.portal.rest.userprofile.UserProfileRESTServlet.initIOHandlerImpl(UserProfileRESTServlet.java:207)
... 31 more

6/18/12 15:02:28:892 EDT 00000013 extension E com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor createServletWrapper Error occured while preparing the servlet for initialization.
javax.servlet.ServletException: javax.naming.NameNotFoundException: The object or context resolver does not exist.; Remaining name: 'resolver/PocService'
at com.ibm.portal.rest.userprofile.UserProfileRESTServlet.initIOHandlerImpl(UserProfileRESTServlet.java:211)
at com.ibm.portal.rest.userprofile.UserProfileRESTServlet.init(UserProfileRESTServlet.java:174)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at com.ibm.portal.rest.userprofile.UserProfileRESTServlet.init(UserProfileRESTServlet.java:167)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:358)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:169)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1809)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:98)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:1038)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:959)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:638)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:436)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:304)
at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:732)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:617)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:376)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1127)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1319)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:610)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:944)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:740)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2051)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:385)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:328)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$300(CompositionUnitMgrImpl.java:113)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:895)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Caused by: javax.naming.NameNotFoundException: The object or context resolver does not exist.; Remaining name: 'resolver/PocService'
at com.ibm.wps.jndi.portal.GenericPortalJNDIContext.lookup(GenericPortalJNDIContext.java:333)
at com.ibm.wps.jndi.portal.GenericPortalJNDIContext.lookup(GenericPortalJNDIContext.java:346)
at com.ibm.wps.jndi.portal.RootPortalJNDIContext.lookupObject(RootPortalJNDIContext.java:155)
at com.ibm.wps.jndi.portal.PortalContext.lookup(PortalContext.java:72)
at com.ibm.wps.jndi.portal.PortalContext.lookup(PortalContext.java:77)
at javax.naming.InitialContext.lookup(InitialContext.java:436)
at com.ibm.portal.rest.userprofile.UserProfileRESTServlet.initIOHandlerImpl(UserProfileRESTServlet.java:207)
... 31 more

6/18/12 15:02:28:908 EDT 00000013 webcontainer I com.ibm.ws.wswebcontainer.VirtualHost addWebApplication SRVE0250I: Web Module User_Profile_REST_Service has been bound to default_host:80,:443,:10000,:10002,:10039,:10029,*:10032.
...

Any help is greatly appreciated.
I've googled and found some possible fixes, but none of them seem to solve this issue.
This is a stand-alone, local Portal 7 install with WCM. I run Windows 7 Professional and I'm using DB2.
Thank you,
Paul
Updated on 2012-06-21T12:45:20Z at 2012-06-21T12:45:20Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    30895 Posts
    ACCEPTED ANSWER

    Re: Error after installing Fixpack 7.0.0.2

    ‏2012-06-20T05:11:05Z  in response to SystemAdmin
    Hi Paul,

    Have you upgraded the WAS 7 to 7.0.0.21 before upgrading the Portal 7 to Portal 7.0.0.2

    One of the pre-requisite of upgrading Portal is to upgrade WAS to the specified version first.

    I guess the issue is due to the same.

    --Devendra
    • SystemAdmin
      SystemAdmin
      30895 Posts
      ACCEPTED ANSWER

      Re: Error after installing Fixpack 7.0.0.2

      ‏2012-06-20T11:43:42Z  in response to SystemAdmin
      I have updated WAS to 7.0.0.21 so that's not the culprit.
      I really appreciate your input.
      • httweed
        httweed
        510 Posts
        ACCEPTED ANSWER

        Re: Error after installing Fixpack 7.0.0.2

        ‏2012-06-20T12:23:50Z  in response to SystemAdmin
        Was this a binary installation by any chance? The errors you quoted remind me of this technote:

        http://www-304.ibm.com/support/docview.wss?uid=swg21500772

        But that is dependent on a binary install and creating the profile later. It may help to see the full SystemOut.log if you're able to upload it.

        ~HT
        The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM
        • SystemAdmin
          SystemAdmin
          30895 Posts
          ACCEPTED ANSWER

          Re: Error after installing Fixpack 7.0.0.2

          ‏2012-06-20T12:33:29Z  in response to httweed
          httweed, you bring up an excellent point. I've checked this same issue.
          It was not a binary install, but I checked the file nonetheless (attached).
          The SystemOut.log is pretty big, so use this link to download the whole thing:
          http://dl.dropbox.com/u/19757/SystemOut.log
          If it would help, I can do the FP install process again so the log will reflect the errors near the bottom.
          What's so frustrating is that the FP installs perfectly: No errors are reported.
          Then I restart the server and that's when I get SystemOut.log errors and I get that message: Error 404: javax.servlet.UnavailableException: Initialization of one or more services failed.
          thanks for your input.
          • httweed
            httweed
            510 Posts
            ACCEPTED ANSWER

            Re: Error after installing Fixpack 7.0.0.2

            ‏2012-06-20T12:55:45Z  in response to SystemAdmin
            Ok, it is indeed the same exception as what happens with a binary install. The main problem in that scenario is that the Portal binaries are updated to 7002, but the Portal profile is not configured with these updates (i.e. the profile is still on Portal v7000). It looks like the same thing has happened in your environment...obviously not from a binary install but the upgrade skipped over upgrading the profile for some reason.

            Could you also send one more file? I'd like to see what happened during the upgrade:

            PortalServer/version/log/<timestamp>_WP_PTF_7002_wp.ptf.config_install

            where <timestamp> is in the format 20120618_xxxxxx (year, month, day _ time of day). Or if it's easier for you, you can zip the PortalServer/version/log directory and upload that. I think for now just need to see that one log though.

            ~HT
            The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM
            • SystemAdmin
              SystemAdmin
              30895 Posts
              ACCEPTED ANSWER

              Re: Error after installing Fixpack 7.0.0.2

              ‏2012-06-20T13:32:06Z  in response to httweed
              Your idea definitely fits with the behavior I'm seeing.
              Her's the log file you need.
              Thanks a million for your help. I've been hitting my head against this problem for a couple days.
              • httweed
                httweed
                510 Posts
                ACCEPTED ANSWER

                Re: Error after installing Fixpack 7.0.0.2

                ‏2012-06-20T17:12:32Z  in response to SystemAdmin
                Thanks for sending that. That is indeed what has happened...the profile wasn't touched during the upgrade. This error is why:

                2012-06-18T14:50:55-04:00 Result: StdErr: 'findstr' is not recognized as an internal or external command,
                2012-06-18T14:50:55-04:00 Result: StdErr: operable program or batch file.

                A batch file is executed that ultimately calls the script to update the profile, and within the batch file we have this command:

                findstr "WpsInstallLocation=" "%WP_PROFILE%\ConfigEngine\properties\wkplc.properties"

                Your environment doesn't seem to know what "findstr" is, so it throws that exception. Unfortunately, a failure at this point just tells the update installer to skip the profile and nothing more.

                To fix the findstr issue with Windows, can you check to see if the <Windows>/system32 path is in your PATH environment variable? Provided that it is not, this is what I think you should do:

                1. Uninstall the fixpack (or if you have an image you can revert to, do that....doesn't matter).
                2. Open a command window and just type this and press enter:

                findstr

                Presumably it will come back saying it's not a recognized command.

                3. Add the system32 environment variable to your Path and restart the computer.

                4. Open a command window again and type the same command and press enter:

                findstr

                It should come back with something like this:

                C:\Users\Administrator>findstr
                FINDSTR: Bad command line

                which means that it should be ok.

                5. Reinstall the fixpack.
                It'll be important that we do not fix the findstr problem until AFTER we uninstall the fixpack. If we fix it before and then uninstall the fixpack, the uninstall process will suddenly realize there is a profile there and try to downgrade a profile that was never upgraded in the first place, and it will fail.

                ~HT
                The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM
                • SystemAdmin
                  SystemAdmin
                  30895 Posts
                  ACCEPTED ANSWER

                  Re: Error after installing Fixpack 7.0.0.2

                  ‏2012-06-20T21:21:33Z  in response to httweed
                  Wow!
                  That worked perfectly.
                  A thousand "thank you's"
                  -paul
                  • httweed
                    httweed
                    510 Posts
                    ACCEPTED ANSWER

                    Re: Error after installing Fixpack 7.0.0.2

                    ‏2012-06-20T21:57:13Z  in response to SystemAdmin
                    Excellent, so just to confirm the solution, in case others have this problem, you did not have the PATH set for system32?

                    ~HT
                    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM
                    • SystemAdmin
                      SystemAdmin
                      30895 Posts
                      ACCEPTED ANSWER

                      Re: Error after installing Fixpack 7.0.0.2

                      ‏2012-06-21T12:45:20Z  in response to httweed
                      Correct: The PATH was not set for Windows/System32 so the Update Installer couldn't execute the findstr command as you pointed out.
                      Thanks again for all your help, I was totally baffled by this.
                      -p