There were a couple of interesting new KB articles in the last couple of days that I haven’t mentioned yet:
831090 “Cannot run the FrontPage Server Extensions on this page” error message when you try to upload a file to your SharePoint Web site. This can happen if someone edits the site’s upload.aspx file with FrontPage 2002. Ouch!
825497 How to use Microsoft Office FrontPage 2003 to create a custom hit counter that cannot be seen on your Web page. Very sneakey!
835298 Support WebCast: Using XML in Microsoft Office Excel 2003 on Wednesday, February 4, 2004: 10:00 AM Pacific time. This is a topic I’m really excited about (more on that later). It will also be covered from the Infopath side in the webcast on Monday (9-10).
833023 How to change the Windows SharePoint Services Web site for an Accelerator for Proposals document. An Accelerator for Proposals document is associated with the original Windows SharePoint Services Web site where it was created. However, you may have to change the location of your Accelerator for Proposals document for a variety of reasons; such as moving the document as part of a workflow for the proposal, or because the server name or the site path has to change.
833031 Document Actions task pane disappears and you receive an “Internal Error” error message when you merge two Accelerator for Proposals documents. In other words, don’t do that!
831795 Microsoft Office InfoPath 2003 cannot use a Web service that returns an ADO.NET DataSet. When an InfoPath 2003 form is created from a Web service that returns an ADO.NET DataSet that is named System.Data.DataSet, you may receive the following error message: The XML data file contains XML Schema Information, which is not allowed. To work around this problem, create a new Web service method that takes the ADO.NET DataSet that is returned from the original Web service method, remove the inline schema and the diffgram elements and the attributes (described in the linked article), and then return the cleaned XML to InfoPath 2003. The “Workaround” section describes two possible implementations of this workaround.
832432 SPS: All incremental crawls against the Microsoft Content Management Server (MCMS) 2002 site are performed as full crawls. When you use Microsoft SharePoint Portal Server or Microsoft Office SharePoint Portal Server 2003 as a search engine to create a search result catalog against a MCMS 2002 Web site, and you then update the search result catalog incrementally (that is, you perform a SharePoint Portal Server incremental crawl), all incremental crawls that are performed against the MCMS 2002 site are performed as full crawls.
[Info, as usual, privided by kbalertz.com]