Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
Level 1
Level 2
Melden Sie sich an, um alle Badges zu sehen
Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
Hello,
I created a custom resource and did the publication. It all worked fine (there was a warning in the logs at this time too). I then redrafted it and it got successfully deleted too with same warning in the logs as below:
I have not experienced any issue but this warning is now appearing every time during publishing so I wanted to understand what it is, it's impact and how to fix it?
Thanks
Gelöst! Gehe zu Lösung.
Zugriffe
Antworten
Likes gesamt
I was able to resolve this error. I went through previous publication logs to see when did this error started coming. I checked all the changes that happened in that particular publication where this error first appeared and noticed extensions in oob resource. I redrafted that resource and did another publication and the error was removed.
I Don't think there is any impact, also neolane is an old system and no longer used correct? May be that instance has some references to it which is triggering that warning message.
Zugriffe
Antworten
Likes gesamt
I was able to resolve this error. I went through previous publication logs to see when did this error started coming. I checked all the changes that happened in that particular publication where this error first appeared and noticed extensions in oob resource. I redrafted that resource and did another publication and the error was removed.
Zugriffe
Antworten
Likes gesamt
@mmbb110As per my understanding, ACS is the containerized/ cloud native form of campaign classic (neolane originally) and internally it's possible that container locations/ paths can have 'neolane' references.
Zugriffe
Antworten
Likes gesamt
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten