Unable to connect to registry on the server (machineName), or you are not a member of the OLAP Administrators group on this server

Michael J. Hamilton, Sr. — Fri, 02 Sep 2005 12:10:00 GMT

Unable to connect to registry on the server (machineName), or you are not a member of the OLAP Administrators group on this server

The devil is always in the details J

The following I wanted to share because this individual sorted through this error and his resolution may help someone else. I am posting a summary of our correspondence.

PROBLEM:

BizTalk Deployment Failing – Error: Unable to connect to registry on the server (machineName), or you are not a member of the OLAP Administrators group on this server

============================================================

From: Shalabh

To: Mike

Date: 8.31.05 2006 hours EST

Subject: Biztalk deployment failing.

Message…

Hello Mike,

I have a 3box setup -

1. BizTalk 2004 (installed DSO and Client Tool for AS) 2. SQL Server 2000 (SP3a and SQL2000-KB810185-8.00.0878-ENU.exe)

3. Analysis Server 2000 (SP3a - sql2kasp3.exe)

My BizTalk 2004 configuration is continually failing with message - "Unable to connect to registry on the server (machineName), or you are not a member of the OLAP Administrators group on this server"

Can you think of anything? Nobody answered to my newsgroup query.

Appreciate your time.

============================================================

From: Mike

To: Shalabh

Date: 8.31.05 2035 hours EST

Subject: Biztalk deployment failing.

Message…

Initially, based on what you have conveyed, the BTS Administrator's Group needs access to the OLAP server's OLAP Admins group.

Usually, the same service account is used for BTS and OLAP - so you do not run into this problem.

Check the service account / user account that is running both the BTS Admins group and the OLAP group.

============================================================

From: Shalabh

To: Mike

Date: 8.31.05 2146 hours EST

Subject: Biztalk deployment failing.

Message…

Okay.

I changed the Analysis Service to run under the credentials of domain\BtsService.

I added the 'domain\BtsAdmin' account and 'domain\Biztalk Server Administrators' as members of OLAP Administrators group on each box.

I still get the same result.

I also changed the Analysis service to run under domain\BtsAdmin but still the same error.

Any more ideas??

============================================================

From: Mike

To: Shalabh

Date: 8.31.05 2204 hours EST

Subject: Biztalk deployment failing.

Message…

There can obviously be a number of issues.

Have you tried walking through the stand-alone deployment that on my bog? It's pretty straight-forward, and works perfectly?

============================================================

From: Shalabh

To: Mike

Date: 9.01.05 1300 hours EST

Subject: Biztalk deployment failing.

Message…

Answer to your questions:

<machinename> is the box where OLAP or Analysis Service is installed. I get my actual machine name in the error message.

I tried running OLAP under local service and still the same result. There are no services running on the BTS box that I can see.

I did check the event viewer and there were no error messages or warnings on both boxes.

I did see this problem listed on msdn and applied the patch they suggested at the bottom of the following page:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/troubleshoo

ting/htm/ebiz_depl_install_fdjh.asp

Problem: You may encounter the error "Unable to connect to registry on the server (machineName), or you are not a member of the OLAP Administrators group on this server" or the BAM cube DTS fails on execution.

Resolution: Install the following software: (download from

http://go.microsoft.com/fwlink/?LinkId=22840)

============================================================

From: Mike

To: Shalabh

Date: 9.01.05 1410 hours EST

Subject: Biztalk deployment failing.

Message…

Open Component Services... Expand Component Services-->Computers, and right-click on My Computer.

Select the MSDTC tab, then in the lower-left, Security Configuration.

Ensure that

NetWork DTC Access - checked

Network Administration - checked

Network Transactions - checked

Network Clients - checked

Transaction Internet Protocol - unchecked XA Transactions - Checked

And it should be running as the NETWORK SERVICE account.

============================================================

From: Shalabh

To: Mike

Date: 9.01.05 1421 hours EST

Subject: Biztalk deployment failing.

Message…

On BTS Server, the Network Clients was not checked and I checked it.

On OLAP box, MSDTC was not enabled. I enabled it and ensured the option below were checked and rebooted the box.

Still the same result.

============================================================

From: Shalabh

To: Mike

Date: 9.01.05 1506 hours EST

Subject: Biztalk deployment failing.

Message…

Found out...need to install sp3a on the BTS box as well.

Thank you so very much.

============================================================

SOLUTION

As you can see, the problem was solved by installing the installing Service Pack 3a on the BTS box. On this box was the SQL Server/OLAP client and DSO (Decision Support Object) tools, but without the SP3a patch, the error was persistent.

I want to thank Shalabh for permission to post this information – and I am glad another problem has been solved.