This may be a bug between Windows 2003 and SQL Server 2005. In the settings of the "Local Security Policy" should be under "User Rights Assignment" the item "Lock pages...