When performing pre-upgrade check for content manager database from Tridion 2009 SP1 to 2011 SP1 I recieve the following error in manager and log files.
Any clues?
<TdmLog DateCreated="2012-04-19T10:20:26" ApplicationVersion="6.1.0.996">
<Event DateTime="2012-04-19T10:20:26" Id="0" Type="1">
<ErrorCode>0</ErrorCode>
<Description>Tridion Content Management Database Upgrade Analysis</Description>
<Source>MainModule.ProcessScripts</Source>
</Event>
Nuno is right. ErrorCode 0 means no errors, so pre-upgrade was successfully performed and found no issues. If there will be any issue found by pre-upgrade check then you will get error message popup and error code won't be 0.
<ErrorCode>0</ErrorCode> suggests that it's OK? I suspect that this is a success message, maybe double check with Customer Support.
Related
Just recently checked out our teams multidimensional solution from from source control and I am continually getting the error below when VS tries to load the data source view.
I'm running Windows 8, Visual Studio 2013.4 (was on .3 when the error started).
Any help would be greatly appreciated. There's nothing in the event logs and the error message seems to be wildly unhelpful.
Thanks for all of your assistance in advance.
EDIT: Additional note, another team member is having the same issue and we're the only two who have upgraded to Windows 8 so that might be a clue.
===================================
An error prevented the view from loading. (Microsoft Visual Studio)
===================================
Error HRESULT E_FAIL has been returned from a call to a COM component. (msddsp)
Program Location:
at MSDDS.IDdsDiagram.CreateConnector(String ProgID, Boolean Visible, IDdsDiagramObject Src, IDdsDiagramObject Dest)
at Microsoft.DataWarehouse.Controls.Interop.AxMSDDS.CreateConnector(String progID, Boolean visible, IDdsDiagramObject src, IDdsDiagramObject dest)
at Microsoft.DataWarehouse.Design.ComponentDiagram.OnCreateConnector(IDdsDiagramShape startShape, IDdsDiagramShape endShape, Object logicalConnector, UInt32 color, String connectorProgID)
at Microsoft.DataWarehouse.Design.ComponentDiagram.CreateConnector(IDdsDiagramShape startShape, IDdsDiagramShape endShape, Object logicalConnector)
at Microsoft.AnalysisServices.Design.DataSourceDiagram.CreateRelationshipConnector(DataRelation dr)
at Microsoft.AnalysisServices.Design.DataSourceDiagram.ShowOtherConnectorsOnRelatedTables(DataTable dataTable)
at Microsoft.AnalysisServices.Design.DataSourceDiagram.ShowTable(DataTable dataTable, Int32 prefX, Int32 prefY, Boolean delayArrangeTables)
at Microsoft.AnalysisServices.Design.DataSourceDiagram.AfterDeserialize()
at Microsoft.DataWarehouse.Design.ComponentDiagram.SetLayoutInfo(String xml)
at Microsoft.DataWarehouse.Design.ComponentDiagram.OnDiagramControlCreated(DdsDiagram dds)
at Microsoft.AnalysisServices.Design.DataSourceDiagram.OnDiagramControlCreated(DdsDiagram dds)
at Microsoft.DataWarehouse.Design.ComponentDiagram.CreateDdsView(Control parentControl)
at Microsoft.AnalysisServices.Design.DataSourceDesignerView..ctor(DataSourceDesigner designer, DataSourceDiagram diagram, IComponent diagramOwnerComponent)
at Microsoft.AnalysisServices.Design.DataSourceDesignerView..ctor(DataSourceDesigner designer)
at Microsoft.AnalysisServices.Design.DataSourceDesigner.CreateDataSourceDesignerView(VsStyleToolBar pageViewToolBar)
at Microsoft.DataWarehouse.Design.EditorWindow.EnsureViewIsLoaded(EditorView view)
I believe this issue is related to a file version in the BI data tools add-in. While the versions are different in my case, I had exactly the same error.
In my case, I had developed an SSAS solution on Windows 7 with Visual Studio 2010. I checked it into TFS, and a colleague made some changes to it before checking it back in. When I tried opening it again, I received the exact error you've described (the program location was shown as MSDDS.IDdsDiagram.CreateConnector, as well).
My colleague has Visual Studio 2013 and the Visual Studio 2013 BI data tools add-in installed, but made his changes in Visual Studio 2010.
I thought that a file version issue might be the problem, so tried installing Visual Studio 2013 and restarted, then opening the solution in Visual Studio 2010 again - the problem persisted. I then installed the BI data tools add-in that goes with Visual Studio 2013 and restarted. When I opened the solution again in Visual Studio 2010 the problem was resolved, I now receive no error and can see the data source view.
So in short, I believe the problem to be a file used in both the 2010 and 2013 BI data tools add-ins which has changed version.
I realise this isn't an exact solution as your versions are different, but hopefully this is enough information to help you figure out the exact installations (or un-installations) you need to carry out. If this does lead to you resolving the issue (or at least determining what it is), could you post with the details for your scenario in case it helps anyone else?
This can happen if someone edits the project on a machine with a earlier version of Sql Server Data Tools (SSDT). It also seemed to happen once after some system updates. It would appear that the updates registered an earlier version of a key SSDT file.
First, view code on one of the dimensions and look for the following:
Now create a new dimension and look at the same value. Commit all your unrelated changes and backup your project.
If the value for ddsxmlobjectstreaminitwrapper is a higher value, attempt to copy that value from the new dimension to the bad dimension and then reopen the bad dimension in your IDE. It should now work. This would be an indication that the dimension was edited on a machine with an earlier version of SSDT.
If the new dimension has a lower value, as it did for me, it indicated that the machine I was on had an earlier version of SSDT; however, I have the latest version so what I did is re-registered DdsShapes.dll
C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Bin>regsvr32 -u DdsShapes.dll
C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Bin>regsvr32 DdsShapes.dll
References:
https://blogs.msdn.microsoft.com/sqlblog/2015/06/10/ssas-dsv-com-error-from-ssdt-ssas-design-data-source-view/
http://www.delorabradish.com/ssas/ssas-dsv-in-dimension-pane-is-empty-or-you-receive-error-error-hresult-e_fail-has-been-returned-from-a-call-to-a-com-component
After upgrade from Tridion 5.3 to Tridion 2011 SP1, we found that we are not able to access Flash folder from Tridion GUI. Whenever we click on that folder it throws below error and do not display any content, in fact there are more than 100 flash files in that folder.
(80040000) ' ' is an unexpected token. The expected token is ';'. Line 1, position 50.Unable to get list of SDL Tridion Content Manager items.
System.Xml.XmlTextReaderImpl.Throw(Exception)
System.Xml.XmlTextReaderImpl.Throw(String,String[])
System.Xml.XmlTextReaderImpl.ThrowUnexpectedToken(String,String)
System.Xml.XmlTextReaderImpl.ThrowUnexpectedToken(Int32,String,String)
System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean,EntityExpandType,Int32&)
System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32,Char,NodeData)
System.Xml.XmlTextReaderImpl.ParseAttributes()System.Xml.XmlTextReaderImpl.ParseElement()
System.Xml.XmlTextReaderImpl.ParseElementContent()System.Xml.XmlTextReaderImpl.Read()
System.Xml.XmlLoader.LoadNode(Boolean)System.Xml.XmlLoader.LoadDocSequence(XmlDocument)
System.Xml.XmlLoader.Load(XmlDocument,XmlReader,Boolean)
System.Xml.XmlDocument.Load(XmlReader)
System.Xml.XmlDocument.LoadXml(String)
Tridion.ContentManager.Data.AdoNet.ContentManagement.ItemDataMapper.CreateBinaryContentData(IdentifiableObjectData,FieldDictionary)
Tridion.ContentManager.Data.AdoNet.ContentManagement.ComponentDataMapper.ReadPost(TcmUri,FieldDictionary)
Tridion.ContentManager.Data.AdoNet.IdentifiableObjectDataMapper.Read(TcmUri,IDataRecord,IDictionary`2)
Tridion.ContentManager.Data.AdoNet.ContentManagement.OrganizationalItemDataMapper.GetListItemsPost(IDataReader,TcmUri,OrganizationalItemItemsFilterData)
Tridion.ContentManager.Data.AdoNet.ContentManagement.OrganizationalItemDataMapper.Tridion.ContentManager.Data.ContentManagement.IOrganizationalItemDataMapper.GetListItems(TcmUri,OrganizationalItemItemsFilterData)
Tridion.ContentManager.ContentManagement.OrganizationalItem.GetListItemsData(OrganizationalItemItemsFilter)
Tridion.ContentManager.ContentManagement.OrganizationalItem.GetListItemsStream(OrganizationalItemItemsFilter)
Tridion.ContentManager.BLFacade.ContentManagement.OrganizationalItemFacade.GetListItemsXml(UserContext,String,ListFilter,ListColumnFilter)
Tridion.ContentManager.BLFacade.ContentManagement.OrganizationalItemFacade.GetListData(UserContext,String,EnumListKind,ListColumnFilter,String)Folder.GetListItems
This is a tricky one, probably best served by SDL Customer Support. However, if you have access to the server directly, I would try pasting the URI of the folder in question into Internet Explorer (this must be on the CMS server itself). This should give you the XML representation of the folder, and may give you some clues. Perhaps you can post that XML in your question also.
We encountered this error when we upgraded from SDL Tridion 2009 to SDL Tridion 2011.
The resolution that worked for us was removing the Linked Schema from the Folder, refreshing and then re-attaching the linked schema.
One of my application was upgraded from SiteEdit 1.3 SP2 to SiteEdit 2009.Now i am upgrading it again to Tridion UI 2012. I restored both the DLL's cm_SiteEdit.dll and cc_SiteEdit2.dll.
In code inside the templates,objects "SiteEdit" and "SiteEdit2" are accessibly used.Object "SiteEdit2" is initialized properly and object "SiteEdit" is throwing below error -
Error 424 occurred while rendering the page Object required:
'SiteEdit'.
Is it possible to go with this implementation to save the development efforts ? if yes , please help to resolve the issue. otherwise your valuable suggestions/inputs would be most welcomed.
This error is typically thrown because you haven't registered "SiteEdit" as a Script Extension in the SDL Tridion Content Manager configuration. From your description, I gather that it should point to the 1.3 script extension.
Once you do, be sure to restart the Tridion COM+ package for the change to take effect.
Peter has already answered your question still I would like to recommend not to use old SiteEdit object. You should update the template code as per Tridion UI 2012.
I am running Tridion 2011 SP1 and am getting the following warnings in my cd_core.xxxx.xx.xx.log file.
2012-10-17 12:37:50,298 WARN FSTaxonomyDAO - TaxonomyDAO is set to File System, which is not supported. Check your bindings settings and/or license file.
I have removed the following element from the cd_deployer_conf.xml
<Module Type="TaxonomyDeploy" Class="com.tridion.deployer.modules.TaxonomyDeploy"/>
but I am still getting warnings.
I think this problem is causing many of my multimedia components to fail when publishing. If fixing the cause of these warnings doesn't help then I'll have at least narrowed it down.
edit
I forgot to mention that I am using the File System as the Content Data Store
The storage bindings are in cd_storage_conf.xml. You need to check in storage config and should be storage to db. Also you should not remove from deployer if you are using taxonomy.
Update:
Taxonomy storage to file system bindings is not supported as far as I Know it can be only to DB, it is the same from release 2009 and What you are seeing is the WARNING message that you are using non supported. I am not sure if you can disable this binding.
Also, Metadata stored on the local file system is deprecated as of SDL Tridion 2011 SP1, in favor of storage of metadata in the database. SDL Doc reference link.
We did a upgrade from Tridion 5.3 to Tridion 2011 SP1. While checking the Broker database tables we have found that structure and name of BINARIES table is changed.
In Tridion 5.3 we had table called BINARIES with columns PATH and URL, But when we check the same in Tridion 2011 SP1 we cannot find the BINARIES table, rather we have table BINARY which don't have column PATH and URL. In which table we can find PATH and URL columns. Which table is updated when we publish Binary content from Tridion.
The PATH and URL columns are now in the BINARYVARIANTS table.
But be careful of introducing such dependencies on the database structure. SDL publishes an API for accessing the Content Delivery database and most use-cases can be met by using this API.
One of the main advantages of sticking to this public API is that your code will largely be insulated from upgrade problems as the one you are experiencing here. SDL spends considerable effort to keep the API kept backwards compatibly between product releases, while the database structure is changed "at will".