Home Blog Page 5

Clearing the InfoPath Cache

0

 Clearing the InfoPath Cache

When you load an InfoPath form, it is cached in the following location on your machine:
          C:\Documents and Settings\[User]\Local Settings\Application Data\Microsoft\InfoPath\[FormCache2]
When a new version of the form is detected, such as when a new version of the form is installed in a SharePoint Forms library, the cached form will be deleted and the new one installed in it’s place.
You can also manually clear the Infopath cache by deleting the files.
Or you can do it via command line by:
            Start > run > Infopath /cache clearall

Copying SharePoint 2010 Workflows

0

 Copying SharePoint 2010 Workflows

When working with SharePoint Workflows, we are usually required to moving or copying a workflow that is created using SharePoint designer between sites or SharePoint List (including the document library, form library…). Following is the How-To steps
To accomplish this, we will use a little tweak associated with the workflow.

  1. In the original (source) site or list, create the required workflow, save and publish it.
  2. Now select Export to Visio option which allows you to save the workflow with a .vwi extension. (Refer this workflow hereafter as source workflow). For instance, Source_WF.vwi
  3. Now go to the destination site or list where you want the workflow to be copied, and create a new workflow with the same name as the previous one & publish it.
  4. Do the same thing at step 2, select Export to Visio option which allows you to save the workflow with a .vwi extension. (Refer this workflow hereafter as Destination workflow). For instance, Destination_WF.vwi
  5. Now you will be having two .vwi files (one of source workflow’s – Source_WF.vwi and other of the destination workflow’s – Destination_WF.vwi). Now add .zip extension to both the files. Now your files names should be Source_WF.vwi.zip & Destination_WF.vwi.zip.
  6. Now open both the zip files, copy workflow.xoml.wfconfig.xml from destination workflow to source workflow. (Its destination to source and not source to destination).
  7. From now on, we will not use the file Destination_WF.vwi.zip. So ignore that file.
  8. Remove the .zip extension from Source_WF.vwi.zip which gives you the Source_WF.vwi file.
  9. Now, go to the destination site, open workflows and click Import from Visio and browse to the Source_WF.vwi file.
    That’s it and your workflow is copied. You can publish the workflow and run it.

Note: In case if your list’s GUID’s (for those lists that you have used in workflow – tasks list, history list or any other lists used in workflow steps) have been changed from source & destination site, you may need to update those steps in the workflow.
Cheers.

Execution permission cannot be acquired

0

 Execution permission cannot be acquired

Error Overview

Execution permission cannot be acquired.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details:

System.Security.Policy.PolicyException: Required permissions cannot be acquired.
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Boolean checkExecutionPermission)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Int32& securitySpecialFlags, Boolean checkExecutionPermission)

Root cause and how to resolve

The error is that there is an assembly is trying to load which has an assembly level RequestMinimum security set specified. The CLR security policy was not going to grant that assembly what it had asked for in its minimum grant set, so the assembly was not loaded and that exception was thrown.
You’ll need to find which assembly is failing to load, It might be an orphan dll when you retract a farm solution or third party solution in your farm, then delete it (or move it over to another location for backup)
In this case, I think there is a dll that related to Ajax is stored in BIN folder of Admin Central virtual directory, such as C:inetpubwwwrootwssVirtualDirectories25108bin. You could take a look at this location and delete it.

User not in directory

0

User not in directory, External access issue on SharePoint Online

Overview

User can’t be found in the tenant.sharepoint.com directory. This is a common issue when your external users have accepted the invitation email with the link by using another email(that differs than the one that was invited) to log on your tenant. Then now he is trying to access by using the one was invited. That will be a problem with access.

 
When you invite/share something in SharePoint Online with someone outside your organization. SharePoint Online will store the emails once it sends out the invitation. So when the invited external user accepted the invitation and log on your SharePoint tenant with an email that differs than the one that was invited. This email will be marked as login credential for the invitation email. For instance, you invite/share something on your SharePoint tenant with UserA@pointtotech.com. When this user received the invitation email, he/she clicks on the link in the email and login with his/her personal email, such UserA@outlook.com. So it means that UserA@pointtotech.com on your SharePoint tenant will have the login credential is UserA@outlook.com, not UserA@pointtotech.com.
If you try to invite/share the user UserA@pointtotech.com to any other contents on your SharePoint tenant again, they also have to use the login credential UserA@outlook.com
If you run the power-shell command to get the information about the external user, you will see something like a picture as below:
Get-SPOExternalUser

