SSAS processing failure

For no reason at all I started getting these error messages last week:

Description="File system error: The background thread running lazy writer encountered an I/O error. Physical file: \\?\D:\SQL Server Data\Analysis Database\DB.0.db\Visitor View.23.dim\45.Visitor Key.astore. Logical file: ." Source="Microsoft SQL Server 2008 Analysis Services" HelpFile="" /><Error ErrorCode="3238133764" Description="File system error: The following error occurred while writing to the file 'LazyWriter Stream': There is not enough space on the disk. ." Source="Microsoft SQL Server ...  The step failed.

Open in new window


It started happening on both of my database cubes. And it happens for different tables on both. Nothing has changed and there doesn't appear to be a good reason for it. Every once in a while I will get a message that the table astore file is corrupted. I am running MSSQL 2008, so I'm guessing all of the 2005 hot fixes are pointless.

I have over 200gigs of free space on this drive, and I don't see any astore file that is over 500megs so I don't think the 4GB limit is an issue.

I can reprocess the measures or any dimension on its own and it works fine. But doing the entire cube fails. Please help
karnaxAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
radcaesarCommented:
Try Increase your virtual memory / Set it to Windows Managed.

Restart your server and Try again.

PS: Generally the VIRTUAL MEMORY size should be 150% of the main memory (6GB in your case).
1
PedroCGDCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.