E-Mail addresses

Prescient Software at





Troubleshooting / Tips

Mun-Ease is a product that has been in existence since 1988. Since that time, we have continually added features that have improved the reliability and ease of use of Mun-Ease. Occasionally though, hardware or other compatibility problems can affect Mun-Ease. This page will present solutions to a few of the more common problems that a user may encounter.


return to top



You have chosen to install the 64-bit version of Mun-Ease on a machine that has the 32-bit version of Microsoft Office installed.

Background: Mun-Ease generates all of its reports with the Crystal Reports report-writing utility. Whenever you request a report, Mun-Ease reads the data from the database, performs all the necessary calculations, and then writes the temporary report data to a Microsoft Access table. It then initiates Crystal Reports to generate the report. Because Microsoft does not allow 64-bit Office drivers to reside on a computer if 32-bit Office drivers are currently installed, you are receiving the "provider not found" error.

Solution: You can either (a) install the 64-bit version of Microsoft Office, or (b) you can install the 32-bit version of Mun-Ease. If you install the 32-bit version of Mun-Ease, you do not need to uninstall the 64-bit version.


At startup, Mun-Ease reads the wmuni.ini file in the user’s personal folder. If Mun-Ease is unable to read this file or if the wmuni.ini file contains erroneous information, Mun-Ease will display an error message and then terminate. Often this problem results from an invalid desktop icon created by the installer. If the installer manually creates an icon with the incorrect startup folder, then Mun-Ease will not be able to read the wmuni.ini file. The user will receive a “path could not be found” error.

There is an easy way to ensure that this problem does not occur. Instead of manually creating icons for the desktop, let the Mun-Ease installation program create the icons for the user. The installation program will create two icons on the desktop: an icon for Mun-Ease and another icon for the various utilities associated with Mun-Ease.


The Installation program creates icons for the various functions of Mun-Ease in the Mun-Ease 2015 group that is created
under the All Programs area of the Start menu. There are two reasons why the user would be unable to see the Mun-Ease icons: (a) The installation program aborted before all of the installation tasks were completed. (Creating the icons is one of the last tasks performed by the installation program). (b) The installer installed Mun-Ease under a Windows sign-on that is different from Windows sign-on of the user. The installer should install Mun-Ease under the user’s sign-on and temporarily give the user administrative rights before initiating the installation process (see Chapters 1 and 2 in the User Guide).

Note that the desktop icons created by Mun-Ease can be accessed by all user accounts on the PC.


Microsoft‘s standard folder conventions differ from Windows XP and Windows 7/8/10. We store the user’s preferences and folder settings in the userdata database table. Thus the user will encounter errors if (a) he has upgraded his computer from Windows XP to Windows 7/8,10 (b) he uses the same sign-on that he previously used under Windows XP, and (c) he references the same database that was used under Windows XP. To correct this problem, the user should sign-on to Mun-Ease with a 3-character ID that does not exist. At the main menu, choose the setup | user options | edit/add/delete another user profile menu option and delete the old user ID. Exit Mun-Ease and start Mun-Ease again. This time, sign on with the user ID that you previously used under Windows XP. Mun-Ease will recreate the user profiles record with the correct Windows 7/8/10 settings. The settings in this record are derived from the information in the wmuni.ini file.


return to top



Diagnosis #1: The hardware key drivers have not been installed or they have been installed incorrectly.

Solution #1: Install or reinstall the hardware key drivers. If the drivers have been previously installed, we recommend that you first uninstall the drivers and then perform a new installation. o For a USB key, choose the start | all programs | Mun-Ease 2015 | USB key driver installation menu option. Choose the default options and driver will be installed. In some cases, you may need to reboot after the driver is installed. Important: During the driver installation, the installation program will ask if it can temporarily disable the firewall. Be sure to answer “yes” to this question.

Diagnosis #2: The hardware key is not connected on the USB port of the computer that you are currently using.

