Okay, I figured it out, kinda stupid, but I'll post the solution for others...

You need a separate file from the license.episerver.com site, I then reïnstalled and provided the file... 

Unfortunatly I'm still stuck with this connector :s Am I supposed to configure a Content Channel? and what other configurations am I supposed to make? If I now go to the File Manager, it just says "A folder for this page has not been created, do you wish to create one now?" Clicking the "Create page folder" doesn't do anything :s

Any help would be appreciated!!!

Hi Veerle,

If you want to access SharePoint files from CMS File Manager - all you need to do is to configure Virtual Path Provider for SharePoint as it is described in installation instructions here.  The message "A folder for this page has not been created, ..." could mean that you have a wrong SharePoint server URL or Document Library name. Please check Virtual Path provider for SharePoint configuration in episerver.config, it should look like:

<add name="SharePointFiles" showInFileManager="true" bypassAccessCheck="false"
  virtualPath="~/SharePoint/" isMOSS="False" wssSiteUrl="http://vm-sp"
  wssDomainName="" wssLogin="Administrator" wssPassword="p@ss1word" useImpersonation="false"
  virtualName="SharePoint" customFileSummary="~/WSSFileSummary.config"
  useCache="True" cacheExpirationTime="30"
  type="EPiServer.VirtualPathWssProvider.VirtualPathWssProvider,EPiServer.VirtualPathWssProvider"
  wssRootFolder="Shared Documents" />

Thanks for your reply!

I ran through those installation instructions but couldn't find where exactly to find the virtual path configuration, so thank you for that. I checked the episerver.config file and I have everything seems okay. I did have to add the "wssRootFolder" property but adding that didn't change anything. I still get the same error in the File Manager.

Could my EPiServer & SharePoint Content Channel be missconfigured? When I try to send content I get errors syaing there were no virtualPathProviders configured to handle the virtual path... I currently have a Library Boekenlijst and a library Shared Documents and I get errors "There is no VirtualPathProvider configured to handle virtual path ~/SharePoint/Boekenlijst/filename.docx, same for Shared Documents... Am I supposed to make a virtual path in the episerver.config for each of these, so ~/SharePoint/Boekenlijst and ~/SharePoint/Shared Documents???

Thanks in advance

Well I'm actually trying both :P

I will try debugging in a minute, but if I understand correct both functions require the VVPs and since neither of the functions work, couldn't I just presume the problem lays with the VVPs?

Content Channel does not require VPP for SharePoint, it can be configured to use any VPP and usually a local CMS file storage is used (like ~/Global/ or ~/Documents/).

Although I'm not entirely sure what I changed, but it works now! I reïnstalled the Connector and now both functions work :)

Thank you Sergii for your answers and explanation!

I have one more question :p

In the second function of pushing the content from SharePoint to EPiServer, I receive two libraries, which is correct because that is how I set the Channel.

In the first function of just showing content from SharePoint in EPiServer, I receive several libraries (Site Assets and Style Library aswell), but when I create a new library this is not shown. How does this work, how is determined which content is shown and which is not?

Thanks!

Never mind, I see now that only Libraries are shown.

Once again thank you for your help!

To be precise only this types of libraries are supported by VPP for SharePoint:

Documents library
Pictures library
Forms library