Issues Sharing BCM Database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have the same issues 4 others have written about, yet there seem to be no
difinitive answers.

When I click on share database and select I want to share my database from
the dialog box, I receive the error "There are no more endpoints available
from the endpoint mapper." If I click ok to continue, I can add users. When
I add users and click finish, it says, "error occurs, changes have not been
applied successfully" In the services Windows the service is for SQL
service is configured to user local system account I am using my windows
account and I belong to both the local admin group and domain admin group.

Additionally, I have tested access from workstations, back to the server. I
can reach the server on my account only. TRIED to allow domain users access
using "SQL Server Management Studio Express CTP" without success. Just get
access denied messages from "SQL Service Manager"

Also noteworthly, the 4 user accounts CAN access the SBA files without issue!

My platform is 2K3, Version 5.2.3790 w/ SP1.
Acting as a PDC
Running RasMan to allow VPNs
NO firewall on Sever

So there are 2 courses to try to correct ....

1) Is there any documentation so I can proper configure my handful of
users?

2) Any work arounds or patches for the BCM share routine?

Anyone actually resolve this able to provide info?

TIA
 
ewr said:
I have the same issues 4 others have written about, yet there seem to be no
difinitive answers.

When I click on share database and select I want to share my database from
the dialog box, I receive the error "There are no more endpoints available
from the endpoint mapper." If I click ok to continue, I can add users.
When
I add users and click finish, it says, "error occurs, changes have not
been
applied successfully" In the services Windows the service is for SQL
service is configured to user local system account I am using my windows
account and I belong to both the local admin group and domain admin group.


Additionally, I have tested access from workstations, back to the server.
I
can reach the server on my account only. TRIED to allow domain users
access
using "SQL Server Management Studio Express CTP" without success. Just get
access denied messages from "SQL Service Manager"

Also noteworthly, the 4 user accounts CAN access the SBA files without
issue!

My platform is 2K3, Version 5.2.3790 w/ SP1.
Acting as a PDC
Running RasMan to allow VPNs
NO firewall on Sever

So there are 2 courses to try to correct ....

1) Is there any documentation so I can proper configure my handful of
users?

2) Any work arounds or patches for the BCM share routine?

Anyone actually resolve this able to provide info?
Click to expand...

Interesting.

Did you run the SVRNETCN tool to enable tcp/ip and netpipes? Did you install
this SQL server on the correct port 56183?

I don't think that adding SQL domain user accounts is supported or even
necessary.
 
Yes.. I had already run SVRNETCN as TCP is NOT installed by default.

I am now testing SQL domain user accounts ared with the documentation Raul
supplied. Follow that link for results.
 
Raul,

Thanks for the info it was helpful. BTW, did NOT know of the 5 user limit
for sharing (per the docs).

Not sure what the real issue is because the troubleshooting process did not
prove fruitful.

However, at this point I was able to give 1 user read/write access by
setting the OrgTable variable to TRUE and adding the domain account to the
security folder using Microsoft SQL Server Management Studio Express.

I still have to research more. Will advise group of results.
 
How come you are using SQL Xpress instead of MSDE?

It _should_ work, but is not a supported scenario with BCM v2.

Note that BCM v2 w/MSDE and BCM v3 Beta w/Xpress use different TCP
ports to communicate with server (so that they can run side-by-side).

The OrgTable is definately critical in allowing BCM to share or not.
The users must also be in the database's shared users group, or DBOs
(everyone in NT admin group is a DBO of every sql database, except work
with Vista betas--security is good for you, and all that).
 
Back
Top