Azure & Office 365

Configure Workflow Manager 2013 with SharePoint Standard or Enterprise

(Workflow 2013 does not work with SharePoint foundation)

I assume you have SharePoint installed and configured on your computer. Also Workflow Manager 1.0 and Wofklow client is installed on the same computer.

When the workflow manager is not configured on your SharePoint farm, you will notice below:

1. You don’t see SharePoint 2013 workflow option in SharePoint designer.

1. When you go to > Central Admin > Service Application > Workflow management service application > you see  Workflow is not connected

Lets Configure Workflow 2013

1. Select Start > Select Workflow Manager 1.0 > click on Workflow manager configuration

1. Now select Configure Workflow Manager with custom Settings

1. SQL server Instance name and make sure below database does not exist on that instance. If they do. Rename the database

1. Provide the Windows account used to manage this service and used in Workflow manager service application pool

1. Make sure port 12290 and 12291 is open on SP and Workflow server for communication. “Allow workflow management over http on this computer” should be checked. By default local administrator will be able to manager workflow services.

6. Now we need to configure Service Bus. We can use same SQL server and confirm that database names does not exist

7. Important thing to notice is. I have selected “Use the same service account credentials as provided for workflow manager” and “Use same certificate generation key as provided for workflow manager”

1. Surely we need Port number 9355, 9354, 9356 opened between SharePoint server but also we need port 9000 to 9004 opened. It does not use single port as mentioned below

1. We can validate the details in summary screen before proceeding with actual configuration. Note that port number is 9000-9004 here

1. Once you hit the tick on bottom of page, it will start the configuration of Workflow and Service Bus. It should be completed in couple of minutes

1. Now we should be able to see with 2 bindings

1. Try to browse them and you should see below reply

1. If you see a 404 or 500 error. Check if your service account has proper permission on local system (Local admin, permission on c:, etc). Try to browse site in different browser. Create DisableLoopbackCheck registry. Add URL in Trusted sites in IE

1. Now open Workflow Manager Powershell as admin and run command “get-wffarm” to check the details of farm

15. Open SharePoint Powershell as admin and run command “Register-SPwrofklowservice –Spsite http://siteURLwithport –workflowhostURI http://workflowserver:12291 -allowoathhttp”:

1. Now you see that Workflow service is connected and your SharePoint 2013 workflow in SharePoint Designer

1. Check if below jobs are running. When did they last run

Microsoft SharePoint Foundation Usage data Import

Microsoft SharePoint Foundation Usage data Processing

 

2. Lack of receivers for my analytics and page usage definitions

 

{

Add-PSSnapin Microsoft.SharePoint.PowerShell

}

$aud = Get-SPUsageDefinition | where {$_.Name -like “Analytics*”}

# if analytics usage definition receivers is empty then manually add back receiver

if($aud.Receivers.Count -eq 0)

{

$aud.Receivers.Add(“Microsoft.Office.Server.Search.Applications, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”, “Microsoft.Office.Server.Search.Analytics.Internal.AnalyticsCustomRequestUsageReceiver”)

}

# if analytics usage definition receiver is not enabled then enable it

if($aud.EnableReceivers -eq $false)

{

$aud.EnableReceivers = $true

$aud.Update()

}

$aud | fl

$prud = Get-SPUsageDefinition | where {$_.Name -like “Page Requests”}

# if page requests usage definition receivers is empty then manually add back receiver

if($prud.Receivers.Count -eq 0)

{

$prud.Receivers.Add(“Microsoft.Office.Server.Search.Applications, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”, “Microsoft.Office.Server.Search.Analytics.Internal.ViewRequestUsageReceiver”)

}

# if page requests usage definition receiver is not enabled then enable it

if($prud.EnableReceivers -eq $false)

{

$prud.EnableReceivers = $true

$prud.Update()

}

$prud | fl

 

 

Thanks to Brian :

 

http://geekswithblogs.net/bjackett/archive/2013/08/26/powershell-script-to-workaround-no-data-in-sharepoint-2013-usage.aspx

A. Check if you are able to browse SharePoint site on all search servers

B. Open Site > Go to Site Actions > Site settings > Search Visibility > select “Always index all aspx pages”

C. Create Disableloopback registry on search server

1. Click Start > Run, type regedit, > OK
2. In Registry Editor, locate:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa > New > DWORD 
4. Type DisableLoopbackCheck, and ENTER.
5. Right-click DisableLoopbackCheck, and Modify.
6. In the Value data box, type 1, and OK.

 

D. Do we have proper IIS binding on all SP Servers

1. Click Start > Run, type inetmgr, > OK
2. Expand Server > Sites > Select you website
3. On extreme right click on Edit Binding
4. Make sure your entry here are proper as per URL given in content source in search service application

 