Resolution

Okay so, how to resolve it? There are two steps to accomplish it (the order of steps doesn’t matter)
First, you need to remove the user, for example, UserA@pointtotech.com, from SharePoint front-end by following below steps or this article:

Delete selected users from site collection
Second, use SPO PowerShell to remove the user from your tenant:

  • Connect to your SharePoint tenant by following below command then enter your tenant admin credential

Connect-SPOService -Url https://tenant-admin.sharepoint.com -credential sharepoint-admin@tenant.com

  • Get User’s UniqueID by running

    Get-SPOExternalUser

  • Delete user by running

    Remove-SPOExternalUser -UniqueIDs {id}

Delete external user
Finally, do re-invite the user again. then you should good to go.

Managed Metadata Navigation not showing to users

0

Why is the Managed Metadata Navigation not showing to users? When you completed a Managed Metadata navigation, then trying to apply it to your SharePoint sites. For some reasons, however, the Managed Metadata Navigation is not showing to some specific users. Why is that?

 
There are two basic settings you could take a look to fix the issue:

  • First, create a customized permission level (recommend copy from existing one) then add ‘Manage Lists’ right to it. Or, use the ‘Edit’ permission level.

Terms store navigation
Permission Level

  • Second, use the Navigation Node Type instead of configure friendly URL settings on Term-Driven pages

Terms store navigation - navigation Terms store navigation - term driven pages
Refer:

How to redirect subsite to new url in SharePoint 2013

0

How to redirect subsite to new URL in SharePoint 2013 (without using the redirect page layout)

There are many options to redirect a page from SharePoint to a new location. Below is 2 essential scripts we can use to make it happens.
1. Use meta tag:
<meta http-equiv=”REFRESH” content=”10;url=https://yourcompanny.sharepoint.com/sites/HR/PTORequest.aspx“/>
With above meta tag, you will be redirected to new location at https://yourcompanny.sharepoint.com/sites/HR/PTORequest.aspx after 10 seconds
2. And another method is that we will use JavaScript to redirect to new location immediately
<script type=”text/javascript”>
// Redirect to the page
window.location=”https://yourcompanny.sharepoint.com/sites/HR/PTORequest.aspx”;
</script>
Next step is to apply one of them to the page you want to have a redirection by opening SharePoint page is edit mode.

  • Add content editor webpart (recommended even though you are using the non-publishing page)
  • Use the “Embed Code” for JavaScript
  • Use the “Edit Source” for Meta tag

Now you’re good to go

Error with Quick Edit mode in SharePoint 2013 List

0
Cannot create a new item with Quick Edit in SharePoint 2013. Here is the issue: “Sorry, you can’t create a new item with Quick Edit because this view is missing one or more required columns. To create a new item, please click “New Item” or add required columns to this view.”

Problem:

Sometimes there is an issue with adding a new item in Quick Edit mode of a SharePoint list, such as task, issue, custom list…
If you modify the view and add Name (for use in forms) to the view, you are then able to add a value to the column and SharePoint allows you to create a new record. It doesn’t seem to matter what you enter into the Name field when adding the record as it replaces my value automatically.

Actually, this column is related to File type and automatically created in your list. I am not sure why it happens and what purpose it is for. If you open that list in SharePoint Designer you will see there is a column called ‘Name’ and it is a File type.

To resolved the problem above, there is only one option is that we open that column in the browser from SharePoint Designer and update it as optional type. Then the issue should be resolved and you will be able to add a new item in Quick Edit mode.
Here are some How-TO pictures:

  • Select the Name column –> Click on Administration Web Page

  • Select No as below picture.


Note that the Name column will not be available to edit in SharePoint Designer, so do not try to update it from there such as double click or using the ribbon button

