While working on the InfoPath Forms Service DSC Resource for SharePoint DSC, I ran into an issue where I couldn’t get access to the InfoPath Forms Service configuration page in Central Administration (General Application Settings > Configure InfoPath Forms Services). Every time I would click that link, I would get presented with a SharePoint error page with the message InfoPath Forms Services is not turned on. (see screenshot below). This was happening for both SharePoint 2013 and 2016.
The issue was caused by me having set a name on the InfoPath Forms Service instance while playing around with PowerShell. In order to obtain a reference to the InfoPath Forms Service in SharePoint, you need to run the following PowerShell cmdlet:
The picture above shows what you should get by default with a clean SharePoint installation after you run the cmdlet. In my case, I had written the DSc resource so that it can also modify the name of the instance. Note how in the picture above, we can see that the name property is empty by default. After playing with the service instance, running the same cmdlet would give me the following result:
We can see from the picture above, that I had renamed my InfoPath Forms Service to have the name “My InfoPath Forms Service“, which is what was causing my issue. Luckily for me, I still had a variable reference to my service instance in the current PowerShell session (in my case, a variable named $is). Running the following PowerShell lines emptied back the Name property of the service instance, and the InfoPath Forms Service automatically went back online.
$is = Get-SPInfoPathFormsService $is.Name = "" $is.Update()
After running the above lines of code, I was able to go back in Central Administration and access my InfoPath Forms Service configuration page as normal.