AppWorx, Dollar Universe and Sysload Community

 View Only
Expand all | Collapse all

After Reboot Unable to Login Automic Web Interface

  • 1.  After Reboot Unable to Login Automic Web Interface

    Posted Jul 07, 2020 11:11 AM
    Edited by Emre Boler Jul 07, 2020 07:16 PM
    Hello,

    I am a newbie about Automic Workload Automation and I am learning with Implementer trainings so I may not understand some of the terms.
    Thanks in advance for your understanding. 

    Today I restarted the test server (WIN) today then when I tried to login to AWI, I received the following error;

    Can you help me about this situation ?

    ***EDTUpgrading from 12.3.2 to 12.3.3 solved the problem but I would like to know the cause of the error.

    The warning When I tried login AWI after reboot
    Also Service Manager like this,

    SMNGR




    ------------------------------
    Technical Consultant
    BT Information Technologies
    Istanbul / Turkey
    ------------------------------


  • 2.  RE: After Reboot Unable to Login Automic Web Interface

    Posted Jul 08, 2020 02:58 AM
    Hello Emre,

    as I see in your ServiceManagerDialog there were no CP's active, so the AWI can't connect to the engine. You have to activate your CP's, WP's, JCP and JWP for a full running system.

    Greetings
    Bernhard

    ------------------------------
    Landeshauptstadt München
    ------------------------------



  • 3.  RE: After Reboot Unable to Login Automic Web Interface

    Posted Jul 08, 2020 04:29 AM
    Hello Bernhard,

    First of all, thank you for your interest.

    Yes, as a result of my research, i learned that it was the problem but i have no idea about its solution.

    When I right click CPs and WPs on Service Manager and click "start service", the status becomes "stopped" within 2 seconds. Is there another method to start CPs and WPs?

    ------------------------------
    Technical Consultant
    BT Information Technologies
    Istanbul / Turkey
    ------------------------------



  • 4.  RE: After Reboot Unable to Login Automic Web Interface

    Posted Jul 08, 2020 06:01 AM
    Edited by Bernhard Flegel Jul 08, 2020 06:02 AM
    Sorry Emre but I don't have experiences with the AE and Windows. Our AE-system is completly running under linux so I can't help you.

    Bye 
    Bernhard

    ------------------------------
    Landeshauptstadt München
    ------------------------------



  • 5.  RE: After Reboot Unable to Login Automic Web Interface

    Broadcom Employee
    Posted Jul 08, 2020 02:10 PM
    Hi @Emre Boler

    did you find any hints in the AE's log-files?
    e.g. "C:\Automic\Automation.Platform\AutomationEngine\temp\WPsrv_log_001_00.txt" and "C:\Automic\Automation.Platform\AutomationEngine\temp\CPsrv_log_001_00.txt"​

    What happens when you use the "coldstart" option at WP1?

    ------------------------------
    Engineering Program Manager
    Broadcom
    ------------------------------



  • 6.  RE: After Reboot Unable to Login Automic Web Interface

    Posted Jul 08, 2020 04:45 PM
    Hi @Bernhard Flegel,  See you again when my Linux based problems occur :) thank you again.

    Hi @Michael Dolinek ,

    There are some SQL and DB errors,I didn't think it might be related to these. You can see log files as attachments.

    Thank you,


    ------------------------------
    Technical Consultant
    BT Information Technologies
    Istanbul / Turkey
    ------------------------------



  • 7.  RE: After Reboot Unable to Login Automic Web Interface

    Posted Jul 09, 2020 02:42 AM
    Hi,
    AE log hints about error while connecting to database.
    please review connection parameters in AE config file with respect to db.


  • 8.  RE: After Reboot Unable to Login Automic Web Interface

    Posted Jul 09, 2020 11:25 AM

    Hi,

    stupid question: Is the naming really "Atomic"?

    SQLDRIVERCONNECT=ODBCVAR=NNNNNNRN,Driver={SQL Server Native Client 11.0};Server=tcp:192.168.90.29,1433;Database=Atomic;Uid=Atomic;PWD=???;MARS_CONNECTION=Yes

    Regards

    Juergen



    ------------------------------
    Juergen Lechner
    Senior Consultant
    setis GmbH
    Germany
    ------------------------------



  • 9.  RE: After Reboot Unable to Login Automic Web Interface

    Posted Jul 09, 2020 11:39 AM
    Hi,

    another hint: You are looking in the wrong log. The error "18456" indicates an error returned by the MS SQL server connected to username or password. It is not send to the outside of the server what is really the case. There is an additional internal number that is found in the respective logs of the MS SQL server. Unfortunately I have never been in the need to find it myself. But the documentation of the server should help you.

    Regards
    Juergen

    ------------------------------
    Juergen Lechner
    Senior Consultant
    setis GmbH
    Germany
    ------------------------------



  • 10.  RE: After Reboot Unable to Login Automic Web Interface

    Posted Jul 09, 2020 12:31 PM
    Hi @Juergen Lechner and Sridhar Ramaiah,

    Unfortunately, the person working on this server before me give the name "Atomic"...
    Since I did not make any changes about SQL Server from the beginning of training, I could not think that the problem could be caused by this.​

    I will be reviewing MS SQL connections then I'll informing.

    Thank you,​​​​​​​

    ------------------------------
    Technical Consultant
    BT Information Technologies
    Istanbul / Turkey
    ------------------------------



  • 11.  RE: After Reboot Unable to Login Automic Web Interface

    Broadcom Employee
    Posted Jul 10, 2020 02:58 AM
    As you can see in the log, AE is not possible to connect to the DB - to be precise the provided user can not login to the DB.
     
    WP log:
    20200708/001725.674 - U00003591 UCUDB - DB error info: OPC: 'SQLDriverConnect' Return code: 'ERROR'
    20200708/001725.674 - U00003592 UCUDB - Status: '28000' Native error: '18456' Msg: 'Login failed for user 'Atomic'.'
    20200708/001725.674 - U00003590 UCUDB - DB error: 'SQLDriverConnect', 'ERROR   ', '28000', 'Login failed for user 'Atomic'.'
    20200708/001725.674 - U00003611 DB OPEN executed. Return Code = '0000003590'
    20200708/001725.674 - U00003620 Routine 'UCMAIN_R' forces trace because of error.
    20200708/001725.674 - U00003590 UCUDB - DB error: 'SQLDriverConnect', 'ERROR   ', '28000', 'Login failed for user 'Atomic'.'

    CP log:
    20200708/001722.736 - U00003545 UCUDB: Opening database ...
    20200708/001722.736 - U00029112 UCUDB - Length of the DB-History area: 100
    20200708/001722.767 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: 2667070  DB-HDBC: 2667150
    20200708/001722.767 - U00003591 UCUDB - DB error info: OPC: 'SQLDriverConnect' Return code: 'ERROR'
    20200708/001722.767 - U00003592 UCUDB - Status: '28000' Native error: '18456' Msg: 'Login failed for user 'Atomic'.'
    20200708/001722.767 - U00003590 UCUDB - DB error: 'SQLDriverConnect', 'ERROR   ', '28000', 'Login failed for user 'Atomic'.'

    The native MS SQL error is 18456.
    When searching this on the internet you might end up at this page with several explanations.
    https://docs.microsoft.com/en-us/sql/relational-databases/errors-events/mssqlserver-18456-database-engine-error?view=sql-server-ver15

    But maybe in your case it was just the fact the DB-server was not up and running (because of a reboot) when you already started your AE-system.

    ------------------------------
    Engineering Program Manager
    Broadcom
    ------------------------------



  • 12.  RE: After Reboot Unable to Login Automic Web Interface
    Best Answer

    Posted Jul 10, 2020 03:31 AM
    Good morning Michael,

    Nope. The server answered.

    20200708/001722.767 - U00003592 UCUDB - Status: '28000' Native error: '18456' Msg: 'Login failed for user 'Atomic'.'

    This comes directly from the SQL Server. Please see the error description: https://docs.microsoft.com/de-de/sql/relational-databases/errors-events/mssqlserver-18456-database-engine-error?view=sql-server-ver15

    As I wrote. The server hides the specific cause.

    Regards,
    Juergen


    ------------------------------
    Juergen Lechner
    Senior Consultant
    setis GmbH
    Germany
    ------------------------------