LaunchGen Login Error E1 Standalone 9.2

Trying to do the e-generation on Standalone 9.2 (Win7) using guide on JdeSource. Logged in to Standalone as demo user, executed CMD as Admin and ran LaunchGen.bat. Generator v5.2 started, then clicked Connect and entered demo credentials demo/demo/demo920/*ALL... Received error message popup: "Unable to login, Please check JAS logs".

Where are the JAS logs located?
Any suggestions how to pinpoint the error?

"generror.log" contents:
-------------
[ 2016-09-05 21:52:47.337 ] **Generator Error Log started at Mon Sep 05 21:52:47 ACST 2016**
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: Failed to read the managementServerPort property and setting it to -1
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: Failed to read managementServerUsingJMXSecurityStr property from system property and setting it to unknown
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: Failed to read httpport property from system property and setting it to -1
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: Failed to read usingssl property from system property and setting it to unknown
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: Invalid configuration file 'C:\E920_1\system\JAS\EA_JAS_80.ear\webclient.war\agent.properties'; the file does not contain an entry 'management.server.name' containing the management console machine name.
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: SCF management agent initialized successfully. This product is not being managed through SCF.
[ 2016-09-05 22:01:11.238 ]
Unable to connect to JAS
----------------------

Thanks.
Randall.
 

JDEE1Tips

Well Known Member
Trying to do the e-generation on Standalone 9.2 (Win7) using guide on JdeSource. Logged in to Standalone as demo user, executed CMD as Admin and ran LaunchGen.bat. Generator v5.2 started, then clicked Connect and entered demo credentials demo/demo/demo920/*ALL... Received error message popup: "Unable to login, Please check JAS logs".

Where are the JAS logs located?
Any suggestions how to pinpoint the error?

"generror.log" contents:
-------------
[ 2016-09-05 21:52:47.337 ] **Generator Error Log started at Mon Sep 05 21:52:47 ACST 2016**
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: Failed to read the managementServerPort property and setting it to -1
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: Failed to read managementServerUsingJMXSecurityStr property from system property and setting it to unknown
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: Failed to read httpport property from system property and setting it to -1
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: Failed to read usingssl property from system property and setting it to unknown
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: Invalid configuration file 'C:\E920_1\system\JAS\EA_JAS_80.ear\webclient.war\agent.properties'; the file does not contain an entry 'management.server.name' containing the management console machine name.
Sep 05, 2016 9:53:24 PM com.jdedwards.mgmt.agent.E1Agent init
WARNING: SCF management agent initialized successfully. This product is not being managed through SCF.
[ 2016-09-05 22:01:11.238 ]
Unable to connect to JAS
----------------------

Thanks.
Randall.


Hi Randall,

We are the one , who created the article on JDESource.

Your generror.log is showing the Waring message and its not related to your issue.

Did you completed the step 2 which is mentioned in our article ?

Step 2 : Make sure to login into Standalone 9.2 using DEMO user ID before starting the Generator

We need jas.log and jderoot.log from the below location to identify the issue and help you further.

Location C:\E920_1\System\JAS\EA_JAS_80.ear\webclient.war\logs
 
We need jas.log and jderoot.log from the below location to identify the issue and help you further.

Hi JDEE1Tips,
Yes, I logged in to the JDE Thick Client with user Demo before executing LaunchGen.bat. I have used your article instructions successfully in the past, but didn't work this time.

I have attached jas.log and jderoot.log to help troubleshoot the error. Thanks for your help.

Regards, Randall.
 

Attachments

  • jas and jderoot logs.zip
    1.2 KB · Views: 19

JDEE1Tips

Well Known Member
Hi JDEE1Tips,
Yes, I logged in to the JDE Thick Client with user Demo before executing LaunchGen.bat. I have used your article instructions successfully in the past, but didn't work this time.

I have attached jas.log and jderoot.log to help troubleshoot the error. Thanks for your help.

Regards, Randall.

We will help you. During our Initial analysis ,we noticed the below error.

Could not reach security server <localhost>, null source

Whether your Local web works fine ? If yes then follow the below steps and update us / If not , first we need to fix the Local web issue.

1. Restart the Machine ( This will clear the old java process and free the required port )

2. Login into E1 Fat client

3. Start the Local web using Tools --> EnterpriseOne

4. Now launch the launchgen.bat

5. Enter the E1 Credentials

If this is not working. Please provide the jas.ini , jdbj.ini and jde.ini from your step to compare with our Sandbox Setup.


 
Call Orchestrations From Excel – The Easy Way to Make the Orchestrator Work for You.
Whether your Local web works fine?
If this is not working. Please provide the jas.ini , jdbj.ini and jde.ini from your step to compare with our Sandbox Setup.
Hi, yes local web works fine. After restart still not working. Attached the 3 ini files for review. Thank you.
 

Attachments

  • jas jdbj jde ini.zip
    9.8 KB · Views: 8
Top