WebSphere_Server gives exceptions when started after changes withinportlet factory - Websphere

This is a discussion on WebSphere_Server gives exceptions when started after changes withinportlet factory - Websphere ; Hi, I am developing portlets using WebSphere Portlet Factory (in RSA 7). 2 days ago I accidentally changed something in the server settings on one of my projects (through RSA). But since then, the WebSphere_Portal server gives exceptions everytime im ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: WebSphere_Server gives exceptions when started after changes withinportlet factory

  1. WebSphere_Server gives exceptions when started after changes withinportlet factory

    Hi, I am developing portlets using WebSphere Portlet Factory (in RSA 7). 2 days ago I accidentally changed something in the server settings on one of my projects (through RSA). But since then, the WebSphere_Portal server gives exceptions everytime im starting it. I check the admin console for virtual hosts settings (because thats what all the solutions from the internet pointed me to look at) but they are all fine.
    If I try to access the main page in Firefox (http://localhost:10038/wps/portal)
    it gives me:
    SRVE0017W: A WebGroup/Virtual Host to handle /wps/portal has not been defined.

    And from the command prompt startserver I get exceptions like:

    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.
    java:85)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.
    java:58)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAcces
    sorImpl.java:60)
    at java.lang.reflect.Method.invoke(Method.java:391)
    at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.jav a:219)
    at java.lang.Thread.run(Thread.java:570)
    Caused by: com.ibm.websphere.management.exception.AdminExcept ion: ADMU7704E: Fai
    led while trying to start the Windows Service associated with server: WebSphere_
    Portal;
    probable error executing WASService.exe: com.ibm.ws.management.tools.ProblemInWA
    SServiceException: ADMU7711E: Unexpected exception associated with WASService.ex
    e: exitCode = -1 during processing of server with name: WebSphere_Portal
    at com.ibm.ws.management.tools.WindowsService.doWASSe rviceAction(Windows
    Service.java:380)
    at com.ibm.ws.management.tools.WsServerLauncher.execW ithWinService(WsSer
    verLauncher.java:157)
    at com.ibm.ws.management.tools.WsServerController.exe cuteUtilityOnWindow
    s(WsServerController.java:128)
    at com.ibm.ws.management.tools.WsServerLauncher.main( WsServerLauncher.ja
    va:115)
    ... 7 more
    ADMU3000I: Server WebSphere_Portal open for e-business; process id is 2100

    So the server still starts, but all the enterprise applications do not, and If i try to manually start them through the admin console, it gives me an error message like this one:
    "Application_Catalog_PA_dlvzaci can not be started because it is installed on a different server."

    I attached a file containing the detailed exception messages from the SystemOut.log of PortalServer

    Does anybody have a solution for this? pleeeease help me
    Thanks

  2. Re: WebSphere_Server gives exceptions when started after changeswithin portlet factory

    Did you ever figure out what was going wrong here? I am encountering the same error after installing my own portal + portlet application on the "WebSphere_Portal" server instance. I'm thinking that I didn't follow the proper instructions for installing the app, will try that over again, but if you have any advice please let me know.

    Thanks!
    Cheryl

  3. Re: WebSphere_Server gives exceptions when started after changeswithin portlet factory

    I didn't get any proper solution. I have tried tracing all the errors and exceptions on the log files, but didn't really come up with a solution. So I uninstall and re-installed WAS and WPS all over again and then everything went back to normal. However, when I put the startserver as windows service, it was starting again with the same errors. So my suggestion would be (if you are starting the server as windows service), to try to remove the services from windows service list, and try to start them manually. If that don't help, Im afraid you might have to to go down the same road Or maybe get help from the experts

    cheers,

    ikram

+ Reply to Thread