European Sharepoint 2013 Hosting Blog
Articles about European Sharepoint Hosting Service
SharePoint 2013 Hosting – HostForLIFE.eu :: Send Email from SharePoint using JSOM
Sep 19th
To send emails from SharePoint, we use SharePoint workflow or SharePoint Utility Email using C#. But what if you want to send emails from your client-side code. So, recently I faced a situation where I have to send emails from my client-side code where I was using JSOM as CEWP mythology. So, I was looking for a way where I found “SP.Utilities.Utility.SendEmail” in my searches. And it is really a very simple way to send email. But there is only one catch on which we have to be concerned as the email recipient(s) have to be the users who have visited the site. Any email accounts that have not been authenticated to SharePoint will throw an error.
Here is the code given bellow:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 |
var sendEmail=()=>{ const emailProps= { To: [], CC:[], Subject: "<Email Subject>", Body: "<Email Body>" }; var siteUrl = "www.tahmid.sharepoint.com/sites/RnD"; //Provide your SharePoint site address var urlTemplate = siteUrl + "/_api/SP.Utilities.Utility.SendEmail"; getFormDigest(siteUrl).then((data)=> { $.ajax({ contentType: 'application/json', url: urlTemplate, type: "POST", data: JSON.stringify({ 'properties': { '__metadata': { 'type': 'SP.Utilities.EmailProperties' }, 'To': { 'results': emailProps.To }, 'Body': emailProps.Body, 'Subject': emailProps.Subject, 'CC': { 'results': emailProps.CC }, } }), headers: { "Accept": "application/json;odata=verbose", "content-type": "application/json;odata=verbose", "X-RequestDigest": data.d.GetContextWebInformation.FormDigestValue }, success: function(data) { console.log("Email Sent"); }, error: function(err) { console.log("Got Error"); } }); }); } var getFormDigest=(webUrl)=>{ return $.ajax({ url: webUrl + "/_api/contextinfo", method: "POST", headers: { "Accept": "application/json; odata=verbose" } }); } |
Here is the way to call the function sendEmail().
|
1 2 3 |
$(document).ready(()=>{ sendEmail(); }); |
In the real-time use, you can send the emailProps when you call the function as parameter. So, before ending the article, just a note that if you get a 403 Forbidden error, following two things could be happened in most cases. You are not getting the context as in you should check that you are getting the digest. If that’s not the case, then upgrading to a newer version of jQuery may solve the issue.
SharePoint 2013 Hosting Recommendation
HostForLIFE.eu’s SharePoint 2013 Hosting solution offers a comprehensive feature set that is easy-to-use for new users, yet powerful enough for the most demanding web developer expert. Hosted SharePoint Foundation 2013 is the premiere web-based collaboration and productivity enhancement tool on the market today. With SharePoint 2013 Foundation, you can quickly access and manage documents and information anytime, anywhere though a Web browser in a secure and user friendly way. SharePoint hosting services start at only at €9.99/mo, allowing you to take advantage of the robust feature set for a small business price. HostForLIFE.eu offers a variety of hosted SharePoint Foundation 2013 plans as well as dedicated SharePoint 2013 Foundation options.
SharePoint 2013 Hosting – HostForLIFE.eu :: Reason For Request Timed Out Error In SharePoint Search
Sep 12th
Sometimes while we work on SharePoint search, we may see the “Request timed out” error in the browser even though the search application topology (all search databases) status is fine. As an example, the status shows as below.
Background of the issue (description)
Let’s say we have a multi servers farm where all web applications hosted in WFE and all SharePoint service are running in App server. The server topology is as below:
- App Server with Search and
- WFE server.
We have configured the search service application in the application server and all components of search crawl are happening fine without any errors. However, if we try to search any item from SharePoint web application, the search box will try to continue to search the item but after a long time we will see the error “search query time out error timed”.
If we look at the uls log, we can see the below entry.
:SearchServiceApplicationProxy::GetQueryHealthMonitoringSettingsForComponents–Error occured: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening to thttp://appserver:32843/db4796fcfe375bd791f98ec5e485999c/SearchService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond :32843 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
Solution
This is the port connectivity issue between WFE and APP server. Ask your system/network admin team to configure the 808,32843,32844 port in WFE and APP server.
Summary
Thus, in this article, we learned the exact causes of the “Request timed out” error with respect to the SharePoint search and the solution.
SharePoint 2013 Hosting Recommendation
HostForLIFE.eu’s SharePoint 2013 Hosting solution offers a comprehensive feature set that is easy-to-use for new users, yet powerful enough for the most demanding web developer expert. Hosted SharePoint Foundation 2013 is the premiere web-based collaboration and productivity enhancement tool on the market today. With SharePoint 2013 Foundation, you can quickly access and manage documents and information anytime, anywhere though a Web browser in a secure and user friendly way. SharePoint hosting services start at only at €9.99/mo, allowing you to take advantage of the robust feature set for a small business price. HostForLIFE.eu offers a variety of hosted SharePoint Foundation 2013 plans as well as dedicated SharePoint 2013 Foundation options.
SharePoint 2013 Hosting – HostForLIFE.eu :: Resolving Wrong Tenant Credentials Error Even Though We Pass The Correct Credential
Sep 5th
Sometimes, while we work with PowerShell and SharePoint online, we may come across the above error. I will explain in which scenario we’ll get wrong tenant credential error while connecting to SharePoint online thru the PowerShell even though we pass the correct credential and how to fix it.
Issue Description
Recently, I was working on how to configure the hybrid environment for our tenant. In order to do that I had picked up the Hybrid Picker Wizard, followed the instructions, and started the configuration. At the initial steps, this will validate your on-premises SharePoint credential and SharePoint online credential. I was using the same account for both on-premise and online wherein on-premise SharePoint authentication was successful but authentication in SharePoint Online was failing – the error message was saying that “Wrong tenant credential.” like below.
It was strange!!! I had tried to log in to SharePoint online site using the same credential and it was successful, and tried to connect SharePoint online site through the ShareGate migration tool using the same credential, and it was successful. It became ever more strange.
In order to do the hybrid configuration as an alternative approach, Microsoft has provided two inbuilt PowerShell Script. I tried to execute those scripts there also but faced the same authentication issue.
Solution
- If your account has MFA (multi-factor authentication) enabled in Azure AD, you cannot connect to SharePoint online using PowerShell or Hybrid Picker Wizard as a temporary solution for time being disable the MFA in Azure AD, then after getting your work done enable it back – after MFA disabling you will not face the above issue.
- Have a dedicated service kind of admin account without MFA enabled and use this account for all sorts of PowerShell execution with respect to SharePoint online and Hybrid Picker configuration – as per me this is recommended or good choice over the previous one.
SharePoint 2013 Hosting Recommendation
HostForLIFE.eu’s SharePoint 2013 Hosting solution offers a comprehensive feature set that is easy-to-use for new users, yet powerful enough for the most demanding web developer expert. Hosted SharePoint Foundation 2013 is the premiere web-based collaboration and productivity enhancement tool on the market today. With SharePoint 2013 Foundation, you can quickly access and manage documents and information anytime, anywhere though a Web browser in a secure and user friendly way. SharePoint hosting services start at only at €9.99/mo, allowing you to take advantage of the robust feature set for a small business price. HostForLIFE.eu offers a variety of hosted SharePoint Foundation 2013 plans as well as dedicated SharePoint 2013 Foundation options.
SharePoint 2013 Hosting – HostForLIFE.eu :: InfoPath-Add Newline In Multiline Text Box Using XML file (SharePoint)
Aug 29th
Here, we will discuss how to add a new line in multiline textbox using XML file in InfoPath.
Let’s start to create the XML file with standard coding. Please follow the below steps to achieve this.
You can copy the code directly from here as well.
Now, your file is ready with code. Now, follow the below steps to implement this task.
Upload your file under SharePoint Site Asset Library.
Try to create a data connection with the connection type as retrieve data.
Click on “Next” and choose the XML file option.
Go to SP site asset and try to copy your XML file path and paste here.
And, finish the Data Connection Creation here.
You have to create a simple text box control, go the textbox properties, and enable the multiline textbox.
Now, you can manage the rule and apply the data connection for a new line in a multiline textbox. I hope your issue has been resolved now.
SharePoint 2013 Hosting Recommendation
HostForLIFE.eu’s SharePoint 2013 Hosting solution offers a comprehensive feature set that is easy-to-use for new users, yet powerful enough for the most demanding web developer expert. Hosted SharePoint Foundation 2013 is the premiere web-based collaboration and productivity enhancement tool on the market today. With SharePoint 2013 Foundation, you can quickly access and manage documents and information anytime, anywhere though a Web browser in a secure and user friendly way. SharePoint hosting services start at only at €9.99/mo, allowing you to take advantage of the robust feature set for a small business price. HostForLIFE.eu offers a variety of hosted SharePoint Foundation 2013 plans as well as dedicated SharePoint 2013 Foundation options.
SharePoint 2013 Hosting – HostForLIFE.eu :: How to Fix The Server Could Not Complete your Request SharePoint 2013?
Aug 22nd
Today, I will explain you How to fix the server could not complete your request SharePoint 2013. When I tried opening SharePoint 2013 site in SharePoint Designer, I got the following error:
When I clicked on Details, it opened another dialog and continuously pop up window is opening and not able to open the SharePoint site.
And here is the error message:
Solution:
1. Go to Run -> then type Inetmgr -> Now Open the IIS
2. In the Web Sites select “SharePoint Web Services” in the list as you can see on the following picture
3. Next step, click on the Authentication and Enable “Anonymous Authentication” as shown on the below picture:
4. After enabling this, I am able to open the SharePoint site in designer without any issues.
SharePoint 2013 Hosting Recommendation
HostForLIFE.eu’s SharePoint 2013 Hosting solution offers a comprehensive feature set that is easy-to-use for new users, yet powerful enough for the most demanding web developer expert. Hosted SharePoint Foundation 2013 is the premiere web-based collaboration and productivity enhancement tool on the market today. With SharePoint 2013 Foundation, you can quickly access and manage documents and information anytime, anywhere though a Web browser in a secure and user friendly way. SharePoint hosting services start at only at €9.99/mo, allowing you to take advantage of the robust feature set for a small business price. HostForLIFE.eu offers a variety of hosted SharePoint Foundation 2013 plans as well as dedicated SharePoint 2013 Foundation options.
SharePoint 2013 Hosting – HostForLIFE.eu :: Import A Specific Module From The Installed SharePoint PnP Powershell Modules
Aug 15th
When working with different versions of SharePoint, we have the respective PnP modules installed. This article explains how to easily load the appropriate Module automatically. I use SharePoint PnP PowerShell cmdlets almost every workday to make a lot of customizations and to perform administrative tasks. I guess no introduction is needed about PnP PowerShell with its huge usage and popularity.
Now, if you are a user like me who is working on different versions of SharePoint, 2013, 2016, 2019 & Online, using the right PnP PowerShell module to target the SharePoint version is tedious. When you install different PnP PowerShell modules (i.e., 2013, 2016, 2019 & Online), we have a cmdlet name conflict because all the modules have the same name for the cmdlets. And none of the modules are loaded initially when you open a PowerShell session.
How are the modules loaded?
When you first run any PnP PowerShell cmdlet (obviously Connect-PnPOnline), the PnP PowerShell module is automatically loaded based on the modules path. Though most of the cmdlets work the same in all versions of SharePoint, there are significant changes in how the authentication is handled and SharePoint Online always has few more cmdlets compared to the On-premise versions. So, we need to load the specific PnP Module depending on the SharePoint version we are using.
Which module (2013, 2016, 2019, Online) is loaded?
When you have different modules installed, PowerShell picks the modules to load from the default modules path (in environment variables). As this appears to be alphabetical, 2013 module is loaded by default in my case.
PowerShell by changing the PSModulePath in environment variables, and using Import-Module whenever we need to target for a different version of SharePoint. This is quick workaround is helpful, but we have to run the Import-Module cmdlet every time we need to use a different version of the PnP SharePoint module.
Another approach to do this
Isn’t it cool to have different icons like this to target the PnP PowerShell module for the specific SharePoint version? This way, you don’t have to manually run any Import-Module cmdlets. These are desktop shortcuts for PowerShell specifying which module to load using the shortcut parameters. And when we open any shortcut, PowerShell is opened with the respective PnP Module already loaded.
This way, I can easily open a PowerShell session for the respective SharePoint version without the hassle of typing Import-Module cmdlets always.
How to do this?
- Right click on your desktop to create a new shortcut
- In the create shortcut window, in the location of the item text box, type the following command.
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoExit -Command “Import-Module -Name ‘C:\Users\ram\AppData\Local\Apps\SharePointPnPPowerShell2016\Modules\SharePointPnPPowerShell2016\SharePointPnPPowerShell2016.psd1’ -DisableNameChecking;”
- And click Next. This basically specifies that we open PowerShell and load the module targeted for SharePoint 2016.
- Type the name (target version of SharePoint) and click Finish.
Now, whenever I open PowerShell with this shortcut, I am ready to write cmdlets for SharePoint 2016. Similarly I keep 4 different shortcuts for 2013, 2016, 2019 and SharePoint Online which is handy, as I dont have to run the Import-Module cmdlet whenever I need to target a different version of SharePoint.
Summary
This shows a simple solution using the windows shortcuts and the -Command parameter to start the powershell, and to load a specific PowerShell module, enabling us to create quick shortcuts for opening the right PnP module.
