[ODBC SQL Server Driver]Memory allocation failure.

  • I have SQL 2000 SP4 Running on A windows 2003 Server with SP1

    One of the applications using the SQL server is MS Dynamics AX4SP1.

    Axapta is setup in 3 tier mode with:

    Application Object Server (AOS)

    Application File Server

    MS SQL Server Database

    I am getting the following error in the AOS Server and not being familiar with SQL .

    Event Type:Error

    Event Source:Dynamics Server 02

    Event Category:None

    Event ID:117

    Date:12/10/2007

    Time:11:05:05 AM

    User:N/A

    Computer:WRGAX1

    Description:

    Object Server 02: The database reported (session 29 (paule)): [Microsoft][ODBC SQL Server Driver]Memory allocation failure. The SQL statement was: "SELECT TOP 1 A.NUMBERSEQUENCE,A.TXT,A.LOWEST,A.HIGHEST,A.NEXTREC,A.BLOCKED,A.FORMAT,A.CONTINUOUS,A.CYCLIC,A.CLEANATACCESS,A.INUSE,A.NOINCREMENT,A.CLEANINTERVAL,A.LATESTCLEANDATE,A.LATESTCLEANTIME,A.ALLOWCHANGEUP,A.ALLOWCHANGEDOWN,A.MANUAL,A.FETCHAHEADQTY,A.FETCHAHEAD,A.MODIFIEDTRANSACTIONID,A.RECVERSION,A.RECID FROM NUMBERSEQUENCETABLE A WITH( UPDLOCK) WHERE ((DATAAREAID=?) AND (NUMBERSEQUENCE=?))"

    Is this error saying the SQL server itself ran out of memory ? or is this error for the ODBC Driver on the AOS Server ? or something else entirely ?

    How would I go about troubleshooting the source of this problem ? it is causing the application to crash and the users are unable to access the system.

    I was watching the SQL server and it was only using 1.8GB of RAM of the 4 GB Physical Memory (3 GB allocated to SQL) on the server when this error came up so I have a hard time believing the SQL server ran out of memory..

    I see no error on the SQL server in the event logs or in the SQL Server log that corresponds to these issues.

    After the latest service restarts of the SQL and AOS services everything is stable for the moment but I'd really like to know what the source of these errors was so it can be addressed.

    Thanks for any suggestions/recommendations

  • Do you get a similar error in the SQL Server error log?

    This can happen at times when the server becomes overloaded. Is this standard edition of SQL Server? The reason I ask is that the typical install of SQL Server uses 1.8GB, regardless of load. It tends to stabilize there. If you have Enterprise edition, you can change the amount of memory, add the /3GB switch, and get a little more memory usage. However memory allocation errors usually mean you need more resources (memory, faster disk, etc.)

    This could be in the ODBC/OLEDB layer of your app server, which is why I'd check to see if you have matching errors on the SQL Server. If you do, then look there. If not, I'd check the app server and maybe get debugging help from the vendor.

  • Steve Jones - Editor (12/10/2007)


    Do you get a similar error in the SQL Server error log?

    This can happen at times when the server becomes overloaded. Is this standard edition of SQL Server? The reason I ask is that the typical install of SQL Server uses 1.8GB, regardless of load. It tends to stabilize there. If you have Enterprise edition, you can change the amount of memory, add the /3GB switch, and get a little more memory usage. However memory allocation errors usually mean you need more resources (memory, faster disk, etc.)

    This could be in the ODBC/OLEDB layer of your app server, which is why I'd check to see if you have matching errors on the SQL Server. If you do, then look there. If not, I'd check the app server and maybe get debugging help from the vendor.

    No, there are no similar or matching errors on the SQL server in the Event Viewer or in the SQL logs.

    This is the Enterprise edition of SQL server 2000 not the standard edition.

    Where would that /3GB entry go ? in the Startup Parameters ?

    The storage array is a Dell MD1000 which is made up of 15K rpm Seagate SAS drives and has 450 GB free out of 900 GB so I would think the storage array should be fast enough.

    My thought was an application problem as well, but of course the App developer says it's a SQL problem and I should un-install SQL, and re-install it, which just sounds wrong to me.. guess he doesn't care about anything else I have running on that server in production...

Viewing 3 posts - 1 through 3 (of 3 total)

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