Vanguard

• Vanguard application log is present at the location “<<AssistEdge>>\data\Command\VanguardYYYYMMDD.log”.
• If a fatal exception is thrown at the Vanguard framework level, then the Vanguard application is stopped. An email notification is sent informing that the application is down. An email will be sent in case SMTP is configured at the product level. From the logs also you can identify if the application is stopped.
• In the rare circumstances when an exception is thrown at the Vanguard framework level, then the following logs in the same sequence should be referred for debugging and troubleshooting. “<<AssistEdge>>\data\Command\vanguard.log”, ae status command, Event Viewer.
• In the rare circumstances in Control Tower, you may see an exception informing some service is down. This may occur in case Vanguard has an exception at the framework level. For ensuring a high-reliability system will auto-restart vanguard framework. You may observe Vanguard status showing as STARTED or STARTING from ae status command. In this case, the log file should be referred as against only checking the current state of Vanguard using the ae status command. The sequence to check the log file or steps to follow is the same as explained in an earlier point.
  
• If the user has either not provided or has provided incorrect details for SMTP detail while installing the product, emails are not sent. Log will have the same exception.
• In case SMTP is not properly configured or From or To email address is not in the correct format, then the below exceptions will be present in Vanguard logs.
• Smtp Host not set -
• "level":"Error","priority":"0","srcmodule":"EV.AE.Notifiers.Core.Email","method":"SendMessage","message":"The SMTP host was not specified."
• Smtp Port not set -
• "level":"Error","priority":"0","srcmodule":"EV.AE.Notifiers.Core.Email","method":"SendMessage","message":"Input string was not in a correct format."
• Smtp From address not set –
• "level":"Error","priority":"0","srcmodule":"EV.AE.Notifiers.Core.Email","method":"SendMessage","message":"The parameter 'address' cannot be an empty string. (Parameter 'address')"
• Smtp To address not set -
• "level":"Error","priority":"0","srcmodule":"EV.AE.Notifiers.Core.Email","method":"GenerateMailMessage","message":"The parameter 'address' cannot be an empty string. (Parameter 'address')" &
• "level":"Error","priority":"0","srcmodule":"EV.AE.Notifiers.Core.Email","method":"SendMessage","message":"The parameter 'address' cannot be an empty string. (Parameter 'address')"
• Smtp To address is of incorrect format -
• [2023-01-04T13:11:23Z] [ERROR] [EV.AE.Vanguard.NotificationPeriodicJobs.Core | SendMessage] Error occurred while sending email for id '24' due to The specified string is not in the form required for an e-mail address. 
• In case if the database is MSSQL, and Vanguard is throwing database connection exception as “A connection was successfully established with the server, but then an error occurred during the login process”, 
  • In SQL check if the certificate setting is set to true, and in AppSettings section of “<<AssistEdge>>\app\Vanguard\appsettings.json” file the key value of SQLEncrypt is true. Once you update restart all the Vanguard nodes.
• In case if the database is MSSQL, and if Vanguard is throwing database connection exception as “Unhandled exception. Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time.”.  
  • In the AppSettings section of “<<AssistEdge>>\app\Vanguard\appsettings.json” file check if the key value of SQLConnectionTimeout is 20, the default value for this is 15 and is in seconds. Once you update restart all the Vanguard nodes.
  • In case if the database is Oracle, and Vanguard is throwing exception as “System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=X.X.X.X, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)”. 
    • This exception occurs because either Oracle DLLs are missing or the versions of the DLLs are different from those required for Vanguard. To verify if correct and compatible Oracle DLLs for “Oracle.EntityFrameworkCore” and “Oracle.ManagedDataAccess” are present in “<<AssistEdge>>\data\Oracle” folder. If the DLL’s present are not compatible, then add the compatible DLLs and restart all the Vanguard nodes. 
    • If the same exception occurs after updating the DLLs then verify if correct and compatible Oracle DLL’s are present in “<<AssistEdge>>\app\Vanguard\” folder, else add the compatible DLL’s and restart all the Vanguard nodes. For more information on the compatible DLL version, refer the AE-RPA-Client Downloadable Software.pdf document.