How to install GFI Faxmaker 10 in SBS 2003.

On a default SBS 2003 installation, the Microsoft Exchange MTA stacks
service and functionality are disabled. Faxmaker requires the interaction
with this service for its Exchange connector to function properly. In order
to get the full functionality of Faxmaker or any other product that requires
the user of a connector through the MTA, the following steps need to be
followed:

How to re-enable the MTA Stacks in SBS 2003.

Enabling the MTA is a two step process; it requires making changes to the
startup type of a service and also perform some registry editions.

Before starting, make sure you have a good working system state backup.

1-Removal of Registry Keys:

1.1-Open Regedit.exe

1.2-Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\servername
\Private-guid_of_private_mdb

Remove (Delete) the following two entries:

            “Gateway In Threads”

           “Gateway Out Threads”

1.3-Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\servername
\Public-guid_of_public_mdb

Remove (Delete) the following two entries:

            “Gateway In Threads”

           “Gateway Out Threads”

1.4-Close Regedit.exe.

2-Changing the startup type of the Microsoft Exchange MTA Stacks service.

2.1-Open the Services MMC (or open Run and type Services.msc and then press
OK).

2.2-Double click on top of the Microsoft Exchange MTA Stacks entry to open
its properties.

2.3-In the General tab, change the Startup type from Disabled to Automatic,
click Apply and then start the service. Close the properties.

2.4-Do not close the Services MMC yet.

3-Re-starting services

3.1-Select the Microsoft Exchange System Attendant service and perform a
re-start, this will also re-start all dependant services. (If Faxmaker was
already installed, re-start the proper services from that product). If in
doubt, re-start the system.

3.2-Close the Services MMC.

4-Install GFI Faxmaker 10 if it has not been installed yet, if it was, after
the services are re-started, faxes should start flowing through Exchange to
FaxMaker.

http://www.eventid.net/display.asp?eventid=8331&source=

If you are getting a wacko error about Path: “f:\titanium\dsa\src\lra\abv_dg\lservagent.cpp”, reboot your server.  While some posts have indicated that you “can” forestprep and other fixes, it’s recommended to try rebooting first.  There is a reported fix in the works, and thus redoing the forestprep/domainprep is not recommended at this time.

UPDATE – THERE IS NOW A HOTFIX:

http://msmvps.com/bradley/posts/4046.aspx

UPDATE – Exchange 2003 sp1 now includes this

From a posting in the newsgroups … RMS can run properly on any Windows 2003 AD server which includes SBS 2K3.

The problem that the external clients cannot reach your RMS server is probably because that the Internet clients cannot find the RMS Services. Since the client machine is not in the domain, it will not automatically query the AD to find the location of the RMS services. I’ve discussed with our RMS support and they suggested that you add two registry values in the client machine to point to the RMS services directly:

” HKLM\Software\Microsoft\Office\11.0\Common\DRM\Corplicenseserver to point to the licensing service like: http: [wack wack] >_wmcs/licensing“

” HKLM\Software\Microsoft\Office\11.0\Common\DRM\CorpCertificationserver to point to the certification service like: http: [wack wack] wmcs/certification“

However, if the problem still occurs, can I suggest that you also post out this issue on the public newsgroup: microsoft.public.rights_mgmt_svcs? In that newsgroup, you will get the most qualified pool of respondents, and so other customers and partners who regularly read the newsgroups can either share their knowledge or learn from your interaction with us.


  

 FIRST
if Microsoft Office 10 Beta is or ever has been installed on the
computer. Office 10 Beta includes a local Web store. This local Web
store registers itself in the following registry key:

HKEY_LOCAL_MACHINE/Software/Microsoft/DataAccess/RootBinder/file

This key contains the following three values:
– //\\.\backofficestorage
– //\\<server_name>\backofficestorage
– //\backofficestorage

These values contain a class ID. The class ID for the Office 10 local
Web storage system is {9da0e11f-86ce-11d1-8699-00c04fb98036}, but the
class ID for the Exchange 2000 Web storage system is
{9da0e0f3-86ce-11d1-8699-00c04fb98036}. If any of these registry values
contain the class ID for the Office 10 Web store, Setup does not work
and you receive the error message in the “Symptoms” section of this
article.

SECOND:
296436 XADM: Setup Cannot Register the Exoledb.dll File
http://support.microsoft.com/?id=296436

THIRD:
How do you feel about an uninstall/reinstall of
IIS/Exchange.  That’s also mentioned as a fix.

Try to make anew Default Web Site and what happens?
1. Start Internet Services Manager.
2. Right-click <YourServerName>, click New, and then click Web Site.
   This step starts the Web Site Creation Wizard.
3. Click Next.
4. Enter a description for this Web site, and then click Next.
5. Set the appropriate Internet Protocol (IP) and port setting, and
   then click Next.
6. Set the path for the Web site, and then click Next.
7. Set the appropriate Web site access permissions, and then click Next.
8. Click Finish.

This is mentioned in:
303063 XADM: An Error Message Occurs and Exchange 2000 Server Setup May
Not
http://support.microsoft.com/?id=303063

Are the entries in the Exchange Server Setup Progress.log consistent in
all these issues?