Saturday, February 29, 2020

TDI Media Driver Service won't start after upgrade to Version 21.82.2123.0

TDI Media driver service won't start after upgrade to version 21.82.2123.0

This note applies to Shoretel Servers running on Windows Server 2008 R2 Enterprise.

Shoreware TDI Media Driver Service fails to start because of a digital signature issue.
Resolution: Install the microsoft patch that adds SHA-2 certificates on new .sys drivers
after jan 1, 2016. Or just use the old pre-2016 version of TDIMedia.sys

Resolution Your system will require the patches if your server is running Windows Server 2008 R2 Standard or Enterprise.

See Advisory 3033929 then download and install the patches as needed, then reboot.

for 2008 Server R2

Or for 2008 Server


Shoretel Upgrade Process

For shoreware director servers running Windows 2008 R2 Enterprise x64, that have not been updated since 2015.  Shoretel TAC advises not to allow automatic windows updates.
  • Install the SHA-2 patch from KB3033929
  • then install Shoretel 21.82.2123.0 onto Shoretel 19.46.1802.0, this would upgrade your shoretel 14.2 to shoretel connect
  • Then install Firefox
  • Re-install your custom CDR database modifications that you had previously.
  • Import your old CDR records because they were wiped out during the upgrade

Thursday, February 27, 2020

You Get Kicked Out of Encompass When Printing Forms

Encompass Quits Suddenly When Printing Forms the Second Time

Suddenly and without warning the app just quits right after printing a custom form. It usually happens when you print for the second time.  The first time you print the form and show it to your Encompass expert it works fine. Then you try it again after she leaves, then it happens.  The Fix is to edit the windows registry and delete the App Compatibility flags

Fix for Printing when it just quits suddenly or you get kicked off

1.  open regedit.exe
2.  open key
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
delete the key within this branch.

3. and then open key
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
delete any encompass.exe related keys within this branch.

Delete This Key and Others Similar to It

Wednesday, February 26, 2020

Intuit Lacerte 19 Fatal Application Error and Exit [ Fixed with Database Rebuild ]

How to Fix Intuit Lacerte Fatal Application Error and Exit by Rebuilding the Database


Recently, Intuit Lacerte 2019 have shown a propensity to suddenly exiting immediately after startup or when switching between modules.  Furthermore, Lacerte 2019 can become very slow and laggard when switching between clients.  As is the case, often the module's database is fouled and switching to it will immediately crash the application with a pop-up dialog that says "EXITING APPLICATION" See the image below.  It is caused by a software defetc AKA "bug" in the application that is triggered by using the e-file utility.  E-File causes database corruption.  Often there will be left-over URN files in the Lacerte shared drive.  URN files are semaphore files that indicate a user is logged on. There is no need to re-install the application as instructed on the Intuit Pro-Connect community.  The instructions apply to Lacerte 2019, to use with Lacerte 2018, just change all 19 to 18.   The Fix is to delete the URN files and rebuild the database.

It happens to lacerte 2018

and it happens to 2019

How to Fix with CLPACK

Before doing anything at all to your Lacerte module's database files, you must make a backup of the database.  Use WinRar or Winzip to make an archive of the whole directory.   Furthermore, you need to tell all users to exit from Lacerte.  You will need to use CLPACK rebuild the suspect module's database files. Each module has a database of files. On your server, you will have a folder DRIVE:\Lacerte\19tax\XData where the X is I for individual, P for partnership, C for corporate.  For example you may have:  V:\Lacerte\19tax\IData for your indivivual module's files. Use the Lacerte Database Repair Utility, on a client computer, which is located in c:\Lacerte\19Tax\ and is called 19clpack.exe

Step 1: Find CLPACK in c:\Lacerte\19Tax\  called 19clpack.exe,

Step 2: Run it, by double-click, then fill in the datapath (it may auto-populate)

Step 3: In CLPack, select a tax type that is suspect, then fill in the correct datapath to the database
Step 4: Choose "Reindex/Repair" The press Start, then wait until completion. then press Reindex Calendar
If you see this message: it indicates that other users are logged on, please tell them to Get Out! If you continue to see it even when no more users are logged on, then you will need to delete the URN files.
This Error indicates that URN files are present
To delete them, open the explorer and go to the Lacerte server drive and then into the 19tax directory, then into IDATA, you will find an URN directory. Delete the files within it.  Also find the option19 directory and then find the URN folder and delete it's contents too. Here's an example of what you will find:

Finally, once you remove the URN files, then press the Start button on the database repair utility program. When finished, this is what you will see.

Step 5: Verify that "no Errors detected" appears in the messages, then press the "Reindex Calendar" button.

Optional Step 6:  Reset the Client Grid
This will fix issues with switching betwen modules

Edit the Lacerte 2019 short cut from your local desktop, (right click, then properties)
ADD TO TARGET APP IN SHORTCUT, append CLGRID to the program arguments. Like this:
C:\Lacerte\19tax\w19tax.exe CLGRID
Save it, then double-click on the icon
finally delete all URN files from share drive server folder and
local c:\lacerte folder

Tuesday, February 4, 2020

Ellie Mae Encompass: Error encountered while downloading manifests [how to fix]

Encompass Starts Up and Shows a Dialog box with "Error Encountered While Downloading Manifests

Encompass Startup Error

This error indicates that the application has not downloaded the correct manifests for your Encompass client ID. It usually means that the client ID is incorrect or has a E following the number. Usually the client ID starts with BE and follows by some numbers. For example:  BE12345678 there are usually 8 digits following the BE, If you are not sure, check with your encompass administrator. Don't try to guess it, or you will end up with an even bigger mess.

How to Fix

Use the remove-uac application to cleanup and scrub the offending manifests and other artifacts. You can find remove uac in c:\SmartClientCache\Apps\Ellie Mae\Encompass

Remove-uac dialog box
After you run this and cleanup all of the files in this folder. You will see most of the files diasspear. Now you should run the app luancher from:  "C:\SmartClientCache\Apps\Ellie Mae\Encompass\AppLauncher.exe"

Enter the correct client ID, and then run it to download all of the correct manifests.

Hire An Encompass Pro Today

Are you still googling around for solutions to your Ellie Mae Encompass problems?  Are you ready for URLA?  How is your compliance management? How is your underwriting and loan processing operations keeping up with Encompass? Do you still run Encompass on Windows 7 and need to upgrade before January? Consider hiring Encompass experts and leave all your software worries to them.  Check out our services that we offer in Southern California and beyond.  Our hourly rates are quite low by industry standards.  In the range of $95 to $125/hour depending upon complexity. Eleven Dimensions Technologies offers onsite support and remote support for Ellie Mae's flagship product.  Call our small business services department at (949)371-5079