return to top

return to top

Database Errors

Network Initialization Failed - (a) Lock violation - File "x":\wmuni\dpdoxusers.net or (b) Multiple Net Files In Use error or (c) Directory is controlled By Another .NET File - Directory is XYZ file

Diagnosis of Problem

One or more Mun-Ease users do not have the proper directory defined for their network registration file.

Background

Mun-Ease is a multi-user system that stores data in a Paradox format through the Borland Database Engine (BDE). Multi-user systems must adopt controls to ensure that one user does not overwrite the work of another user. This capability is accomplished by Paradox through the use of the network registration file (Pdoxusrs.net) and locking files (Pdoxusrs.lck).
The network registration file maintains a list of active users on the system. Associated with network registration file are one or more locking files. Locking files exist for each database directory. Thus within Mun-Ease, you will have at a minimum, a locking file for both the Munidb and Muniexamples databases. The locking files are used by Paradox to chronicle the database records currently in use by users.

When you place the database files on a network server, Paradox requires that ALL database users use the SAME network registration file. This requirement is logical; doing otherwise would defeat the locking mechanism that Paradox uses to ensure that one user does not overwrite the work of another.

If Mun-Ease is the only application at your site that uses Paradox, we recommend that you define the registration directory to be <x>:\wmuni where <x> is the network drive. If you have other applications that use the BDE you might consider a more generic name for the directory such as <x>:\BdeNetDir.

Solution

• Request all Mun-Ease users to exit Mun-Ease. Also if you have other Paradox applications running at your site, request those users to quit their applications.
  
• Go to each user's computer. Start up either the BDE configuration or BDE Adminstration program (see below). Examples of the screens for running these programs are displayed in the chapters 1 (Installing Mun-Ease) and 20 (LANs).
  

If you encounter a user who has incorrectly specified the 'Net Dir' option, you must remove all of the 'LCK' and 'NET' files that he has created. Through Explorer, search for all files ending with an extension of '.Net' and '.Lck.' Delete these files. Be sure to search for these files on both the network drive (s) and local drives. Note that Paradox will automatically recreate these files when the user signs on to Mun-Ease and/or other Paradox applications.

Specific Steps

You can user either the BDE Configuration (BDEConfig) or the BDE Administration program to set up the network registration file. The BDE Administration program is a newer version of the configuration program. BDE Admin can only be run from an administrator signon under Window NT/2000 while there are no such restrictions on the BDE Config program.

Using BDE Configuration

Go to each user's computer. Start up the BDE configuration program (Start | Programs | Mun-Ease 2000 | BDE Config (32-bit)). While in the Drivers tabbed window, select the Paradox driver. On the right-hand side, click on the Net Dir field (network directory). Update the network directory if the directory is incorrect. Choose the File | Save menu option, then choose File | Exit. Repeat the same process for each PC on the network that uses Mun-Ease and/or other BDE applications.

Using BDE Admin

Go to each user's computer. Start up the BDE administration program (Start | Programs | Mun-Ease 2000 | BDE Administrator (32-bit)). While in the Configuration tabbed window, click on the plus (+) button to the left of drivers. Then click on the plus button left of native. Highlight Paradox and on the right-hand side, click on the Net Dir field (network directory). Update the network directory if the directory is incorrect. Choose the Object | Exit menu option, and if necessary save the configuration. Repeat the same process for each PC on the network that uses Mun-Ease and/or other BDE applications.

Network Initialization Failed - Unknown Internal Error in Muneas11.Exe

Diagnosis #1

You are running a Novel network and you are using a version of the Novel client that has a bug. This bug affects programs that use the BDE.

Solution #1

Sign on to the Novel support site and download a version of the client that fixes the bug.

Diagnosis #2

Tthe user does not have the authority to write to the folder where the network registration file resides (pdoxusrs.net).

Solution #2

Your LAN administrator must grant you read/write capabilities to the pdoxusrs.net file.

Invalid or corrupt index for database table error

Diagnosis of Problem

The index to the database table is either corrupted or out-of-date.

Background