Add Icon for Webpart Tilte

0

This is a very basic about using SharePoint webpart.

SharePoint Webpart comes with a lot of features that we can use to customize a beautiful webpart. I will show you how to add an icon into your webpart title.

Let get started

Find your icon

There are many ways to get an icon. It very easy and convenient. I will show you a very simple way to get an icon and add it into your webpart.

  • Open the browser and navigate to http://iconfinder.com.
  • At the search box, do a search for any icon you want and you will be redirected to search result with a bunch of related icons

  • Now just select any icon you like, then change the icon size and click the download (some are free and some need a subscription). In this case, we just need an URL of the icon. So if you are using google chrome, just right click and copy the image URL. We will use this URL for the next part


Note: there are some purchase plans that you can sign up for premium icon and support

Use the icon in your webpart title

Now this is a time we use our icon URL from iconfinder.com

  • On the webpart page in edit mode, click on arrow down button to open the webpart property window

  • On the Webpart property window, expand the Advanced tab and paste the icon URL into the ‘Title Icon Image URL’

  • Now click on OK button, then save the page (and publish it if you are using publishing feature).

Finally, open your page and check your great outcome 🙂

Convert a sub site to site collection

0

Convert a sub site to site collection on SharePoint Online

Since we don’t have many options to move sites around on SharePoint Online environment like we have on On-Prem. Following is a quick and basic guideline how to move site around SPO. In this tutorial, I show you how to convert a sub site to Site Collection

Step 1. Save a site as template

  • Open any SharePoint site that you want to move and append to the end of site URL the path that follows “/_layouts/15/savetmpl.aspx“. For instance https://companyA.sharepoint.com/sites/HR/_layouts/15/savetmpl.aspx.

Step 2. Create a site collection from Admin portal

Step 3. Apply the template to new site collection

  • Now Open the new site collection. You should see as below picture

  • Just go ahead and select the Solution Gallery to upload your template site from step 1


  • Once the file is uploaded, click on Activate to make it available on custom tab for applying site template to the new site


Finally, Just confirm the existing user groups or create new groups then you good to good

SharePoint Administration Groups Level

0

Server or farm level

    • Farm Administrators group Members of the Farm Administrators group have Full Control permissions to and responsibility for all servers in the server farm. Members can perform all administrative tasks in Central Administration for the server or server farm. They can assign administrators to manage service applications, which are instances of shared services. This group does not have access to individual sites or their content.

  • Windows Administrators group Members of the Windows Administrators group on the local server can perform all farm administrator actions. Administrators on the local server can perform additional tasks, such as installing new products or applications, deploying Web Parts and new features to the global assembly cache, creating new Web applications and new Internet Information Services (IIS) Web sites, and starting services. Like farm administrators, members of this group on the local server have no access to site content, by default

Shared services level

  • Service application administrators These administrators are designated by the farm administrator. They can configure settings for a specific service application in a farm. However, these administrators cannot create service applications, access any other service applications in the farm, or perform any farm-level operations, such as topology changes. For example, the service application administrator for a Search service application in a farm can configure settings for that Search service application only.
  • Feature administrators A feature administrator is associated with a specific feature or features of a service application. These administrators can manage a subset of service application settings, but not the entire service application. For example, a Feature administrator might manage the Audiences feature of the User Profile service application.

Web application level

  • The Web application level does not have a unique administrator group, but farm administrators have control over the Web applications within their scope. Members of the Farm Administrators group and members of the Administrators group on the local server can define a policy to grant individual users permissions at the Web application level.

Site level

  • Site collection administrators These administrators have the Full Control permission level on all Web sites in a site collection. They have Full Control access to all site content in that site collection, even if they do not have explicit permissions on that site. They can audit all site content and receive any administrative message. A primary and a secondary site collection administrator can be specified during the creation of a site collection.
  • Site owners By default, members of the Owners group for a site have the Full Control permission level on that site. They can perform administrative tasks on the site, and on any list or library within that site. They receive e-mail notifications for events, such as the pending automatic deletion of inactive sites and requests for site access.