I have a fairly simple custom assembly for adding some functions to a cube. Having a reference to the assembly in the cube project causes the following error when I try and run the aggregation wizard for the cube:
Message: Errors in the metadata manager. The system assembly cannot be modified by a user request. To restart the process, resolve the problem and then click start.
I get the message after the "Specify Object Counts" step, when it starts the process of determining the aggregations.
Is this a bug or is there something I need to do in the custom assembly differently I started with the code framework from the AdventureWorksAMO sample project, and added/removed functions.
Custom Assembly generates error in Aggregation Wizard
RWP
After applying SP1, I now get the following error when running the aggregation wizard:
"clr assembly must have main file specified"
The workaround is to remove the assembly reference and then run the aggregation wizard, and then re-add the assembly reference.
Although this works, it bring into question why the error in the first place Any CLR assembly I've tested causes the same problem.
Anonymous34134
This error will be fixed in the next SP, meanwhile the work-around is indeed to remove the assemblies and add them back after designing aggregations.
About why the error happens in the first place:
- when ran from BI development studio, the aggregation design wizard can have unsaved changes in the background (in the cube and/or dimension editors). or the entire BI project database might not have been deployed
- the wizard requires the database to be saved to the server in order to use the aggregations designing algorithm, so it does temporarily deploy the database (in a transaction that is being rolled back at the end); this is where the error about the assemblies happens
Adrian Dumitrascu