locked
AS2005 September CTP Memory Error RRS feed

  • Question

  • I get "Memory error: While attempting to store a string, a string was found that was larger than the page size selected. The operation cannot be completed." while executing query set with cube browser in SQL Server BI Dev Studio. The same error I get while executing query with VB code (via ADOMD). The source of the error is AS2005 OLEDB Provider.

    One important information: I have installed Sept CTP on clean Windows XP Pro, there were no previous versions of SQL 2005 installed.

    Any ideas what's up? Maybe some missing parameter in connection string?
    Sunday, September 18, 2005 11:20 PM

Answers

  • From another message board:


    This is a known issue with the September CTP and it has been fixed in
    post-CTP builds. The problem surfaces with client-side record sizes greater
    than 1k, so a possible workaround might be to rework the cube structure to
    reduce record sizes.

    --
    -Raman Iyer
    [This posting is provided "AS IS" with no warranties, and confers no
    rights.]

    Tuesday, September 20, 2005 7:45 PM
  •  Luther Smith wrote:
    I tried deploying a cube from a SQL 2000 data source using the September CTP, but ran into the same problem.  Do you have any idea whether your successful deployment had a smaller string size and if so how it got one?


    Sorry, I wasn't specific enough - I just meant that I had deployed non-AdventureWorks cubes sucessfully on SeptCTP. I don't know how to find out the string size, but if you tell me, I'll check it out and let y'all know.

    disclaimer - I'm using SQL2005 Sept CTP x64
    Wednesday, October 5, 2005 8:43 AM
  • This is the approach we're taking to work around this:

    I have a colleague here who's new to AS, and in order to let him proceed through the tutorial, we've just set him up with JuneCTP, and he's going through that.

    We've also set up a SeptCTP system, and although the AdventureWorks doesn't work on that, our 'real' data does seem to work.

    So that lessons my colleague is learning on JuneCTP he can put into practice on our real data on the SeptCTP.

    I'm not new to AS, so don't need AdventureWorks, and I'm working away on our data on SeptCTP no worries.

    It's a bit messy, but at least we can keep working.
    Wednesday, October 12, 2005 8:22 AM
  • It looks like there is problem with CTP16's msolap90.dll
    There is a hotfix but only TAP customers it at this time.

    See Mosha's response on the following link.
    http://www.dbforums.com/t1197398.html
     

    The 3 first lessons seem to have the browsing problem. However my advice is that unless you've never worked with analysis Services you don't need to browse the cubes as the 3 lessons are very basic.
    In the 4th lesson you have to load an enhanced version of the tutorial project and that seems to work fine.

    hope this helps
    Monday, October 17, 2005 6:03 PM
  • I had the same issue finally got it tracked down.  See here

    Quick extract :


    Please update the client PTS9 drivers with the RTM version at:
    http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

    You need to update the client bits along with upgrading the server to RTM.

    _-_-_ Dave




    Dave Wickert (MSFT)



    Hope that helps ...

    Tristan
    Friday, December 2, 2005 7:40 PM

