Every time I want to use the Publishing Queue, I have to change User to myself then show the tasks. Tridion knows who I am, so why can't the form automatically display with my name selected?
This is a defect in SDL Tridion 2011 GA (I believe it worked in most versions of R5 and Tridion 2009). It is fixed in SDL Tridion 2011 SP1, so you best bet is to upgrade to the latest release.
Related
Rumor has it (see Publishing ends up publishing many Components and runs out of memory for example) that custom resolvers are available in Tridion 2009. My question: how can you configure one without a TridionContentManager.config? Or am I completely off track and DOES 2009 come with this config file?
On my 2009 test system it's there (in the same location as 2011).
<Tridion Home>/config/Tridion.ContentManager.config
We installed Microsoft Visio 2010 Premium on the Tridion 2011 SP1 CMS Server. We also installed Tridion Workflow designer plug in available in Tridion 2011 SP1 installer. When we try to access this add-on in Visio 2010 it is displayed under "Inactive Add-on's List"
How to activate this add-on so that we have upload workflow to CMS server and use it?
First step, make sure that it is properly enabled:
1.- Go to the Tools menu, click Trust Center, and then click Add-ins.
2.- In the Add-ins box, at the botton select COM Add-ins and click Go
3.- Select the check box for the TCM Workflow Add-in
If this is not working, play with the other options of the Trust center, as there is some setting in it, that is blocking it from being loaded
In Tridion 5.3 SP1 version we use SiteEdit.ComponentPresentation(objCP) to display editable component presentation on page.
This is working fine in Tridion 5.3 SP1. We are migrating to Tridion 2011 SP1 so wanted to confirm that this function still exists in Tridion 2011 SP1 or its deprecated?
If its deprecated then let us know the alternate function for the same.
Upgrading from SDL Tridion R5.3 to SDL Tridion 2011 is not a step to take lightly but it is a supported path. The first thing you should focus on is the changes in product prerequisites on SDL Tridion 2011 SP1. SiteEdit is also still supported (even on VBScript templates) but for SDL Tridion 2011 SP1 its is a complete newer version of the product named User interface update for SDL Tridion 2011 SP1 (login required see here for details). Since you are coming from SiteEdit 1.3, you should contact Customer Support about getting the SiteEdit Script Extension DLL for the upgrade from SiteEdit 1.3, since the documentation only mentions it from SiteEdit 2009 SP3.
The upgrade process itself is described in our documentation (login required see here for details). Robert Curlette also wrote a nice Blog article about the upgrade to SDL Tridion 2011.
The most important things to understand here is the big step you are going forward, from your example code I see you are still using VBScript templates, which are still supported in SDL Tridion 2011 SP1, but they are deprecated so you should be looking into replacing them with our new template models. However SDL Tridion does not recommend you to include this in the upgrade project, because this would make the project too big and possibly unmanageable.
Probably the best advice I can give you for such an upgrade is to contact SDL Tridion Professional Services and have them do an upgrade scan, which will point out all the pain-points of this upgrade. Then they can also advice you the best way forward as depending on the details of your implementation, the details of the upgrade process might be different as well (like should you stay on VBScript templates or does it make sense to upgrade them, what to do with your event system and your extensions or customizations etc.).
I am trying to set my new laptop up with a developer installation of MS Dynamics AX 2009.
I start by installing MS SQL Server 2008 R2, this goes in fine, I create a new database in here.
I then launch the AX 2009 setup, I firstly install the Application Files, go through this, all is OK.
I then re-launch the AX 2009 setup, installing the AOS, I login using a specific username / password setup for the AOS.
I then re-launch the AX 2009 setup and install the Client and Debugger.
When I go to launch the AOS in Services the service gets 'stuck on "Starting" and after 5/10/15 minutes waiting and refreshing nothing happens?
Do I need to install the Database files in the AX 2009 setup as well?
Many thanks...
Yes you need to have an AX 2009 database. Either install it via the AX 2009 installer or deploy the contoso example database from Microsoft. Easier to install from the installer.
The first start of the AOS can take some time, but if you don't have a database, I can't imagine how it would work.
Go to (Administrative Tools>Microsoft Dynamics AX 2009 Server Configuration) and click the database tab of your instance, and what does it have? Does that database exist or is anything selected?
You should check the windows event viewer under "applications" to see issues during service startup.
/This isn't really code btw...
We recently upgraded our biztalk server 2006R2 to SP1. The problem is that we're having some small issues now, for example the administration console crashes when I browse for a folder if I want to make a file send/receive port.
Any idea what might cause this problem?
I'm having no problems when I browse for a folder with our normal explorer and then copy paste its address into the biztalk folder browser.
Make sure you update towards the latest CU for your service pack.
For BizTalk 2006 R2 with SP1, this is CU4.
See http://support.microsoft.com/kb/2682056 for more information on CU4 for BizTalk 2006 SP1.
If this still does not help, there is a temporary workaround to export/import bindings of existing receive locations/send ports with a FILE adapter. This allows you to still create the ports/locations you need and unblocks the situation.
In any case, if the problem persists, you might want to check with Microsoft about the issue.
That is in case your license includes the extended support option which lasts until 12 July 2016.
If you don't have extended support, the support ended on July 11th 2011 I'm afraid...