The one workaround I've noticed is to open the database directly in BI Studio, and make the changes there, but this is obviously less than ideal for multiple reasons.
hello,
i'd suggest to check what's the deployment server specified in your project and whether it's as expected. right click on the project node in solution explorer, and go to Properties->Deployment, Target->Server.
also, it should be possible to use SQL Server Profiler to start a trace for the specific AS server, and see what happens on the server when you do a Build->Deploy Solution...
hope this helps,
|||The target server is just "localhost" (which is correct). When I put profiler on it, I can see the large XMLA deployment script, but it doesn't reveal anything about the current status..|||Ok. I created a fresh, new, import from 9.0 project, and made my changes there. Now when I tried to deploy it actually looks like it's doing something (i.e. there's activity in profiler, and the deployment progress tab actually shows what dimensions/measure groups are being processed..)Very weird.|||Restart the Analysis Services Service on the target deployment server (if possible) before you try to deploy the roject again and see what happens. Seems like something may be hanging up the service when this happens.
No comments:
Post a Comment