"We couldn't open that location. It might not exist or you might not have permission to open it.
Please contact the owner of onenote: http://<site url>/workspace/OneNote/Forms/template.onepkg for more information."
Creating OneNote notebook works great when you create it from OneNote 2013 to SharePoint 2013, but fails when created from SharePoint 2013 to OneNote 2013.
I'm using two different SharePoint 2013 on-premises installations in two different environments. I have win 7 (64bit), ie9 (32bit) and Office 2013 (32bit) machines in my use in both environments. The results are absolute same in both environments.
I tried to reinstall Office 2013 on workstation in both environments. I also tried to enable WebClient service and did boot after every modification, but no avail.
I also tried to create new template2.onepkg tempalate and made a new content type for it. OneNote 2013 gave the same error.
I also tried to use Win 7 (64bit), ie9 (32bit), Office 2010 (32bit) on both environments and OneNote 2010 worked like charm when creating OneNote notebook from library.
Does anybody have similar experiences with SharePoint 2013 OneNote library and OneNote 2013?
Br,
Markus
Hi,
Based on the description, creating OneNote notebook worked great when you created it from OneNote 2013 to SharePoint 2013, but failed when created from SharePoint 2013 to OneNote 2013.
I suggest as follows:
- Manage permissions for a document library.
- Set WebDav to "Allowed" in IIS.
Here is a similar thread for you to take a look at:
More information:
OneNote Notebook in SharePoint Server 2013: http://elczara.wordpress.com/2012/11/12/onenote-notebook-in-sharepoint-server-2013/
Resolve document library errors when using OneNote with SharePoint: http://office.microsoft.com/en-us/onenote-help/resolve-document-library-errors-when-using-onenote-with-sharepoint-HA102647129.aspx
Best Regards,
Linda Li
Hi,
Thank you very much for your help! I followed the instructions mentioned in the last link, but that didnt do it. Permissions are also set as Owner in both cases, but that didnt help.
Setting WebDav to "Allowed" in IIS might do the trick, but part of the site will be connected to the internet so WebDav wont be allowed because of the security issues. Ill try to set a test enviroment to test this.
Thanks again for all the great help!
Best regars,
Markus
- Edited by Markus Peltola 2 hours 56 minutes ago