Solution #2: Connect the hardware key. If the key is installed, make sure it is securely fastened.

Diagnosis #3: The hardware key did not respond in a timely manner to the Mun-Ease request for authentication.

Background: The routines that we use to make inquiries to the hardware key are supplied to us by the vendor Safenet. Safenet requires that the key respond to inquiries within a few milliseconds. This requirement is to ensure that the inquiry is a legitimate request and not an attempt by a hacker to breach the security of the key. We have noticed on very few occasions that the hardware key will fail to meet the response time requirements if the user has several large applications open at the same time. This situation occurs because Windows is busy swapping out the other applications from memory to disk and swapping Mun-Ease into memory from the hard drive.

Solution #3: Try terminating Mun-Ease and all other applications. Then restart Mun-Ease. If Mun-Ease still does not recognize the hardware, then reinstall the drivers for the hardware key.

Diagnosis #4: The USB port is not enabled.

Solution #4: If you are printing to a network printer, many times the local USB port has not been enabled. To test whether your USB port is enabled, try printing to a printer connected to the port. If you cannot print to the local port, your port has not been enabled. You can enable the port through the Windows control panel. For more information about the hardware keys, view the Mun-Ease Installation Chapters (chapters 1 and 2) or the support page of Safenet’s website at: http://www.safenet-inc.com/support/tech/sentinel.asp



return to top

Calculation Problems


Diagnosis: The par amount is not divisible by the denomination.

Solution: Change the denomination to a value that is divisible by the par amount. (Choose the file | fixed rate bonds | edit menu option and change the denomination in the basic inputs window.)


If a bond issue contains maturities that meet the arbitrage yield-to-call test, Mun-Ease will calculate the arbitrage yield limit by assuming that those maturities are called on the call date the provides the lowest arbitrage yield limit. Thus the debt service schedule cannot be used to calculate the WAM since the WAM calculation is calculated to the maturity date for all maturities.
In other words, the WAM calculation ignores the fact that some (or all maturities) of a bond issue must be calculated to the call date. You can work around this limitation by first calculating the arbitrage yield limit through the arbitrage | yield limit menu option. If asked, instruct Mun-Ease to calculate the WAM to the original maturity date. After you perform this calculation, THEN perform the yield-to-call test (arbitrage | yield tests | yield-to-call test). Although Mun-Ease will perform the requisite yield-to-call tests and will modify the arbitrage yield limit calculation if necessary. However it will not override the original WAM calculation.


While you can perform a NIC calculation on a bond issue that contains zero coupon maturities, it is not recommended. The results will be nonsensical because of the limitations in the formula used in this calculation. Please see the Interest Calculations Chapter (chapter 17) for more details.


Diagnosis of Problem:

Discrepancies can be caused by one of four error conditions:

1. Incorrect dates – Be sure that you have entered the correct dated date, delivery date, first coupon date, maturity date, term
date, and call date.

2. The underwriter performed the calculation by (a) entering the yield and calculating the price whereas you performed the calculation by entering the price and calculating the yield or (b) the underwriter performed the calculation by entering the price and calculating the yield whereas you performed the calculation by entering the yield and calculating the price.

3. The yield or price quoted by the underwriter was calculated to the call date under the price-to-worst or yield-to-worst rules.

4. You are attempting to perform a price/yield calculation on a maturity that you have set the call switch to “Y.” If the call switch is set to “Y”, then Mun-Ease assumes that you want to insert the yield-to-call calculation in the reoffering yield column. To correct this situation, set the call switch back to “N” and redo the calculation. You can reset the call switch back to “Y”
by choosing the file | fixed rate bonds | call and defeasance dates menu option. This option will not change the price/yield calculation that you previously performed while in the Maturity grid.

