Error when attempting to link a PASOE server to a database - Forum - OpenEdge General - Progress Community

Error when attempting to link a PASOE server to a database

 Forum

Error when attempting to link a PASOE server to a database

This question is answered

Hi,

I'm currently having the issue that when starting the default oepas1, PASOE server while not connected to a database it starts fine. However, if I modify its run configuration to connect to the sports2010 database I get the following error. I'm running Progress OpenEdge Developer Studio 11.7.2 for reference.

C:\OpenEdge\WRK\oepas1\logs\oepas1.2018-03-14.log:11:09:44:31.516/12181 [eRMuEdJ-R7uHdbxX-I03sA-starter-0] ERROR com.progress.O4gl.Trace - CONNECT write IOException: java.net.SocketException: Connection reset

C:\OpenEdge\WRK\oepas1\logs\oepas1.2018-03-14.log:12:09:44:31.564/12229 [eRMuEdJ-R7uHdbxX-I03sA-starter-0] ERROR com.progress.O4gl.Trace -

C:\OpenEdge\WRK\oepas1\logs\oepas1.2018-03-14.log:35:09:44:32.567/13232 [eRMuEdJ-R7uHdbxX-I03sA-starter-0] ERROR com.progress.O4gl.Trace -

C:\OpenEdge\WRK\oepas1\logs\oepas1.2018-03-14.log:58:09:44:32.654/13319 [eRMuEdJ-R7uHdbxX-I03sA-starter-0] ERROR com.progress.appserv.PoolMgt.Agent - AgentStarter:call(eRMuEdJ-R7uHdbxX-I03sA) : unexpected error in startup of agent 1X_TevxFSLOaC8bbq-i81Q (com.progress.ubroker.util.NetworkProtocolException: A com.progress.open4gl.dynamicapi.SessionPool$NoAvailableSessionsException: SessionPool : NoAvailableSessions[Could not connect to the AppServer: General Error: Connection refused: connect. (7203)] network protocol error occured: SessionPool : NoAvailableSessions[Could not connect to the AppServer: General Error: Connection refused: connect. (7203)] (9996):A com.progress.open4gl.dynamicapi.SessionPool$NoAvailableSessionsException: SessionPool : NoAvailableSessions[Could not connect to the AppServer: General Error: Connection refused: connect. (7203)] network protocol error occured: SessionPool : NoAvailableSessions[Could not connect to the AppServer: General Error: Connection refused: connect. (7203)] (9996))

C:\OpenEdge\WRK\oepas1\logs\oepas1.2018-03-14.log:59:09:44:32.654/13319 [localhost-startStop-1] ERROR com.progress.appserv.PoolMgt.Agent - startAgent(eRMuEdJ-R7uHdbxX-I03sA) : startup of agent 1X_TevxFSLOaC8bbq-i81Q failed (java.util.concurrent.ExecutionException: com.progress.ubroker.util.NetworkProtocolException: A com.progress.open4gl.dynamicapi.SessionPool$NoAvailableSessionsException: SessionPool : NoAvailableSessions[Could not connect to the AppServer: General Error: Connection refused: connect. (7203)] network protocol error occured: SessionPool : NoAvailableSessions[Could not connect to the AppServer: General Error: Connection refused: connect. (7203)] (9996):com.progress.ubroker.util.NetworkProtocolException: A com.progress.open4gl.dynamicapi.SessionPool$NoAvailableSessionsException: SessionPool : NoAvailableSessions[Could not connect to the AppServer: General Error: Connection refused: connect. (7203)] network protocol error occured: SessionPool : NoAvailableSessions[Could not connect to the AppServer: General Error: Connection refused: connect. (7203)] (9996))

C:\OpenEdge\WRK\oepas1\logs\oepas1.2018-03-14.log:60:09:44:32.679/13344 [localhost-startStop-1] ERROR com.progress.appserv.Agent - TcpAgentManager(eRMuEdJ-R7uHdbxX-I03sA) : Error prestarting agent 0 = com.progress.appserv.broker.exception.BrokerException$NoAvailableAgentsException: Agent:No Available Agents[java.util.concurrent.ExecutionException: com.progress.ubroker.util.NetworkProtocolException: A com.progress.open4gl.dynamicapi.SessionPool$NoAvailableSessionsException: SessionPool : NoAvailableSessions[Could not connect to the AppServer: General Error: Connection refused: connect. (7203)] network protocol error occured: SessionPool : NoAvailableSessions[Could not connect to the AppServer: General Error: Connection refused: connect. (7203)] (9996)]:Agent (18278)

