File System Error: The record ID is incorrect . Physical File:. Logical File:.

Question

File System Error: The record ID is incorrect . Physical File:. Logical File:.

manoj sharma-403194

SSC Enthusiast

Points: 165
More actions
May 13, 2009 at 12:49 am

#132148

Hi All,
I am also facing the below issue .In live environment we are using the below reporting services version
Microsoft SQL Server Reporting Services Version 9.00.1399.00
for analysis server we have already installed service pack2 which is mentioned in the below link http://support.microsoft.com/kb/950992
In my mdx query I am not using TopCount function.The strange thing is I am getting the error only in 2 report which was working fine 2 days back .Now suddenly the below error is appearing .
Cannot read the next data row for the data set xxxxxx. (rsErrorReadingNextDataRow)
File System Error: The record ID is incorrect . Physical File:. Logical File:.
Please help if you have any solution for this .

Viewing 9 posts - 1 through 8 (of 8 total)

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

Steven D. Clark SSC Rookie Points: 39 More actions · Answer 1

I am having the exact same problem. I started getting this error immediately after receiving a memory address error message from SQL Analysis Service. I'm not sure the two are connected, but the two seemed to go hand-in-hand.

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

I'm now seeing this error on a SQL Server 2008 R2 machine. Anyone ever find a fix for it? I'm going to try reprocessing the cube and see if that fixes it.

Bummer,

Rick Todd

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

Ugh, a year later and I find my own post via Google. Still having this problem. Deleted the cube, redeployed from code, reprocessed, same error. SQL Server 2008 R2...

Rick Todd

mark 38539 SSC Eights! Points: 848 More actions · Answer 4

That could be anything..what mdx generates the error...are any events logged...are any dump files written...what does your ssas config have for memory settings...did you run a profiler and capture all the events that lead up to the error...do you think it is storage engine or forumla engine problem?

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

No events logged. Minidumps created (trying to read them now). I think it's an MDX problem. There's something about the way we're building customer groupings in Excel Pivot Tables, I bet. Profiler is a good idea. Maybe seeing the MDX will allow me to pull it into SSMS and narrow it down, then either fix it or find a work around.

Cheers,

Rick

Rick Todd

mark 38539 SSC Eights! Points: 848 More actions · Answer 6

mark 38539

SSC Eights!

Points: 848

November 12, 2011 at 9:50 am

#1406714

can you capture the mdx and post it?

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

I guess my"now" was misleading. I'll look at this again on Monday when I'm back at work. Unless now is the only time you have to look at it.

Thanks

Rick Todd

mark 38539 SSC Eights! Points: 848 More actions · Answer 8

nah, just post on Monday and we can figure it out. It might take a ticket to microsoft, but someone knows the answer.