- First place I turned to troubleshoot this error was support.microsoft.com. I found this hotfix KB 923028. I won’t detail the hotfix here you can read the KB yourself. So I applied this hotfix and at first the error appeared to have been fixed. I didn’t see the error for about a week then it’s started back up again. So I obviously had to try something else.
- The next thing that I tried was un-provisioning/re-provisioning the Central Administration Site. I used the psconfig utility to complete this. For those of you unfamiliar with this utility it’s located in the bin folder in the 12 hive. This utility is like stsadm but for the Central Administration Site, you can check out more details on TechNet.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Or
Reason: Not enough storage is available to process this command.
Then there’s the technical details about the error that I am not going to detail but if you get these errors I am sure you are familiar with.
In this Blog I am going to details how you can try to address these errors. I have applied the fixes below to two seperate MOSS server farms. For the one case the event’s went away, well logged for over two months now.
The other case I applied the same steps below and they still show up. When I contacted Microsoft PSS we went over the steps that I had taken and they simply stated that they know this error occurs and currently have no solution but are working on a solution. Here’s what the support professional told me in my last email with her,
It was my pleasure to serve you during your <7076, 6398, 6482 error in the application log> issue. I hope that you were delighted with the service provided to you. As we discussed this is a known issue and the final fix for this issue is yet to come.
So although I will give you suggestions on how to solve this error there is always the chance that you won’t be able to solve this issue until Microsoft gets the final fix. They haven’t given me any details as to when this will be delivered. I will keep you posted once I hear something.
Here are the three steps that you can try to fix these errors on your MOSS farm. After each step in the process I would wait a few days to see if you have solved your error. There’s no need to do additional steps if you don’t have to.
- Make sure you make note of what port CA is on before you un-provision CA.
- From the Command Prompt navigate to the bin folder in the 12 hive
- Unprovision the Central Administration
- Re-provision the Central Administration
- The last thing that I tried was to reestablish the service account credentials on the Windows SharePoint Services Timer Service and restarted the service.
First go to Services under Computer Management.
So here are the steps that you will need to follow to un-provision/re-provision.
C:Program FilesCommon FilesMicrosoft Shared Web Server Extensions12bin
psconfig -cmd adminvs -unprovision
psconfig -cmd adminvs -provision -port [Enter port number that CA was on]
The events came back to my Application Log rather quickly after I applied this fix. I wouldn’t suggest skipping this step though since I followed all of these steps to fix one farm.
Find the Windows SharePoint Services Timer Service in the window on the right and double click it to display the properties.
Click on the Log On tab and reenter your service account credentials. After you complete that come back to the general tab and click on stop and then start.
At the completion of this step I stopped receiving errors on the one farm. The other farm the error came back after a few days.
Give these steps a try and see what happens. They did fix one SharePoint Farm I am working with but the other is still logging these errors but I believe there may be something else going on that I haven’t found yet.
On another note, I have a 64 bit MOSS Farm that I am running that I don’t get this error. I don’t know if this chance or has something to do with the way the system is referencing the RAM and disk space. I will keep you posted.
