- Products & services Products & services
- Resources ResourcesCustomer resources
- Customer resources
- Customer support Find more information about engaging support and get help
- Services guide Find more information about working with Services teams
- Free resources Leverage our free tools and trainings
- Modernize to Identity Security Cloud Transition to the cloud for advanced capabilities and a future-ready security posture
Learning- Learning
- Identity University Get technical training to ensure a successful implementation
- SailPoint professional certifications & credentials Advance your career or validate your identity security knowledge
- SailPoint recertification program Get recertified by demonstrating ongoing learning
- Training onboarding guide Make of the most of training with our step-by-step guide
- Training FAQs Find answers to common training questions
- Community Community
- Compass
- :
- Discuss
- :
- Community Wiki
- :
- IdentityIQ Wiki
- :
- Why do I get null pointer in method invocation error?
- Article History
- Subscribe to RSS Feed
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Content to Moderator
Why do I get null pointer in method invocation error?
Why do I get null pointer in method invocation error?
Product
IdentityIQ
Environment
All
Error
Null pointer in method invocation BSF info: <RULE NAME> at line: 0 column: columnNo
Root cause
The rule indicated by this error message is incorrect.This is due to incorrect coding or using a rule that has deprecated method in it. Fortunately, BSF directs you to the cause of the exception. After the colon and before the word"at", you will see the name of the custom coded rule which causes this error message. Here, I inserted <RULE NAME> as an example.
Workaround/Fix
IdentityIQ Support team is unable to support the various, site specific custom coded rules. There is an Expert Services Group that does such work, which can be contracted by asking your Account Manager to assist you in gaining a resource.
This debugging article should assist you in quickly finding the root cause of your rule error:
