ETL Agent stop executing etl package schedule

Greetings,

We are now on UAT - testing phase and we scheduled all our packages and let the ETL Agent (aetlagent) execute all these scheduled packages. After 24hrs period, the agent in windows service still showing started but it is not executing any of the packages. I have to restart the agent manually in window service.











Please advise.

Why do you have two Advanced ETL Processor Agent services.. installed?
(Second screenshot)

I cant see the full name...

Two ETL Processor installed on two separate server but using the same functional (group) account with administrator privileges.
TPSETL01 & TPSETL02 are the two separate server with each ETL Processor installed but sharing the same domain account and ETL Repository database (SQL Server)
TPSETL01 server is running different ETL packages than TPSETL02 server.

this is the screen shot of TPSETL02 - agent and management console in windows service.
The agent will execute all packages for that server and after a while if there is no activities, the agent will still show started but not executing any of the packages as scheduled.

When agent fails to start or there any problems with it,
it writes an error message into the log file.
The log file is located in the same folder as the agent

Can you post it here please

here it is again, after a while the aetlagent stop executing all packages schedule.
This is a big issue for us and we need this resolve before we go live. Almost every morning we have to restart the etl agent service.

You have those messages in the log.
May be it is because the database is shutdown every night for backups?

2/3/2015 4:34:36 PM [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
2/3/2015 4:40:30 PM First Attempt
2/3/2015 4:40:30 PM Cannot open database "ETLRepositoryDB" requested by the login. The login failed
2/3/2015 4:40:30 PM Second Attempt
2/3/2015 4:40:30 PM Cannot open database "ETLRepositoryDB" requested by the login. The login failed

Can you post here your repository connection settings please