Error Connecting To Awe4
have a ticket in with Automic but I figured i would ask the community to see if anyone has experienced this before. We upgraded our TEST instance to Applications Manager 9.0.1 just today. The upgrade went fine until it tried to start the java awapi process. That failed to start, and now when I try a "startso" or "startso all" I get "rmiserver did not start". The full error log when I try to run Applications Manager will be posted below, but has anyone seen this issue before? If so what did you do to fix it? Any assistance is appreciated greatly. Tagged: upgrade applications manager 0 Best Answers Luu Le Posts: 270 admin August 2015 Answer ✓ For this particular issues, support was able to resolve the issue:After debug on the RMI Server was enabled, it produced some additional information upon it startup.ErrorMsg: AwE-5001 Database Query Error (8/24/15 12:08 PM) Details: getConnection null java.sql.SQLException: Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptorThe issue had been that the services name & connect string was not correct; once that was corrected the system started up normally. 5 Josh Rogalski Posts: 3 August 2015 Answer ✓ A big thank you to support. In the end, the method in which you specify an Oracle connection string was different. In this case during the upgrade it asked for an "Oracle SQL*NET Connect String". I wasn't sure what to put in this and the default during the upgrade was just an "@ symbol. After some discussion and experimentation, we found that we should type in the @ symbol followed by the beginning of the servicename in the TNS Names file. So if your service name was APMPROD.business.com" you would type in "@apmprod" for the sql*net connect string. This took a while to figure out. Thanks again. 5 Answers Josh Rogalski Posts: 3 August 2015 As promised, here is the log I get:ErrorMsg: AwE-5009 RMI connection failure, check if RmiServer is running (8/24/15 11:58 AM) Details: nulljava.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine at java.net.DualStackPlainSocketImpl.connect0(Native Method) at java.net.DualStackPlainSocketImpl.soc
Error Messages Automic Error Messages automic MainCampus staff Overview: Automic, formerly called AppWorx,is an administrative systemsautomation toolwith which users can do process-dependent scheduling. Problem: When logging in, you receive the following error messages: AwE-5103: network socket error AwE-5009: RMI connection failure, check if RMI Server is https://community.automic.com/discussion/5554/error-after-update running Solution: If you cannot log in to Automic, you may need to update your version of Java. Automic requires Java 7 Update 71 to work properly. To see what version of Java you have, view the "How can https://wvu.teamdynamix.com/TDClient/KB/ArticleDet?ID=5676 I find which version of Java is installed without running an applet in Windows or Mac?" at java.com. For additional information, check these categories in the Knowledge Base: Business Management and Reporting Hardware, Software, and Printing Need assistance? See the following related services: Business Management and Reporting Hardware, Software, and Printing Sign in to leave feedback 0 reviews Details Article ID: 5676 Created Mon 5/11/15 1:50 PM Modified Fri 8/19/16 1:04 PM Deleting... × Share Recipient(s) - separate email addresses with a comma Message Check out this knowledge base article I found in the West Virginia University knowledge base. https://wvu.teamdynamix.com/TDClient/KB/ArticleDet?ID=5676 Automic Error Messages Troubleshooting for Automic (formerly called AppWorx) login errors. Send Close
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 09 Oct 2016 13:10:56 GMT by s_ac5 (squid/3.5.20)