2013 – Expired Workflow Manager certificates

OK, you have the same problem as before. At WFM, you have to replace the certificates before they expire.
You can either:

1. Recreate the WFM farm with new certificates and use the DR Restore method to retrieve the old WFM farm data.

2. Do a little hack.
Basically you need a third (intermediate) certificate, the validity of which extends over your old and new certificate. Nobody will backdate the certificate for you. However, you can trick the system with a self-signed certificate that you create on a computer with the clock turned back. (Please note that I only used this method on the QS scheme. I would choose option 1 for PROD.)

Problem with Workflow Manager 2013 is that you cannot update the certificate when it expires. You have to do it before it expires. Here's how to do it. I did it like this:

  1. Move the clock back to the server and create a new self-signed certificate that spans the old and new certificates.
  2. The time on the server is synchronized so you have to change it again.
  3. Change the time (before the original certificate expired) and update the Workflow Manager certificate to selfSigned.
  4. Wait for the time synchronization and now change the certificate to your new certificate

2013 – SearchExecutor does not return results with non-privileged users

In short "test user" is "TE", "administrator user" is "admin".

I am currently working on a SharePoint project in Visual Studio that provides a web part that uses the search engine. The code returns values ​​for the administrator, but this is not the case for TE. TE has rights to some items.

My goal is to search with TE and get the items that he has access to. Do you know a way to do this?

Now the code looks like this:

internal static DataTable Search(string query, string urlSite, List properties, KeywordInclusion typeSearch)
{
  DataTable dataTable = null;
  using (SPSite site = new SPSite(urlSite))
  {
    site.AllowUnsafeUpdates = true;

    KeywordQuery keywordQuery = new KeywordQuery(site);
    keywordQuery.fill( query, properties, typeSearch);

    SearchExecutor searchExecutor = new SearchExecutor();
    ResultTableCollection resultTableCollection = searchExecutor.ExecuteQuery(keywordQuery);

    ResultTable resultTable = resultTableCollection.FirstOrDefault();
    dataTable = resultTable.Table;

    site.AllowUnsafeUpdates = false;
  }
  return dataTable;
}

Renewal method:

internal static KeywordQuery fill(this KeywordQuery keywordQuery, string query, List properties, KeywordInclusion typeSearch)
{
  int rowLimit = 10000;
  int queryTimeOut = 30000;
  bool duplicated= false;

  keywordQuery.QueryText = query;

  keywordQuery.KeywordInclusion = typeSearch;
  keywordQuery.TrimDuplicates = !duplicated;
  keywordQuery.RowLimit = rowLimit;
  keywordQuery.Timeout = queryTimeOut;

  foreach (string propertie in properties)
    keywordQuery.SelectProperties.Add(propertie);

  return keywordQuery;
}

SP 2013 – What is the correct syntax to add the results of two or more If statements?

I want to create a "scorecard" where the user simply selects "yes" or "no" for each field in the list. Then I would like to assign a point value to "Yes" or "No" and add the point values ​​in a calculated "Total" field call.

"No" values ​​are always zero (0). Here is one of my many iterations – all of which fail:
= (IF ((CEU Completion QTR 1) = "yes", 5.0)) +
(IF ((CEU Completion QTR 2) = "yes", 5.0))

The fields (CEU Completion QTR 1) and (CEU Completion QTR 2) are yes / no fields (check boxes). There are other fields, but when I resolve them, I know how to add the other fields. I know there is a limit of 7 nested fields. I have 14 fields that I need to assign a point value to and add up to a total to avoid more than 7 nested If statements – advice is welcome.

SharePoint 2016 – MySite upgrade from SharePoint 2013 – Wrong URL

I have upgraded from SharePoint 2010 to SharePoint 2013 to SharePoint 2016 for database attachments. I updated my site's host URL in SharePoint 2016 UPS My Site to the new site collection, but Newsfeed, Onedrive, and Sites still point to the SharePoint 2013 URL.

Example:

My SharePoint 2013 website URL: http://sharepoint2013.domain.com/mysite
URL of my SharePoint 2016 website: https://sharepoint2016.domain.com/mysite

Note: In SharePoint 2016, read permission for my website, I can add users, click OK, but in "No exact match was found. Click the items that have not been resolved for more options." Same behavior with the secondary owner under "Clean up my website".

I also display 0 person results in SharePoint 2016 in my employee directory.

Any ideas on what I missed after upgrading my sites in SharePoint 2016.

SharePoint Workflow 2013 always shown paused Looking up a value with a key is not supported

I have this problem in SP Workflow 2013 that it always goes into the stopped phase every time it is run.

