In a Windows 200X system (Windows 2000, Windows XP, Windows 2003), to start the printer wizard with another user like administration, go to the command line and execute this:
runas /U:administrator "rundll32.exe shell32.dll,SHHelpShortcuts_RunDLL AddPrinter"
Sunday, 7 March 2010
Friday, 5 March 2010
Proclarity: The selected page could not be opened because the cube could not be found
Here's a slightly dated but still fantastic document from Dawn Fink regarding cube could not be found errors. Check out the link near the bottom for a whitepaper on Kerberos Delegation and PAS.
SYMPTOMS:
Opening a book with the Standard Web Client displays a warning message. The message states, "The cube used by this page could not be found" [The selected page could not be opened because the cube could not be found.]. The message also states that the details of the condition have been recorded and sent to the web site administrator and that if immediate assistance is required, contact the administrator.
CAUSE:
The message fundamentally means that the ProClarity Analytic Server (PAS) could not contact Microsoft SQL Server Analysis Services (SSAS) successfully. There are many reasons why this might happen. This article will cover some common issues.
Configuration 1:
PAS is located on a separate machine from SSAS, and IIS authentication is set to "Windows Integrated," and Kerberos Delegation is not configured. This is also known as the "two-hop" problem.
Cause:
Because of intentional security restrictions, it is not possible in to have the OLAP server and PAS server on separate physical machines, use Integrated authentication and have OLAP security respected at the same time - unless you configure Kerberos Delegation.
Resolution:
There are a few possible solutions to this problem.
1. Set the IIS authentication to Basic only. This will allow PAS (IIS) to receive credentials and pass them on to the OLAP server. Note that when this is done IIS will display a warning about credentials being passed in clear text when using this mode - please use SSL to secure Basic traffic.
2. Move SSAS and PAS (IIS) to the same machine. This will eliminate one of the two hops in the two hop problem.
3. Do not use any security settings on SSAS by allowing the Anonymous IIS user access to the cube. This means that everyone will have access to all of the information on the server.
4. Configure your network to use the Kerberos Delegation. Please see the document below.
Configuration 2:
PAS and SSAS are located on the same machine OR they are located on separate machines AND IIS authentication is set to "Basic" and not "Windows Integrated".
Cause:
The user attempting to access SSAS does not have sufficient privileges to access the desired data.
Resolution:
Check the security roles on SSAS at both the cube level and the database level. Be sure the user has access to the data they are attempting to view.
Configuration 3:
PAS and SSAS are located on the same machine OR they are located on separate machines AND IIS authentication is set to "Basic" and not "Windows Integrated" (or you are leveraging the features of Kerberos Delegation). SSAS data has recently been migrated to another machine, the SSAS machine name has changed, one or more of the catalog names have been changed, or one or more of the cube names have been changed.
Resolution:
Please use ProClarity Professional and the Change Connection Information Wizard to verify you are pointing to the correct server, database (catalog), and cube.
http://blogs.technet.com/proclarity/attachment/3172290.ashx
SYMPTOMS:
Opening a book with the Standard Web Client displays a warning message. The message states, "The cube used by this page could not be found" [The selected page could not be opened because the cube could not be found.]. The message also states that the details of the condition have been recorded and sent to the web site administrator and that if immediate assistance is required, contact the administrator.
CAUSE:
The message fundamentally means that the ProClarity Analytic Server (PAS) could not contact Microsoft SQL Server Analysis Services (SSAS) successfully. There are many reasons why this might happen. This article will cover some common issues.
Configuration 1:
PAS is located on a separate machine from SSAS, and IIS authentication is set to "Windows Integrated," and Kerberos Delegation is not configured. This is also known as the "two-hop" problem.
Cause:
Because of intentional security restrictions, it is not possible in to have the OLAP server and PAS server on separate physical machines, use Integrated authentication and have OLAP security respected at the same time - unless you configure Kerberos Delegation.
Resolution:
There are a few possible solutions to this problem.
1. Set the IIS authentication to Basic only. This will allow PAS (IIS) to receive credentials and pass them on to the OLAP server. Note that when this is done IIS will display a warning about credentials being passed in clear text when using this mode - please use SSL to secure Basic traffic.
2. Move SSAS and PAS (IIS) to the same machine. This will eliminate one of the two hops in the two hop problem.
3. Do not use any security settings on SSAS by allowing the Anonymous IIS user access to the cube. This means that everyone will have access to all of the information on the server.
4. Configure your network to use the Kerberos Delegation. Please see the document below.
Configuration 2:
PAS and SSAS are located on the same machine OR they are located on separate machines AND IIS authentication is set to "Basic" and not "Windows Integrated".
Cause:
The user attempting to access SSAS does not have sufficient privileges to access the desired data.
Resolution:
Check the security roles on SSAS at both the cube level and the database level. Be sure the user has access to the data they are attempting to view.
Configuration 3:
PAS and SSAS are located on the same machine OR they are located on separate machines AND IIS authentication is set to "Basic" and not "Windows Integrated" (or you are leveraging the features of Kerberos Delegation). SSAS data has recently been migrated to another machine, the SSAS machine name has changed, one or more of the catalog names have been changed, or one or more of the cube names have been changed.
Resolution:
Please use ProClarity Professional and the Change Connection Information Wizard to verify you are pointing to the correct server, database (catalog), and cube.
http://blogs.technet.com/proclarity/attachment/3172290.ashx
Subscribe to:
Posts (Atom)