Background: When quoting a price to a customer, MSRB Rule G-12(c)(v)(I) requires that broker/dealers quote the lower of the price-to-call or price-to-maturity. Conversely, the Rule requires underwriters to quote the lower of the yield-to-call or yield-to-maturity. Generally the call date is only relevant for these types of calculations whenever there are early call options and the maturity is sold at large reoffering premium. When performing a price/yield calculation within the Maturity Grid, Mun-Ease will provide a yellow warning in the bottom message panel if the price/yield calculation is based on the call date. Solution Recheck the dates that you entered to ensure that there are no errors. If you performed the calculation by entering the yield, redo the calculation by entering the price (or vice versa). To determine whether the calculation is performed as of the call date, expand the maturity grid to include call features, and enter the call date and call price. Then redo the price/yield calculations. Refer to
the user guide - Chapter 4 (Tips for New Users), Chapter 6 (File Options–Part I), and Chapter 17 (Interest Calculations) for more information about this subject.


Diagnosis or problem:

In most cases, these problems are due the user using an out-of-date or invalid profile for the refunding or sizing analysis. Background Mun-Ease allows you to retrieve the inputs you previously used in a sizing or refunding analysis. This option
minimizes the data entry when you wish to redo a previous analysis with only slightly different options. Sizing profiles have an extension of “Sz2015Profile” while refunding profiles have an extension of “Rf2015Profile.” If you use a profile to size a bond issue with different dates (e.g., dated date, first coupon date, first principal date, etc.) than defined by the profile, you will encounter “max iterations exceeded” errors. This occurs because Mun-Ease maintains many hidden date and day count calculations within the profile.

Solution: Only use a profile for a specific analysis or case study. Don’t retrieve an old profile for a new analysis. If you do encounter this error, then size the new-money or refunding bond issue without a profile. When you’ve successfully completed the analysis, then you can save the profile to your personal directory for future use.

return to top

Report Problems


Diagnosis: Data in the report needs to be refreshed. Click on the report button again to regenerate the report.


This is a generic error in Crystal Reports that occurs whenever the report query fails. While there are a number of reasons why Crystal Reports could generate this error, the most common reason is that Crystal Reports does not have sufficient memory to generate the report. Exit and restart Mun-Ease and try generating the report again.


Diagnosis: In most cases, this problem occurs when a user upgrades from a Windows XP computer to a Windows 7/8/10 computer.

Background: The folder conventions are different for a Windows 7/8/10 computer than for a Windows XP computer. Mun-Ease stores the folder locations in the UserData database table. When the user upgrades to Windows 7, the locations are no longer valid. You can correct this problem by:

Signing on to the Windows 7/8/10 computer with a user ID that doesn’t exist (a temporary user ID). Mun-Ease will initialize the folders for the user by reading information from the wmuni.ini file.

Delete the old user ID in the Userdata database table. (setup| user options | edit/add/delete another user’s profile).

Sign off Mun-Ease and log on with the old user ID. Mun-Ease will initialize the user ID with the correct settings. You can then delete temporary user ID.


Diagnosis of Problem:

You do not have the requisite fonts installed on your computer.


Reports within the Sizing, Refunding, and Arbitrage modules use BT Lydian fonts. Almost all of the modules use Garamond font. If you do not have BT Lydian fonts installed on your computer, Crystal Reports instead displays the report with a Arial font. If the Garamond fonts are not installed on your computer, Crystal Reports displays the report with the Times font. You can install these fonts by starting Windows Explorer and browsing to the \fonts subfolder from your personal directory: (c:\users\<user ID>\AppData\Prescient Software\Mun-Ease folder for Windows 7/8/10 users). Windows Explorer displays a list of fonts used by Mun-Ease. Right-click on the font and choose the Install font option from menu. If Windows responds that the font is already installed, press cancel button to discontinue. Right-click on the next font in the folder and attempt to install it. Continue this process for each font in the \fonts folder.

return to top



