Sharepoint Document Library custom Document Template will not delete and/or will not "take" updates
I have a Sharepoint document library which I need to change the template for monthly. Rather than overwrite "template.xlsx" each time, I've named it Spreadsheet 2010-06.xlsx based on the month. When I've edited the actual template through the Advanced Settings window and saved it, the updated version doesn't consistently "stick." Same thing for overwriting the file with a version from my desktop. Inconsistent. Additionally, when I actually delete the document template from the Forms folder in Explorer View, it restores itself. In this library: Content Approval is required Major Versions are created Users can see only their own documents Documents are not required to be checked out before they can be edited Are my issues related to versioning or content approval? Does the admin need to change the caching settings on the server for this subsite? Is there a patch? We are running SP 2007. Thanks in advance!
July 15th, 2010 12:18pm

Hi Beckie, I suspect this may be an Explorer View issue. Can you upload this same .xlsx spreadsheet to another library via Explorer View, not as a template but just as a file? Do the changes stick, do files restore themselves if deleted? Start with this whitepaper: Whitepaper - Understanding and Troubleshooting the SharePoint Explorer View http://www.microsoft.com/downloads/details.aspx?familyid=c523ac7a-5724-48be-b973-641e805588f4&displaylang=en Thanks!
Free Windows Admin Tool Kit Click here and download it now
July 22nd, 2010 3:13pm

Hi Beckie, Some additional information for you! Scenario 1 – 'Middle man' issues can cause an issue. Explorer view normally relies on WebDAV client (operating system layer) to communicate with SharePoint. Windows XP has some known problems with WebDAV client (especially if you have a proxy for example). Another common cause of issues is Vista SP2 as FBA authentication was added to WebDAV client. FBA works with authentication tokens and the concept of redirection: if user needs to login via a login page, the redirection will be dealt by the operating system layer. Prior to SP2, the redirection was returned as it was sent to the application level (Word for example). In brief, if some intermediaries, like proxies or custom handlers, are in the way, WebDAV will not work well. This is the workflow of a scenario where a middle man (proxy or custom http handler misbehaves): When opening an Office doc, office first attempts accessing the file over WebDAV. A WebDAV PROPFIND request is sent to the server. If the server does not support WebDAV then it should respond to the PROPFIND request with an appropriate error status like '501 - Not Implemented'. Instead the server responds with '200 OK' - success. The response body is not formatted according to WebDAV protocol. The PROPFIND response should contain properties of the file in xml format. Instead the response body is the file itself. (The response is same as that for a HTTP GET request). When WebDAV client parses this response body, it fails with ERROR_INVALID_PARAMETER. On Vista SP1, this error is passed back to the app and office will attempt to open the file without using WebDAV (FrontPage RPC for example). On Vista SP2, as part of the support added for Forms Based Authentication, we change the error status from invalid parameter to ERROR_ACCESS_DENIED. This accessed denied error causes WebDAV client to prompt for credentials. Scenario 2 – WebDAV failing because of Loopback Check in server. - If the server needs to be accessed via FQDN follow http://support.microsoft.com/default.aspx?scid=kb;EN-US;926642 (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\DisableLoopbackCheck = 1) - Make sure WebDAV is enabled on the Server (default) Scenario 3 – Documents are not checked out in Explorer View (looks like your problem) - Enable Explorer view to enable checkout in the Vista SP2 Client (HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Internet\OpenDocumentsReadWriteWhileBrowsing = 1) - http://support.microsoft.com/kb/870853 As already mentioned, though, you can also see more information at the link below. Whitepaper - Understanding and Troubleshooting the SharePoint Explorer View http://www.microsoft.com/downloads/details.aspx?familyid=c523ac7a-5724-48be-b973-641e805588f4&displaylang=en Thanks!
July 22nd, 2010 6:37pm

You have not created an Excel Template if you saved it as "template.xlsx". Naming it template does not make it a template. Use the Extention *.xlt, *.xltm(macro embedded), or .xltx. Hope this helps...looks like this was a while back.
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2012 4:42pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics