Today
I was monitoring the SP servers along with some regular sanity checks that need
to be carried out on daily basis. While doing that, I noticed one error based
on this InfoPath rendering in the Health check analyzer! But let me tell guys InfoPath is perfectly
working in our environment without any issues and nobody has reported any incident
also then why this error is showing in the health analyzer? – you must be
thinking the same but no need to worry about as this is not a big one which
will take lot of your time, some minor checks and you are done.
Error message:
InfoPath Forms Services forms cannot be filled out in a Web browser
because no State Service connection is configured.
If
this is your new configuration then you need to follow this existing official documentation
from Microsoft which is pretty awesome!
In
our case, we have already done this configuration long time back and as I said,
it’s working fine. The error message is little bit misleading one as its asking
you to check the “state service” service application to be online or not but that’s
not the case. We have already configured this service application long time
back so where exactly the issue is and why it’s throwing the error?
Let
me tell you the trick which we sometimes ignored – Look out the error in the
HAL rule – see the below:
You
will notice that it’s also giving you the URL of the web application for whom
its failing and name of the servers also.
In
our case, we have recently created a new web application in the farm and its
been reflected in that! What it means? Pretty simple – the ‘state service’
service application is not configured for the same.
So
what we need to do now for this re-association? Here are the details:
Resolution:
1. Open the central
Administration
2. Application
management
3. Service
applications
4. Configure service
application associations
5. Select the web
application for whim it’s failing
6. Click on custom
7. It will open the
service application options
8. Select the state
service check box and click OK
Once
you are done with the above steps then come back to health analyzer list, click
on the same rule and hit “Reanalyze now” – that’s it, you are done.
That
error won’t be there! Happy SharePoint once again…
If
you have any queries/questions regarding the above mentioned information then
please let me know. I would be more than happy to help you as well as resolves
your issues, Thank you.
Note:
If you find a different solution, please report it as a comment to
this post. Be sure to double-verify it: undo your solution and verify that the
problem comes back, then redo it and verify that the problem goes away.
Product Applies To:
o
SharePoint
2010
o
SharePoint
2013
o
SharePoint
Foundation 2013
o
SharePoint
Foundation 2010