Each database table within Mun-Ease is accessed through a database index or key. Indexes allow Mun-Ease to locate records quickly without having to search sequentially through the database tables for the desired record. Indexes for database tables have an extension of PX, XG*, or YG*. Because indexes are used to locate records on database tables, they must be synchronized with underlying table data. The above error message will occur if an index is out-of-date or if it points to a non-existent database record.

Diagnosis of Problem

Often the error is result of one or three situations:

1. Your database table may be filled to its maximum capacity.
   
2. The error may be the result of a crash on a network or a hard disk failure.
   
3. The error message is the result of a user loading a backup version of a database table without the corresponding index file(s).

(Note: This is one very important reason why we encourage users to use our backup utility. Our backup utility creates one large zip file of all tables within the database that ensures that the data and indexes are synchronized.)

Solutions

Purchase Paradox from your local retailer. From the main menu, select the database (usually Munidb). Then choose Tools | Table Repair. Click on the Rebuild button.

If the table is filled to capacity, initiate Paradox and choose Tools | Table Repair. In the Table Information tabbed window, enter Paradox 7 as the file format and enter 32 in the block size. Click on the Rebuild button. (In all liklihood, these settings will ensure that your table will NEVER be filled to capacity again.)

If the database table is a temporary table (e. g., Rptdtl.db or Rpthdr.db), you can just copy an empty table to your database directory. Through Windows Explorer, copy empty database tables from the wmuni\empty directory to the wmuni\db directory. The database tables that you should copy are: Rptdtl.db, Rptdtl.px, Rpthead.db, Rpthead.px, Rpthead.fam, and Rpthead.tv.

If you do not own Paradox or do not feel comfortable rebuilding the indexes, call us we help you restructure the table.
Problems Restoring Data From a Backup Disk - Corrupt or Out-of-Date PdoxUsers.Lck File

Diagnosis of Problem

When you restored the data from a backup disk, you mistakenly restored the pdoxusrs.lck file.

Background

The Pdoxusrs.lck file is a file that Paradox uses to chronicle the activities of active users on the database. Restoring an old .lck file would invalidate the locking controls currently in place and thus result in a Paradox locking error.

Solution

With Windows Explorer, search all folders copies of the Pdoxusrs.lck and Pdoxusrs.net files. Remove all copies and restart Mun-Ease.

return to top

Driver Problems

USB Key not found Error

Diagnosis: Safenet recently released a new version of their USB key drivers. Download the following file and follow the directions to install the new drivers.

Right click here to download the USBKey722.w01 File (approximately 6 megabytes in size)

Instructions: Save the USBKey722.W01 file to your wmuni folder on your local drive. Rename USBKey722.w01 to USBKey722.Exe. From the Windows start menu, choose Start | Run | c:\wmuni\USBKey722.exe.

Hardware Key Not Found Error

For more information, refer to the following document:

www.rainbow.com/support/files/endusertroubleshooting.pdf

Diagnosis #1

The hardware key is not installed on the parallel port of the computer that you are currently using.

Solution #1

Install the hardware key. If the key is installed, make sure it is securely fastened.

Diagnosis #2

The parallel printer port is not enabled.

Solution #2

If you are printing to a network printer, many times the local parallel printer port has not been enabled. To test whether your LPT1 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.

Diagnosis #3

You are using an operating system (Windows NT/2000) that requires the use of drivers to communicate with the hardware key. You have not installed the drivers.

Background to Diagnosis #3

The installation program creates an icon in your Mun-Ease group to install windows drivers for the hardware keys. The installation of the drivers is optional if you are running Windows 3.1, 95, or 98. Installing the driver is mandatory if you are running Windows NT/2000. Even though drivers are optional for all operating systems other than NT, Rainbow Technologies, (the manufacturer of the hardware keys) recommends that you install hardware key drivers for those operating systems. Communicating to the hardware key through a Windows driver helps eliminate the possibility of conflicts with other applications.

Solution #3

Install the drivers for the hardware key. The instructions for installing the drivers are in Chapter 1, Installing Mun-Ease.

Diagnosis #4

You are using a computer that uses a nonstandard address for the parallel printer port. This occasionally happens with printers that are using a docking station.

Solution #4

