Dynalogic, Inc.
Integrated Financial Solutions for Organizations requiring fund
or encumbrance accounting
Pride in Quality
Software
Our Business is based on Customer Satisfaction
|
Technical Support
This page list many of the questions asked to us by our clients.
These questions are categorized as follows:
If you get the following message:
wrun32wisp.exe - Entry Point Not found
The procedure entry point ACUndefineVariables could not be located in dynamic link library acme.dll
Check to be sure your wconfig file is set to the correct Wisp verson. (Run wisp4406\bin\wconfig)
Also make sure your PATH contains the path to the correct Acucobol version
your are using
and verify wrun32wisp.exe and wrun32wisp.dll are in the acucbl521\AcuGT\bin directory
If you get the following message:
%WIN32_PRINTFILE-E-SYS
System error: The print name "\\printer name" was not found.
This screen appears when the PrntMode is set to "S" and not "K"
Access Help, F3 Print Mode defaults
If you get the following message:
ERROR FROM LINKING TO 0020DISPLAY
This screen appears if wordpad.exe cannot be found
Make sure wordpad.exe is on your path (put in c:\winnt or c:\windows) and make sure directory used is on your path
This information is for a Network Version of Co*Star running under Windows 2000 users
If the message "Connection refused" given when accessing Dynalogic using Co*Star, from your server machine, try this:
1. From the Control Panel, go to Administrative Tools
2. Access Services
3. Find the Co*Star License Server line
4. If it does not show start, Right Click and Start
5. Right click to access the Properties function
4. Verify the Start Type is Automatic and path is correct.
This problem applies to Windows 2000 users (not using the Co*Star interface)
1. From the icon, Right click on the tab to access the Properties function
2. From the Command Prompt Properties,
disable the Edit Options "QuickEdit Mode" and "Insert Mode".
This problem applies to Release 5.3 users.
In the OPTIONS file found in your Wispxxxx\CONFIG directory, check to be sure that the
READFDRV1 line is
uncommented (that is, the # symbol is not in front of this statement).
WISP Users only
When running a program in Payroll, the message "A01PW Program missing or inaccesible" occurs
The problem is most likely that the Acuconfig file for Wisp is incorrect or cannot be found.
First check to see that wrun.cfg in the wisp4406\config directory contains the following on the Options line
OPTIONS -b -c 'x':\dyn\wisp4406\acufig53
if that looks okay but the problem still exists, call Dynalogic and they will help you run the
wdiag.exe program from the wisp4406\bin directory.
Unix Users only
Workstation is not displaying the full 132-characters on a report legibly when function key 6 pressed from the
Display utility.
This can be fixed by increasing the Windows screen resolution to a greater pixel count (such as 1024 x 768).
Note: This most likely will affect the display of screens from non-Dynalogic software.
There are two known situations during the A/P Check run that can cause this error:
1. The backup directory DYyymmdd, where yymmdd is today's date, already exists.
2. Another user is in the Dynalogic system and has a file open that is to be backed up.
Please delete the backup directory, make sure there are NO users in the Dynalogic system,
re-enter the Dynalogic system (you will need to reset user counts for your id
see System Control),
and retry the check run.
The Dynalogic system warns users if it senses a User Id is in the Dynalogic system more than one time.
Each time a user logs into the Dynalogic system, the User Id count is incremented by one. When the user
gracefully exits the Dynalogic system, the User Id count is decreased by one. If, for some reason, the
user cancels out of the Dynalogic system or cannot exit from the Main Menu, the User Id is not decreased.
Therefore the next time the user logs into the system, the message stating
System shows you are already logged into Dynalogic with this User ID is shown to the user.
The user can continue system use by pressing the Enter key. However, if this is the only Dynalogic session
for this User Id, the user count should be reset.
You must be a Dynalogic System Administrator to reset user counts.
- To reset user counts, press function key 26 (Sys Ctl) from the Dynalogic Main Menu.
This takes you to the "Termination Dates and User Activity Control" screen.
- From this screen press function key 13.
The "Fund Accounting User Records with non-zero counts" screen is displayed.
- To reset particular users, input a "Y" next to their user Id and then press ENTER.
Be careful not to reset users that actually are logged into the Dynalogic software.
For Windows 95/98/NT users
Temporary files created on each users local drive in the C:\TMP\WISPTMP directory should be manually
deleted when the user is not logged in. These files start with RC_ and WPS_. The RC_ files contain return
codes. The WPS_ files contain the usage constants in use at the end of each session. If a session
abnormally halts, a WPS_ file could contain the payroll usage constants and be inadvertently selected the
next time the user logs into the system.
For Unix users
Temporary files created on the server in the /var/tmp directory should be deleted when there are no users
logged in. These files start with PERSON and contain the usage constants in use of the end of each
session. If a session abnormally halts, the PERSON file could contain incorrect usage constants and be
inadvertently selected the next time the user logs into the system. When these files are deleted, the
system is forced to correctly use the users PERSONALITY file located in their home directory.
This problem applies to Windows 2000 users.
When the Dynalogic Accounting Window is up, right click at the top-most left corner of the screen.
1. Select the Properties Tab.
2. Select the Font Tab.
3. Change the Font size (for example to 11x18)
4. Press OK
This problem applies to Windows 95/98 users only.
WISP for Windows NT/95 uses "Console Mode I/O" for the workstations I/O. On Windows 95/98 the console
will select an unreadable small font unless it is configured to use a specific font. You can configure
the console by create a PIF file for the CONAGENT.EXE program.
1. Using Explorer select file c:\windows\system\conagent.exe
2. From the File menu, select Properties
3. Select the Font tab.
- Select a font size other than "auto" (for example, select "8"x"12")
- Click the Apply button
4. Select the Screen tab.
- Deselect the "display toolbar" checkbox
- Click the OK button
This will create file c:\windows\system\conagent.pif
If you get the message
"unable to properly size the console window - consider creating a pif file",
then delete the existing conagent.pif file and create a new one using the steps above.
This problem applies to Windows 2000 users (and possibly Windows 98)
If upon initial entry into the Dynalogic system the program screen overflows the windows boundaries
and no Taskbar is available, try this:
1. Press ALT + TAB to switch active applications. The Desktop and Taskbar should appear.
2. Find the tab that references the Dynalogic application
3. Right click on the tab to access the Properties function
4. Set the Display option from Full Screen to Window.
Windows 95/98/NT Users
Occasionally a report can print lines from a previous page at the bottom of the next page. This can occur
if there are many 'underline' lines on the printed page (for example, an Expense Summary report).
Each of the 'underline' lines count as one printed line. If the FORMS file used for printing has
page length as 66 lines (pl=66), these underlines can go over the 66 line limit and the 'extra' lines
are not cleared prior to printing the next page.
To fix: in the FORMS file (contained in the wisp\config directory),
change pl=66 to pl=80.
A holdover from our prior release is the suppression of leading zeroes in date fields.
This means that a date of 01 02 00 could display as _1 _2 __ (where the _ indicates a blank value).
As we are modifying programs (either for fixes or for other reasons), we will be changing the date
fields to display the leading zeroes. If you do not see the 00 (for the year 2000), please know that
the computer system does read the screen correctly.
The vutil32 utility can be used to examine files and rebuild corrupted
files.
This program should be located in the dyn/acucbl42/acugt/bin directory.
For ease of use, we suggest you copy this program into your production data directories,
such as dyn/dyfa53li and dyn/dypr2000.
The utility syntax is: vutil -function [files]
where -function can be one of the following:
- -info
- This function returns basic information about the files.
see example
- -check
- This function tests a file and returns a status code about each file.
see example
- -zero
- This function is used to clear non-zero user counts
see example
- -rebuild
- This option is used to rebuild an index file. A file should be rebuilt
if it is corrupted or contains a large number of deleted records.
see example
Examples
vutil32 -info *.* > info.out
This command can be used to list information about all files in your data directory and
to put that information in the file info.out for later review.
vutil32 -check *.*
This command is used to test all files in your data directory. The following information could be listed
for files tested:
- Non-zero user count
- This means that either there are users currently accessing the file
or a user who was accessing this file had an abnormal termination of their program.
You can use the vutil32 -zero option to clear when all users are
out of the system.
- File is broken
- This file needs to be rebuilt!
- Incorrect file type
- This file is a non-indexed sequential file and can be ignored
- File is locked
- If all users are out of the system and this message still appears by the file,
we suggest you reboot the server containing this data.
vutil32 -zero *.*
This command is used to reset the user counts to zero.
vutil32 -rebuild -3 [file]
This command is used to rebuild a file if it is corrupted or contains a large number of deleted records.
It is important that you specify the -3 option after -rebuild. The -3 option tells vutil32
to rebuild this file in vision 3 format.
*AcuCobol is a registered trademark of AcuCorp, Inc.
Error Code 30 [33]
This error occurs when the system is unable to gain access to a file after a certain amount of time.
We suggest you do the following to alleviate this problem
- Run the vutil32 utility to test the integrity of your data files.
Rebuild any files that seem to have problems.
- Reboot the server
other ideas include:
- Add the configuration variable "V-LOCK-METHOD" to "1" in the acufig53 file contained
under the dyn/wisp/config directory. This option selects the locking method used by AcuCobol to
control simultaneous access to indexed files. If you want additional information
regarding this option, please contact us at Dynalogic.
- Add the configuration variable "LOCKING-RETRIES" to 32767 in the acufig53 file contained
under the dyn/wisp/config directory. If you want additional information
regarding this option, please contact us at Dynalogic.
Error 94 [20] indicates the system is having trouble accessing this file. We have found that
this occurs when a virus checker has been activated on the server containing the data.
Please check to see whether new system options have just been implemented.
Often prior to this error occurring you will notice a slowdown of the system and will possibly
have gotten one or more Error 98s.
Error 98 indicates the index file is corrupt. The file should be rebuilt using the
vutil32 utility.
Files can become corrupted if a process dies while a user is in the middle of a record update.
Dynalogic has recommended that client installations use the AcuCobol Vision 3 format for data files.
You can see which Vision format used for your data files by running the
vutil32 -info utility.
Files showing a VIX extension indicate the data file is in the AcuCobol Vision 4 format.
Files in this format really contain two files with the same name. The first, without the VIX extension,
contains the data. The second file, with the extension, contains the indexing structure.
If you have vision 4 data files, please contact support@dynalogicinc.com
to determine what (if anything) should be done.
This error message is given when the object file of the program called has been transferred to your system as
ASCII instead of BINARY. Please contact your support person at Dynalogic to receive an updated version of the
program.
You can also obtain technical support by:
calling us at (206) 533-1050
e-mail us at support@dynalogicinc.com
Questions regarding this web site should be directed to
webmaster@dynalogicinc.com
Copyright © 1999-2006 Dynalogic, Inc. All rights reserved.
January 30, 2006.
