We need to start with a copy of the deployment log (which you can get from the Repository under Activities), and you might check the application event viewer at the time of the deploy. If there are privacy concerns with sharing this information here, it might be better to open a support case.

Along with what Vickie Ortega  said, did the DBA see a specific error in the aborted deploy?

Vickie Ortega  

Thanks for the prompt response, so according to our DBA manager, there are no errors in any database logs or event viewers. The behavior observed is indicative of either a deadlock situation or complete consumption of system resources. In each instance, our DBA team intervened to mitigate the issue before it escalated.

I checked the activity log and it ends with this error:

INFO -- Verifying endpoints...
INFO -- The environment endpoint "MoveRecordOnCheckIn" was reachable.
INFO -- The environment endpoint "MoveRecordOnValidation" was reachable.
INFO -- The environment endpoint "MoveRecordOnCheckOut" was reachable.
ERROR -- The environment endpoint "StandardNotificationReceiver" was not reachable.

Activity Summary
===============================================
User: ------------
Version: 1,878
Label: Version 1.4714.060
Destination Environment: PROD Environment
Server time zone: Mountain Daylight Time (America/Denver)
Start time: 5/23/24 6:17 PM
Stop time: 5/23/24 6:17 PM
Total time: 0 min, 7 sec
Status: failed
===============================================

it sounds like it is not a SQL database issue as they stated. And the application deployment failed seven seconds after it was launched, as shown in the activities log, which I think is not enough to make that load on the server resources. A few months ago I added three new fields to the same table with some default values and it has been deployed successfully, but usually, I dont use that "Verify endpoints" option.

it looks like the deployment was aborted in 7 seconds, but some SQL commands were still running and didn't stop which caused the deadlock and high consumption of the server resources.

The error says:

ERROR -- The environment endpoint "StandardNotificationReceiver" was not reachable.

So, you should check the endpoint. Log into the Repository, and go to Environment > pick the destination environment > Endpoint tab > find the one called "StandardNotificationReceiver". Copy the URL and put it in a clean browser tab. What happens? I assume you'll get an error. What is it? If it is not a security risk, maybe you can share the URL here too. Even if we can't access the URL, seeing the URL might spark more ideas.

Let's check the Application Engine\Log directory for ts_import.log for the steps it took before it failed.

  What is the path of the ts_import.log ?

Mohammad Alsharayri That is part of the Application Engine, so SBM\Application Engine\Log.

I have unchecked the endpoint verification checkbox and deployed it to PROD, but it is stuck :

  Vickie Ortega any thoughts, please?

06/06/2024 19:26:23: Begin Importing C:\Program Files\Serena\SBM\Application Engine\app23582.adf

Stuck there