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 18, 2018

Windows Checking For Updates Stuck

Operating System Affected: Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008, Windows 8.1, Windows Server 2012
Symptoms: Windows Update stuck “Checking For Updates” for long periods of time, related process (i.e. svchost.exe) runs constantly at 10-99% CPU even during idle
Cause: Windows/Microsoft Update Failure

I’ve expanded this post to include possible solutions for all windows editions affected. The symptom to look out for is if:
1) Windows Update is enabled and svchost.exe or an equivalent process is running continuously with high RAM and CPU utilization
2) Windows Update is manually started with “Checking for Updates” and it never stops. The checking for updates stage of the process should not take longer than a couple minutes and without fixing this I’ve let it run for days with no result.

The solutions are:
1) Completely disable the Windows Update service and live with no updates, not just setting it to “Never check for updates (not recommended)” as this doesn’t fully stop it
2) Upgrade to Windows 10 (not always an option)
3) Fix the problem outlined below for your respective operating system version

Install the following patches in right order (increasing KB package value) and according to the proper operating system, bit-architecture, and IE version (when applicable) [all important!].

Windows XP and Windows 2003

Windows Vista

Windows 7 SP1 and Windows Server 2008 R2

Windows 8.1 and Windows Server 2012 R2

With Office installed
Having Office 2007, Office 2010, or Office Compatibility Pack SP3 installed will also cause the same problem even if you installed any of the above patches. You’ll have to install the below patches as well if you’re still stuck on checking for updates phase.
KB4011605KB4011607 – Office compatibility Pack SP3
KB4011657 – Word 2007
KB4011602 – Excel 2007
KB4011659 – Word 2010
KB4011660 – Excel 2010

Although power consumption may not scale linearly compared to CPU utilization, a constant increase in CPU utilization is bound to result in higher power consumption and heat generation anyways, neither of which are great. Think about it, you have an office of computers running at 100% CPU 24/7 cause they’re searching for those updates, and for the longest time I had no idea this was happening. The computer just felt a bit sluggish, as once you start using it the OS will intelligently reallocate resources to what you’re doing, and we had computer components dying prematurely from being constantly used by Windows Update. Planned obsolescence at its finest.

Note: For Windows Vista, you’re wondering if you have to install all of them and really in that order? Yes, I’ve tried installing just the last two, just the first couple, any combination and this is the only way that worked for me. This solution was compiled for many sources, too many to list, but mainly bleepingcomputer and mydigitallife. Also, just updated from Vista because it’s truly terrible.

ARTICLE CREDIT GOES TO: http://blog.jonmwang.com/2017/04/19/windows-checking-for-updates-stuck/

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/

June 4, 2018

Office 365 is no longer officially supported on Office 2007/2010. It still soft-off works OK on Office 2010. Here are the patches and updates you need.

Update your Office completely! (If you do, you might not need half of those updates below)

Outlook 2007 – Microsoft Online Services Sign-In Assistant (32/64) > SP3 (32) > Outlook 2007 update: November 13, 2012 (32)

Outlook 2010 – Microsoft Online Services Sign-In Assistant (32/64) >  SP2 (32/64) > KB2583935 (32/64) > KB2597051 (32/64) > KB2566458 (32/64) > KB2687623 (32/64)

Once all patches/updates are installed, you can go ahead and setup O365 on your old-school Outlook!