Page 1 of 1

RunTime Error During Retirement Check

Posted: Thu Sep 10, 2009 9:58 pm
by BigParrot
Has anyone experienced a run time error during retirement check during the off season with 1.8.3?

The screen that say "The following players have decided to call it quits" is displayed for a few seconds before an error window pops up saying:

Run-time error '70'
Permission Denied

I click on OK and Puresim crashed to the desktop. When I restart the association, Puresim acknowledges a problem during the off season and attempted to correct it. After a few seconds, the amateur draft starts with the no players found. A bunch of scrubs are created. You can complete the draft, but the no players issue comes up with the free agent draft as well, but no scrubs are created.

I tried using my backup and rebooting, same issue

RE: RunTime Error During Retirement Check

Posted: Thu Sep 10, 2009 10:17 pm
by KG Erwin
What year are you using? If it's 2009, then of course all new players will be fictional when you rollover into 2010. My suggestion is to d/l 1.84 release candidate 2. If the problem persists, then restart the game using the debug.exe. Any further problems will prompt you to send the association to Shaun.

RE: RunTime Error During Retirement Check

Posted: Thu Sep 10, 2009 10:26 pm
by BigParrot
Using a fictional league set in 1959 (league started in 1950)

I will try 1.84 and see what happens.

RE: RunTime Error During Retirement Check

Posted: Fri Sep 11, 2009 8:56 am
by puresimmer
ORIGINAL: BigParrot

Using a fictional league set in 1959 (league started in 1950)

I will try 1.84 and see what happens.

Thanks, and if it still happens in 1.84, can you run puresim2k7_debug.exe (in the same folder as the puresim2k7.exe)? That will produce a crash dump and prompt you to paste the results into an email that will get sent to me. I'll be able to pinpoint exactly what is causing that issue on your computer with that info.


RE: RunTime Error During Retirement Check

Posted: Tue Sep 22, 2009 10:38 pm
by BigParrot
Update..  Loading 1.84 seems to have corrected the problem without any ill effects.