Using Fiddler I found out that the TokenService was registered on the localhost domain. That's why the webapplication (which was running on my local machine) couldn't access the TokenService on the ...

Found my answer on: http://www.tridiondeveloper.com/using-a-configuration-file-for-your-custom-tridion-content-delivery-code. public MyStorageExtension(String storageId, EntityManagerFactory ...

Peter Kjaer and Bart Koopman gave the right hints. When I checked the POST request (using the 'Network' tab in Google Chrome), I saw the following: Some TemplateId's were 'null'. This is because that ...

The solution was very simple. I created a new Business Process Type, based on the Topology Type of the Development environment and added that to the publication. So publishing works now. Next step is ...

FOUND IT! It has cost me (and you) a lot of time, and the issue was indeed not in the code / configuration itselves. The solution is so simple that I am almost ashamed to share it ... When exporting ...

The issue is now reported on GitHub. I found out that there are multiple issues when working with the DXA Model Service together with DD4T. There is an issue related to keywords and there seems also ...

Finally found the solution. The other applications on the webserver were 64-bit applications. This application was 32-bit. So I had to install Java 32-bit. It didn't work at first time, because the ...

I did some research and there is no such criteria to look for components in a certain folder. BUT in your case for multimedia components you should try: PublicationMultimediaPathCriteria criteria = ...

These servers have restricted which TLS version can be used. Adding the following line of code fixed the issue: System.Net.ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls11 | ...

We requested a copy of the Content Management DB, but our hosting supplier delivered a copy of the old 2013 SP1 installation. So this error happens when you restore a 2013 SP1 database in your SDL ...

I had the same issue after removing 'old' accounts from the server. The Content Manager snap-in was also unavailable, so this article pointed me in the right direction: https://stackoverflow.com/...

Finally we found the rootcause. The Web Application Proxy (WAP) is very strict in which kind of requests it accepts. According to the standards, a comma value is not allowed, see: https://curl.haxx.se/...

Issue is solved! We discovered a deadlock on the brokerdatabase (at the same time the incoming folder was 'full'), caused by the following query: delete from REFERENCE_ENTRIES where PUBLICATION_ID=@...

The solution was a combination of the above. I already used the '.dll.config' file for configuration (via a custom class ConfigurationHelper). But .NET wasn't able to recognize the connectionstrings ...

I found a solution. This answer helped me: HTTP Deployer displays slow transport throughput on high latency networks. We are now using a SFTP deployer. Publishing still takes a few minutes but no ...