For performance reasons, both the SQL Server and the ElevateDb databases attempt to perform most database operations in memory. To ensure that the database operations are applied in a timely manner, Mun-Ease forces both SQL Server and the ElevateDb database to empty their memory cache whenever the user returns to the main menu. However, other users will not see the changes immediately unless they press the refresh button on the navigator pad.


The Mun-Ease installer specifies the folder locations for the Mun-Ease executable files, report specifications,
UDL files, database files, and the database configuration file. In a multi-user environment, the installer must install the databases and database configuration file in a common location. Typically the standard databases are installed in three subfolders off the root Mun-EaseDbs folder (Mun-EaseElevateEmptyDb, Mun-EaseElevateMainDb, and Mun-EaseElevateExsDb). The EDB configuration file is also installed in a subfolder off of the root Mun-EaseDbs folder (EDBConfig). If you encounter errors at start up, we recommend that you check the settings used for the installation in both the wmuni.ini file and the EDB Configuration file. These settings should be same for all users if the database is installed on a server.


  1. Open the wmuni.ini file in Notepad. This file resides in the personal folder of the user (c:\users\<user ID>\appdata\prescient software\Mun-Ease).
  2. Check the locations for the databases and the EDB configuration file.

    For example:



  3. Start the EDB Manager (Start | All Programs | ElevateDB-ADD). Sign on with the User ID of Administrator and password of EDBDefault. Check the location of the configuration file for the Default session by right-clicking a session named Default and choosing edit session menu option. The location of the configuration file is shown under the local tabbed window. Editing EDB Session: You can also check the location of the databases opening up the databases icon under the default session. The location of the database is shown at the bottom of the middle tabbed window.


By default, Mun-Ease will install four Uniform Data Link (UDL) files to the user’s computer which are used to connect to each database. These UDL files are called Mun-EaseMainDb.UDL, Mun-EaseExamplesDb.UDL, Mun-EaseEmptyDb.UDL and AccessRptDbforMun-Ease.UDL. For Windows 7/8/10 users, the default location is c:\Users\<UserID>\AppData\Prescient Software\Mun-Ease\UDLFiles folder where <userID> is the windows sign-on or “public”.

Steps: (The Installation Chapter contains additional information about initializing UDL files.)

  1. Double-click on Mun-EaseMainDb.UDL icon. The Windows operating system will initiate the UDL
  2. Click on the provider tabbed window and choose Microsoft OLE DB provider for SQL Server from the OLE DB Provider list box.
  3. Click on the Connection tabbed window. Enter the server name. If you have not installed SQL Server locally
    on the client computer and you do not have a named instance, enter (local) as the server name.
  4. While in the Connection tabbed window, choose between Windows integrated security or enter a user name and password. (For the sake of simplicity, we generally recommend that the installer choose Windows integrated security.)

Enter Mun-EaseMainDb as the name of the database. Click on the test connection button to ensure that you have a good connection to the database. 6. Repeat the above steps for the Mun-EaseExamples.UDL and Mun-EaseEmptyDb.UDL datalink files. Be sure to substitute the Mun-EaseExamplesDb and Mun-EaseEmptyDB databases for the Mun-EaseMainDb database in each respective data link file.


Background: With few exceptions, the reports generated by Mun-Ease do not draw their data from the primary bond database tables. Instead, every time you run a calculation or a report, new values are placed into the Rpthead and Rptdtl database tables. Mun-Ease then executes Crystal Reports which reads data from these tables to generate the requested report(s). Data in these tables is indexed by the user ID and the report ID. The Rpthead database table contains information that is displayed in the report header and footer. The Rptdtl table contains information in the body of each report (Mun-Ease creates a record for every line in the requested report). Both the EDB and SQL Server versions of Mun-Ease maintain the report database tables on in a separate database located on each client computer. We chose this architecture so that the reporting process does not negatively impact server response time. By choosing to generate the reports locally, Mun-Ease will update these two tables on each client computer instead of the server. The two tables are located in the AccessRptDbForMun-Ease database located in the C:\Mun-EaseDbs\Rptdb. These two tables are in a Microsoft Access format and are updated through the Microsoft Jet Engine.

