AWE Enable - More Problems

Question

Post reply

AWE Enable - More Problems

Bidec

SSCommitted

Points: 1666
More actions
May 10, 2005 at 11:40 am

#89150

I had made some changes to the memory configuration on our production box. For 3-4 days everything went fine.
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=180205
But now I have started getting these kind of errors. When a job tries to execute a DTS package it fails with the error messages specified below.
I am wondering if this has got anything to do with enabling awe option of if this is totally different.

There is another error( I dont have to screen shot for that :
SALMaint.exe
The instruction at "0x77f51340" referenced memory at "0xfffffff8". the memory could not be "read"
Please help me with these error messages otherwise I will have to roll ack the awe enable changes that I had made.
Thanks.

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

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

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 1

Did you enable /3GB at same time with "AWE"? Are all instance run i same physical server or in different nodes?

sa24 SSCrazy Eights Points: 8027 More actions · Answer 2

In what instance are you seeing the error message ?

Bidec SSCommitted Points: 1666 More actions · Answer 3

first I enabled AWE and then recycled the service and then set /3GB /PAE in boot.ini and then rebooted the server. Which I believe was not exactly how should it have done. But after rebooting it seemed to work fine for 3-4 days.

Just on the first instance where I have allocated 4GB of memory all the jobs which are scheduled to execute DTS pacages are not working. If I copy the "dtsrun" command from the job and execute it in command prompt on the server it works fine without any error.

But if execute the job I immediately see this error message box on the console on the server.

Hope this gives you enough information.

sa24 SSCrazy Eights Points: 8027 More actions · Answer 4

Can you try running the dts package manually outside the job ?

Bidec SSCommitted Points: 1666 More actions · Answer 5

Yes I tried to execute the DTs package outside the job and it worked fine.

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 6

Since you are able to run package using dtsrun outside SQL Server, It looks like you need to increase the memory reservation in SQL Server process with paramemter -g for other applications to run in the SQL Serevr process.

By default, SQL Server starts up with 384MB, Try to adjust it a little higher.

sa24 SSCrazy Eights Points: 8027 More actions · Answer 7

I agree to Allen, you might want to set a higher value for memtoleave area.

Steve-3_5_7_9 SSChampion Points: 10832 More actions · Answer 8

what is max server memory set at? sp_configure

turn off "priority boost" if it's on.

We were receiving memory errors, more specifically "insufficient memory available" and had to put a MSFT call in. Although server configurations vary for your environment they had us:

1. turn off priority boost (useless option which probably doesn't need to be in sql server at all, see caution in BOL)

2. set max server memory to 3.5 gb (we have 4 gb ram on this server)

3. add the -g512 parameter to the startup parameters. You'll want to read the BOL on this one because it states to only change this for a specific memory error (contiguous memory), but MSFT had us increase it anyway. if not set, default -g parameters is 256. I would definitely run this on a test server first to see how the behavior changes.