Cannot Find Session Info in Baan and Infor LN: Causes and Fix
cannot find session info
Also searched as
- cannot found session info
- baan cannot find session info
- infor ln session info not found
- baan session not in runtime data dictionary
Short answer
This message means the bshell could not find the definition of the session you tried to start in the runtime data dictionary for your package combination. Check that the session exists in a VRC in your package combination, then convert the data dictionary to runtime again for that VRC and restart the user session.
Applies to: Baan IV, Baan 5 and Infor LN 10.x on-premise. The exact wording and session names may differ slightly between versions.
How to fix cannot find session info
- 1Note the exact session code the user tried to start and the user's package combination.
- 2Check that the session exists in the session definitions of a VRC that is part of that package combination.
- 3Check the user's package combination and VRC derivation: a session in a VRC outside the chain is invisible to the user.
- 4If the session was imported or changed recently, run the convert to runtime data dictionary session for the VRC and wait for it to finish.
- 5Have the user log out fully and start a new session so the runtime dictionary is re-read.
- 6If it persists, compare against a user who can start the session to find the difference in package combination or authorization.
What the bshell is looking for
When a session starts, the bshell looks up its definition in the runtime data dictionary built from the session definitions in the VRCs of the user's package combination. The runtime dictionary is a compiled copy, so changes to the definition only take effect after a conversion. If the definition or the runtime copy is missing the lookup fails with this message.
That makes the typical causes simple: a wrong or incomplete package combination, a session that was never imported to the VRC, or a runtime dictionary that was not rebuilt after an import or a patch.
Package combination and VRC problems
Each user belongs to a package combination, and each package in it is tied to a VRC (version, release, customer). Customer VRCs derive from standard ones. If a customization is in a customer VRC that the user's combination does not include, the user will not find it even though a colleague does.
After upgrades and solution installs check the combinations of all users, not just the administrator who tested.
Rebuilding safely
Convert to runtime in a quiet period if you can, since the process touches shared files and users may need to restart. Check the log for errors. If the convert reports errors, fix them before expecting the message to go away, and keep a backup of the dictionary files before large imports.
Try it here, free
Infor LN and Baan ERP Table List by Package
Filterable list of commonly used Infor LN and Baan tables by package, with the naming convention, key fields and where a Baan IV table differs from LN.
Common pitfalls
- !Converting the wrong VRC and wondering why nothing changes.
- !Testing only as the administrator, whose combination differs.
- !Not asking users to log out fully after the convert.
- !Importing solutions without checking convert errors.
How an ERP-grounded AI assistant handles this
Because this error depends on package combinations and VRC derivation, an assistant that can read those definitions can tell you which VRC lacks the session and which users are affected. Netray's agents stay read-only on the environment; the convert is run by your administrator.
Frequently asked questions
What does cannot find session info mean?
The bshell could not find the definition of the session in the runtime data dictionary for the user's package combination.
Why does it work for one user but not another?
They have different package combinations or VRC chains, so one of them cannot see the VRC that holds the session.
Do I need to restart the server?
Usually no. Reconvert the dictionary and have users start new sessions, unless the vendor guidance for a patch says otherwise.
Is this a data corruption problem?
Rarely. It is normally a configuration or conversion issue, but check disk space and convert errors if it keeps returning.
Related
Infor LN 'unable to create a session': causes and how to fix it
This message means the client reached LN but the server could not start the session process (a bshell) or could not load the session. Work from the server side: check the bshell log, licence and user limits, the user's authorizations, and whether the session or its dependent objects exist and are compiled.
Error fixInfor LN Not Authorized to Run This Session: How to Fix It
Infor LN refuses to open a session with a not authorized message when the logged-in user's assigned role does not include that session, or when the session is blocked for the company they are logged into. Grant the session through Common > Authorization Management > Roles, or check the user's role and company context, and the session opens on retry. In most cases this is a permissions configuration issue, not a bug.
How-toHow to Check the Infor LN Version and Current Package VRC
An Infor LN installation has four separate version facts: the application release and feature pack, the porting set that carries the bshell and database drivers, the package VRC that each user or company runs, and the installed solutions. The release is shown in the Help > About dialog of the client, the package VRC in the Tools package administration sessions, and the porting set on the server through the installation tooling.
Error fixInfor LN bshell Process Stuck at 100% CPU: How to Diagnose and Fix It
A bshell process pinned at 100% CPU on the Infor LN application server almost always means one session is stuck in a 4GL loop, scanning an unindexed table, or waiting on a database lock. End the session from the Sessions Monitor first, then kill the OS process only if that fails, and check for a blocking database transaction before assuming it is a bug.
Error fixInfor LN DAL Out of Sync After a Custom Field: Cause and Fix
Infor LN throws a DAL, or table, out of sync error, or simply drops a new custom field silently, when a table's dictionary definition is changed but the generated DAL and dependent forms are not regenerated afterward. Running the standard sequence, table compile, DAL generation, then session/form compile, in Tools > Development after every dictionary change resolves it. Skipping any one of the three steps is what causes the mismatch.
Error fixInfor LN Jobs Stuck in Active or Waiting: Fix the Job Daemon
Infor LN background jobs, reports, batch processes and print jobs, get stuck in Active or Waiting status when the job daemon on the enterprise server has stopped or lost its connection, or when a prior job crashed without releasing its status. Restart the job daemon and reset the stuck job's status through the Jobs session, and the queue resumes. A daemon that keeps stopping usually points to a memory, license or database connectivity problem on the server.
AI for ERPAI for Legacy Baan IV/V: Capture the Knowledge Before It Walks Out the Door
Use AI to capture knowledge from ageing Baan IV/V systems, document undocumented customisations, and de-risk a future migration to LN or CloudSuite.
AI for ERPAI for Infor LN: Sessions, BODs, and Engineer-to-Order Work
Add grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.
Stuck on Infor LN / Baan?
Talk to engineers who work inside Infor LN / Baan every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Infor LN and Baan ERP Table List by PackageFilterable list of commonly used Infor LN and Baan tables by package, with the naming convention, key fields and where a Baan IV table differs from LN.
- Infor LN Session and Module Code ReferenceSearchable list of the Infor LN / Baan package and module codes (tisfc, tdsls, whinh and others) with what each one covers.
- Infor LN 4GL Session Script TemplateGenerate a clean Baan / Infor LN 4GL session script skeleton with declaration, field, choice and table I/O sections.
ERP fixes and how-tos
- How to Check the Infor LN Version and Current Package VRCFind your Infor LN version, feature pack, porting set and current package VRC from the About box, Tools sessions and the server shell, and learn how to read them.
- Infor LN 'unable to create a session': causes and how to fix itFix Infor LN or Studio failing to create a session: bshell start-up, licensing, authorizations, session code and server-side logs to check, in order.
- Infor LN General Table Maintenance: Finding and Editing Tables SafelyWhere general table maintenance sits in Infor LN, how to find the right session for a table, and how to change table data safely, no direct DB edits.
Guides
- AI Integration with Infor LN and Baan: A Technical GuideIntegrate AI with Infor LN or Baan: ION API patterns, business object documents, session versus web service access, and where AI agents should not write.
- Infor LN Domain Structure Design: Architecture GuideDesign robust Infor LN domain structures including data dictionary domains, table relationships, key definitions, and index strategies for BAAN/LN development.
- Infor LN Session Programming GuideComplete guide to Infor LN session programming. Session architecture, form design, data handling, and business logic implementation for LN developers.