How to Verify the Report UDL File Settings (32-bit computers)

  1. Double-click on the AccessRptDbForMun-Ease.UDL file located in the UDLFiles subfolder of the user’s personal directory. Windows initiates the UDL wizard.
  2. Click on the Provider tabbed window and choose the Microsoft Jet 4.0 Db Provider option from the list box.
  3. Click on the Connections tabbed window. Click on the browse button and choose (or enter) the database from
    the Browse window (AccessRptDbForMun-Ease.mdb in the C:\Mun-EaseDbs\RptDb subfolder.) Enter the name of the user (Admin) and a blank password.
  4. Press the Test Connection button to ensure that you have correctly connected to the report database.

    How to Verify the Report UDL File Settings (64-bit computers) If you install Mun-Ease 2015 on a 64-bit computer, the installation program creates an additional icon called “Access DB Driver Instructions for 64-bit computer” in the Mun-Ease 2015 group. This icon contains a text file with instructions on how to set up the Access UDL file on a 64-bit computer. The text file is named LInstructions64bit.Txt and is located in the \UDL subfolder.

    How to Verify the Report UDL File Settings (32-Bit Version of Mun-Ease on a 64-bit Computer)

    When you double-click on the AccessRptDbForMun-Ease.UDL file on a 64-bit computer, the Windows 7/8/10 UDL wizard assumes that you are installing 64-bit drivers. Thus you cannot manually install the Access drivers using the UDL wizard if you are running the 32-bit version of Mun-Ease on a 64-bit computer. Instead you’ll need to click on the Windows Start button and choose the Run menu option. Insert the following statement into the Run text box:

    C:\Windows\syswow64\rundll32.exe "C:\Program Files (x86)\Common Files\System\Ole DB \oledb32.dll",OpenDSLFile C:\Users\<USERNAME>\AppData\Prescient Software\Mun-Ease\UdlFiles\AccessRptDbForMun-Ease.udl

    (Be sure to change the <USERNAME> text to the actual user name.)

return to top



Diagnosis of problem:

In most cases, these problems are due a user not having sufficient permissions to run Mun-Ease. Make sure that the user has read/write access the database folders, the user’s personal directory, and the folder where the network registration file

Shown below are the default folder locations where the Mun-Ease Installation program will install files for Windows 7/8/10 users.

Personal Files:

C:\Users\<UserID>\AppData\Prescient Software\Mun-Ease

This is the default folder location where the Mun-Ease personal data files and temporary files used for calculations reside. The user needs read/write permissions to this folder and all subfolders. The user needs permissions to read and update wmuni.ini file that resides in this folder.

Program Files:

C:\Program Files\Prescient Software\Mun-Ease (64-bit version on 64-buit computers)

c:\Program Files (x86)\Prescient Software\Mun-Ease (32-bit version on 64-bit computers)

This is the default folder where all executable files will reside. The Crystal Report DLLs are usually placed folders under the c:\Program Files\Crystal Decisions folder.

Database Folders (ElevateDb database):

The standard Mun-Ease databases reside in the subfolders off of the Mun-EaseDbs folder. The subfolders are: Mun-EaseElevateMainDb, Mun-EaseElevateExsDb, and Mun-EaseElevateEmptyDb. The EDBConfig folder is where the
network registration file resides. The location for this file is defined in the Mun-Ease installation program and wmuni.ini file. You can also check the location through the the ElevateDB-ADD program. Note that ALL users must define a common location for this file. Thus the user needs read/write access to the database tables.

Database Folders/Permissions (SQL Server Database)

The location of the database is defined in the SQL Server Studio Manager . The DBA also defines the rights/permissions for each user also in the SQL Server Studio Manager. Each user should have read/write authority to all tables within the database. One user should be designated as DB_Owner and DB_Creator.

