RAID 0 (Stripe set without parity)

•No Fault Tolerance
•Best read and write performance
•I/O per disk calculation: (reads + writes) / number of disks

RAID 1 (Mirrored Volume)

•Fault Tolerance: 1 Disk may fail
•Performance: Good read, Acceptable write
•I/O per disk calculation: [(Reads + (2 x Writes)] / 2

RAID 5 (Stripe set with parity)

•Fault Tolerance: One disk may fail
•Performance: Excellent read, fairly poor write
•I/O per disk calculation: [(Reads + (4 x Writes)] / Number of Disks

RAID 10 (Stripe of Mirrors)

•Fault Tolerance: Half of the disks may fail (but not both disks in any mirrored pair)
•Performance: Excellent read and write
•I/O per disk calculation: [(Reads + (2 x Writes)] / Number of Disks

Have you ever wondered exactly how Windows is assigning physical memory, how much file data is cached in RAM, or how much RAM is used by the kernel and device drivers? RAMMap makes answering those questions easy. RAMMap is an advanced physical memory usage analysis utility for Windows Vista and higher. It presents usage information in different ways on its several different tabs:

Use Counts: usage summary by type and paging list
Processes: process working set sizes
Priority Summary: prioritized standby list sizes
Physical Pages: per-page use for all physical memory
Physical Ranges: physical memory addresses
File Summary: file data in RAM by file
File Details: individual physical pages by file

Use RAMMap to gain understanding of the way Windows manages memory, to analyze application memory usage, or to answer specific questions about how RAM is being allocated. RAMMap’s refresh feature enables you to update the display and it includes support for saving and loading memory snapshots.

RAMMap

More From pstilgoe

• How to auto populate InfoPath forms using the people picker
• How to configure Kerberos for SharePoint / MOSS 2007
• How to rename your web application in Sharepoint Services & MOSS

Article ID : 946517
Last Review : August 7, 2008
Revision : 4.0

SYMPTOMS

Consider the following scenario. You have a process that has more than one thread. Additionally, the process uses the Internet Information Services (IIS) Active Directory Service Interfaces (ADSI) provider to access IIS. Two threads access IIS at the same time. In this scenario, you may be unable to manage IIS by using Server Manager.

When this problem occurs, you must restart IIS, or you must restart the process that uses the IIS ADSI provider.

This problem is likely to occur for the SharePoint Timer service (OWSTimer.exe) in Microsoft Office SharePoint Server 2007. When this problem occurs for the SharePoint Timer service, you may experience the following symptoms:

• In SharePoint Server 2007, tasks that are scheduled do not run.

• On the SharePoint Web front-end server, you see repeated errors in the Application log in Event Viewer. These errors usually include one of the following three events:

• Event ID 6398
• Event ID 6482
• Event ID 7076

For example, you may see an error message that resembles the following:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: (964)
Event ID: 6398
Date: 11/7/2007
Time: 5:45:38
PM User: N/A
Computer: 44MOSSAGRUK
Description:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob
(ID 02b5e3f2-21e3-4552-bf1d-6e152749458a) threw an exception. More information is included below.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

• When you try to manage IIS by using Server Manager, you receive a blank page, or you receive the following error message:
the path specified cannot be used at this time

RESOLUTION
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

More From pstilgoe

• How to configure Kerberos for SharePoint / MOSS 2007
• Microsoft Office SharePoint Server (MOSS) 2007 Limits
• HP ProLiant Sizer for Microsoft Office SharePoint Server 2007

Techinal Details:

System.UnauthorizedAccessException: Access Denied! Only site admin can access Data Source object from user profile DB.

at Microsoft.Office.Server.UserProfiles.SRPSite.AdminCheck(String message)

at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(IDataRecord rec)

at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(String strDSName)

at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site, Boolean fAllowEveryoneRead)

at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site)

at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.GetDataSource()

at Microsoft.Office.Server.UserProfiles.BDCConnector.RefreshConfiguration(String sspName)

Resolution:

Grant the following rights in shared services –

Default Content Access Account:Manage Analytics, Manage Audiences, Manage User Profiles, Personal Features, Personal Site, Set Permissions

Search Service Account: Manage Analytics, Manage Audiences, Manage User Profiles, Personal Features, Personal Site, Set Permission

This error should now be resolved.

More From pstilgoe

• Import data from CSV and SQL to a SharePoint list
• Enable anonymous access on a Sharepoint site
• Using a lookup to return data from a list on a different site

Current implementation is Windows 2008 server, IIS 7.0 & MOSS 2007, when defining the Shared Service Provider Application Pool Account it is stated that you dont need to grant it any permissions as they will get added automatically upon creation eg:

When each application pool is setup, you must specify an account that will be used for that specific application pool’s identity. This account will be used to access the content databases associated with the web application. It is recommended that a new service account is created for each application pool. This should be a Domain Account with no specific permissions. When the account is specified & SharePoint creates the application pool, it automatically grants the account additional needed permissions.

However in my environment this is not the case as upon creation of this SSP no accounts appear to be able to access the SSP config page. In the short term I have set the App pool account for the SSP as SPadmin (my install / admin account) until I have time to figure out exactly what is causing this & what permissions are required.

More From pstilgoe

• Enable anonymous access on a Sharepoint site
• SharePoint/MOSS Active Directory Self Service Web Part
• Error: Cannot retrieve the information for application credential key

I have just used this procedure which I found on Steve Graegerts blog (http://graegert.com/) & it work perfectly:

WSS 3.0 and MOSS 2007 can only be installed with Service Pack 1. You need to download WSS 3.0 including SP1 not WSS 3.0 & SP1. You cannot download MOSS 2007 with SP1 included so we will have to slipstream the installation.

In order to allow MOSS 2007 to be installed on Windows Server 2008 we have to provide the necessary updates prior to installation. Here is how it can be done:

1. Copy all installation files from you MOSS 2007 CD/DVD to a temporary directory (i.e. D:\Temp\moss).

2. Copy both the WSS 3.0 SP1 and MOSS 2007 SP1 to another temporary directory (D:\Temp\sp1)

3. Next, we need to copy all files inside the SP1 archives into the MOSS 2007 Updates directory usually located at \x86\Updates depending on your platform:

1. Open a console (Start > Run > Enter: cmd) and navigate to the SP1’s temporary directory
cd D:\Temp\sp1

2. Extract both archives to the Updates directory using the following commands:

officeserver2007sp1-kb936984-x86-fullfile-en-us.exe /extract:D:\temp\moss\Updates

wssv3sp1-kb936988-x86-fullfile-en-us.exe /extract:D:\temp\moss\Updates

You will find all extracted files in the Updates directory.

4. Start the MOSS 2007 installation as normal and follow the instructions.

More From pstilgoe

• Enable anonymous access on a Sharepoint site
• How to configure Kerberos for SharePoint / MOSS 2007
• Renaming a MOSS server