LEAGUE::load_from_disk() - unable to read past positions

Having difficulty installing or running EHM? Having trouble purchasing the game through Steam? Unable to get an addon or patch to work correctly? This is the place to ask for help! Please note that this is purely unofficial support offered by the TBL community.
Forum rules
Data Editing Forum: Editing the game, databases or saved games. Home of the EHM Editor and the EHM Assistant.

Game Add-ons Forum: Database projects, graphics and sounds. Any discussion which does not relate to editing databases or saved games.

Game Knowledge Discussion: Attributes, coaching, drafting, scouting, tactics and training/practice.

Rosters Forum: Discussion relating to all database and roster projects for Eastside Hockey Manager.

Technical Support: Difficulties, crashes and errors when installing or running the game (and nothing else). Any issues relating to the TBL Rosters must be posted in the TBL Rosters forum. Questions about how to install add-ons must be posted in the Game Add-ons Forum.

General EHM Chat: Anything relating to Eastside Hockey Manager 2004 / 2005 / 2007 / 1 which does not fall within any of the other forums.

Please carry out a forum search before you start a new thread.
Post Reply
Tbag188
Learning to skate
Posts: 1
Joined: Sat Apr 27, 2019 10:32 am
Favourite Team: Pelicans Lahti

LEAGUE::load_from_disk() - unable to read past positions

Post by Tbag188 »

I got this Error notification when trying to load up a save where I used a database that heavily modified the Finnish league structure (promotions, relegations and extra levels below Suomi-sarja). Has anyone encountered it before? If so how to fix it?
User avatar
archibalduk
TBL Admin Team
Posts: 20372
Joined: Tue Jul 06, 2004 8:44 pm
Custom Rank: Seaside + Fruit Juice Mode
Favourite Team: Guildford (EPL) / Invicta (NIHL)
Location: United Kingdom
Contact:

LEAGUE::load_from_disk() - unable to read past positions

Post by archibalduk »

I don't know how to fix it. I would suggest reverting to the unmodified database and then making your changes incrementally before testing. That way, you will be able to narrow down the source of the issue.
Post Reply