Issue accessing cube file

Question

Post reply

Issue accessing cube file

karthik -450760

Ten Centuries

Points: 1362
More actions
March 29, 2010 at 11:26 am

#139963

Hi,
One of the users reported the below error
"File system error: Error opening file; "\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\.........fact.data " is not a disk file or file is not accessible. "
Any idea why this error could have occured.
thanks!!!

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Rick Todd Hall of Fame Points: 3302 More actions · Answer 1

Are all users getting this, or just the one?

Rick Todd

karthik -450760 Ten Centuries Points: 1362 More actions · Answer 2

Hi,

Thanks for the reply. I dont think its an access issue. The user tries to get this error when trying to get reports couple of days back. Now that the issue is resolved, the user wants to know the root cause of this issue. As I m new to analysis services, I would like to know if there is any analysis service log where i can check for any errors.

Thanks..

Rick Todd Hall of Fame Points: 3302 More actions · Answer 3

Man, I swear I've seen that before, but thankfully it's been a while so I can't remember! I would try the Event Viewer and see if there's anything in there. A surprising number of MS applications make good use of it. If I had to guess I'd say either the server was temporarily confused, or was in the midst of processing, although I typically see a different error when the latter is the case, but our users are virtually always accessing through Excel, so maybe the message is suppressed.

Cheers,

Rick Todd

karthik -450760 Ten Centuries Points: 1362 More actions · Answer 4

Since the error occured couple of days back and since the eventviewer has been recycled, i cannot view the old logs in the event viewer. I can see the mini dump file, flightrecorder trace in the server. I know that these files has got somethign to do with OLAP but not sure how to analyse these files. It does not contain much information at all.. Filghtrecorder trace do not have much information too..

Optimization jobs run during weekends on SQL Server and DBCC Checkdb ran on all the databases. The user says that the problem got resolved after checkdb ran in the sql server. I am sure checkdb has got nothing to do with this file access... am I right?

I m entirely clueless!!!!! :w00t:

Rick Todd Hall of Fame Points: 3302 More actions · Answer 5

I've never had much luck with those files either. Not sure what to tell you. While theoretically the checkdb process could have affected it, in terms of making the server busy, it sounds pretty unlikely. Sorry to not be more help!

Rick Todd

karthik -450760 Ten Centuries Points: 1362 More actions · Answer 6

Thanks for your assistance.. Actually, the user thinks that the issue got resolved because of checkdb. She is asking me to confirm that, so that whenever she get this error, she says she will execute dbcc checkdb to get rid of the error..

:-D. I don't think the issue got resolved because the checkdb ran.;-)