E. Do we have any entry on host file on any SharePoint servers? if yes why

F. Make sure Search Service Application connection proper

1. Open Central Admin > Application Management > Manage Web Application

2. Select you website > Select Service Connections from top ribbon

3. Check if your Search service application is selected

 

G. Create New Search Service Application and try

H. Check “Crawl Logs” in Search Service application. Make sure your URL is crawled.

 

We have stretched across two sites, primary and DR. Wan link is 150Mbps and we have encountered some network issue. We are planning to rate limit/ policy on traffic destined to DR site to 100Mbps. Not aware as will the packets be dropped after reaching the limit of 100Mbps.

 

Ans: Exchange would do is just throttle back and queue up the replication traffic.   So, at worst, your D/R site would just get behind on replication.

Need to build a DAG with 2 mailbox servers. Need a guidance in doing this. What test need to be performed to be sure that everything works well

 

Ans: As you Enterprise edition you can configure your mailbox servers into a DAG. For further details you can follow below article:

http://exchangeserverpro.com/exchange-server-2010-database-availability-group-installation-step-by-step/

Need to export edb and log files from Exchange BKF file. Due to some network issue, backup process got interrupted which caused bkf file to be non-accessible. Please advise any efficient utility to export data from damaged exchange bkf file?

 

Ans: You can try any of the following Exchange BKF Repair tools:

http://www.stellarinfo.com/email-repair/exchange-bkf-repair.php

http://www.taskmanagerfix.com/exchange-bkf-to-pst.html

http://www.bkfrepairtool.org/exchange-bkf-recovery.html

http://www.exchangebkfrepair.com/

We have exchange 2007 in 2008 windows root domain. I removed a child domain from the forest and now cannot view the mailboxes of the users belonging to that child domain.

Is there a way to export mailboxes of that child domain using edb or ost file.

 

Ans: You can use the following two tools to export mailboxes using ebd file

http://www.edbtopstutility.com/

http://www.edbtopst-converter.com/export-exchange-mailbox-pst.html

Or

use the following tool to convert OST file to PST

http://www.ost2.com/

Moved one user AD account to another OU and since then he isn’t able to use activesync on his phone. When checked his ‘manage mobile device’ in EMC it gives error

http://209.85.62.24/365/183/0/p408925/r.jpg and in EMS as oops.. will replace it later.

Ans: The error message just indicates a process that didn’t finish correctly. Click “Refresh” from the EMC and then click on Manage mobile device

OR

Try to reconnect the user mailbox with the AD account:

1. Open EMC, expand to recipient configuration, right click the user and choose disable.

2. In Disconnected mailbox, right click the disconnected mailbox and choose connect. If the disconnected mailbox does not appear, right click “Disconnected mailbox” and choose “Connect to server”. Select the mailbox server which hosting this user’s mailbox.

3. When reaching the Connect mailbox page, click “Existing user”, then select this user’s account

We have coexistence of Exchange 2010 SP3 and Exchange 2013 CU3. Outlook Anywhere and Autodiscover point to Exchange 2013 CAS server.

Outlook Anywhere with Exchange 2010 mailboxes are able to connect via Outlook 2010.

The only issue is when Outlook Anywhere is being used from Internet or from Internal network and user goes in Outlook 2010 -> File -> Automatic replies get the following error: –

“Your automatic reply settings cannot be saved. The server might be unavailable, or your automatic reply message might have exceeded the size limit on the server”

This issue occurs only if the connection passes viz Exchange 2013 CAS. Also It works fine if user mailbox is on Exchange 2013 Sp1

 

Ans: The following resolves the issue.

On E2k13 CAS server à IIS manager

highlight EWS virtual directory and select Configuration Editor

In the drop down, select System.WebServer/ServerRuntime/

Then in the middle pane select UploadReadAheadSize and set it to 49152

Do an IISReset

We have coexistence of Exchange 2010 SP3 and Exchange 2013 CU3. Outlook Anywhere and Autodiscover point to Exchange 2013 CAS server and everything works fine irrespective of the mailbox being located on Exchange 2010 or Exchange 2013. But when tried to access auto mapped Exchange 2013 mailbox from primary Exchange 2010 mailbox it errors stating ” Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance”.

Exchange 2013 OutlookAnywhere “Externalclientauthenticationmethod” is Basic and “Internalclientauthencitcationmethod” is NTLM. Everything is setup as per the Tech-net recommendations.

Checked both these articles but still it is not working:

http://support.microsoft.com/kb/2839517

http://support.microsoft.com/kb/2834139

Ans: It is an issue with Exchange 2010 Sp3 Rollup 4. Once you upgrade it to Rollup 5 it resolves the issue.

You can download RU5 from the following:

http://www.microsoft.com/en-in/download/details.aspx?id=42001