SharePoint manifest error

Thursday, February 11, 2010

Today I had the following error (in an english SharePoint farm with dutch language pack) when I clicked the help icon in SharePoint:

“HC niet gevonden. (MS.OSS.manifest , 1043)” (in English: HC not found … )

After some searching I found that I had to check the HelpFold in the Central Administration site. In the Content folder (<CAsite>/HelpFold/Forms/AllItems.aspx) there was no 1043 folder so the help text couldn’t be found. To solve this follow these steps on this site:

http://www.information-worker.nl/2008/11/20/sharepoint-manifest-error/#ixzz0fDa6fRp6

SQL Server 2008 Evaluation Edition Expiration Problem

Wednesday, February 10, 2010
 

With SQL Server 2008 passing its 6 months since RTM date, a common problem is popping up in the forums and is now listed on Connect.  When an install of Evaluation Edition Expires, the services stop functioning until an upgrade is made to a full version of SQL Server 2008.  This is normal.  The problem is that during the Edition Upgrade, SQL Server Management Studio is not upgraded, and a persistent popup will occur stating that the evaluation version has expired.

image

There is currently a workaround that can be done to resolve this problem.  Open RegEdit and change the value of the CommonFiles REG_DWORD under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\ConfigurationState registry from 1 to 3 and then rerun the Edition Upgrade.  This will allow the Upgrade to Management Studio to complete properly.

image

Microsoft Forefront Protection 2010 for SharePoint RC is Available

Monday, February 8, 2010

Microsoft Forefront Protection 2010 for SharePoint prevents users from uploading or downloading documents containing malware, out-policy content, or sensitive information to SharePoint libraries.

System Requirements
  • Supported Operating Systems: Windows Server 2003; Windows Server 2008; Windows Server 2008 R2

Forefront Protection 2010 for SharePoint* minimum server requirements
Important: Due to a difference in system resources, FPSP performs significantly better on a 64-bit operating system (OS) than on a 32-bit OS. If your organization expects to have large capacity requirements on SharePoint server, it is recommended that you install the 64-bit OS and a 64-bit SharePoint front-end server before installing FPSP.
  • Microsoft Windows Server 2003 SP2 (Standard, Enterprise, Datacenter, or Web Edition), Microsoft Windows Server 2008, or Microsoft Windows Server 2008 R2.
  • Microsoft .NET Framework 3.5.
  • Microsoft XML Core Services (MSXML) 6.0 SP1.
  • Internet Information Services (IIS) in IIS 6.0 worker process isolation mode.
  • Microsoft Chart Controls for Microsoft .NET Framework 3.5. If these controls are not already present, they will be installed during the FPSP installation process.
  • Windows PowerShell 1.0.
  • NTFS file system.
  • Microsoft Office SharePoint Server 2010, Microsoft Office SharePoint Server 2007 SP1, or Microsoft SharePoint Foundation version 3 SP1.
  • Microsoft Filter Pack 2.0
  • 2 gigabytes (GB) of free memory** in addition to that required to run SharePoint server. For more information about the memory requirements for running SharePoint server, consult your SharePoint server planning documentation.
  • 2 GB of available disk space. This is in addition to the disk space required for SharePoint server. Utilizing a server as a redistribution server for updates requires additional disk space.
  • A four core server with 2.0 GHz or higher processors is recommended. Lower performing servers are supported, but file latency times may increase.


* If both the Exchange and SharePoint products are installed on the same server, only Forefront for Exchange Server can be installed, to protect Exchange.
** Less memory is required if Intelligent Engine Management (IEM) is not enabled and fewer than 5 engines are selected (approximately 250 MB of memory per engine).

Forefront Protection 2010 for SharePoint Release Candidate (RC) is available for download here.