Could anyone take a look at the A0 assignments to prevent them from going to old clients (v4 and v5) ?
A0 WUs assigned to v5 clients cause issues
Moderators: Site Moderators, FAHC Science Team
-
toTOW
- Site Moderator
- Posts: 6516
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
A0 WUs assigned to v5 clients cause issues
One of my team mates received an A0 WU on a old v5 client which is an issue : this old client doesn't have the ability to deal with A0 bundle (core + DLL), so it's stuck in a loop with error code 63 (unable to start core error) because of the lack of the DLL file 
Could anyone take a look at the A0 assignments to prevent them from going to old clients (v4 and v5) ?
Could anyone take a look at the A0 assignments to prevent them from going to old clients (v4 and v5) ?