Why is BizTalk Admin Console erroring about “Unable to access Rule Store Provider. Verify is Business Rule Engine Feature is installed and configured”

Aaron Palma Gil 1 Reputation point
2021-04-29T06:10:55.463+00:00

Recently I have been tasked to downgrade our BizTalk Non Production environment as it was running on BizTalk 2016 enterprise. After all the backups I then uninstalled BizTalk 2016 enterprise and installed Biztalk 2016 developer edition I then configured the BizTalk server to join the existing BizTalk databases for the Group and features such as SSO and Business Rules engine and finally I restored the master secret. I made sure that these features were part of the installation.

After that I opened the console everything seems to be in order except for when I import/export a policy

92466-image.png

adding a policy

92467-image.png

I restarted all the services I could think of, rule engine service, WMI, DTC, the server itself to no avail. I even checked the Business Rules Composer and I could see all our policies/vocabularies. I checked the Registry and I could see BizTalk and BusinessRules entries and couldnt find anything different from a working environment(the one I have not touched yet)

So here I am wondering if anyone have encountered this issue and how did you solve it?

Microsoft BizTalk Server
Microsoft BizTalk Server
A family of Microsoft server products that support large-scale implementation management of enterprise application integration processes.
349 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Aaron Palma Gil 1 Reputation point
    2021-05-03T00:52:36.077+00:00

    The answer lies in this blog post that Colin Dijkgraaf have commented - business-rule-composer-error-in-the-configuration-of-bre

    Root cause The table dbo.adm_Group in the BiztalkMgmtDb - somehow the values for RuleEngineDBServerName and RuleEngineDBName disappeared when I uninstalled the BizTalk Runtime for the downgrade, even worse the DateModified column didnt get changed.

    Fix - I inserted the values for the columns mentioned and its now fixed

    0 comments No comments