14-Mar-2018 09:44:34.00 ERROR [main] One or more multi-session Agent startup failures - see Agent logfiles

Verified Answer
  • >>"Problem in OpenEdge Explorer: The oemanager web application is not accessible
     
    [Sanjeev]: We usually see this error when oemanager.war file is not deployed to PAS OE instance. Can you please check availability of oemanager.war under instance’s webapps folder (<DLCWRK>/<InstanceName>/webapps).
    If oemanager.war file is not available under instance’s webapps folder, you can deploy from proenv command prompt. Launch Proenv and run the following commands to deploy oemanager.war and manager.war files:
    1. <instance-name>\bin\tcman.bat deploy <DLC>\servers\pasoe\extras\oemanager.war (example: oepas1\bin\tcman.bat deploy C:\Progress\OpenEdge\servers\pasoe\extras\oemanager.war)
    2. <instance-name>\\bin\tcman.bat deploy <DLC>\servers\pasoe\extras\manager.war (example: oepas1\bin\tcman.bat deploy C:\Progress\OpenEdge\servers\pasoe\extras\manager.war)

     

    Hope this helps,
    Sanjeev
     
  • Everything published successfully, thanks a lot Sanjeev!

    As for the other problems, OpenEdge Explorer wasn't connecting because it seems I need to manually launch fathom on start of my computer now for some reason and the original error was (I suspect) because I was using the sports database which came with the caveat "only licensed for local logins" (EDIT this is incorrect, it works on my work workspace for reasons unknown but connecting to the same databases on my personal workspace retrieves the original error. Sorry I don't have the solution for this one). The work database worked first time. Thanks for all the help everyone!

