So you build a Small Business Accounting Program and you call it a multi user version…and then you don’t install it on SBS in such a way so that the msde datafile is ‘on’ the server, but rather on a desktop inside the office.

Okay ….lemme get this straight… why does EVERYONE see the word ‘multi-user’ and translate that to “Peer to Peer” except for me?  I WANT that datafile ON the Server.  I mean that’s WHY I have a network you know so that data can be better protected over there.  I don’t see peer to peer networks as being of value to me.  I WANT a server.  I WANT the active directory goo.  I WANT the control.  So what’s a gal to do? 

She gets advice from her fellow geeks who hack up the way to get it on the server. 

So here is the unofficial, unsupported instructions to get SBA on SBS 2003.

“What I have done is install Small Business Accounting on SBS2003.  This results in an MSDE instance called MICROSOFTSMLBIZ being installed there.  The instance can host the BCM database as well.  You would install BCM on your workstation, set it up for sharing and add users.  Then shut down Outlook and SQL on your workstation, copy the BCM database and log file to the server and use SQL Enterprise Manager to attach them there.  Restart SQL and Outlook on the workstation.  You should now be able to redirect Outlook to the copy of the database on the server.

Unfortunately this method is not supported by Microsoft as I mentioned in the meeting.  In fact, if you have SBS Premium you can upgrade the MSDE instance to full SQL to remove any database size or number of user limitations.”

Remind me to email Dennis Clark and give him feedback to take back that they DO start supporting SBA on SBS.  I mean… it just makes sense, you know?


4 Responses to SBA on SBS [the unsupported instructions to get the datafile ON the network]

  1. Greg says:

    I installed SBA 2006 on my SBS2003 Premium SP1 server. When attempting to enable Multi User mode SBA crashes. I posted this to the Microsoft SBA newsgroup and received the following response:


    At this time it is not on the list of supported configurations but we are

    continuing to evaluate the need to add SBS 2003 to the list of supported


    There is a known issue when attempting to enable multi-user when the

    Windows Firewall is disabled on SBS server (or on XP/2000 boxes if ICS is

    not started). As stated earlier, there is not a published KB or white

    paper on th supporting SBS 2003 (Premium or Standard).

    This service will need to be started in order to enable the multi-user

    access for your database, once it has been enabled the service, verify you

    are able to connect from machines on your network that have been given

    access to SBA.

    Keep in mind that you will need to use the MSDE instance that is installed

    with the application (MICROSOFTSMLBIZ) and by enabling multi-user, you are

    enabling the TCP/IP and named pipes protocols for this instance.

    Once multi-user has been enabled it is opening connection to the SQL

    database via port 56183 so via ISA you would need to have this port open.

    There are end-users that have been able to implement SBA on SBS Server and

    enable Multi-user but did have to enable the Windows Firewall in the

    Services list but to warn you, there is a known issue on SBS with Service

    Pack 1 if you enable the Windows Firewall it may cause problems with your

    remote access.

    Some end-users have had to do the following to get around the problem with

    Remote Access:

    Uninstall SP 1 for Windows 2003.

    Disable RRAS.

    Install SP 1 for Windows 2003 again.

    Configure RRAS.


    While I know it’s not a supported configuration, I’m not trying to use SQL Server.

    What are your thoughts about this response?



  2. Greg says:

    As a followup, there is a white paper Microsoft published that discusses using SBA in a multi user environment.

    I posted this article back to the newsgroup and am waiting for the engineer’s response.

    I’ll keep you posted.



  3. Greg says:

    Here is the configuration that worked for me – steps supplied by Microsoft:

    On SBS

    1. Go to Start | Run, type in svrnetcn and choose OK

    2. Choose MICROSOFTSMLBIZ from drop under instance "SQL Server Network Utility" dialog

    3. On the Left side of the dialog in the "Disabled Protocols" window select "TCP/IP" and click on "Enable" button.

    4. On the right side of the window select the "TCP/IP" and click on "Properties" button.

    5. In the "Default Port" field of the new dialog type 56183

    6. Click OK to confirm

    7. Click OK on the next dialog to confirm

    8. Click OK on the Message "Any changes made will be saved; however, they will not take effect until SQL server service is stopped and restarted".

    9. Click OK on the next dialog

    10. Go to Start | Run, type in services.msc and choose OK

    11. In the Service Window, locate the MSSQL$MICROSOFTSMLBIZ instance and highlight

    12. Choose to Stop the Service

    13. Start the service

    Then Perform the following steps:

    1. Go to File | Manage Users, create your users

    2. Once that completes go to File | Data Utilities

    3. Choose Rebuild File, create a new .sbc file (give file unique name that you will recognize)

    4. Send that .sbc file you create to client computer (where user you created on step 1 has access) where SBA is installed

    5. Attempt to launch using the .sbc file

  4. Bill Watters says:

    I like CRM, but it’s too much for most of our client base…I’ve been looking for a way to get the BCM db onto the SBS w/out installing outlook on it (this being a bad thing from what I understand ;-P) it’s so simple, but I just had not put it together.
    Bill Watters