Problem: When PeopleSoft is launched (http://appswindows.domainname.com:8000/psp/fsdmo/?cmd=login&languageCd=ENG&), the PeopleSoft login page appears and the following error is displayed:
CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS, BECAUSE OF: bea.jolt.ServiceException: Invalid Session
Solution: Change the value of the psserver variable in the configuration.properties file from machine name to IP address.
Tried the following:
1. On appswindows, checked directory E:PT849FS900appservFSDMOLOGS. Checked files MONITORSRV_0823.LOG, TUXLOG.082311, APPSRV_0823.LOG, but no errors noted.
2. In PSADMIN.EXE, stopped FSDMO application server domain, cleared cache (E:PT849FS900appservFSDMOCACHE), then restarted FSDMO application server domain.
3. Stop and relaunched startPIA.cmd:
E:>cd PT849FS900webservfsdmobin E:PT849FS900webservfsdmobin>dir Volume in drive E has no label. Volume Serial Number is C4CF-D1B6 Directory of E:PT849FS900webservfsdmobin 08/22/2011 02:22 PM <DIR> . 08/22/2011 02:22 PM <DIR> .. 08/22/2011 02:23 PM 1,398 BatchProjectExecutor.bat 08/22/2011 02:22 PM 3,207 createThreadDump.cmd 08/22/2011 02:23 PM 1,394 HashKeyGenerator.bat 08/22/2011 02:22 PM 9,616 installNTservicePIA.cmd 08/22/2011 02:23 PM 1,391 MessageExport.bat 08/22/2011 02:22 PM 1,280 PSCipher.bat 08/22/2011 02:23 PM 29,092 pskeymanager.cmd 08/22/2011 02:23 PM 7,347 redeployWSRP.cmd 08/22/2011 02:22 PM 12,126 setEnv.cmd 08/22/2011 02:22 PM 2,826 singleserverStatus.cmd 08/22/2011 02:22 PM 6,689 startPIA.cmd 08/22/2011 02:23 PM 3,274 StartSendMaster.bat 08/22/2011 02:22 PM 3,728 stopPIA.cmd 08/22/2011 02:23 PM 1,689 tcpmon.cmd 08/22/2011 02:22 PM 1,886 uninstallNTServicePIA.cmd 08/22/2011 02:23 PM 4,791 wssTest.cmd 16 File(s) 91,734 bytes 2 Dir(s) 6,075,355,136 bytes free E:PT849FS900webservfsdmobin>startPIA.cmd Attempting to start WebLogic Server 'PIA' starting weblogic with Java version: java version "1.5.0_04" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05) Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode) java -server -Xms256m -Xmx256m -XX:MaxPermSize=128m -Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform -Djava.util.logging.config.file=E:PT849FS900webservfsdmoapplicationspeoplesoftlogging.properties -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Dweblogic.Name=PIA -Dps_vault=E:PT849FS900webservfsdmopsvault -Djavax.net.ssl.trustStore=E:/PT849/FS900webservfsdmokeystorepskey -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=E:beaWEBLOG~1serverlibweblogic.policy -Dssl.debug=false -Dps_home=E:/PT849/FS900 weblogic.Server <Aug 23, 2011 2:35:32 PM GMT-04:00> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath: E:PT849FS900webservfsdmolibendorsedxalan.jar;E:PT849FS900webservfsdmolibpluto-1.0.1.jar;E:PT849FS900webservfsdmolibportlet-api-1.0.jar;E:PT849FS900webservfsdmolibps_patch.jar;E:beaweblogic92platformlibp13np13n-schemas.jar;E:beaweblogic92platformlibp13np13n_common.jar;E:beaweblogic92platformlibp13np13n_system.jar;E:beaweblogic92platformlibwlpnetuix_common.jar;E:beaweblogic92platformlibwlpnetuix_schemas.jar;E:beaweblogic92platformlibwlpnetuix_system.jar;E:beaweblogic92platformlibwlpwsrp-common.jar> <Aug 23, 2011 2:35:33 PM GMT-04:00> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0_04-b05 from Sun Microsystems Inc.> <Aug 23, 2011 2:35:34 PM GMT-04:00> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 2006 783464 > <Aug 23, 2011 2:35:37 PM GMT-04:00> <Info> <WebLogicServer> <BEA-000215> <Loaded License : E:bealicense.bea> <Aug 23, 2011 2:35:37 PM GMT-04:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> <Aug 23, 2011 2:35:37 PM GMT-04:00> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool> <Aug 23, 2011 2:35:37 PM GMT-04:00> <Notice> <Log Management> <BEA-170019> <The server log file E:PT849FS900webservfsdmoserversPIAlogsPIA_weblogic.log is opened. All server side log events will be written to this file.> <Aug 23, 2011 2:35:40 PM GMT-04:00> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.> <Aug 23, 2011 2:35:43 PM GMT-04:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY> <Aug 23, 2011 2:35:43 PM GMT-04:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> <Aug 23, 2011 2:36:21 PM GMT-04:00> <Notice> <Log Management> <BEA-170027> <The server initialized the domain log broadcaster successfully. Log messages will now be broadcasted to the domain log.> <Aug 23, 2011 2:36:21 PM GMT-04:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN> <Aug 23, 2011 2:36:21 PM GMT-04:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[4]" is now listening on 127.0.0.1:8500 for protocols iiops, t3s, ldaps, https.> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Warning> <Server> <BEA-002611> <Hostname "appswindows.domainname.com", maps to multiple IP addresses: x.x.x.x, 192.168.161.1, 192.168.137.1, 169.254.95.175> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 192.168.137.1:8000 for protocols iiop, t3, ldap, http.> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Warning> <Server> <BEA-002611> <Hostname "appswindows.domainname.COM", maps to multiple IP addresses: x.x.x.x, 192.168.161.1, 192.168.137.1, 169.254.95.175> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on x.x.x.x:8500 for protocols iiops, t3s, ldaps, https.> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[1]" is now listening on 192.168.161.1:8500 for protocols iiops, t3s, ldaps, https.> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on x.x.x.x:8000 for protocols iiop, t3, ldap, http.> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 169.254.95.175:8000 for protocols iiop, t3, ldap, http.> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.161.1:8000 for protocols iiop, t3, ldap, http.> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[2]" is now listening on 192.168.137.1:8500 for protocols iiops, t3s, ldaps, https.> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[3]" is now listening on 169.254.95.175:8500 for protocols iiops, t3s, ldaps, https.> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on 127.0.0.1:8000 for protocols iiop, t3, ldap, http.> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "PIA" for domain "fsdmo" running in Production Mode> <Aug 23, 2011 2:36:23 PM GMT-04:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
4. When the web browser is pointed to the FSDMO PeopleSoft instance, the following messages appear in the startPIA.cmd Command Prompt window:
<Aug 23, 2011 2:37:27 PM GMT-04:00> <Notice> <Stdout> <000000> <JoltSessionPool: bea.jolt.SessionException: Cannot connect to any //appswindows.domainnname.com:9000. Reason:NwHdlr: Cannot open socket> <Aug 23, 2011 2:37:27 PM GMT-04:00> <Notice> <Stdout> <000000> <Jolt Session Pool cannot provide a connection to the appsever. This appears to be because there is no available application server domain.> <Aug 23, 2011 2:37:29 PM GMT-04:00> <Notice> <Stdout> <000000> <JoltSessionPool: bea.jolt.SessionException: Cannot connect to any //appswindows.domainnname.com:9000. Reason:NwHdlr: Cannot open socket> <Aug 23, 2011 2:37:29 PM GMT-04:00> <Notice> <Stdout> <000000> <Jolt Session Pool cannot provide a connection to the appsever. This appears to be because there is no available application server domain.> [Tue Aug 23 14:37:29 GMT-04:00 2011] bea.jolt.ServiceException: Invalid Session Application Server last connected java.lang.Throwable at psft.pt8.net.NetReqRepSvc.sendRequest(NetReqRepSvc.java:556) at psft.pt8.net.NetService.requestService(NetService.java:138) at psft.pt8.net.NetReqRepSvc.requestService(NetReqRepSvc.java:327) at psft.pt8.net.NetSession.connect(NetSession.java:308) at psft.pt8.net.NetSession.<init>(NetSession.java:186) at psft.pt8.auth.GetWebProfileSvc.<init>(GetWebProfileSvc.java:130) at psft.pt8.auth.WebProfile.loadProfile(WebProfile.java:502) at psft.pt8.auth.WebProfile.checkAndLoadProfile(WebProfile.java:79) at psft.pt8.psp.service(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at psft.pt8.psfilter.doFilter(psfilter.java:81) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3212) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) ERROR: WebProfile loading internal default settings because of an Exception while communicating with "appswindows.domainnname.com:9000" bea.jolt.ServiceException: Invalid Session at bea.jolt.JoltRemoteService.<init>(JoltRemoteService.java:109) at psft.pt8.net.NetReqRepSvc.sendRequest(NetReqRepSvc.java:534) at psft.pt8.net.NetService.requestService(NetService.java:138) at psft.pt8.net.NetReqRepSvc.requestService(NetReqRepSvc.java:327) at psft.pt8.net.NetSession.connect(NetSession.java:308) at psft.pt8.net.NetSession.<init>(NetSession.java:186) at psft.pt8.auth.GetWebProfileSvc.<init>(GetWebProfileSvc.java:130) at psft.pt8.auth.WebProfile.loadProfile(WebProfile.java:502) at psft.pt8.auth.WebProfile.checkAndLoadProfile(WebProfile.java:79) at psft.pt8.psp.service(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at psft.pt8.psfilter.doFilter(psfilter.java:81) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3212) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
5. Check the configuration.properties file and ensure that it points to the correct application server and jolt port numbers. This file is located at:
E:PT849FS900webservfsdmoapplicationspeoplesoftPORTALWEB-INFpsftdocsfsdmoconfiguration.properties
#----------------------------------------------------------------------- # Source Control Information: #----------------------------------------------------------------------- # ALL ENTRIES IN THIS FILE ARE CASE SENSITIVE. # >>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< # >>>>>>>>>>>>>>> R E A D T H I S F I R S T <<<<<<<<<<<<<<<<<<< # >>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< # To maintain the web server configuration settings, go online to: # PeopleTools > Web Profile > Web Profile Configuration # >>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< # psserver must point to your application server machine name (recommended) or IP address # and JOLT port. The PeopleTools release of the application server must match the PeopleTools # release of the PeopleSoft files on the web server. # # To enable jolt failover and load balancing, provide a list of application server # domains in the format of; psserver=AppSrvr:JSLport,... psserver=appswindows.illuminatnm.com:9000 # The next three fields must be valid for the database referred to in psserver. # WebProfile is the name of the profile used to configure this web site. # The user id and password are the values used to get the profile. # NOTE: If you change the password of this user in the database then # run the PSCipher script with the new password and paste the encrypted output here. # The pre-delivered profiles are: DEV, TEST, PROD, and KIOSK # DEV has standard developer options set # TEST has standard testing options set # PROD has standard production options set # KIOSK is like PROD but has additional settings relevant to KIOSK usage ## sd="Web Profile", dt="dx", ld="The web profile is a named group of configuration property settings that the portal applies throughout your PeopleSoft system to control all portal-related behavior.", tip="This may be set to DEV, TEST, PROD or KIOSK. Additional web profiles may be delivered and created for your application" ## option(va = DEV, sd="Standard developer option set") ## option(va = TEST, sd="Standard testing option set") ## option(va = PROD, sd="Standard production option set") ## option(va = KIOSK, sd="Similar to Production but has Kiosk option set") WebProfile=DEV ## sd="Web User Id", ld="The User Id that the Portal uses to access the web profile" WebUserId=<username> ## sd="Web Password", dt="e", ld="The User Password that the Portal uses to access the web profile", tip="The password is automatically encrypted on the server side" WebPassword=<password> # Report Repository file path # This is the installation default entered on the screen in setup.exe # If one is not specified in the Web Profile then this is used. ## sd="Report Repository File Path", rq="N", tip="This location is only used if this detail is not specified in the Web Profile" ReportRepositoryPath=E:/PT849/psreports #IgnoreParamTempl takes names of URL query string parameters to ignore when the portal servlet looks up template for the URL. #Do not change the default parameters list as they are required for navigation collection. #If your URL has query string parameters but cref was not registered with those parameters, add those parameters #to this comma separated list. ## sd="Ignore Param Template", ld="The names of URL query string parameters to ignore when the portal servlet looks up templates for the URL." IgnoreParamTempl=PORTALPARAM_PTCNAV,EOPP.SCNode,EOPP.SCPortal,EOPP.SCName,EOPP.SCLabel,EOPP.SCFName, EOPP.SCTargPortal,EOPP.SCSecondary.EOPP.SCVirtual,EOPP.SCPTcname,EOPP.SCPTfname,EOPP.SCSecondary, FolderPath,IsFolder,IgnoreParamTempl,pt_fname,Folder
6. Checked netstat for port 9000:
TCP 192.168.137.1:9000 0.0.0.0:0 LISTENING TCP 192.168.137.1:9001 0.0.0.0:0 LISTENING TCP 192.168.137.1:9002 0.0.0.0:0 LISTENING TCP 192.168.137.1:9003 0.0.0.0:0 LISTENING TCP 192.168.137.1:9004 0.0.0.0:0 LISTENING TCP 192.168.137.1:9005 0.0.0.0:0 LISTENING
In Network Connections, disabled VMware Network Adapter VMnet8 and VMware Network Adapter VMnet1.
7. Checked netstat for port 9000:
TCP 169.254.95.175:7000 0.0.0.0:0 LISTENING TCP 169.254.95.175:7001 0.0.0.0:0 LISTENING TCP 169.254.95.175:8000 0.0.0.0:0 LISTENING TCP 169.254.95.175:8500 0.0.0.0:0 LISTENING TCP 169.254.95.175:9000 0.0.0.0:0 LISTENING TCP 169.254.95.175:9001 0.0.0.0:0 LISTENING TCP 169.254.95.175:9002 0.0.0.0:0 LISTENING TCP 169.254.95.175:9003 0.0.0.0:0 LISTENING TCP 169.254.95.175:9004 0.0.0.0:0 LISTENING TCP 169.254.95.175:9005 0.0.0.0:0 LISTENING
In Network Connections, disabled TeamViewer VPN.
8. Stopped FSDMO application server domain, stopped PIA (typed Ctrl+C in startPIA.cmd window), then restarted FSDMO application server domain and ran startPIA.cmd.
Launched FSDMO instance and page appeared without errors.
9. Re-enabled TeamViewer VPN, stopped FSDMO application server domain, stopped startPIA.cmd. Edited configuration.properties (E:PT849FS900webservfsdmoapplicationspeoplesoftPORTALWEB-INFpsftdocsfsdmoconfiguration.properties) to change machine name.
Changed:
psserver=appswindows.domainname.com:9000
To:
psserver=200.x.x.x:9000
Then restarted FSDMO application server domain and ran startPIA.cmd.
Launched FSDMO instance and page appeared without errors.
[amazon asin=0071664939&template=iframe image&chan=default] [amazon asin=1430237074&template=iframe image&chan=default] [amazon asin=0071787925&template=iframe image&chan=default]
check antvirus firewall, i had same problem , turn off firewall from Mccafee temporarily and bingo it was working