OneNote 2007 SP1 - Can't Create notebooks On Some Servers

re: OneNote 2007 SP1 - Can't Create notebooks On Some Servers

DenverCoug — Mon, 20 Sep 2010 18:43:15 GMT

Here is how I resolved the issue.

1. Create folder on SharePoint. Example: "Meeting Notes"

2. Open OneNote and select to Open a Workbook. Select the Folder you create in SharePoint

3. Create a new tab for your OneNote Workbook. Example: "Status Meetings"

4. Right-click on the tab and select "Save As". Save it in the Folder you created in Step 1.

5. Close OneNote

6. Go go your SharePoint site folder. Launch the Workbook file (not the files created for your tabs)

7. Enter some test content into one of your tabs and sync.... This got my sync'ing to work and I was able to continue create the rest of my tabs without issue.

re: OneNote 2007 SP1 - Can't Create notebooks On Some Servers

DenverCoug — Mon, 20 Sep 2010 17:57:19 GMT

bdmorgan,

Did you find a solution as I'm getting the exact issue you encountered described in your post. Anyone else have a solution?

re: OneNote 2007 SP1 - Can't Create notebooks On Some Servers

Tim Taylor — Mon, 12 Jul 2010 21:55:22 GMT

@Tom Burke

We've got the exact same issue. If anyone has a fix for it, that would be wonderful. I realize this post is old, but we have been hard pressed to find any info on this particular issue.

re: OneNote 2007 SP1 - Can't Create notebooks On Some Servers

Tom Burke — Mon, 07 Jun 2010 19:17:24 GMT

I have the same problem, but I have verified that we are NOT running WebDAV on the server. I am running Server 2008 R2 64bit as a file server only, and we have Windows 7 64bit clients. We have about a hundred Notebooks, one for each of our projects, and we are unable to open any of them. We get the error "onenote needs a password to sycnch some of your notebooks, click here to see a list of notevbooks and sections". As people have noted above, there is no way to enter a password in Onenote.

We can have all of our employees go through the full UNC path, but we have a very deep tree to our projects directory, so I know that there is going to be a lot of problems. Is anyone else getting this problem and they don't have WebDAV running? This is a big problem for us, if Notes is going to be broken for several months, this will need to move on to another program. The fix above may work for new notebooks, but we need access to our existing notebooks.

re: OneNote 2007 SP1 - Can't Create notebooks On Some Servers

Axel Doms — Mon, 08 Feb 2010 09:35:56 GMT

I recently ran into a very similar onenote problem but not quite identical.

OS : Windows XP SP2 (Dutch)

Office : 2007 Enterprise SP2 (Dutch)

Issue :

Creating a new notebook over a UNC paths work fine, but that same path mapped as a network drive does not work. Instead of taking the mapped drive Onenote again tries to put http:// in front of it, treating it as webdav.

This issue does not occur before installing SP2, so I am running without it.

The patch that fixed the SP1 issue (http://support.microsoft.com/kb/950130) does not work on this one (says that it is not applicable)

re: OneNote 2007 SP1 - Can't Create notebooks On Some Servers

SBobcat — Wed, 07 May 2008 02:48:21 GMT

I have experienced the problem, thought the work-around seems to work.

re: OneNote 2007 SP1 - Can't Create notebooks On Some Servers

bdmorgan72 — Mon, 21 Apr 2008 19:26:57 GMT

I'm experiencing this problem. I have full control of the directory in which I want to create the new notebook. Tried the workaround, which allows me to open the notebook, but will not sync and create the actual section files within the notebook. I've tried copying notebooks from other sources (i.e. my C: drive), but same problem when I try to open those notebooks in the shared directory location. In fact, if I've copied one of these notebooks and the corresponding sections to the new shared locations, I'm not able to see the sections in the notebook at all.

I also get the dialog box at the top of the notebook: "OneNote needs a password to sync some of your notebooks. Click here to see the list of sections and notebooks that require passwords."

Of course, there's no password prompt, and syncing won't work.

I'm not sure what is running on the server, as I'm not the network admin. I was under the impression that it was simply a file server, and didn't offer any web services, but I can't say that for sure. This problem will keep me from implementing a shared documentation project for my employer using onenote until this is resolved. Drat. Guess we'll just have to stick with the hundreds of word documents scattered all across the network in the meantime. Uggghh.

re: OneNote 2007 SP1 - Can't Create notebooks On Some Servers

enagel — Sat, 12 Apr 2008 03:05:39 GMT

David,

Yep I ran into it too and it was driving me crazy before I found your post. I have a SOHO set-up and I've got everrything on one server here, so I guess I'm one of those guys likely to get hit with the problem. Your workaround worked great... whew!

Thanks so much for putting this up.

re: OneNote 2007 SP1 - Can't Create notebooks On Some Servers

BetaBet — Mon, 17 Mar 2008 20:22:36 GMT

Hello- I am very interested in the outcome of this issue. I have a ReadyNAS box which supports webDAV through an add-on component. I verifed the "cannot create" error message. However, it seems there is an additional issue of synchronization. Reference

http://blogs.msdn.com/descapa/archive/2007/02/20/follow-up-to-webdav-support-with-onenote-2007.aspx

which states:

"For clients running Windows XP

=====================

Unfortunately in XP, OneNote notebooks on plain WebDAV servers won't be

supported. The reason being XP issues unauthenticated OPTIONS, PROPFIND, and

MOVE WebDAV requests even when the client is authenticated. Because these

requests fail on secured DAV servers, OneNote fails to sync.

If you insist, there is an UNSUPPORTED work around to enable this scenario.

To do this, enable unauthenticated OPTIONS and PROPFIND requests on your DAV

server. Please do not, I repeat, DO NOT, allow unauthenticated MOVE requests

for security reasons. This allows XP OneNote clients to host notebooks on a

plain DAV server, but won't be able to rename or move sections.

To do this on Apache, edit httpd.conf to allow unauthenticated access for

PROPFIND and OPTIONS requests to the notebook.

For example, it may look like this:

AuthType Digest

AuthName DAV

AuthUserFile conf/digest.passwd

require valid-user

</LimitExcept>

For Clients Running Vista

================

In Vista, accessing WebDAV with basic authentication over non-SSL servers is

flat out not allowed. That's because we don't ever want to send your

For all other WebDAV servers, OneNote notebooks on WebDAV servers should be

supported in Vista. However, we've hit some issues that prevent this from

working and we're working with the Windows WebDAV team to fix that up. Stay

tuned for an update on this soon...

Hope this helps,

David Tse[MS]"

This suggests that even if the create problem is fixed, OneNote and webDAV will not play nicely. I tried a sync process with the ReadyNAS and it ran for a very long time eventually aborting with a stack overflow error code. This happened repeatedly with a Windows XP Pro workstation connecting to the ReadyNAS locally. Hope this info is of some help-I am hoping that both ambiguity of what works and what doesn't and fixed to the concrete stuff will happen as we have a real need for XP, ReadyNAS, and OneNote shared notebooks to function.

re: OneNote 2007 SP1 - Can't Create notebooks On Some Servers

DavidRas — Sun, 16 Mar 2008 17:25:51 GMT

Just an update on this for everyone. Thanks everyone for providing details on your configuration. We now have a fix internally for this problem that we believe addresses all these cases. We're going through test processes and release processes to get this publicly available. This process takes a while (a couple of months for non-security fixes...).

Scot, thanks for the details on what happens when sending a link. That looks like a manifestation of this bug. You can manually rewrite the link address as you have done above and then it should work. That would be a work around for now, but we'll make sure that is fixed as part of this too.