Cause

The DATE field requirement is changed in a custom list on a Windows SharePoint Services 3.0 Web site. If you try to export the custom list to a spreadsheet, Microsoft Excel starts, and a workbook that contains the data does not appear. Additionally, you receive the following error message:

Cannot get the list schema column property from the SharePoint list.

Workaround 1: 

1. In your custom list on the SharePoint site, click Settings, and then click List Settings.
2. Click Date and Time.
3. In the Additional Column Settings section, type a date under Default value in the correct format, and then click OK. For example, type 12/12/2008.
4. Click Date and Time again.
5. In the Additional Column Settings section, change the default settings back to no default. To do this, click to select (None) in the Default value field, and then click OK.
   Note The Default value setting caused the issue. The fix will now prevent the issue from breaking Excel.

  Workaround 2:

1. In your custom list on the SharePoint site, click Settings, and then click List Settings.
2. Change the Date/Time column to a ‘Single line of text’ column and then change it back to Date/Time

  Workaround 3:

1. Install Excel 2007

To enable the crawling of sites that require forms-based authentication or cookie-based authentication, use the AddRule.exe command-line tool after you apply this hotfix. To obtain the AddRule.exe command-line tool, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=D5090BC4-5B4F-411B-8CDE-E37D33F7EFDF

Command-line use

You may receive the following error messages if the XML file is malformed.

• If there is no <Rules> tag, you receive the following error message:

  Syntax error: [rules] element not found as the only node at the root.

• If a required node is missing in the XML file, you receive the following error message:

  Syntax error: <missing node> element unexpected.

• If a node in the XML file is incorrectly duplicated, you receive the following error message:

  Syntax error: <node name> element already exists for the current rule

• If the type is not "FORM" or "COOKIE," you receive the following error message:

  Syntax error: unrecognized value for the <type> element

• If the login_type is not "POST," you receive the following error message:

  Syntax error: unrecognized value for the <login_type> element

  Note If the administrator reruns this command by using another input file and then finds that the path is identical to an existing rule, the command will modify the rule.

Crawl rules object model

The CrawlRuleAuthenticationType enumeration includes the following new values:

• FormsRuleAccess = 4
• CookieRuleAccess = 5

The SetCredentials method in the crawl rules object model is overloaded with two new implementations.

The forms-based authentication rule takes the following input parameters in the following order:

• type::CrawlRuleAuthenticationType: This will be FormsRuleAccess.
• AuthSubmissionMethod::String: This will be "POST."
• AuthSubmissionPath::String: This is the URL in which the parameters should be posted.
• authData::NameValueCollection: This is where the hidden name value pairs are stored.
• privateAuthData:: NameValueCollection: This is where the encrypted name value pairs such as user names and passwords are stored.
• errorPages::StringCollection: This will store the various error pages that would indicate to the crawler to refetch a cookie or to fail the URL with an "Access Denied" error message.

The cookie-based authentication rule takes the following input parameters in the following order:

• type::CrawlRuleAuthenticationType: This will be CookieRuleAccess.
• cookies::StringCollection: This will store the cookies that the crawler should use.
• errorPages::StringCollection: This will store the various error pages that would indicate to the crawler to fail the URL with an "Access Denied" error message.

Note The encryption of the name value pairs and of the cookies is performed by using the same mechanism that is currently available.

Reference: http://support.microsoft.com/kb/934577