All Replies
  • The SessionManager log ( oepas1.<date>.log ) is telling you that it cannot start the multi-session agent process and that no ABL sessions are available to service client requests.

    What is in the multi-session agent log file ( oepas1.agent.log )?  Most of the time I find an error or alert message that indicates why the database connection described in the agentStartupParam failed.

  • Hi,

    Check the contents of oepas1.agent.log.What messages are there?

  • Hi, thanks for the replies. This is the contents of oepas1.agent.log on my most recent attempt to run it.

    -------------------------------------------------------------

    [18/03/14@11:19:21.335+0000] P-007324 T-007160 1 AS-Aux-0 MSAS Agent Starting Up -- Progress OpenEdge Release 11.7  build 1497.

    [18/03/14@11:19:21.335+0000] P-007324 T-007160 1 AS-Aux-0 -- Logging level set to = 2

    [18/03/14@11:19:21.335+0000] P-007324 T-007160 1 AS-Aux-0 -- Log entry types activated: ASPlumbing,DB.Connects

    [18/03/14@11:19:21.335+0000] P-007324 T-007160 2 AS-Aux-0 AS Starting MSAS Session for oepas1.

    [18/03/14@11:19:21.384+0000] P-007324 T-007160 2 AS-Aux-0 AS MSAS Session Startup. (5473)

    [18/03/14@11:19:21.394+0000] P-007324 T-007160 1 AS-Listener -- Log entry types activated: ASPlumbing,DB.Connects

    [18/03/14@11:19:21.394+0000] P-007324 T-007160 2 AS-Listener AS Starting MSAS Session for oepas1.

    [18/03/14@11:19:21.394+0000] P-007324 T-007160 2 AS-Listener AS MSAS Session Startup. (5473)

    [18/03/14@11:19:21.405+0000] P-007324 T-007160 1 AS-Listener MSAS Spawning New Worker Thread. Number: 4

    [18/03/14@11:19:21.412+0000] P-007324 T-000940 1 AS-ResourceMgr -- Log entry types activated: ASPlumbing,DB.Connects

    [18/03/14@11:19:21.412+0000] P-007324 T-000940 2 AS-ResourceMgr AS Starting MSAS Session for oepas1.

    [18/03/14@11:19:21.412+0000] P-007324 T-000940 2 AS-ResourceMgr AS MSAS Session Startup. (5473)

    [18/03/14@11:19:21.808+0000] P-007324 T-000940 2 AS-ResourceMgr MSAS Incremented connection count for sports2000 (sports2000): 1

    [18/03/14@11:19:21.858+0000] P-007324 T-000940 1 AS-ResourceMgr -- There is no server for database C:\sports2000\sports2000. (1423)

    [18/03/14@11:19:21.909+0000] P-007324 T-000940 1 AS-ResourceMgr -- Error initialising the application server. (5479)

    [18/03/14@11:19:21.910+0000] P-007324 T-007160 1 AS-Listener MSAS Resource Manager Initialization Failed -- Shutting down...

    [18/03/14@11:19:21.910+0000] P-007324 T-007160 1 AS-Listener MSAS Agent Shutting Down. Status: -1005

    [18/03/14@11:19:21.910+0000] P-007324 T-006984 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 4, Status: -16

    [18/03/14@11:19:21.910+0000] P-007324 T-007160 1 AS-Listener MSAS Spawning New Worker Thread. Number: 5

    [18/03/14@11:19:21.910+0000] P-007324 T-001220 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 5, Status: 0

    [18/03/14@11:19:21.916+0000] P-007324 T-007160 1 AS-Listener MSAS Agent Shutdown Complete.

  • This is the important line...
     

    [18/03/14@11:19:21.858+0000] P-007324 T-000940 1 AS-ResourceMgr -- There is no server for database C:\sports2000\sports2000. (1423)

  • Do you know how to fix this Brian? I can run ABL code easily enough on the database. It is set to autostart in the database configurations.

  • Thanks Brian but do you know how to fix this? I have no problem accessing the database with ABL code and it is set to autostart in the database configurations

  • Make sure you are connecting with the correct -H and -S parameters.  If you aren’t sure, grab the parameter list from the PAS install config and run it manually from a proenv command prompt
     

  • Point 1 - Check the configuration to know about the hostname (-H) and Service (-S)

    1. Execute command from PAS Instance/bin directory:      oeprop.bat  AppServer.SessMgr.<instance name>.agentStartupParam  ( configuration settings are in pasinstance/conf/openedge.properties )
    2. The above command will help to know about the startup parameters
    3. Open .pf file to know about -H and -S 
    4. Start the database using the command:   proserve <database> -H <hostname> -S <service / port>

    Start Database - 

    Point 2 - Automatically start a database server when the developer studio runtime starts

    1.  Double click the PAS Instance in Sever view in PDSO
    2. Open Launch Configuration
    3. Goto Database section
    4. Click on database connection and edit or create a new connection
    5. After configuring the database connection profile, go to Database server configuration
      1. Check the checkbox auto-start database server 

  • Thanks a lot sauqad. Point 2 is the settings I had before and it doesn't work. Does the specific port number matter? As for point 1, I'm lost a bit on how to do #4, I've not used proenv much. I've tried typing "proenv  -db C:/sports2000/sports2000.db -H localhost -S 4256 -ld sports2000" and it just seems to restart the proenv session every time. But I found the .pf file with the configuration in, thanks for that.

  • Your welcome.

    I am sorry for typing a wrong command in the post. Correct command is - proserve <database name>. proenv opens a (pro)gress (env)ironment. I have edited the post and updated with new screenshot too.

    Kindly execute the command - proserve C:/sports2000/sports2000.db -H localhost -S 4256 -ld sports2000

  • Thanks again Sauqad. This is the response I get when I enter that command.

  • I've also had to remove the port number from the database configuration as Test Connection was failing and my ABL code could not find the tables I was referencing. Is there a correct port number or something?

  • This means that the database has already started.
    In the database log, find the -S parameter since the last start or attach the log here.

  • Sorry it's taking me so long to reply, I have to keep reposting as my posts never show up from waiting for approval.

    I've tried a few different port numbers, but when I had port numbers (which come up as -S parameters on the run arguments) entered into the port box then my ABL code can't connect to the database and I get "ambiguous table" errors.

    -S was 4256. I'd link the log but I don't know how to attach files without just pasting the whole massive log here.

  • Graahhhhh nothing I post here ever gets approved so I can't respond to these posts!!!!!!!!