All replies

  • I'm having the same problem after I uninstalled the June CTP and installed Sept CTP.  I'm getting the error in BIDS and SSMS, I can browse dimensions but when I try to drag a dimension or measure onto cube browser I get the error.  I tried deleting the AS database, redeploying, and reprocessing and I'm still getting the error.  Any help would be appreciated.
    Monday, September 19, 2005 8:17 PM
  • From another message board:


    This is a known issue with the September CTP and it has been fixed in
    post-CTP builds. The problem surfaces with client-side record sizes greater
    than 1k, so a possible workaround might be to rework the cube structure to
    reduce record sizes.

    --
    -Raman Iyer
    [This posting is provided "AS IS" with no warranties, and confers no
    rights.]

    Tuesday, September 20, 2005 7:45 PM
  • Trying to work thru the as2005 tutorial and am stopped by said memory issue.

    Any solutions to this?  Any measure,dimension that i use causes the problem.
    Reworking the cube structure to reduce record sizes??  Anyone been successfull w/ that?

    Are there any post-CTP (september) builds available
    thanks

    Wednesday, September 21, 2005 3:07 PM
  • ttt

    Same problem here.

    There seems, however, to be some users on the forum who have gotten through the AS2005 tutorial without a hitch.  I would assume these people did not have to reduce record sizes or anything like that.

    Has anyone had any luck yet?  Has anyone tried building a cube from non-AdventureWorks data?  I tried but had a problem deploying so I didn't get to even test the memory error.

    Anyone from MS have a solution or workaround?
    Tuesday, September 27, 2005 5:36 PM
  • I encountered this very same error.  Can you tell me where I could find a post-CTP build?
    Monday, October 3, 2005 5:00 PM
  • Same problem here. Was this functionality available in earlier betas, and did it work properly? I suppose that would be far easier than trying to get a NEWER build...
    Tuesday, October 4, 2005 7:59 AM
  • I have built and depolyed a non-Adventureworks cube on September CTP with no problems at all.

    Tuesday, October 4, 2005 2:47 PM
  • I tried deploying a cube from a SQL 2000 data source using the September CTP, but ran into the same problem.  Do you have any idea whether your successful deployment had a smaller string size and if so how it got one?
    Tuesday, October 4, 2005 4:11 PM
  • I currently use April CTP and everything works fine. I encountered two minor problems: slow first initialization of metadata during reading it with ADOMD (not NET) and there is no way to get value of unary operator property of member.

    Best regards!
    Tuesday, October 4, 2005 6:49 PM
  • Yup. Same here. Any chance of a hotfix or something? This basically halts SSAS development for my team on Sept CTP (we will have to roll back :P)
    Tuesday, October 4, 2005 9:39 PM
  •  Luther Smith wrote:
    I tried deploying a cube from a SQL 2000 data source using the September CTP, but ran into the same problem.  Do you have any idea whether your successful deployment had a smaller string size and if so how it got one?


    Sorry, I wasn't specific enough - I just meant that I had deployed non-AdventureWorks cubes sucessfully on SeptCTP. I don't know how to find out the string size, but if you tell me, I'll check it out and let y'all know.

    disclaimer - I'm using SQL2005 Sept CTP x64
    Wednesday, October 5, 2005 8:43 AM
  • Same problem here.

    I've been trying to track this down for a few days now. The problem is reportably fixed in the Nov release, but no hot fix is available.

    Based on some configuration testing, the problem appears to be in either the PTS layer or specifically in the OLE DB drivers. I managed to recreate the issue in the June CTP (CTP 15) configuration, where the Sept drivers were installed. I could access the server fine from a remote PC, but localling, the error poped up.

    Tuesday, October 11, 2005 3:56 PM
  • Is there a download for the hotfix?  It seems ridiculous to have to back out the CTP16 or to have to wait until the RTM is released.  I need to start developing on SSAS 2005 immediately.  Help??

    Tuesday, October 11, 2005 7:17 PM
  • I agree.  I have gone through all sorts of uninstalls and reinstalls between the June and September CTP's.  Nothing worked to get past the memory error.  I need to start learning 2005 right away!
    Tuesday, October 11, 2005 8:21 PM
  • This is the approach we're taking to work around this:

    I have a colleague here who's new to AS, and in order to let him proceed through the tutorial, we've just set him up with JuneCTP, and he's going through that.

    We've also set up a SeptCTP system, and although the AdventureWorks doesn't work on that, our 'real' data does seem to work.

    So that lessons my colleague is learning on JuneCTP he can put into practice on our real data on the SeptCTP.

    I'm not new to AS, so don't need AdventureWorks, and I'm working away on our data on SeptCTP no worries.

    It's a bit messy, but at least we can keep working.
    Wednesday, October 12, 2005 8:22 AM
  • Once you get to the Lesson 4 Tutorial, the Memory Issue goes away.  I loaded the Project found in the C:\Program Files\Microsoft SQL Server\90\Tools\Samples\AdventureWorks Analysis Services Project\Enterprise folder.  Alles gut!

    Wednesday, October 12, 2005 4:26 PM
  • But how does this fix it?  I am not using a tutorial, I'm taking a class (where the rest of the students and the instructor are using June ctp) so I don't know what to do to finish my project.

    I loaded the project you mention above, I can drag and drop attributes without error, but when I go back to my own project I am trying to build, I still have the error.  I am using a copy of AdventureworksDW.

    Does anyone know why it would be different or how I can fix my own project cube??

    Sunday, October 16, 2005 11:44 PM
  • It looks like there is problem with CTP16's msolap90.dll
    There is a hotfix but only TAP customers it at this time.

    See Mosha's response on the following link.
    http://www.dbforums.com/t1197398.html
     

    The 3 first lessons seem to have the browsing problem. However my advice is that unless you've never worked with analysis Services you don't need to browse the cubes as the 3 lessons are very basic.
    In the 4th lesson you have to load an enhanced version of the tutorial project and that seems to work fine.

    hope this helps
    Monday, October 17, 2005 6:03 PM
  • I had the same issue finally got it tracked down.  See here

    Quick extract :


    Please update the client PTS9 drivers with the RTM version at:
    http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

    You need to update the client bits along with upgrading the server to RTM.

    _-_-_ Dave




    Dave Wickert (MSFT)



    Hope that helps ...

    Tristan
    Friday, December 2, 2005 7:40 PM