archive-nl.com » NL » M » MAVENTION.NL

Total: 609

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Blog - Mavention
    access to SQL Server Aangemaakt op 22 1 2015 door Octavie van Haaften Find All Activated Web Analytics Features When upgrading SharePoint 2010 to SharePoint 2013 the web analytics service application and features should be removed prior to the upgrade process Aangemaakt op 2 10 2014 door Octavie van Haaften Updated Mavention Profile Info App Today an update for the Mavention Profile Info app is available in the Office Store

    Original URL path: http://www.mavention.nl/blog?k=PublishingContactNameOWSTEXT%3a%22Octavie+van+Haaften%22&start=5 (2016-02-18)
    Open archived version from archive


  • Blog - Mavention
    12 2011 door Octavie van Haaften Creating additional SharePoint 2010 farm administrators Lately I have noticed that people are struggling with user accounts that need to be a SharePoint 2010 Farm Administrator Aangemaakt op 8 11 2011 door Octavie van Haaften Customizing ListItem Forms using RenderingTemplates I was asked to add the SocialCommentWebPart on the display form for a particular list so users can comment on a list item If you are not a developer you would probably start SharePoint Designer right now create a custom Display Form and add the webpart to this form and voilá But if you are a developer you want this solution to be deployable and maybe generic Aangemaakt op 6 9 2011 door Octavie van Haaften How to disable the process termination by IIS when debugging When you are writing great lines of code for your SharePoint solution you ll probably be testing and debugging that code as well You deploy your solution attach Visual Studio to the worker process and when the debugger hits the breakpoint you examine what happens and read the values of your variables at that moment And before you know it you get the message that IIS has terminates

    Original URL path: http://www.mavention.nl/blog?k=PublishingContactNameOWSTEXT%3a%22Octavie+van+Haaften%22&start=26 (2016-02-18)
    Open archived version from archive

  • Unexpected exception - Failed to process hub site - Blog - Mavention
    can see the settings and you are also able to run it now The Issue To examine my issue I created a content type in the hub and published it Then I ran the Content Type Hub timer job To see the logging information I needed to know on what server the timer job is executing This information can be found on the Job History page Then I logged in on that server and started the ULS Viewer tool I ran the timer job Content Type Hub once again and monitored the ULS Then an exception was thrown Failed to process hub site http sharepoint sites cthub The changeToken refers to a time before the start of the current change log Aha There is the issue What is this changeToken and Change Log Every web application has a setting for its change log This can be found at the web application management page and then Resource Throttling settings for the selected web application The change log keeps track of all changes in sites lists and items For more detailed information http msdn microsoft com en us library bb447511 v office 14 aspx It keeps this information for 60 days by default My issue was apparently that I had no changes at all for over 60 days in the Content Type Hub site The last synchronization by the Content Type Hub timer job stored a changeToken that was before the start of the current change log and that threw an exception Solution When searching the net for a solution I encountered several posts about this issue Not entirely the same situation like I have but close enough This issue occurred on SharePoint 2010 installations up to June 2011 CU and a hotfix was released then http support microsoft com kb 2553016

    Original URL path: http://www.mavention.nl/blog/unexpected-exception-failed-to-process-hub-site (2016-02-18)
    Open archived version from archive

  • SharePoint 2013 Search Continuous Crawling - Blog - Mavention
    minutes In the first schedule A the crawler retrieves a content set and can handle that set within 15 minutes No problem here The next schedule B is executed and this time the crawler retrieves a bigger content set but now it cannot be handled within 15 minutes but it takes 20 minutes Now a problem arises Because only one crawler at a time can be executed the third schedule will be killed immediately We have to wait for the next window that the schedule takes place This will be C at 45 minutes So in this case we had 30 minutes between 2 Incremental Crawls instead of the scheduled 15 minutes So the bigger the content set to handle by the crawler to more risk there is to miss scheduled crawling windows This results in a lesser up to date search index SharePoint 2013 Now Continuous Crawling comes to the rescue With Continuous crawling you don t have to schedule anymore Crawlers are running in parallel and the crawler gets changes from the SharePoint sites every 15 minutes This is the default setting and it can be changed using PowerShell So when a crawl is executed and finished it continues to crawl immediately in spite of the length In our previous situation when a crawl is taking more then 15 minutes to handle the content set another crawler is started It is even possible that a second crawl is started only a few minutes after the first crawl This way your newly added or changed data is almost immediately available through search How cool is that Now a few things to bear in mind Continuous crawls can only be enabled for content sources based on SharePoint sites Also it can be resource intensive for your server running all the

    Original URL path: http://www.mavention.nl/blog/sharepoint-2013-search-continuous-crawling (2016-02-18)
    Open archived version from archive

  • Content Type Hub Inconvenient Updates - Blog - Mavention
    a document library and I will rename the content type and let s see what the results are Before The My Content Type in the library is inherited from the site content type My Content Type The latter one has been published from the content type hub And by design all published content types are readonly After I renamed the content type My Content Type to My Renamed Content Type in the hub republished it started all necessary timer jobs and went back to my document library So the site content type is updated but not the library one For us developers this seems like a SPContentType Update and not a SPContentType Update true The quest But let s take a deep dive into the code I use ILSpy but Reflector will do too The update is performed by the Content Type Subscriber timer job After some searching and digging it all starts with the assembly Microsoft SharePoint Taxonomy and the namespace Microsoft SharePoint Taxonomy ContentTypeSync Internal Starting from SubscriberTimerJobDefinition jumping to SubscriberImport and you will see the SynchronizeSite method Some interesting lines of code are 1 2 3 subscriberImport Import current subscriberImport ImportContentType current In both methods you will

    Original URL path: http://www.mavention.nl/blog/content-type-hub-inconvenient-updates (2016-02-18)
    Open archived version from archive

  • Error "The content type is in use" explained - Blog - Mavention
    not checked in yet Try this you have a Document Library with your content type as default and check out check in is required Then you upload multiple documents After the upload the items are still checked out and you are the only one that can see them As of this moment your content type cannot be deleted Everything needs to be checked in and modify the content type for each item Previous minor version exists Try this you have a Document Library with Minor Major versioning enabled Upload a document and give it your content type Publish your document to version 1 0 Then edit the properties and give it another content type This will be 1 1 As of this moment your content type cannot be deleted You ll need to publish it first to the next major version So you have checked everything No content using the content type Recycle Bins are empty etc Sure Well I can tell you that you still might not be able to delete the content type Trying so can show you this error message Some lovely SharePoint solution WSP with a feature deployed the content type And to protect the solution

    Original URL path: http://www.mavention.nl/blog/error-the-content-type-is-in-use-explained (2016-02-18)
    Open archived version from archive

  • SharePoint 2013 It’s here! - Blog - Mavention
    now part of Search The SharePoint App Management Service allows you to install SharePoint apps from the Office Marketplace or the App Catalog It s responsible for storing and providing information regarding SharePoint App licenses and permissions The SharePoint Machine Translation Service allows you to automatically translate content It provides built in machine translation capabilities on the SharePoint platform It can translate documents pages and sites The SharePoint Machine Translation Service uses an online service and therefore the server running this Translation Service needs to have a connection with the internet On port 80 and that may be an issue for some companies Other service applications have improved in many ways Business Connectivity Service BCS supports SharePoint Apps BCS models for Apps are scoped at the app level and not farm level BCS provides alert capability for external lists that have improvements for performance filtering sorting export to Excel Developers can access BCS with CSOM The User Profile Service has improved mainly the synchronization part Better performance more reliable and compatibility AD Connections can now be set up with AD Direct Import and not using FIM I was able to setup this AD Direct Import successfully However the steps to

    Original URL path: http://www.mavention.nl/blog/sharepoint-2013-its-here (2016-02-18)
    Open archived version from archive

  • Blog - Mavention
    22 8 2014 door Octavie van Haaften Adding Site Logo Not Working Properly During some tests in my project I have noticed some strange behavior when adding a site logo This blog post describes 2 issues and what caused them Aangemaakt op 23 5 2014 door Octavie van Haaften Beware of styling changes after SP1 When planning to install Service Pack 1 you should test everything to make sure it

    Original URL path: http://www.mavention.nl/blog?k=PublishingContactNameOWSTEXT%3a%22Octavie+van+Haaften%22&start=10 (2016-02-18)
    Open archived version from archive



  •