Friday, January 16, 2009

Renaming an existing SharePoint Server

Use the following in order to rename a SharePoint server. I have personally only done this with WFE servers, not sure if it will work with a standalone box, but it should.

• Open a command prompt and change the path to: c:\program files\common files\Microsoft shared\web server extensions\12\bin
• Run the following command to change the server name
Stsadm.exe -o renameserver -oldservername -newservername

• Run the following command to change the Alternate Access Mapping for the Central Administration website. The Port variable in the command below is the port number of the Central Administration site.
stsadm -o addalternatedomain -url :http://: -urlzone extranet -incomingurl :http://:

• Now Open Central Administration/Operations page/Global Configuration heading to finish fixing the Alternate Access Mappings for the SSP/MySites etc. Change the mappings from http://oldservername to http://newservername and select the correct zone (setting as default instead of intranet/internet/extranet).
• Run an IIS reset on the server, and you should be back in business with the new server name.

Wednesday, January 7, 2009

SharePoint Timer error Event ID's 7076, 6398 and 6432 fix available

In the Server Application Logs the SharePoint timer service repeatedly throws errors with the following Event ID's 7076, 6398 and 6432 , with this mesage within:"Attempted to read or write to protected memory".

Microsoft has released a patch for this issue, and lo and behold, it is related to IIS.
See the following KB

You will have to register for the Hotfix then download and install.
In my particular case, I did that and when i tried to install it I received the following message:

“Not Enough Server Storage is available to Process this command”

Ok so now I have to troubleshoot the patch? what gives? after doing some searching around the InterGoogle, I found this blog entry:
Which suggested the following registry fix:

Registry entry HKLM\System\CurrentControlSet\lanmanserver\Parameters

Add IRPStackSize (DWORD) value, right click, select ‘modify’, add 18 as the default Decimal value. Max Value is 50.

Restart the server.

Since the system I was attempting to fix was not in use by anyone, I went ahead and attempted the registry fix. And sure enough that solved the issue. Not sure on the how and the why, but the IIS patch then ran sucessfully and solved the IIS Issue and in turn that stopped the SharePoint timer errors from occuring.