We’re rewarding the question askers & reputations are being recalculated! Read more.

Hot answers tagged

18

The problem is VBscript templates in your migrated 2011 publication. This can easily be fixed by installing the Legacy Pack. You can install the legacy back by running the Tridion 2013 CM installer with an additional option. This allow you to install the legacy pack. For more info see the Decide if you want to install legacy features section of the manual (...


14

I have seen problems like this before. Here's the thing: During installation of Oracle client, installer checks for .Net version installed on the box. It then installs corresponding components. In your case, most probably you had .Net 3.5 at that time, so Oracle installer installed components for .Net 3.5. Later, Tridion installer updated your .Net version ...


11

You should upgrade your existing Default Templates by opening Template Builder, choosing Tools | Create Default Building Blocks from the menu, and selecting the parent folder for the "Default Templates" folder in the relevant parent Publication. For instance, if your default templates are in "Building Blocks\Templates\Default Templates", you need to choose "...


10

I had the same problem when calling Set var = CreateObject("DLL.Class"). This was happening from Workflow Visio VB Script. I created a simple VB script do the same and object was created without any problem. After bumping my head against a very hard desk a few times, it dawned on me if I was using the correct version of RegAsm utility to register my DLL. ...


10

I don't think the XML format is documented anywhere (at least I could not find it) but following Nuno's comment I ran a simple VBscript to check. It seems that the main features that I need are compatible and work unaltered: Search on a particular (metadata) field using the IN operator Search in location Based on schema Type (component) Modified between ...


9

You have to unblock the Tridion.Database.Management.dll as described in the documentation (bullet 6, login required)


8

Here are some notes that I wrote in the past when upgrading to Tridion 2011 GA, but the issues will probably still be similar. This covers some more general issues as well as some technical ones. Do you use any Custom URLs (Opened as popups from the Tridion CME GUI when clicking on the field name of a Component)?   If so, then I found that a couple of ...


8

Few points need to remember while setting up Tridion on a different machine, which are below You need a different licence file for your new CD server, which you need to put on upload folder. Make sure your all servers allow access by doing changes in your firewall settings. You need to enable a few ports through which you are able to access data. Can ...


7

It seems that the upgrade process does not upgrade the Tridion.SiteEdit.Templating TBB - this is needed for the new tags to be interpreted. You need to manually do this, by opening the TBB, and uploading the upgraded Tridion.SiteEdit.Templating.dll (which can be found in [tridioninstallroot]/bin


7

In Tridion 2013 you do not need YAWF anymore, you can directly write CoreService codes in script window, or even have external compiled activity being executed. In order to understand why it does not, you need to know that since 2013 the TcmWorkflowAgent.exe hands over the execution of legacy scripts to LegacyScriptExecutor which is hosted in Tridion COM+ ...


7

Upgrade should be fairly painless. 2011sp1 and 2013 are the same architecture and so not too many surprises there. If you run VBScript tempalates, you'll need the legacy pack since 2013 no longer requires COM+ for Templates or APIs. You'll need to re-compile any C# TBBs, Core Service, Event System, or other custom applications that rely on Tridion ...


7

For the Java version of DD4T: Tridion 2011 to Tridion 2013 No upgrade needed. DD4T versions 1.31 and 2.0.0+ will work with Tridion 2013 as well, with one important note: The DD4T web application will need to be compiled against JDK 7 and the Tridion CD API version 7.1.0 instead of version 6.1.0. Tridion 2011/2013 to SDL Web 8 In-Process The same is true ...


7

i also faced similar kind of issue which got resolved after applying Hotfix Rollup #1 for SDL Tridion 2013 SP1 as suggested by SDL. Kindly contact SDL for the hotfix or log a ticket in SDL support


7

I believe this is a known defect on 8.1.1 installer, which got fixed in 8.5. The work around involves using a different Topology Manager database for the 2nd install, then change the 2nd server to use the first one (and delete the second one). One has to wonder though... why aren't you deploying 8.5 rather than 8.1.1?


6

First of all you should subscribe to TransactionComitted phase - this is the phase in which you can be sure that operation succeeded. I have just checked it on my system and it is working like a charm. I suspect the problem is that your component has no corresponding dynamic component template and is not actually published, so no event triggered. I don't ...


6

No - an upgrade can (and usually will need to) be performed while there are active Workflow process instances. The changes to workflow in 5.3 do have an impact on existing workflows, but this is mostly related to the fact that in 5.3 and later versions workflow processes are Blueprinted. In 5.2 (and earlier versions), if you wanted to use the same ...


6

My suspicion would fall on permissions. Check the logs for DCOM failures. Tridion doesn't have any magical influence over how CreateObject works. If you can CreateObject("DLL.Class") succesfully from other VBScript code running on the same server, then there's no reason why it can't work just as well from within Tridion. I'd start by executing your test ...


6

The TDF part of CWA 2011 has specifically changed most of the namespaces so you can still use the old TFD with the new CWA. If you wish to use some utility methods that you were using from old TDF, you're free to keep on using them. TDF was not fully included in CWA 2011. Only the pieces used specifically by CWA were brought to this version. Keep in mind ...


6

The upgrade from Tridion 2011 SP1 to 2013 (SP1 presumably) is fully supported by SDL, well documented and should be quite straightforward. With regards to the upgrade, I would recommend that you do a full audit of the modules and add-on products that you already have, and the APIs that you are currently using, to establish what aspects will need attention ...


6

The issue here appears to be having URL in the Link text. Current implementation of CIL does encode link text but since we have URL, it needs double encoding so that CIS can handle the request. As a workaround, this link text can be encoded before passing it to the API. As a result, the response will contain encoded link text which needs to be decoded again....


5

You shouldn't have Hybrid setups. It is a bad practice to upgrade your environment only partially. Even if as Nuno states you might not find any issue (Tridion typically supports mixed versions of Delivery as a way to help upgrading, it's really not meant to work long term) it is also possible that you might find some. What I would recommend is to upgrade ...


5

It should work if you have a regular Tridion install. However I do see issues in you have installed products like Experience Manager, UGC or any product that is dependent on the Content Delivery Web Service to Push Data or Fast Track Publish. These products need direct connectivity between the CM side and the CD side via a POST method. In case you have ...


5

It depends on what you want to test with your POC. If your goal is functionality or you also want to perform load and performance tests. I would say give your DB the most resources (especially RAM) as possible, since the Publisher and the CM will slow down based on lack of DB resources. Next, I would give resources to the CM box, because the Publisher ...


5

Actually, you can run a 2011 content manager on a 2013 content delivery. Documentation can be found here: http://sdllivecontent.sdl.com/LiveContent/web/pub.xql?action=home&pub=SDL_Tridion_2013&lang=en-US#addHistory=true&filename=StagedUpgradeSteps.xml&docid=concept_2F44AFBC950B4A5FA354DCF035B2524F&inner_id=&tid=&query=&scope=&...


5

Media Manager connector shipped with a "cumulative hotfix" that is needed on Tridion 2011SP1. I do not remember the exact number of this hotfix, but I think it was included with the install files for the Media Manager Connector. If not you can get it from SDL support.


5

The output of the templates is slightly different from the old ones. I suggest you check how the default templates are actually being used on your websites (they are quite ugly, so I would be surprised if they were actually used on your live sites). Perhaps the one to be most concerned about is the Default TBB which had functions that could be used by other ...


5

You can Content Port from earlier versions of Tridion in to SDL Tridion 2013 SP1 - I did this recently, between Tridion 2011 SP1 HR1 and Tridion 2013 SP1. One thing to note is that you will need the Content Porter 2013 SP1 Client to be able to import in to SDL Tridion 2013 SP1. Although SDL Tridion 2013 SP1 now comes with the Import/Export Webservice as ...


5

If memory serves me correctly, LDAP has a limit set for the maximum resultset available to a single query. You could ask your LDAP administrator to increase the maxpagesize on your LDAP server (1000 by default). However, this does not explain why it worked in 2011. Alternatively, you could install the AddUser power tool available to download as part of ...


5

It would be totaly same on cloud environment, only thing where you need to put your effort is domain controller for setting up the LDAP otherwise rest is same. and yes need to open few ports between CMS , DB and CD servers. Usually your architecture vary only for the DTAP environments not wheather you are using cloud or your local servers. Dev Environment -...


5

Thanks to Elena Linhares for putting me on the right track. I queried the TDS_DB_INFO table in the Tridion_Broker database and discovered that it had not been upgraded yet as it was showing version 6.1.xxx Upgrading the Tridion_Broker database in the normal way fixed the exception.


Only top voted, non community-wiki answers of a minimum length are eligible