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.
Crashes in EViews 9, corrupted databanks
Moderators: EViews Gareth, EViews Moderator
-
EViews Steve
- EViews Developer
- Posts: 844
- Joined: Tue Sep 16, 2008 3:00 pm
- Location: Irvine, CA
Re: Crashes in EViews 9, corrupted databanks
Gordon:
I have a few questions about your issue:
1. Is your E drive going out over the internet? Is it going to an FTP server or a cloud drive? Are you using any third party software to make this link?
2. Is this problem something new with EViews 9 -- were you able to use the same E drive using EViews 8?
3. I assumed you are using the STORE command to write to an EViews database. Is that correct?
If you're E drive is something remote, you can try using a local drive instead to see if the problem is with EViews or with the E drive implementation. If it's with EViews, I'd like to know some details on how you're using STORE and what your general workflow is with it.
Steve
I have a few questions about your issue:
1. Is your E drive going out over the internet? Is it going to an FTP server or a cloud drive? Are you using any third party software to make this link?
2. Is this problem something new with EViews 9 -- were you able to use the same E drive using EViews 8?
3. I assumed you are using the STORE command to write to an EViews database. Is that correct?
If you're E drive is something remote, you can try using a local drive instead to see if the problem is with EViews or with the E drive implementation. If it's with EViews, I'd like to know some details on how you're using STORE and what your general workflow is with it.
Steve
Who is online
Users browsing this forum: No registered users and 1 guest
