Error Retrieving User By Identity Hyperion
PMNo score for this postAbi from IP address 208.240.243.170Hi All, We have Business rules which do not take more than a minute to run. This BR works sometimes and sometimes it does not (and both times i'm not doing anything different). It gives the following error through the web "An error occurred while running the specified calc script. Check the log for details." On running Planning in the forground mode i found out that whenever the user is not able to run the BR this error would show up INFO [ACTIVE] ExecuteThread: '3' for queue: 'weblogic.ke rnel.Default (self-tuning)' com.hyperion.hbr.plugin.essbase.EssbaseMetadataServe rElement - Cannot connect to olap service. Cannot connect to Analytic Server. Er ror:Analytic Server Error(1200332): Error parsing formula for [REGION DEFINITION] (line 0): invalid number format Application Log: [Tue Jan 22 09:31:02 2008]Local/Expense/xxx/Error(1200332) Error parsing formula for [REGION DEFINITION] (line 0): invalid number format [Tue Jan 22 09:31:02 2008]Local/Expense/xxx/Error(1200332) Error parsing formula for [] (line 0): invalid number format [Tue Jan 22 09:31:02 2008]Local/Expense/xxx/Warning(1080014) Transaction [ 0x10e000b( 0x47962856.0xb30cb ) ] aborted due to status [1200332]. And the next moment the BR would run just fine :) Any help is apprechiated thanks Scoring disabled. You must be logged in to score posts.Respond to this messageAuthorReplySeb121.217.151.28More logsNo score for this postJanuary 25 2008,1:43 AMHi, Anything in the HBRClient and HBRServer.log?? What about the Planning log?? Can you reproduce the error if you launch the HBR from the AAS console instead of Planning web? Sounds like it cant connect to Essbase for some reason. Also you may want to check your database cache settings and make sure they are optimised. SebScori
Versions NUMSysCMDLauncher 1.0 Essbase Member Operations Essbase Member Operations 1.4 Older Versions Essbase Member Operations 1.3 Essbase Member Operations 1.2 Essbase Member Operations 1.1 Planning Client Utils Planning Client Utils 1.0 EsbImportTextList EsbImportTextList 1.1 Older Versions EsbImportTextList 1.0 jMnDLoader jMnDLoader 1.0 Oracle - Hyperion Labs Explore more Explore more Menu Home » 11.1.2 » Workforce issue while enabling custom dimension Search for: Archives Archives Select Month October 2016 (1) September 2016 (6) August 2016 (5) July 2016 (3) June 2016 (1) May 2016 (1) March 2016 (3) February 2016 (2) January 2016 (2) December 2015 http://www.network54.com/Forum/58296/thread/1201134375/Strange+behaviour+with+HBR++(Planning+931) (1) October 2015 (4) September 2015 (2) August 2015 (1) July 2015 (2) June 2015 (1) May 2015 (2) April 2015 (2) March 2015 (3) February 2015 (1) January 2015 (3) December 2014 (2) November 2014 (3) October 2014 (4) September 2014 (3) August 2014 (1) July 2014 (2) June 2014 (1) May 2014 (1) April 2014 (2) March 2014 (1) February 2014 (1) January 2014 http://www.orahyplabs.com/2011/05/workforce-issue-while-enabling-custom.html (1) December 2013 (2) November 2013 (2) October 2013 (3) September 2013 (3) August 2013 (2) July 2013 (3) June 2013 (2) May 2013 (3) April 2013 (5) March 2013 (2) February 2013 (2) January 2013 (2) November 2012 (2) October 2012 (2) September 2012 (2) August 2012 (2) July 2012 (2) June 2012 (2) May 2012 (1) April 2012 (2) March 2012 (2) February 2012 (2) January 2012 (3) December 2011 (3) November 2011 (3) October 2011 (3) September 2011 (2) August 2011 (2) July 2011 (4) June 2011 (4) May 2011 (3) April 2011 (4) March 2011 (4) February 2011 (3) January 2011 (2) December 2010 (3) November 2010 (5) October 2010 (5) September 2010 (4) August 2010 (3) July 2010 (5) June 2010 (3) May 2010 (6) April 2010 (7) Categories 11.1.2 (6) 11.1.2 Planning (5) 11.1.2.3 (4) 11.1.2.4 (1) API (17) ASO (5) Attributes (1) Awesomeness (4) Batches (17) BatchScheduler (1) biography (2) Calc Manager (17) Capex & Workforce (2) CDF (9) Changes (1) CloudMap (1) Console (1) CRM (1) CSSImportExport (1) Customization (9) DATAEXPORT (2) DataForm (4) Discovery (1) EAS (4) Encryption (2) Endeca (1) EPM (2) EPMA (4) Essbase (57
computer PitStop Library error code 8006 Index ImportSecurity.cmd - Error retrieving user -0001-11-30 Views:1 Body Advertisement Hi, I am trying to import the Secfile.txt with http://www.amicuk.com/importsecurity-cmd-error-retrieving-user/ the security settings using the ImportSecurity.cmd command. When I run the command I get the following message (after a successful logon) WARN main com.hyperion.hbr.security.HbrSecurityAPI - Error retrie Hi, I am http://www.rittmanmead.com/blog/2010/11/oracle-bi-ee-11g-security-integration-with-microsoft-active-directory/ trying to import the Secfile.txt with the security settings using the ImportSecurity.cmd command. When I run the command I get the following message (after a successful logon) WARN main error retrieving com.hyperion.hbr.security.HbrSecurityAPI - Error retrieving user by identity Henceforth none of the security gets imported. Mon Jun 22 14:37:51 BDT 2009 :: Total Rows Provided=286 Added Successfully for=0 Mon Jun 22 14:37:51 BDT 2009 :: Logging off from application .... Mon Jun 22 14:37:51 BDT 2009 :: Logged out of the application. Mon Jun 22 14:37:51 BDT 2009 :: Import security error retrieving user Completed successfully. Can anyone please help regarding this? Shehzad The replay answer Advertisement John, I have checked the import using just one line in the secfile.txt file and it still doesn't work. I'm adding the first few lines of the output to illustrate that the utility logs in correctly and the error I get for each line being imported. And also apologies for my english. Henceforth isn't a user. The user I am using to login to the system is admin user. I've also tried it with other administrative users ensuring that they were the application owners as well. I have tried adding users and groups to the Secfile.txt but I still have no success. Mon Jun 22 15:37:56 BDT 2009 :: The length of the string:: 1 Mon Jun 22 15:37:56 BDT 2009 :: Validating the Secfile.txt... Creating rebind thread to RMI Mon Jun 22 15:37:56 BDT 2009 :: Logging into the application Setting Arbor path to: E:\Hyperion\common\EssbaseRTC\9.3.1 Setting HBR Mode to: 2 HBR Logging Config File : HBRServer.properties 2009-06-22 15:37:58,640 WARN main com.hyperion.hbr.security.HbrSecurityAPI - Err o
as a framework for security in BI EE. In BI EE 10g, integration with external LDAP security had to be done through the use of Init Blocks and LDAP Servers setup within the repository. In BI EE 11g, the older method of integration is still supported and will work. But the recommended approach is to setup the LDAP as a security provider in Weblogic. In today's blog post, we shall see how to go about setting up Active Directory as a security provider in Weblogic. When we install BI EE 11g, a Default Security provider is configured out of the box. So, any new user/group that we add to the Default Security Provider can be assigned to Application Roles directly. To change the Default Security Provider to an Active Directory Provider we will have to follow the steps outlined below. First step is to make sure that we are changing the Control Flag property of the Default Security provider from SUFFICIENT to OPTIONAL. This step ensures that we can have users coming in from other Providers as well. This is done from the Admin Console (http://localhost:7001/console) After this, the next step is to add a provider to Weblogic to connect to the Active Directory instance. This step requires us to know 4 main Active Directory Properties 1. Base DN - The base path from where the LDAP search will happen (for users & groups) 2. Bind DN/Principal - This is the Active Directory Administrator user DN that has the privileges to get all the users/groups from the Base DN. Also the password for this user will be required. 3. Active Directory ServerName & Port 4. User Attribute - This attribute is what will be extracted as the username for the users residing in Active Directory. For AD, the attribute name will be sAMAccountName. Before making any change in Weblogic, ensure that you have all the properties identified correctly. To ensure whether we have got all the properties correctly, there are a couple of methods. 1. In the first method, create a dummy LDAP server connection to Active Directory using the traditional 10g method. This will help us in validating the connection. In my case, the properties that i have are Base DN: CN=Users,DC=venkatad,DC=venkatlap,DC=com Bind DN: CN=Administrator,CN=Users,DC=venkatad,DC=venkatlap,DC=com AD port: 389 (Default LDAP port without SSL) User Attribute - sAMAccountName (this does not change across instances) Lets test this out from the LDAP Server setup within the rep