Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

File System Error: The record ID is incorrect . Physical File:. Logical File:. Expand / Collapse
Author
Message
Posted Wednesday, May 13, 2009 12:49 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, February 11, 2014 8:53 AM
Points: 1, Visits: 47
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 .
Post #715695
Posted Wednesday, July 08, 2009 9:43 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, May 13, 2013 11:13 PM
Points: 1, Visits: 11
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.
Post #749432
Posted Thursday, April 29, 2010 7:18 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, March 11, 2014 2:39 PM
Points: 216, Visits: 422
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
Post #912812
Posted Thursday, November 10, 2011 10:29 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, March 11, 2014 2:39 PM
Points: 216, Visits: 422
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
Post #1203721
Posted Friday, November 11, 2011 8:30 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, September 18, 2013 11:30 AM
Points: 38, Visits: 188
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?
Post #1204546
Posted Saturday, November 12, 2011 9:25 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, March 11, 2014 2:39 PM
Points: 216, Visits: 422
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
Post #1204633
Posted Saturday, November 12, 2011 9:50 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, September 18, 2013 11:30 AM
Points: 38, Visits: 188
can you capture the mdx and post it?
Post #1204637
Posted Saturday, November 12, 2011 10:37 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, March 11, 2014 2:39 PM
Points: 216, Visits: 422
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
Post #1204648
Posted Saturday, November 12, 2011 11:21 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, September 18, 2013 11:30 AM
Points: 38, Visits: 188
nah, just post on Monday and we can figure it out. It might take a ticket to microsoft, but someone knows the answer.
Post #1204655
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse