carolai asked a question.
SLM 9.22.1 is in a pre release and I installed that last week.
Since that time DUJ daily tells me, it failed in procedure MainStream.dbo.RefreshExclusionView due to Invalid column name 'DccName'
I created a ticket, but did not get feedback yet.
Do anybody notice the same error? Otherwise I will try to reinstall SM 9.22.1
Thank you very much for your quick answer Axel.
I will reinstall SLM 9.22.1 and see if that would help.
Hi @Carola Iberl​ We don't have that problem, our test environment is on 9.22.01 build 8245 and the DUJ has been running normally. But I hope you get a fix for that.
Today support helped to solve that issue.
DUJ Procedure dbo.RefreshExclusionView is used for checking Compliance Exclusions.
I have some active Compliance Exclusions. One of them refers to a Clustername.
In Criteria this internally was referred as dcc.dccname until 9.22.0
But with SLM 9.22.1 this naming was changed to dcc.Name. I needed to open and save the compliance exclusion again. After that the criteria was saved dcc.Name
From then on that procedure in DUJ did not create an error anymore.
@Falk Schoenefeld​ In case you also do have your DUJ error in that procedure dbo.RefreshExclusionView, then you can try to save all your compliance exclusions.
Perhaps that then will also help you to avoid the DUJ error.
My special error for dccname does only appear with SLM 9.22.1, this did not happen with 9.22.0
Looking at the compliance exclusions I found out that we had a custom field renamed, which caused the compliance exclusion to fail. Updating the exclusion rules has solved our issue. Many thanks for pointing me into this direction.
Today support helped to solve that issue.
DUJ Procedure dbo.RefreshExclusionView is used for checking Compliance Exclusions.
I have some active Compliance Exclusions. One of them refers to a Clustername.
In Criteria this internally was referred as dcc.dccname until 9.22.0
But with SLM 9.22.1 this naming was changed to dcc.Name. I needed to open and save the compliance exclusion again. After that the criteria was saved dcc.Name
From then on that procedure in DUJ did not create an error anymore.