Data Server Installation

[Guest]

Group: I have been trying to get BCM loaded properly onto a data server with
MS Exchange 2003, where all workstations using the product will utilize one
centralized database. After scouring around, it seems like this has been a
question posed by a few people in this newsgroup.

I should have an answer within the next few days on a simplied installation,
where there is little to no need to know MSDE commands in a command window.

Right now, we are stuck on an error message that pertains to endpoint
mapping. This may have to do with a firewall, but that is inconclusive at
the moment, as well as the shared database accepting the users.

As soon as I have that info, I will post it here.

At present, we are also looking at other CRM products that integrate with
Outlook and Exchange, and are seamless and customizable. One product is
OutlookCRM, but it is very pricey. I'll keep the group informed on what we
discover.

Larry

 

[Luther]

Endpoint mapping is usually associated with the RPC service. Typically
that error means one machine is calling a port on another machine and
cannot find that port.

Note that BCM has customized their MSDE instance. For example they've
turned off the UDP port SQL Server normally uses has listening for
connections, and have instead configured a dedicated TCP port. That's
great from a security perspective, but makes it more difficult if you
want to just throw something together quickly. For example, you need to
open your firewall to that specific TCP port.

In a typical install, when you run the wizard to share the database,
BCM configures everything for you. If you want to host the database on
a dedicated server, you'll need to do everything BCM does through their
wizard.

 

[Guest]

Thanks for the info Luther. I did discover the problem. In this particular
case, the solution is to start Windows Internet Firewall on the server
through services. This resolved the issue.

Larry