Choose the Install Sentinel Driver menu option. Mun-Ease displays a dialog box with appropriate directory prefilled for you. Click OK. Choose the Functions | Quit menu option to exit the program. Reboot your computer and the driver will be installed. See Chapter 1 (Installing Mun-Ease) for more details.

Diagnosis #5

You are using a printer/scanner that does not comply with the IEEE standard that governs how devices are to communicate through the LPT ports.

Solution #5

Use a different printer or connect the nonstandard printer through another LPT port.

return to top

Calculation Problems

Mun-Ease Displays a "Max Iterations Exceeded Error" During a Refunding or Sizing Calculation

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 "Sz2003Profile" while refunding profiles have an extension of "Rf2003Profile." 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.
Yield Calculation Problems

OID/OIP is Not Equal 0 when I enter a Price of 100.

Diagnosis of Problem

The par amount is not divisible by the denomination.

Solution

Change the denomination to a value that is divisible by the par amount.

Price/Yield Calculations Are Different From the Underwriter

Diagnosis of Problem

Discrepancies can be caused by one of three 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 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.
   

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 relevent 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, and enter the call date and call price. Then redo the price/yield calculations. Refer to Chapter 4 (Tips for New Users), Chapter 6 (File Options-Part I), and Chapter 17 (Interest Calculations) for more information about this subject.

Report Problems

ReportSmith Fact Sheets

ReportSmith Fact Sheet #1

ReportSmith Fact Sheet #2

ReportSmith Fact Sheet #3

ReportSmith Fact Sheet #4

Occasionally ReportSmith Does Not Start When I Press The Report Button

Diagnosis of problem

Assuming that you have (a) correctly installed ReportSmith and (b) there are no problems with your ReportSmith "con" or "ini" files, it appears that problem is that ReportSmith is in a minimized state. Always exit ReportSmith when you have finished viewing a report. If you minimize ReportSmith, it will be in a minimized state the next time you run a report. Therefore you won't be able to see the report since ReportSmith is in a minimized mode.

Solution

