Sorry, didn't see you were still having problems with this. I have
importing all our Siebel data into bcm for the last couple weeks.
Did you set the permissions and sharing on the Database? I remember that
the greyed out database issue was from different versions of the bcm
client. If you are using the final release, the new database must be
created in the final version. The beta client will not connect to a
final database, or the other way around.
These are the only permissions I set on the database to get it working.
sqlcmd -S {server\instance} -d {databasename} -E -Q "Update OrgTable Set
SharedServer = N'{ServerName}'"
sqlcmd -S {server\instance} -d {databasename} -E -Q "Update OrgTable Set
OrgName = N'{databasename}'"
sqlcmd -S {server\instance} -d {databasename} -E -Q "Update OrgTable Set
LocaleID=N'en-US'"
sqlcmd -S {server\instance} -d {databasename} -E -Q "exec
PublicTurnOnSharing 1"
You should be able to connect from the machine you created the database
on. By the way, i have not seen a difference between using a 32 or 64 bit
client. Both connect to the server. Just the fact you can see the
database means you have it on the server and have user permissions. The
final release database version number is 4.0.9812.0
Russell Reid wrote:
> OK, i followed this procedure and got the database copied over to our SQL
> server. Added the users. But when i try to connect using BCM the database
> is still greyed out. Am i missing a permission? What database permissions
> are required for shared users in the database?
> > Russell Reid
> "ChrisF" wrote:
>
> > Russell,
> > The only way I could get this working was to create a local database in
BCM.
> > Detach the database and copy to your server. Attach the copied database
in
> > sql.
> > After it is attached run the following in a command window:
> > sqlcmd -S {server\instance} -d {databasename} -E -Q "Update OrgTable Set
> > SharedServer = N'{ServerName}'"
> > sqlcmd -S {server\instance} -d {databasename} -E -Q "Update OrgTable Set
> > OrgName = N'{databasename}'"
> > sqlcmd -S {server\instance} -d {databasename} -E -Q "Update OrgTable Set
> > LocaleID=N'en-US'"
> > sqlcmd -S {server\instance} -d {databasename} -E -Q "exec
> > PublicTurnOnSharing 1"
> > After this you will want to add your users:
> > sqlcmd -S {server\instance} -E -Q "exec sp_grantlogin [domain\user]"
> > sqlcmd -S {server\instance} -d {databasename} -E -Q "exec ir_AddSharedUser
> > [domain\user]"
> > That's it. The beta tools will not work due to the db version being
> > different. I couldn't get it to upgrade using the scripts either (too
many
> > conflicts).
> > Thanks.
> > -Chris
> > "Raul Thomas" wrote:
> >
> > > Hi Russell
> > > > I haven't tested it so cant tell you for sure. The RTM build of the tool
> > > should be posted once the product is available of the shelf for
consumers .
> > > > I'm hopefully that this would be taken care by the end of this month.
> > > > Also if you can check the permission if you have SQL management studio
for
> > > SQL 2008 installed.
> > > > Also is the database hosted on the server a 32 or a 64 bit of SQL 2008 ?
> > > Because it 64 then the clients connecting to it need to be 64 bit .
> > > > > > Regards
> > > > Rahul Thomas
> > > > MSFT
> > > > "Russell Reid" <RussellReid> wrote in message
> > > news:2801F6FA-98FE-4472-9F82-218D1A2113F7@microsoft.com...
> > > > I found this KB article when i was searching. I followed through on
the
> > > > steps and am able to successfully connect to the remote database using
> > > > sqlcmd. But when i try to connect with BCM the database is greyed
out. I
> > > > set up the remote database using the Database Admin Tool (beta).
Could
> > > > that
> > > > be the problem? When will the Full release of the Database Admin Tool
be
> > > > available?
> > > > What else can i check to determine if i have the correct permissions
on
> > > > the
> > > > database?
> > > > > > > > Russell Reid
> > > > > > > > "Raul Thomas" wrote:
> > > > > >> Hi Russell
> > > >
> > > >> Do you encounter any error when connecting to the database from the
> > > >> client
> > > >> computer ?
> > > >
> > > >> Also can you try connecting to the server machine using sqlcmd (as per
> > > >> KB953745)
> > > >> > > > >> Regards
> > > >
> > > >> Rahul Thomas
> > > >
> > > >> MSFT
> > > >
> > > >> "Russell Reid" <RussellReid> wrote in
message
> > > >> news:8B213CF0-9BB3-4C49-86D1-4324E8D2A5B1@microsoft.com...
> > > >> > We are an SA license holder and have downloaded the RTM 2010
versions
> > > >> > of
> > > >> > office and BCM. We are trying to set up a test database for BCM on
an
> > > >> > existing SQL 2008 server using the BCM 2010 database admin tool beta
> > > >> > (since
> > > >> > the i cannot find the RTM of this tool). The database gets created
> > > >> > without
> > > >> > error. I am able to add users to the shared database without
error.
> > > >> > But
> > > >> > when i try to connect to the remote database with a client BCM, the
> > > >> > database
> > > >> > is greyed out and it will not let me connect. Is this because the
> > > >> > database
> > > >> > was created with the beta admin tool while the BCM install is RTM?
Or
> > > >> > am
> > > >> > i
> > > >> > missing permissions on the database that will allow the client to
> > > >> > connect?
> > > >> > > > > >> > Russell Reid
> > > >>
>
Posted from
http://outlook-center.com
Outlook forums, articles, tips.
