cannot deploy an assembly to a Multidimensional instance from CTP3 - by GregGalloway

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 698559 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 11/2/2011 1:03:58 PM
Access Restriction Public


Go to the following URL:

Download the SQLQuery assembly.

Open SSMS from Denali CTP3. Connect to a SSAS Multidimensional instance. Right click on the Assemblies folder and choose New Assembly and choose that unzipped DLL. Then click OK. You get the error message:


Clr Assembly must have main file specified.

Program Location:

   at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection impacts, Boolean expectEmptyResults, Boolean throwIfError)
   at Microsoft.AnalysisServices.AnalysisServicesClient.Create(IMajorObject parent, IMajorObject obj, ObjectExpansion expansion, ImpactDetailCollection impact, Boolean allowOverwrite, XmlaWarningCollection warnings)
   at Microsoft.AnalysisServices.Server.Update(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
   at Microsoft.AnalysisServices.Server.SendUpdate(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
   at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options, UpdateMode mode)
   at Microsoft.AnalysisServices.ManagementDialogs.OlapRegisterClr.SendDataToServer()

Sign in to post a comment.
Posted by GregGalloway on 2/21/2013 at 12:38 PM
We found another way of generating this error. Trying to create the assembly from a network drive:
Posted by GregGalloway on 2/12/2013 at 7:16 PM
Another way of generating this error message is by using the wrong version of SSMS to create the assembly. For example, let's say you use SSMS2008 to connect to an SSAS2012 server and try to create an assembly. You'll get this error message. If you do the same from SSMS2012 then it should work.

See this thread here:

And see this KB article and specifically Resolution #2 it lists which says to use SSMS2012:
Posted by Christian_B on 11/11/2011 at 3:50 AM
Hi Ashwini - I can confirm that this does resolve the problem. As soon as the file was Unblocked, I was able to add and call the dll.

Posted by Microsoft on 11/10/2011 at 4:33 PM
Hi Greg,

This isn't something AS 11 is doing explicitly, but I believe our move to .Net 4.0 causes this.

Posted by GregGalloway on 11/9/2011 at 6:11 PM
You're right! Thank you for clarifying.

Is unblocking the file something new since AS2008 R2? On an AS2008 R2 instance on Win2008 R2, it doesn't appear you have to unblock the DLL first. The reason I ask is because we'll need to document this change in the install instructions for the ASSP project.

Thanks for the help, Ashvini. Sorry for the false alarm.
Posted by Microsoft on 11/9/2011 at 11:34 AM

We're able to deploy SQLQuery.dll after unblocking it from the file properties in Windows Explorer. Can you confirm?

Ashvini Sharma
Program Manager
Analysis Services
Posted by Microsoft on 11/4/2011 at 1:10 PM
Hi Greg, thanks for reporting this issue. We are taking a look.

Cathy Dumas