Created attachment 10950 [details]
abend of s4 connector

so if you have a computer bound to the  UCS
then the user operates it in standalone mode

when you return it back to the network with the UCS  and attempt a rename, it throws the following error.

This *might* be related to problems caused by a 2008 sp2 migration in jan/feb 2022

where the sys volume errored due to broken ucs handling, and a re-attempt to migrate was made.

there should be trapping for this , instead of continually trashing the log files until the working volume fills up.

in the UCS front end there needs to be an area to clean & manage sync jobs that have errored instead of endlessly spamming the log files.

it is critical becasue of hte amoinut of contiinual spam it is producing , and the state it had left the LDAP/samba in

are tehy synced or are they not ?