After completing the web service call and reading the d / results, however, the error is displayed

Enter the image description here

RequestorId: 3d5f4981-27fc-e36f-0000-000000000000. Details: An unhandled exception occurred while the workflow instance was running. Exception Details: System.InvalidOperationException: Looking up a value using a key is performed in an instance of & # 39; Microsoft.Activities.Dynamic.DynamicPrimitive & # 39; unsupported. at Microsoft.Activities.Dynamic.DynamicItem.TryGetValue (String key, DynamicItem & value) at Microsoft.Activities.Dynamic.DynamicValueBuilder.PathSegmentFactory.ObjectPathSegment.Get (DynamicItem obj) at Microsoft.Activity.Get1.Execute(CodeActivityContext context) at System.Activities.CodeActivity1.InternalExecute (ActivityInstance instance, ActivityExecutor-Executor, BookmarkManager bookmarkManager) under System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody (ActivityExecutor-Executor, BookmarkManager bookmarkManager, Location resultLocation)

please help

Cheers, thanks!

Sharepoint 2013 – Add the "Expand / Collapse" button for two grouping levels

I am not a programmer. I have a FAQ page that is a newsletter style list view. Two grouping levels are used: 1st category 2nd question.

I want to add a shift key or 2 expand all and collapse all buttons.
I've tried using some codes from the web, but it looks like they either only work with a grouping level or don't expand or collapse a partially open list.

If anyone has a solution, please help!

User authorization API in the Sharepoint 2013 workflow

Some APIs, such as adding a user to the group and assigning a role to the user, keep returning Unauthorized.
Have already tried the following steps:

1. Complete control of the workflow in appinv.aspx (both with and without / web in the area)
2. Check "Workflows can use app permissions" in ManageFeatures
3.Request digest in the header

Please let me know if settings need to be configured at the list or site level.

Note: I can successfully run Breakroleinheritance before I call addroleassignment. All steps are in App Step.

"There was an error running the detection" when I try to patch SharePoint Server 2013

There are some things we could look for with this fix.

Solution 1:

This error usually occurs when the Windows Installer cache files (C: Windows Installer) are missing / corrupt. To further narrow the problem, you can try running ROISCAN on the computer and see how many installation cache files are missing. If these cache files were manually cleared during a cleaning process, it would be very difficult to restore the files. However, if you have a different working environment (test / staging), you can copy the installation program's cache files and rename them according to the unique version number from the associated registry keys. Fortunately, I was able to find a PowerShell script by Ahmad Adel Gad that does this task for you. You just have to:

Download the script.

Copy the script to the target computer.

Make sure that the current local identity has read / write permissions to the C: Windows Installer folder on the target computer and read permissions to the source folder. (If the source is a computer name, make sure that you have read permission in the local C: Windows Installer folder on the source computer).

Run the script locally on the target computer with the following parameters, as shown in the following examples.

. Restore-InstallerFiles.ps1 -SourceMachine "Machine1", "Machine2", "Machine3";

. Restore-InstallerFiles.ps1 -SourceFolder "D: InstallerFiles", "E: InstallerFiles", " MachineX D $ MSI files";

. Restore-InstallerFiles.ps1 -SourceFolder "D: InstallerFiles", "E: InstallerFiles", "D: InstallerFiles2" -LogFile "D: Log.txt";

Source of the above solution:

"An error occurred while running the discovery" Sp2013 upgrade SP1

Solution 2

Try downloading the patches again. There is a low chance that downloaded files have been corrupted.

Here are some detailed steps to fix this problem:

An error occurred while trying to patch SharePoint servers

Solution 3

Generally if we go that route c: windows installer Folder – This path may be damaged or files may be missing.

Copy the folder c: windows installer from another working SharePoint server to a local folder c: temp on your faulty server.

Follow the steps below:

Copy the above script to a file. I suggest using a text editor like Notepad ++ instead of a normal notepad. I tried to copy the code into Notepad and errors occurred because Notepad reads certain characters as ASCII characters. So if you try to run it as a .vbs script, the error is returned: unknown characters. Or you can download it from me: OpUtil.txt. Open it, watch it if you want, but be sure to rename it as a .vbs file instead of a .txt file. Also put this script in your c: temp folder for organization.

Open the command prompt on your faulty server. Navigate to c: windows installer and run the following command:

runas / user: DOMAIN Admin_Account "cscript.exe c: temp OpUtil.vbs / RepairCache / srestorelocation = c: temp "

Open a PowerShell window and run Get-SPProduct -local to update the farm configuration database.

Run psconfig.exe to update everything. You should now be ready to install your updates.

The above solution comes from:

An error occurred while running the discovery.