Showing posts with label SSAS. Show all posts
Showing posts with label SSAS. Show all posts
Can not insert a level from SSAS cube into Report Studio crosstab
You might run into strange Cognos Report Studio behavior when inserting a level of a hierarchy into a crosstab. First time you drag and drop the level it does nothing and the second time it would generate a warning/error that some insert operation is already in progress, like the one below:
Problems with SSAS role creation are soon to be history
It used to take for ever, I would always make some careless mistake and would always dread the day when I had to create many SSAS security roles or, even worse, make changes to the existing ones. Well, soon enough we will no longer have to worry about this little annoyance. Check out SSAS role management tool easyROLES! It is currently in beta and you can sign up for testing if you want.
Here is a video showing how fast it is to create many SSAS roles with the tool:
Fast and painless!
Here is a video showing how fast it is to create many SSAS roles with the tool:
The whole concept is based around the idea that you always get some kind of access list from "the business" according to which you set the roles up. So, why not just copy/paste the specs and let the machine do the dirty work? Try in test environment, verify that all looks as it should, paste into production and be done with it.
Fast and painless!
Cognos promptmany and SSAS member unique name
When you want to supply prompt values to a Cognos Report Studio report via URL (or for any other reason it is only possible to pass through values as plain text ID's and not member unique names) dealing with the parameters might not be as straight forward as it seems in the beginning. As an example let us use CRM application that links customer ID to a sales report in Cognos BI. That means we would be running the Cognos report via a url that looks similar to this:
http://servername.yourcompany.com/ibmcognos/......&p_CustomerID=302156
http://servername.yourcompany.com/ibmcognos/......&p_CustomerID=302156
Kerberos and other things you need for fully functional authentication of SSAS through Cognos (Part 2)
So far we have set up our OS and it is ready to use Kerberos for user authentication in Cognos and SSAS cubes displayed within Cognos. Now it is time to take a look at the web server configuration.
Kerberos and other things you need for fully functional authentication of SSAS through Cognos (Part 1)
In previous post I gave a little overview of what needs to be done in order to get Kerberos authentication working between your Cognos and Microsoft SSAS environments. Now we will look into the Windows related bits and pieces of the process.
Kerberos and other things you need for fully functional authentication of SSAS through Cognos (Intro)
Kerberos is one of the topics that gives the creeps to most BI folks... The setup is seriously full of strange abbreviations and vaguely explained features which might look scary the first time you encounter them (sure got me confused...). Anyhow, upcoming will be a series of posts with which I will try to demystify Kerberos setup for your Cognos installation so you can finally enjoy a fully functional data level security setup in your SSAS cubes.
The end of yk-err-0001 story
I was whining a lot lately about yk-err-0001 error in Cognos related to Microsofts SSAS and Cognos load balancing. Today is time for the final chapter of this babble! It has finaly been solved- for real this time!
If you're currious, here is the original post with a temp workaround solution. If you are ready to fight this issue till the end - grab a seat and read on ;)
Why a seat? Because it's a lot of work waiting for you :)
To be realy honest, after loosing all hope to solve this matter in a civilized way, we did a mass cleanup- completely reinstalled OS on all servers and at the same time upgraded Cognos to version 8.4.1. That is it! No more issues with SSAS and load balancing! Have no idea whether it was general reinstall that helped or if it was the version upgrade that fixed a mysterious bug in Cognos load balancer... But the whole thing was surely worth the effort!
More details on the upgrade from 8.4 to 8.4.1 are getting ready to be published any day now. Want a sneak preview- no major pitfalls!
M.
If you're currious, here is the original post with a temp workaround solution. If you are ready to fight this issue till the end - grab a seat and read on ;)
Why a seat? Because it's a lot of work waiting for you :)
To be realy honest, after loosing all hope to solve this matter in a civilized way, we did a mass cleanup- completely reinstalled OS on all servers and at the same time upgraded Cognos to version 8.4.1. That is it! No more issues with SSAS and load balancing! Have no idea whether it was general reinstall that helped or if it was the version upgrade that fixed a mysterious bug in Cognos load balancer... But the whole thing was surely worth the effort!
More details on the upgrade from 8.4 to 8.4.1 are getting ready to be published any day now. Want a sneak preview- no major pitfalls!
M.
One more SSAS in Cognos 8.4 issue
One more thing (kind of related to previous SSAS in Cognos mess) is failure to establish first connection.
The symptom is never finished first report of the day. After the session to SSAS dies, the first user that runs a report against it might be getting the never ending spinning sand watch cartoon...
So far the only solution is to cancel and start the report again. Brilliant, huh?
Looking forward to try this out in 8.4.1... Might even start praying a bit...
M
The symptom is never finished first report of the day. After the session to SSAS dies, the first user that runs a report against it might be getting the never ending spinning sand watch cartoon...
So far the only solution is to cancel and start the report again. Brilliant, huh?
Looking forward to try this out in 8.4.1... Might even start praying a bit...
M
Error YK-ERR-0001 Resolved - NOT!
UPDATE: Finally this issue can be solved. Click here to read the solution.
No solution from the great vendor for the SSAS issue from early March... Still 'limping' on one server...
Just to make it clear- it is possible to work arround the issue. Check out the solution here.
No solution from the great vendor for the SSAS issue from early March... Still 'limping' on one server...
Just to make it clear- it is possible to work arround the issue. Check out the solution here.
ERROR:YK-ERR-0001 Multiple server environment IBM Cognos and Microsoft SSAS
UPDATE: Finally this issue can be solved. Click here to read the solution.
You might be lucky enough and come across strange behavior in a multiple server Cognos environment, when trying to work towards Microsofts SSAS cubes as data sources.
It shows up by randomly failing to establish the connection from one of the application servers to 2005 Analysis Services client. So if you go into the connection details (in Cognos Administration) and try testing it by selecting all of your application servers, the resuld would look simmilar to this:
If you try the same action again, it will either fail on the same server or might fail the other one absolutely randomly.
The error code is YK-ERR-0001 and it is whining about not being able to establish connection to the server. But it actualy manages to do that sometimes (schizo? :) ).
Anyway, at this point in time there is no info at IBM Cognos regarding this matter. We solved it by routing the package to only one application server using Advanced Dispatcher routing properties (RTFM here). Assign one of your application servers to a unique group and route all traffic from your SSAS package to that new group.
Not the perfect solution as it eliminates the loadbalancing, but it works for now and eliminates the symptoms completely.
Got better ideas? Share in the comment section!
//MxD
You might be lucky enough and come across strange behavior in a multiple server Cognos environment, when trying to work towards Microsofts SSAS cubes as data sources.
It shows up by randomly failing to establish the connection from one of the application servers to 2005 Analysis Services client. So if you go into the connection details (in Cognos Administration) and try testing it by selecting all of your application servers, the resuld would look simmilar to this:
The error code is YK-ERR-0001 and it is whining about not being able to establish connection to the server. But it actualy manages to do that sometimes (schizo? :) ).
Anyway, at this point in time there is no info at IBM Cognos regarding this matter. We solved it by routing the package to only one application server using Advanced Dispatcher routing properties (RTFM here). Assign one of your application servers to a unique group and route all traffic from your SSAS package to that new group.
Not the perfect solution as it eliminates the loadbalancing, but it works for now and eliminates the symptoms completely.
Got better ideas? Share in the comment section!
//MxD
Subscribe to:
Posts (Atom)