Hello, I did get this error yesterday in my Mid sourcing instance. It's now working properly, so I'd like to know why did this error appear and if I should worry about this.
Hello, this error has shown up intermittently over the years and typically indicates a deadlock on certain tables. That said, you could submit a ticket to Campaign Support and reference NEO-75920 to validate, as XML changes may be required to the notification template to mitigate this issue in the future.
Hello, this error has shown up intermittently over the years and typically indicates a deadlock on certain tables. That said, you could submit a ticket to Campaign Support and reference NEO-75920 to validate, as XML changes may be required to the notification template to mitigate this issue in the future.
Hello, thank for your help, with this and some time we discovered there was a bugged registry in the database which wouldn't allow other registries to be added
