On a DMA 10.1 cluster we fixed a driver (small fix of 2 characters).
We signed it, uploaded on our internal systems and it works perfectly.
But at the customer : Protocols & Template pages shows that the new protocol is in production. but if we look at the logfile of the elements : still the old protocol is running.
We tried to change 1 element and set it to that new protocol (right cluck in the cube on that element edit - version change to the new protocol - apply) and a popup appears indicating
"Not able to save element on the DMA"
Remark the element is not located on DMA-1.
We changed the version of some other protocol, signed it, uploaded and set it : same popup, and new version not used.
We did the same with the protocol of an element that resides on DMA-1 : and that one succeeded.
Do you have any idea why "Not able to save element on the DMA" popup appears + why this perfectly working new protocol can not be set ?
Hi Cristel, without more details, it's hard to pinpoint the cause of this. I would suggest reaching out to tech support and providing additional logging so we can determine the root cause.
Hi,
I see that this question has been inactive for some time. Do you still need help with this? If not, could you select the answer that has been most helpful for you (using the ✓ icon) to indicate that the question is resolved?