# Cannot Find Session Info in Baan and Infor LN: Causes and Fix

> Source: https://netray.co/erp-help/cannot-find-session-info-baan-infor-ln-fix
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## 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.

## Kind

error

## System

infor-ln

## Erp

Infor LN / Baan

## Module

Tools / Data Dictionary / Runtime Dictionary

## Query

cannot find session info

## Alternate Queries

- cannot found session info
- baan cannot find session info
- infor ln session info not found
- baan session not in runtime data dictionary

## Applies To

Baan IV, Baan 5 and Infor LN 10.x on-premise. The exact wording and session names may differ slightly between versions.

## Steps

### How to fix cannot find session info

**Items:**

- Note the exact session code the user tried to start and the user's package combination.
- Check that the session exists in the session definitions of a VRC that is part of that package combination.
- Check the user's package combination and VRC derivation: a session in a VRC outside the chain is invisible to the user.
- If the session was imported or changed recently, run the convert to runtime data dictionary session for the VRC and wait for it to finish.
- Have the user log out fully and start a new session so the runtime dictionary is re-read.
- If it persists, compare against a user who can start the session to find the difference in package combination or authorization.

## Sections

### What the bshell is looking for

**Body:**

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

**Body:**

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

**Body:**

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.

## 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.

## Ai Angle

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.

## Faq

### What does cannot find session info mean?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** Rarely. It is normally a configuration or conversion issue, but check disk space and convert errors if it keeps returning.

## Search terms

cannot find session info, cannot found session info, baan cannot find session info, infor ln session info, baan runtime data dictionary, baan convert to runtime, baan package combination, infor ln vrc session missing

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json