Installation on server

[Guest]

Since BCM is shareable, and claims to work with SBS 2003 Exchange, I was
wanting to place the database for BCM on the server. Has anyone done this,
and how did you go about doing it?

TIA

 

[Bob Cooley [MSFT]]

Hi Larry,

Installing Outlook/BCM on a Exchange server machine is not recommended or
supported because of potential MAPI conflicts from Outlook and Exchange
Server. Just put Outlook/BCM on another box - the size limit of the BCM
database is 2GB, so there is no need to put the db on a huge HD. Then, just
share the db out to everyone...

--
Regards,

Bob Cooley, [MSFT]


This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

Hi Larry,

In order to setup a common database on your server, install Outlook 2003 and
BCM upgrade on that machine. Setup a profile and create a BCM database. Share
this Database using the menu :
"Business Tools --> Share Database"

From your client machines, access the shared database by giving the machine
name and selecting the database, while setting up the BCM database in your
outlook profile.

For more information on this, visit:
http://office.microsoft.com/en-us/assistance/HP011537571033.aspx

Please note that this feature is available only with BCM upgrade. and not
with BCM v1. You can download the upgrade from:
http://www.microsoft.com/office/outlook/contactmanager/prodinfo/update.mspx

Thanks.

 

[Guest]

Since BCM is shareable, and claims to work with SBS 2003 Exchange, I was
wanting to place the database for BCM on the server. Has anyone done this,
and how did you go about doing it?

TIA

 

[Guest]

I tried this, but keep getting an error when I try to share it out... When I
first choose to share the database and click next, it comes up saying "No
endpoints available from endpoint mapper". Then it lets me click next and add
users, but when I click on finish, it says "Error occured applying changes,
your changes have not been applied successfully".

Any idears appreciated!

Brendan

 

[Guest]

I receive exactly this 2 errors - have you any information ?

Jaro

 

[Luther]

There aren't sufficient details to diagnose your problems, but an
endpoint
in this context is a tcp port.

A few things to consider.

In a typical BCM 2 installation, BCM creates its own SQL instance,
without the default
UDP port mapping utility turned on. Normally when SQL starts up it
picks a TCP port.
Typical SQL apps query the port mapping utility via UDP, and it returns
the TCP port
being used by the SQL instance. BCM uses a fixed TCP port, 56183, and
all its
clients (Outlook/BCM) use that port. If you install a BCM database on
another SQL
instance, you need to make that instance use TCP port 56183 if the BCM
clients are
to connect successfully.

In addition, any firewall on the machine with the instance must allow
traffic on port
56183 through, or clients will fail to connect.

The BCM v3 beta is using SQL Xpress, instead of MSDE. Xpress is
essentially the new version
of MSDE. This new Xpress instance is using tcp port 5356.

 

[Larry]

Is this a Windows 2003 Server?

If so, go to Start > Run > Services.msc
Then Disable the Routing and Remote Access service
And Enable the Windows Firewall/Internet Connection Sharing (ICS) Service

Hope this helps!


--
Regards,

Larry, [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

This is a SBS 2003 Premium server SP1 (with ISA 2004)
I try this - thank you very much

Jaro

Is this a Windows 2003 Server?

If so, go to Start > Run > Services.msc
Then Disable the Routing and Remote Access service
And Enable the Windows Firewall/Internet Connection Sharing (ICS) Service

Hope this helps!


--
Regards,

Larry, [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.

I receive exactly this 2 errors - have you any information ?

Jaro