Thursday, July 03, 2008

 

Error: Look up of symbol - ObInitEventAPI failed

If you ever receive an error like this when trying to configure an identity system .NET based PPP event, check the action; chances are it is set to lib instead of managedlib.

"Event API call for the event returned STATUS_PPP_ABORT" Error^base\obport.cpp:845: Error: Look up of symbol - ObInitEventAPI failed - The specified procedure could not be found.%0d%0a.

Labels: ,


Comments:
How to resolve Oblix Bug Report while modifying authorization rules ?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Issue Description
=================
Oblix debug error while trying to modify an authorization rule in Oblix policy if AD group is deleted directly in AD.

Navigation Path:
Oblix Netpoint Access Manager 6.5 --> Policy --> Authorization Rule --> Allow Access tab --> Click Modify

Issue happens if and when an AD group which was added in the policy had been deleted in native AD directly.
Henceforth, if one has to add or remove AD group to the Allow Access tab, user is redirected to Oblix Bug Report Form!

Error Message
=============
Oblix Bug Report Form
An error has occurred while executing the application.
Your browser does not support automatic mail sending.
Please E-Mail to admin@test.com the following information

Your Name
Organization
E-Mail Address
Phone Number
Comment
Make sure to append the following traceback in the mail.
-----------------------------------

Traceback \Oblix\np652\palantir\webplugins\src\policyservcenter.cpp:10745: Error: Exception re-thrown in PolicyServCenCommon::GenModifyAuthorPolicyPage
\Oblix\np652\palantir\webplugins\src\policyservcenter.cpp:12062: Error: Exception re-thrown in PolicyServCenCommon::CreateModifyAllowDenyTable
\Oblix\np652\palantir\dblib\src\group_db.cpp:1267: Error:
\Oblix\np652\palantir\dblib\src\group_db.cpp:1261: Error:

Product NetPoint Access System Version 6.5.5.3 Build FCS1.1
Platform Microsoft Windows NT/2000

Work Around
===========
Manually duplicate the authorization rule - add all the AD groups once again; the drawback is to manually add all the AD groups especially if the number of groups is large, .
Start using the new authorization rule in all policies in place of the problematic authorization rule.

Solution
========

Your say ??
 
You're likely beyond support with this on version 6.5. I'd suggest exploring to see if the issue exists in 10.1.4.2.0 and, if so, pursuing it with Oracle.
 
Post a Comment

Links to this post:

Create a Link



<< Home

This page is powered by Blogger. Isn't yours?