Search to see if ReportSmith has been minimized (check the Windows taskbar at the bottom of your screen to see if there is a ReportSmith icon. Maximize ReportSmith, then choose the File|Exit option to exit ReportSmith.

ReportSmith Generates a "No Rows Found" Error message or ReportSmith Displays The Wrong Report Data.

Diagnosis of problem

These problems can be caused one of four error conditions:

1. Information in the Userdata database table is incorrect or out-of-date. This situation frequently occurs if you have upgraded to a new PC and have copied the contents of the database directory from old PC. The userdata settings will be incorrect if Mun-Ease is installed in different folders than on the old PC.
2. 
   Path names for the database directory exceed 68 characters. (We store the path name of the database directory in an 80-character field in the Userdata.db database table. Thus the path plus the name of the table (which is 12 characters) cannot exceed 80 characters.
3. Incorrect information in the wmuni.ini file.
4. Incorrect information in one or more of the Reportsmith initialization or connections files. These files reside in the Windows or Winnt directory and are named Rptsmith.ini, Rptsmith.con, and Rs_run.ini.

Solutions

If the path names for the database directory exceed 80 characters, reduce the length of the path name by remapping the path name to a drive letter. Reinstall Mun-Ease using the new path name. If the database resides on a network, all users should use the same path name.

Check the contents of the wmuni.ini file located in the wmuni directory. Review Chapter 2 (Getting Started) for an explanation of the wmuni.ini settings. You can modify the settings in the wmuni.ini file through the Notepad utility or you can reinstall Mun-Ease. (The Mun-Ease installation program overwrites the contents of the wmuni.ini file.)
Check the contents of the Userdata.db database table by pressing the User Ops speed button. If the contents are incorrect, press the Refresh Dirs button in the Directories/Names tabbed window. Click Ok to update the record and to return to the main menu. (When you press Refresh Dirs button, Mun-Ease refreshes the user's options from the wmuni.ini file.) If the contents are still incorrect, delete the user ID by signing on as a new user ID, and deleting the old user ID through the settings|user options|delete/edit menu option. Exit Mun-Ease and restart using the user ID that you deleted. Mun-Ease will add the record to the userdata dataset using information from the wmuni.ini file.

Update the contents of the rs_run.ini and rptsmith.con files. Choose the setup|rptsmith directories menu option. Make sure that you have entered the correct path for the ReportSmith runtime viewer. Mun-Ease will update the "ini" and "con" files for reportsmith using data that you have entered and data from the wmuni.ini file and the Userdata.db database table. Also make sure that the user has the rights to update the "ini" and "con" files in the Windows/Winnt directory.
If none of the above options work, uninstall ReportSmith, remove the "ini" and "con" files from the Windows/Winnt directories, and then reinstall Reportsmith.

ReportSmith Runs Slowly.

Diagnosis of Problem

Most likely, your report database tables have gotten so large that their size is affecting response time.

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, new values are placed into Rpthead.db and Rptdtl.db, and ReportSmith takes data from these files. The report database tables are organized by report ID and user ID. When you run a report, Mun-Ease places a record in the Rptdtl.db table for each line in the report. That data remains in the table until the next time the user runs a report.

Solution

We provide a program to the empty the report database tables. The program is called speed.exe and is located in your wmuni folder. You can execute this program by choosing the Mun-Ease 2003 | Make my reports run faster icon from the Windows Start menu. Note that all users must be logged-off Mun-Ease before you can execute this program.
Alternatively, you can copy empty database tables from the wmuni\empty directory to the wmuni\db directory through Windows Explorer. The database tables that you should copy are: Rptdtl.db, Rptdtl.px, Rpthead.db, Rpthead.px, Rpthead.fam, and Rpthead.tv. The aforementioned tables are all temporary tables and can be replaced by an empty version from the wmuni/empty directory.

Unable To Load Rs_Api.Dll Error When ReportSmith Is Initiated

Diagnosis of Problem

Your LAN administrator has not given you read-access the Borland group in your Windows Registry.

Background

By default, Windows NT/2000 users do not have read-access to the registry on their machines. Because Mun-Ease passes information to ReportSmith through the Registry, you will need read-access to the Registry.

Solution

Ask your LAN administrator to grant you access by running RegEdt32. The specific steps to grant read-access to the registry are described in Chapter 1, Installing Mun-Ease.

Incorrectly formatted Report On the Printed Page - Information is Truncated or the Fonts Are Incorrect.

Diagnosis of Problem

Your printer does not have enough memory to format the printed page in memory.

Background

Laser printers format the each page of a report in memory before printing the page. At a minimum you must have at least 8 megabytes of memory in your laser printer. Generally we recommend 16-20 megabytes of memory.

Solution

Use another printer or buy more memory. Note that ink-jet printers do not require as much memory as laser printers since they do not format the complete page in memory before printing the page.

When you initiate a Report From Mun-Ease, RptSmith Crashes with an Error stating that there is an Invalid Page Fault in RSBDS47.DLL

Diagnosis of Problem

The user who is running Mun-Ease and ReportSmith does not have the authority to create temporary files in the directory defined by the Reportsmith.Ini file.

Background

ReportSmith generates all of its reports through SQL. With SQL, ReportSmith creates temporary tables and then merges these tables through a Cartesian join. After the initial installation of ReportSmith, the default location for these temporary files is the root directory of the user's C drive. However the location of these files can be changed by updating entries within the Rs_run.Ini file. (The location is defined by the Macropath and Binarypath entries in the MACRO32 group within the Rs_Run.Ini file.)

The 11.0 release of Mun-Ease changes the location where the RptSmith temporary tables are created by updating the Rs_run.ini file whenever it generates a report. (Mun-Ease changes the location to the Rs_Run32 folder (or the folder where the user has defined ReportSmith to reside). Thus users will need read/write access to the Rs_run32 folder.

Solution

Choose the setup | define ReportSmith directory menu option from the Mun-Ease main menu. As shown below, Mun-Ease will update the Macro32 group in the rs_run.ini file.

[Macro32]
BinaryPath=C:\RS_RUN32
MacroPath=C:\RS_RUN32

Back to top

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

Copyright© 1989-2003 j. dillavou

Authorized Licensor: Prescient Software jrd, inc. 24661 Del Prado #2• Dana Point, CA 92629 • Ph (949)248-5788 • Fax (949)248-5789 • jdillavo@mun-ease.com