Crashes in EViews 9, corrupted databanks
Posted: Tue Aug 11, 2015 6:49 am
Hi,
I'm running EViews 9, with patches installed through the current date (8/11). Over the past two days, I have tried to run programs that utilize the STORE command for a group and my connection to the database on the E drive pathway (and internet more generally) gets dropped, at which point I receive a message about an IO error. The after the third time today, I ran the program on a colleague's computer (also using most recent version of EViews 9) and got the same error message. I tried repairing and testing the database integrity, and got an error message stating "allocation information inconsistent. Rebuild file immediately!."
I'm pretty sure the database is corrupted (rebuilding from scratch now). It might be that my internet connection has dropped at precisely the wrong times (also looking into), which is the cause, not anything directly in EViews. However, three crashes in two days on similar EViews code is pretty suspicious to me in terms of causality. As a point of consensus, has anyone else had similar difficulties recently, or further in the past?
I would be obligated for any advice given. Thanks.
I'm running EViews 9, with patches installed through the current date (8/11). Over the past two days, I have tried to run programs that utilize the STORE command for a group and my connection to the database on the E drive pathway (and internet more generally) gets dropped, at which point I receive a message about an IO error. The after the third time today, I ran the program on a colleague's computer (also using most recent version of EViews 9) and got the same error message. I tried repairing and testing the database integrity, and got an error message stating "allocation information inconsistent. Rebuild file immediately!."
I'm pretty sure the database is corrupted (rebuilding from scratch now). It might be that my internet connection has dropped at precisely the wrong times (also looking into), which is the cause, not anything directly in EViews. However, three crashes in two days on similar EViews code is pretty suspicious to me in terms of causality. As a point of consensus, has anyone else had similar difficulties recently, or further in the past?
I would be obligated for any advice given. Thanks.