Exception calling “LoadFile” with “1″ argument(s): “An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See

I see what the issue is. Rightclick ClaimsAuth.dll > properties > unblock.

Seems to be a security feature of Microsoft that blocks all downloaded DLL´s.

 

image

 

image

Automatically created managed properties in SharePoint Server 2013

How site columns become managed properties

When you add columns to a SharePoint library or list, you can choose to add regular columns or site columns.

In SharePoint Server 2013, only site columns that contain values will automatically become managed properties when they are crawled. Regular columns will not automatically become managed properties when they are crawled.

Manually request crawling and re-indexing of a site, a library or a list

In SharePoint Online, content is automatically crawled based on a defined crawl schedule. The crawler picks up content that has changed since the last crawl and updates the index. In some cases, you may want to manually request crawling and full re-indexing of a site, a document library, or a list.

Re-index a site

WARNING    Re-indexing a site can cause a massive load on the search system. Don’t re-index your site unless you’ve made changes that require all items to be re-indexed.

  1. On the site, click Settings > Site Settings.
  2. Under Search, click Search and offline availability.
  3. In the Reindex site section, click Reindex site.
  4. A warning appears, click Reindex site again to confirm. The content will be re-indexed during the next scheduled crawl.
  5. image

image

Re-index a document library or a list

  1. On the site, go to the list or library that you want to re-index.
  2. In the ribbon, click the Library tab or the List tab.
  3. In the Library ribbon, choose Library Settings,
    or,

In the List ribbon choose List Settings.

  1. On the Settings page, under General Settings, choose Advanced settings.
  2. Scroll down to Reindex Document Library or Reindex List, and click the button. The content will be re-indexed during the next scheduled crawl.

image

 

image

Re-index after changing managed properties

When people search for content on your SharePoint sites, what’s in your search index decides what they’ll find. The search index contains information from all documents and pages on your site.

The search index is built up by crawling the content on your SharePoint site. The crawler picks up content and metadata from the documents in the form of crawled properties. To get the content and metadata from the documents into the search index, the crawled properties must be mapped to managed properties. Only managed properties are kept in the index. This means that users can only search on managed properties.

When you have changed a managed property, or when you have changed the mapping of crawled and managed properties, the site must be re-crawled before your changes will be reflected in the search index. Because your changes are made in the search schema, and not to the actual site, the crawler will not automatically re-index the site. To make sure that your changes are crawled and fully re-indexed, you must request a re-indexing of the site. The site content will be re-crawled and re-indexed so that you can start using the managed properties in queries, query rules and display templates.

You can also choose to only re-index a document library or a list. When you have changed a managed property that’s used in a library or list, or changed the mapping of crawled and managed properties, you can specifically request a re-indexing of that library or list only. All of the content in that library or list is marked as changed, and the content is picked up during the next scheduled crawl and re-indexed.

Learn more about search and crawled and managed properties in Manage the search schema in SharePoint Online.

New Managed Property limitation on SharePoint Online

In SharePoint Online, when you create a new managed property, it will have some limitations. For example, the property can only be of typeText or Yes/No, and it can’t be refinable or sortable.

Yup, no sorting for you, and no refinement panel goodness. And no search queries against date ranges. You can potentially search for a particular date, but not ‘between 1st Feb and 23rd March’.

 

I hope Microsoft can improve this function at least provide date ranges for the search query

How to activate SharePoint Server Publishing Feature for a site

Site

The feature being activated is a Site scoped feature which has a dependency on a Site Collection scoped feature which has not been activated. Please activate the following feature before trying again: SharePoint Server Publishing Infrastructure f6924d36-2fa8-4f0b-b16d-06b7250180fa

Web

The Site scoped feature being activated has a dependency on hidden Site scoped feature ‘FeatureDefinition/15/22a9ef51-737b-4ff2-9346-694633fe4416′ (ID: ’22a9ef51-737b-4ff2-9346-694633fe4416′). Hidden features cannot be auto-activated across scopes. There may be one or more visible Site scoped features that auto-activate the dependent hidden feature.

Web

The Site scoped feature being activated has a dependency on hidden Site scoped feature ‘FeatureDefinition/15/dffaae84-60ee-413a-9600-1cf431cf0560′ (ID: ‘dffaae84-60ee-413a-9600-1cf431cf0560′). Hidden features cannot be auto-activated across scopes. There may be one or more visible Site scoped features that auto-activate the dependent hidden feature.

If you got the above error, just following the steps below:

Log into this specific site collection as administrator.
- Go to Site settings and click Site collection features in the Site Collection Administrationsection.

- Activate SharePoint Server Publishing infrastructure feature.

Then go to you web –> Site Settings –> Manager Site Feature

image

Remove Vertical scroll bar in client web part SharePoint 2013

image

#s4-workspace
{
    overflow:visible !important;
}

image
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }

add this into your app css. it will remove the scroll bar.
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }

Follow

Get every new post delivered to your Inbox.

Join 39 other followers