We Offer Services
It’s a Story About Our Team

Great things are done by a series of small things.

October 16, 2018

Starting in Outlook 2016 version 16.0.6741.2017, Microsoft has enabled a new feature called Direct Connect to Office 365. What this feature does is connect Outlook directly to Office 365 if Autodiscover is not working. This is great feature but a network hiccup may cause your mailbox to connect to Office 365 rather than your on premise Exchange, even with a valid autodiscover record.

For Direct Connect to take effect the user must have an active mailbox on Office 365 with a valid license. Typically Direct Connect would be a neat feature unles you are in the middle of a migration to 365, but a network hiccup could incorrectly connect you to 365 even though you havent completed your migration yet.

During 365 migrations deom Hosted Exchange or On-Premise, we recommend disabling this option from the user computer registry:

You can stop Outlook from checking Office 365 for settings by setting a registry key.

DWORD: ExcludeExplicitO365Endpoint
Value = 1

Then restart your computer and it should stop trying to connect to Office 365. When you are ready to flip the switch on your migration, remove this registry key.


Credit: https://www.gothamweb.com/portal/index.php/knowledgebase/8/Outlook-bypasses-AutoDiscover-and-connects-directly-to-Office-365-mailbox.html

August 14, 2018

imageDuring an installation of Softpro Classic SQL it is possible to run into a SQL database check error that won’t let you continue.The Error is Unable to establish a connection to the SQL Server


clip_image003There are a couple of things that can cause this issue.

First let’s see if there are any ODBC connectors setup.

On 64 bit machines start %windir%\syswow64\odbcad32.exe

on 32 bit machines start, %windir%\system32\odbcad32.exe.  Using this on 64 bit machines will lead you down a dead-end path, which can cause issues.

It should look something like the picture, if you don’t have an SQL installation, this document likely won’t help.


If it does not

clip_image004Run SpSqlReg.exe from theSoftPro Share, usually \\servername\Softpro, by right clicking and selecting Run as Administrator.Click GO, it will report 7 or more Database’s registered


The setup will likely still fail at this point

Restart OdbcAd32 to see the update. Click on the System DSN tab.




Double click on a Data Source, or select one and click Configure.clip_image007


Click Next







Click Client Configuration

Change the Client Settings of The Database to Named Pipes, the installation should now work.


If it is already Named Pipes, Check the SQL server to see if Named Pipes are enabled for the database instance, or try TCP/IP explicitly on Port 1433, and dynamically.

A single update here affects all ODBC connectors to the instance specified. Typical installations have one instance for SoftPro thus this only needs done one time.

The DSN Configuration window can be closed

Click Next, Next, Finish, then either Test and OK.

If your installer is still open, click back then Next, and the SQL Server Connection Check will pass.

After the installation the settings may return to dynamically determine port, polling 1433 to start the connection, no worries as long as SoftPro apps run.


An error in these settings also cause a PFWIN-028 error when starting a SoftPro ProForm client program. Sometimes followed by a SPFUNCS-63174 Error, unable to open licensing file as it has no idea where the shared folder is and looks locally for it.

I have had to uninstall the client when the ODBC connector tests good, but ProForm fails to find it’s database. Classic has a nicely updated and running installer, it uninstalls everything important, so re-installs are more likely to solve problems than in earlier Enterprise 6 or Standard 12 installations.


Article Taken from: http://danvanfleet.com/index.php/proform-classic-client-install-database-error/