Problem
You attempt to create a new XenDesktop 5.6 deployment with SQL Server 2012 as the back end server but receive the following error when configuring the first desktop delivery controller:
Cannot write Property Collation. This Property is not available on SQL Server 7.0
Clicking on the Details button displays the following error details:
Exception:
System.Reflection.TargetInvocationException Exception has been thrown by the target of an invocation.
at Citrix.Console.Common.CallbackEventArguments.OperationCompleteSynchronizer`1.GetResults()
at Citrix.Console.Common.CallbackEventArguments.OperationCompleteSynchronizer`1.WaitForResults()
at Citrix.Console.DeliveryCenter.UI.Dialogs.FullDesktopDeploymentWizardViewModel.Commit()
at Citrix.Console.CommonControls.Wizard.ViewModel.PageContainerViewModel.CommitProgressOperation.PerformOperationInternal()
Inner exception:
Microsoft.SqlServer.Management.Smo.UnknownPropertyException Cannot write property Collation.This property is not available on SQL Server 7.0.
at Citrix.Console.InteractionCore.ThreadedScript`1.<ExecuteNext>d__9.MoveNext()
at Citrix.Console.InteractionCore.ScriptBase.<ExecuteImplementation>d__1.MoveNext()
at Citrix.Console.InteractionCore.Scheduler.ExecuteNext(ScriptExecution execution)
HelpLink.ProdName : Microsoft SQL Server
HelpLink.BaseHelpUrl : http://go.microsoft.com/fwlink
HelpLink.LinkId : 20476
HelpLink.ProdVer : 10.50.1600.1 ((KJ_RTM).100402-1540 )
HelpLink.EvtData1 : Collation
You’ve gone through the following KBs:
Microsoft SQL 2012 - Citrix Known Issues – 2012
http://support.citrix.com/article/CTX133393
Unable to Create New XenDesktop Site Using SQL 2012 Server
http://support.citrix.com/article/CTX132438
… and proceed to download the:
Shared Management Object Library from:
Microsoft® SQL Server® 2008 R2 SP1 Feature Pack. Installing the Service Pack 1
http://www.microsoft.com/en-us/download/details.aspx?id=26728
Then proceed to install it on the DDC via executing SharedManagementObjects.msi:
… but notice you still get this error:
Solution
The solution was actually quite simple and that was to restart the server.
No comments:
Post a Comment