15
Check \SDL Web\web\WebUI\WebRoot\Configuration\System.config and see if the Repair added a duplicate of one of the <editor> sections.
If yes, remove the duplicated one.
12
Technically the message is right - there is no Content Porter Server installer anymore, this is now included in the standard Content Manager Core.
But the client installer is not included in the CM Core (long story short: we couldn't finish the client in time for the 2013 SP1 release).
So you still need to run an installer (you can get it from Customer ...
12
It is an Environment variable called TRIDION_TTM_SERVICEURL
You can also add -TtmServiceUrl parameter to all your commands (but this is mostly used if you want to run Powershell script from another machine), for example
Add-TtmCdTopologyType -Id StagingTopologyType -Name StagingToplogyType -EnvironmentPurposes "Staging" -TtmServiceUrl http://host:port/...
11
The issue was I had Java 9 installed and Web 8.5 only supports Java 8. Just removed Java 9 and installed Java 8 and it worked fine.
10
If you don't see any other errors, I'm guessing it is a port conflict. The default port for the Content Service is 8081; perhaps something else on your machine is already running on that port.
You can check that using PowerShell:
Get-NetTCPConnection | where { $_.LocalPort -eq 8081}
If that returns anything, there is something running on that port.
(You ...
9
Indeed! documentation is bit unclear, an example command not work for windows, I did manage to install successfully, I have sent the message to fix the documentation, I will leave the comment in the documentation.
Try the following steps to fix the installation of DXA Model Extension:
Option1:
Create the extensions folder in content service root.
Copy the ...
7
There has been some changes in the eventsystem handling in SDL Tridion 2013 (async handling) that prevents the 2011 Tridion integration from functioning correctly so you will need an updated version of the eventsystem that takes care of the synchronization between Tridion and Quatron. Today this is not product but we use it in the CXC demo.
7
Your assessment of the dependency of CM on Distributed transactions is 100% correct. It's not only that SDL doesn't support Cloud databases - it will not work. I've heard rumors of people being able to run CM on Oracle RDS, but I can guarantee that at some point (especially if you use add-ons like Translation Manager) you will run into trouble.
Regarding ...
7
looks like a problem with bin/config/cd_dynamic_conf.xml in your web application. Double check that the Publication element has the correct Id in here matching that of your 400 Example Site publication. If this is OK then its probably due to the configuration not being successfully published, perhaps due to the previous issue you had with Publish Settings ...
7
As you are using Https protocol, please specify the port number as 443 to get rid of the error and continue with installation
6
The capture-import command (and pretty much all other commands!) should be run from the fredhopper installation directory, not from the bin directory.
6
Linking service is moved to root of the content service. You can access it like
http://my.sdlweb8.server:86/linking
For example to get Component link
http://localhost:8081/linking/componentLink?sourcePageURI='<id>'&targetComponentURI='<id>'&excludeTemplateURI='<id>'....
6
The username can be anything you want, MTSUser was the default user name for Microsoft Transaction Server (MTS) in the past, and we never bothered changing the default name.
Security-conscious people will tell you that you should rename it to something else.
This account is used to connect to the search indexers (configurable in the MMC plug-in) and to run ...
6
As I suspected based on the logging, it seems that the problem (at least indirectly) was that the server was a domain controller. This was the default setup for Windows Server, but I don't really need a DC, as the machine in question is just my own Tridion research image.
I removed Active Directory Domain services, and a few other things like DNS and ...
5
COM+ not allowed? Then you shall not run SDL Tridion! The Licencing module is still COM+ even in Tridion 2013 SP1...
Legacy pack contains the TDSE COM+ application as well as DLLs, configuration entries and database items (you already have the database items in your database hence the problem because you do not have the corresponding DLLs and configuration ...
5
For the first error:
When accessing the web application I see:
[ArgumentNullException: Value cannot be null.Parameter name: paths]
System.IO.Path.Combine(String[] paths) +6626904
Sdl.Web.Common.Mapping.SemanticMapping.Load(String applicationRoot) +379
Sdl.Web.Common.Configuration.SiteConfiguration.Refresh() +304
Sdl.Web.Site.MvcApplication....
5
The following lines from your trace indicate that you have an issue with the license configuration in your cd_storage_conf.xml:
com.tridion.services.BaseService.getLicenseManager(BaseService.java:186)
~[cd_core.jar:na] at
com.tridion.services.BaseService.processLicensing(BaseService.java:126)
~[cd_core.jar:na] ... Caused by: java.lang....
5
Your understanding seems to be quite OK.
If you want to minimize the number of DBs, you could combine the Discovery and Content Broker DBs, but I wouldn't recommend that; it's more convenient to keep your content and infrastructure info separate.
It is essential that each CD Environment has its own Discovery Service (DB).
With Topology Manager, the ...
5
I was having a similar issue in a Windows environment with SDL Web 8.1.1. What got me past the error was removing these two attributes from the ConfigRepository element in the cd_storage_conf.xml I used to run the discovery update:
ClientId="registration"
ClientSecret="encrypted:xXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxX"
Since I am not using OAuth, I guess ...
5
SDL Web 8.5 does not support dockerization. In the future planned release we are exploring supporting docker to run the content manager, however, nothing is concrete as of yet. And indeed this error we have seen when looking at it OOTB, and we are not aware of any known workarounds.
5
Your signalrBackplaneHub config is not valid. Use one described in documentation https://docs.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20Sites-v1/GUID-8B1C96F2-464E-442F-9727-3F4E7B21AF23
4
From the error message it seems like it cannot find the object MULTIPLE_OPERATIONS object in database. It is a table in Tridion 2011 SP1 database, from the log it looks like it is failing in the step trying to upgrade from 2011SP1 database. Please ensure that the database is not corrupt or not missing any tables/sps or an earlier partial upgrade was not done ...
4
If all else fails you can also install the PowerTools manually, see https://sdltridionworld.com/articles/sdltridion2011/tutorials/GUIextensionIn8steps.aspx.
Or use Robert Curlette's lightweight installer script, see http://www.curlette.com/?cat=13.
4
Note also that you will not need a Content Porter license when running Content Porter 2013 SP1 on a Tridion 2013 SP1 system.
4
When you install the Tridion Content Manager, the credentials of the MTSUser (which you specify during the install) are stored in the registry, in the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Tridion\Installer\
Here you'll find the following keys:
system_account_domain
system_account_name
system_account_password
For some reason, the ...
4
By looking at the error message I could say it is not a single machine installation of Web 8. The error message is indicating that your web server is not able to connect with your SQL server instance. Some of the common reason for this kind of issue are:
TCP/IP for both IPV4 or IPV6 is not enabled on the web server.
Firewall is blocking the inbound port ...
4
As specified in the processor info, your machine has 8 logical processors. That's more than allowed by your license.
The processor info also states that there are 4 Cores. That probably means that HyperThreading is enabled. This is something you may be able to disable in the BIOS/UEFI settings.
4
There was an issue due to SecureRandom in unix platforms which caused timeouts when generating OAuth token. This was fixed as a hotfix and available in latest 8.1.1 hotfix release. Applying hotfix should fix this issue.
4
I downloaded the latest nuget package Sdl.Web.Cil version 8.1.1 (released 5th April) and I do get the Sdl.AudienceManager.ContentDelivery reference in there:
If that isn't working for you could try installing the SDL Web Audience Manager nuget package directly:
4
Yes, it is supported in Web 8. You can download the latest version here, http://razor-mediator-4-tridion.googlecode.com/files/RazorMediatorInstaller_v1.3.3.1.msi
There is also a nice presentation about debugging Razor Templates in Visual Studio at the Tridion Developer Summit this year here:https://vimeo.com/177712049
Only top voted, non community-wiki answers of a minimum length are eligible