return to top



Diagnosis of Problem:

Mun-Ease displays a warning to you if you initiate a new instance of Mun-Ease when you have an existing copy of Mun-Ease running.

Solution #1 to Problem:

If you receive this warning, check to see if you have minimized an existing copy of Mun-Ease. If a minimized copy of Mun-Ease exists, press “yes” to terminate the new instance of Mun-Ease.

Solution #2 to Problem:

In two other instances you will encounter this error. It is caused by one of two situations: (a) you abnormally terminated Mun-Ease in a prior session and the Mun-Ease database has a record of you currently being active, or (b) another user has signed on to Mun-Ease with the same user ID as you.

Background: Mun-Ease requires each user to have a unique three-character user ID. We use that ID to log the activities of each user in a database table called Semaphr2. By logging the activities of users, Mun-Ease has the capability to prohibit concurrent updates of a bond issue by different users. Thus if a user is entering rebate transactions for a bond issue, other issuers will be prohibited from performing any other update to that bond issue until the first user finishes. You can view other users and their activities through the setup/who’s here menu option. Solution to Problem If you abnormally terminated your session, press “yes” in the above dialog box. Press “no” if you believe another user has signed on to Mun-Ease with your user ID.


Diagnosis of Problem:

You have specified large fonts in the display settings or your computer has an incorrect video driver.

Background: Before discussing this problem, we will review the relationship between the screen resolution and the font size on your PC. You define your screen resolution by clicking on the Display Settings icon in the Control Panel. If you run with a high screen resolution, fonts and programs will appear smaller. Conversely, a lower screen resolution will increase the size of fonts and windows. Mun-Ease screens are designed to viewed at 1024x768 DPI. We also include a feature for users who run Mun-Ease with a screen resolution higher than 1024x768 DPI. This feature allows a user to expand the size of a window and the data grid within the window. You initiate this feature by clicking on the high resolution radio button at the bottom of the screen. When you initiate this feature, Mun-Ease will expand the size of the window and data grid to take advantage of the additional screen space. This capability is available when you are viewing the bond maturity grid, the rebate transaction grid, and the variable rate transaction grid. We have been able include this capability by anchoring the panels below the data grids (and buttons within those panels) to the bottom of the window. If your computer has invalid video drivers or you have configured your video driver to display large fonts, the bottom panel will not be in clear view. Be sure that you have installed the correct video driver. Also your video driver must be configured to display normal (small) fonts and not large fonts. Mun-Ease windows are not compatible with large fonts.


Diagnosis of Problem:

When attempting to import the SLGS rates from the Bureau of Public Debt web site, your computer starts Excel and attempts to read the comma-delimited file. Excel incorrectly converts one of the columns in the file to a date format.

Solution to Problem:

Windows allows the user to associate a type of file (as defined by its extension) with a program. In your case, the comma-delimited (.csv) files are associated with Excel. Shown below are the steps to change the default program
that opens a .CSV file:

1. Start Windows Explorer and go to the \DbImports folder in your personal directory (c:\users\<user ID>\AppData\Prescient Software\Mun-Ease folder for Windows 7/8/10 users).

2. Right-click on any file that has a .CSV extension. Choose the Open With menu option. Windows opens a Window. If Notepad is listed, choose it. Otherwise, click on the choose default program menu option. Browse to the c:\windows\notepad.exe file and choose it.

3. Optional step: Choose the task bar and start menu option in the control panel. Click on the customize button in the start menu tabbed window. In the downloads section, click on the display as a link radio button.

return to top


Prices/features | How to Buy | Downloads | Support | User Group | SLGS Rules | News | Classes | Tips

Copyright© 1989-2015 j. dillavou

Authorized Licensor: Prescient Software jrd, inc. 23732 Hillhurst Ave. #37, CA 92677• Ph (949)248-5788 • Fax (949)248-5789 • jdillavo@mun-ease.com