Unsolved
4 Posts
0
501
ADME ATO-BATCH-FAILURE: Env#-2 is currently locked by batch owner
Hi guys,
From ADME GUI I'm trying to run the specific job, but when I tried to start immediately it showing Env-locked in the last error.
I checked the logs and its shows:
ATO-BATCH-FAILURE: Env#-2 is currently locked by [ Batch-Owner . . .
If you have an idea kindly advise.
Thanks in advance.
Blaasvaer
4 Posts
0
March 24th, 2023 06:00
I had the same problem, and even if you have probably solved your problem during these 2 years, I think it can help someone else with the same problem. What I did was I started a SSH session to the Avamar server and deleted the tmp env directory. I logged in as admin and su - to root. My problem was with env4, so you should replace the number with your env number
cd /home/admin/admeadmin/tmp/
mv atocfg4 atocfg4bak
mkdir atocfg4
chown admin atocfg4
chgrp admin atocfg4
chmod g+w atocfg4
I am not sure if I had to create the directory, but did it anyway.