TimeWise Error Messages
 

For answers to frequently asked questions about TimeWise, go to the TimeWise Frequently Asked Questions page.

Tried everything and still need our help? Consider a TimeWise support plan.



Jump to error messages beginning with:A B C D E F G H I J K L M N O P Q R S T U V W X Y Z other

General notes on error messages

Some error messages appear centered in a box with the choice to Cancel or Ignore. After you have read the message, choose Cancel to leave TimeWise, unless instructed by this documentation or our technical support staff to choose Ignore. If you choose Ignore, you are essentially telling TimeWise to continue even though something is wrong... kind of like running a red light: you may get away unharmed, or you could get really damage something.

If you do not find the error message you seek here, look in the Error Messages--Additional help topic.

Sometimes TimeWise can fix a problem automatically, in which you also have the choice to Retry, so you can attempt to continue from where you were.

Whenever you wish to turn off your computer, always leave TimeWise first, if possible. By turning off your computer with TimeWise running, you risk damaging your information files.

Some error messages originate from Windows or the Mac OS. For these, you can consult your operating system documentation for additional information.
 

[top]



Abort, Retry, Fail

See Other Error Messages.
 

Arial Bold Font Not Available

The Arial Bold TrueType font is not available. Many TimeWise screens will not display properly (for example, the opening screen may have words extending beyond the right edge of its rectangle), and Position Is Off The Screen error messages may result, due to your computer substituting a larger font for missing Arial fonts.

In Windows 3.x, click Fonts in the Control Panel group, and Add the fonts Arial and Arial Bold if they are not already installed. If the fonts do appear in the list, they may be damaged and must be reinstalled from the Windows distribution disks.

In Windows 95, 98, NT or ME, use the Fonts Control Panel to add the fonts if they are not already installed. If they are already installed, try removing and reinstalling them. If you wish to try to remove and reinstall the Arial fonts, and you cannot delete them through the Control Panel, instead edit the registry REG.DAT file to remove them (after carefully backing up your Registry first... if you are not familiar with editing the Registry then have an expert do this for you instead).

In Windows 2000, or XP, simply drag the fonts into the Fonts folder (which is found in the Windows folder (Windows XP) or the Winnt folder (Windows 2000).

On a Macintosh, reinstall TimeWise. For detailed instructions on installing fonts, refer to your operating system documentation.

[top]



Bad command or filename

This suggests Windows cannot find a program file.

If launching TimeWise from a Command Prompt or batch file, it is possible that you have misspelled a command or are not in the current drive. Try typing these commands from a command prompt:

C:     (assumes TimeWise is on drive C)
CD\TIMEWISE  (assumes TimeWise is installed in directory TIMEWISE)

and press Enter at the end of each line. Then try to launch TimeWise again.

If this does not work, TimeWise is likely not installed properly on your hard disk. Run INSTALL again.

If this message appears while using the Backup command, your computer's COMSPEC setting may not be configured properly. Consult your Windows documentation for more information.

[top]



Cannot create file

The operating system has returned an error to TimeWise indicating that the new file cannot be created. The inability to create a new file is usually the result of a full disk or folder, entry of an invalid file name, or not having the proper requirements needed to access the folder which is to contain the file.
 

Cannot locate desired version of FoxPro

TimeWise for Windows cannot find the file FOXW2600.ESL. Re-install TimeWise to fix this problem.

These files are normally in the directory in which you installed TimeWise. On a network, the network administrator may have relocated these files to another directory or local hard drive, indicating in the CONFIG.FP file (CONFIG.FPW file in TimeWise for Windows, CONFIG.FPM in TimeWise for Macintosh) where TimeWise is to find them.
 

Cannot open configuration file

TimeWise found its CONFIG.FPW (Windows) or CONFIG.FPM (Macintosh) file but did not have the proper rights to open it.
 

Cannot open file

The operating system has returned an error to TimeWise indicating that the file cannot be opened. The inability to open a file is usually the result of attempting to open a file which does not exist, entry of an invalid file name, or not having the proper permission needed to access the file.
 

Cannot locate FoxPro support library

On Windows 95, 98, ME, or NT, if launching from a shortcut, check that the Shortcut section of the Properties icon has Target and Start In set to the drive and directory that contains TimeWise (or, in an advanced setup, the local drive that contains the FOXW260A.ESL file).
 

Cannot locate selected database

This message suggests that an information file is missing or corrupt. You can repair database files with a utility program such as Norton Disk Doctor or PC Tools' FILEFIX. If that does not help, restore from your most recent Backup Set using Backup (from the Tools menu) or TWUNZIP, thus losing all activity since then. Then restart TimeWise and try the same operation again.

If you are considering restoring only one file (since only one file has trouble), don't! Information files are synchronized: if you restore only one file, databases may no longer correspond, which can lead to a worse situation.
 

Cannot open file

This message suggests that a program file has disappeared or become so damaged that TimeWise cannot recognize it. Back up your information using Backup (from the Tools menu) or TWZIP and then run INSTALL to reinstall TimeWise. Running INSTALL does not affect any existing information, unless you specifically instruct INSTALL to replace it.

On a NetWare network, this can be caused by SHARE.EXE being loaded in the AUTOEXEC.BAT file. Try removing SHARE.EXE and see if the problem goes away. If that solves the problem, and you need SHARE for some other program, try increasing the value of SHARE's L and F parameters.
 

Cannot open file \TIMEWISE\SBT\...

This message suggests TimeWise is having trouble locating or using an SBT file. Reindex Files in SBT.

Cannot update the cursor 

This message indicates that some information files are wrongly marked read only. Make sure that all files that end in .dbf and .dbt are marked read only. To be thorough, the following series of commands can be typed at a Command Prompt to make sure that only those files that should be marked as read only are marked as such, and this is only necessary on a multiuser installation: on a single user installation, you can more conveniently uncheck the Read Only attribute for all files.

ATTRIB -R C:\TIMEWISE\*.* (assumes C:\TIMEWISE)
ATTRIB +R C:\TIMEWISE\*.EXE
ATTRIB +R C:\TIMEWISE\*.ES?
ATTRIB +R C:\TIMEWISE\*.BAT
ATTRIB +R C:\TIMEWISE\*.COM
ATTRIB +R C:\TIMEWISE\CONFIG.FP?
ATTRIB +R C:\TIMEWISE\*.BMP
ATTRIB +R C:\TIMEWISE\*.LB?
ATTRIB +R C:\TIMEWISE\*.DLL
ATTRIB +R C:\TIMEWISE\TWHELP.*
ATTRIB +R C:\TIMEWISE\TWUSER.*

 

Cannot write to a read only file

If this message occurs when adding or updating client profiles in an installation that is linked to SBT, this indicates that the user does not have access rights to the SBT folder in the TimeWise folder.

Can't find ESO file

A file with the extension ESO is not available. Reinstall TimeWise.
 

COLORSET RESOURCE NOT FOUND

This error suggests that the file TWUSER.DBF is not available. Re-install TimeWise to fix this problem.

This error can occur if the TWUSER.DBF does not have a read only attribute.

To fix the problem in Windows or DOS, type this command at a DOS prompt:
ATTRIB +R C:\TIMEWISE\TWUSER.DBF
(This example assumes that TimeWise is in the directory TIMEWISE on drive C and that the Windows\Command folder is in the directory path.)

To fix this problem on a Macintosh network, select TWUSER.DBF in the Finder, select Get Info and check the Locked checkbox.

It is possible on a network that a network administrator will have relocated the TWUSER.DBF for a particular user by setting up a separate CONFIG.FP file (CONFIG.FPW for TimeWise for Windows, CONFIG.FPM in TimeWise for Macintosh) for that user. For more details on this, consult the Speeding Up TimeWise help topic.
 

Could not allocate segment

Refer to Not Enough Memory.

[top]



Data type mismatch

You have found a bug in our software. Please contact David Berman Developments Technical Support.
 

Database is not ordered
Database operation invalid while indexing

Choose Ignore, and then immediately perform First Aid (from the Tools menu, launch First Aid from the Windows or Macintosh desktop, or type FIRSTAID at a Command Prompt).
 

Disk full

If this message appears, you are out of room on your hard disk. TimeWise was trying to write some information and had nowhere to put it. Clear at least one megabyte of additional space on your hard disk and start TimeWise again.

 

Divide by zero error

This message appears when launching TimeWise for Windows version 6 release B11 or earlier on some brands of Pentium processors of speeds 333MHz or faster. To fix the problem, update TimeWise for Windows to version 6 release B12 or greater. If you are running TimeWise for Windows version 5 or earlier, you must upgrade to version 6. If you are running version 6, you can get a free updater to the most recent release at our patch page.
 

Division by 0

You have found a bug in TimeWise. Please contact David Berman Developments Technical Support.

[top]



End of file encountered

This usually indicates a corrupt database file. Restore from your latest backup.
 

Error in label field definition

An invalid expression was encountered in a LABEL file (.LBL).
 

[top]



File access denied

This message indicates that a file has a "read only" attribute (on a Macintosh, this is instead known as "locked") that should not. On a network, this message appears if more than one user attempt to use a single user version of TimeWise simultaneously (you must have a multiuser version of TimeWise to concurrently use the program on more than one network station.)
 

File does not exist

If you see this message under Windows 95, 98, ME, or NT followed by the message "You cannot proceed TimeWise cannot find the file NET2.TXT" on a networked installation this likely indicates an illegal use of UNC. If using Windows 95, 98, ME, or NT built-in peer-to-peer networking, you cannot always directly reference the networked drives using UNC (universal naming convention). For example, \\server\c\TimeWise\timeww.exe will not work as a pointer where server is the name of the computer and c is the name of the drive where TimeWise shared files are located. Instead, your network administrator must map the shared drive to a letter and then use the drive letter to access the shared directory. In this example, you would map \\server\c to local drive E: and then specify E:\TimeWise\timeww.exe as the location of TimeWise in the TimeWise icon.
 
 

File in use by another

This message suggests you are trying to use a single-user TimeWise license in a multiuser environment, possibly due to upgrading a multiuser license with a single-user upgrade. This can also occur if running on a computer where SHARE is loaded when it should not be (if it must be loaded, try setting the F parameter to at least 5120 and the L parameter to at least 500).
 

File ["<file>"] does not exist

The file you have specified does not exist.
 

File is in use by another

An attempt was made to use a file which is being used by another user in a multiuser system.
 

File is in use

An attempt was made to use a file which is currently open.
 

File is read only

An attempt was made to write to a read only file (or "locked" on Macintosh).
 

File not open

An attempt was made to read from or write to a file which is not currently open.
 

File read error

An error was returned by the operating system while TimeWise was attempting to read a file.
 

File write error

An error was returned by the operating system while TimeWise was attempting to write to a file. Most often, this error is the result of an attempt to write to a write-protected disk.
 

FOXUSER file is invalid

Your TWUSER.DBF or TWUSER.FPT file has been corrupted. Reinstall TimeWise.

[top]



General Protection Fault

Please refer to the General Protection Fault help topic in the context-sensitive help from the TimeWise Help menu for more information on this message.
 

[top]



Index does not match database file. Recreate Index.
Index file does not match database
Index tag not found

Choose Ignore, and then immediately perform First Aid (from the Tools menu, launch First Aid from the Windows or Macintosh desktop, or type FIRSTAID at a Command Prompt).
 

Insufficient memory (TimeWise for Macintosh)

If you see this message, increase the memory allocation for TimeWise by selecting the "TimeWise" (or "TimeWise for PPC" if you are using a Power Macintosh) icon in the TimeWise:Resource folder, then select Get Info from the Finder File menu. Increase the Preferred Memory allocation in increments of 1000 K until the message stops appearing or you reach 9000 K.

If you reach 9000 K, and the message is still appearing, try these other remedies:

1. Open the Control Panel and select Monitors. Be sure the number of colors is set to 256 or 16. A setting greater than 256 colors can cause the "Insufficient memory" error message in TimeWise on some machines.

2. Be sure that enough memory is available to applications on your computer. Choose the "About this Macintosh" menu option to check the amount of memory used by the system software. If you're using a Power Macintosh, be sure to turn off Modern Memory Manager and restart the Macintosh. You may need to remove unneeded fonts, sounds, or extensions from the System and Extensions folders.

3. Turn on Virtual Memory. The Macintosh will use some of your free hard drive space as extra memory. Overall performance may decrease, but the additional memory may make it possible to run TimeWise. It may also be necessary to close other applications prior to running TimeWise for Macintosh.
 

Insufficient memory (TimeWise for Windows)

This error message originates from Windows: consult your operating system documentation for additional information.

Use the MEM command to learn how much RAM is available.

If you cannot launch TimeWise because of a lack of memory, and you need to back up TimeWise information, type these commands at a DOS prompt:
C:
CD\TIMEWISE
TWZIP  (assuming TimeWise is on hard disk C, directory TIMEWISE)

If the message appeared while Restoring, the Restore was not successful. To restore, place the last disk of the Backup Set in disk drive A and type
C:
CD\TIMEWISE
TWUNZIP (assuming TimeWise is on disk C, directory TIMEWISE)
  

Internal error: Too many characters in report

The total size of all the headings and expressions defined for the report in Design Memorized Report is too large.

 

Invalid directory

Try installing TimeWise in another directory or drive.
 

Invalid index number

Choose Ignore, and then immediately perform First Aid (from the Tools menu, launch First Aid from the Windows or Macintosh desktop, or type FIRSTAID at a Command Prompt).
 

Invalid keyboard macro file format

An attempt has been made to use a keyboard macro file with invalid data.
 

Invalid or missing EXE file

An EXE either is corrupted or there is not sufficient network rights to use it. Reinstall TimeWise (you can reinstall TimeWise over your existing data without losing any data...and the process will rewrite all your EXE files making sure they are all healthy).

If you get this message while trying to launch TimeWise on a network workstation, it is possible that TimeWise is having trouble resolving the UNC path to the file Timeww.exe on the server. Try mapping the TimeWise folder on the server as a drive letter on the workstation, then launching timeww.exe from there through that path. (for instance, you may end up with more success launching TimeWise as "H:\timeww.exe" or "H:\TimeWise\timeww.exe" rather than trying to launch it as "\\server\c:\TimeWise\timeww.exe").
 

Invalid path or file name

You've attempted to execute a TimeWise command that contains an invalid path or file name.
 

Invalid printer redirection

Refer to Printer Not Ready.
 

I/O operation failure

DOS or Windows is unable to perform a file or hardware operation.
 

It seems unlikely that it is really January 1, 1980, as reported by this computer. The most recent job was started on February 1, 2004. You may corrupt data if you use TimeWise with the wrong date!

This message indicates that TimeWise suspects the date that the computer is using is incorrect. If you agree that it is incorrect, refer to the problem discussion "TimeWise is suggesting ridiculous dates" in the Problems Without Error Messages help topic.

[top]



Macro not defined

An attempt has been made to play a macro that does not exist.
 

MEMO file is invalid/missing

This message indicates that an information file with the extension FPT or DBT has become corrupt, cannot be found or is missing. Restore from your most recent backup.

If restoring from a backup is undesirable, you may be able to fix a damage memo file by following this procedure:

First determine which file is involved. You can isolate which file is involved by using First Aid from the Tools menu to invoke the error message, and note which information file was being re-organized when the message appears.

"Re-organizing jobs" indicates the ASSIGN database.
"Re-organizing the archive" archive indicates the ARCHIVE database.
"Re-organizing client information" indicates the CLIENTS database.
"Re-organizing forms" indicates the FORM database.
"Re-organizing vendor information" indicates the VENDORS database.

Now, backup your TimeWise data before proceeding.

Then launch TimeTool™. In the window type these commands very carefully (this example assumes we are using ASSIGN...substitute the database name above as appropriate)
CLOSE ALL
SET DELE OFF
USE ASSIGN
COPY TO ASSIGNX
CLOSE ALL
COPY FILE ASSIGNX.DBF TO  ASSIGN.DBF
COPY FILE ASSIGNX.FPT TO  ASSIGN.FPT
DELETE FILE ASSIGNX.DBF
DELETE FILE ASSIGNX.FPT
QUIT

Then launch TimeWise again, and select First Aid. If the message does not appear during First Aid, then the file has been fixed.
 

Memory variable file is invalid

If this message appears when starting TimeWise or TimeTool™, it indicates corrupt TWUSER.* files. Choose Cancel, leave the program, then re-install TimeWise from your most recent distribution set.
 

Missing Expression

If this message appears when launching TimeWise, it likely indicates a damaged PREF.DBF file, especially if you had just been modifying that file using TimeTool™ to some advanced tinkering. A blank record in the PREF.DBF file could be the culprit...any record that does not exactly comply with what TimeWise expects will cause this message. If you do get such a message, carefully fix PREF.DBF if you are capable or go back to the backup version of the file you made before attempting to modify it.

If you are an advanced computer user and wish to attempt to avoid having to entirely restore from your last backup, consider this additional information. Since PREF.DBF contains your preferences, this file can typically be restored independently of other TimeWise files without causing any trouble (of course, this assumes that PREF.DBF is the only damaged file). You can selectively restore it from the backup made with the TimeWise for Windows Backup command by using PKUNZIP to restore just the PREF.DBF file from the TIMEWISE.ZIP file that the Backup command creates. Since you likely do not change your Preferences every day, there is a high likelihood that you can take this approach and not have lost any information. After restoring the one file, use the Preferences Wizard in TimeWise to walk through the Preferences and confirm that they look okay. If you do not have a backup of the file, you can attempt to hand-fix the PREF.DBF using TimeTool™, removing any obvious corruption while comparing the file's structure to the original PREF.DBF file that is located in the ORIGINAL folder of your TimeWise folder (on the Macintosh, the Original folder in the Resouce folder of your TimeWise folder).
 

Missing operand

An operator that requires two operands was used without the second operand, for example "? (13+4)/".
 

[top]



Network Delay

There are a number of different Network Delay messages. They are fully explained in the Networks help topic: select that topic, then search for the phrase Network Delay.
 

Network violation

This message appears when trying to run a multiuser version of TimeWise with network software that demands that certain TimeWise files have a read only (locked on Macintosh), shareable status. Achieve this with command prompt ATTRIB command. All other files should be read/write, shareable. Type these commands at a Command Prompt:

ATTRIB -R C:\TIMEWISE\*.* (assumes C:\TIMEWISE)
ATTRIB +R C:\TIMEWISE\*.EXE
ATTRIB +R C:\TIMEWISE\*.ES?
ATTRIB +R C:\TIMEWISE\*.BAT
ATTRIB +R C:\TIMEWISE\*.COM
ATTRIB +R C:\TIMEWISE\CONFIG.FP?
ATTRIB +R C:\TIMEWISE\*.BMP
ATTRIB +R C:\TIMEWISE\*.LB?
ATTRIB +R C:\TIMEWISE\TWHELP.*
ATTRIB +R C:\TIMEWISE\TWUSER.*

If the message persists, consult your operating system documentation for more information.
 

No database in USE

A database was not in use at the time TimeWise attempted to use one. Call TimeWise Technical Support.
 

No parameter statement found

This error occurs if you try to launch TimeWise with an illegal parameter on the command line. For example, if you type TIMEWISE BANANA at a Command Prompt or have set such parameters on the Cmd Line option of a Windows icon, the parameter BANANA means nothing to TimeWise.
 

Not a character expression

This error appearing when launching TimeWise indicates a corrupt PREF.DBF file. Restore from your most recent backup, or just of this file (this file can be restored without affecting any other TimeWise files...it contains almost all of your preferences, so restoring an older version will mean that you will have simply lost any changes to preferences that have occurred since the file was backed up).
 

Not enough disk space for G:\86569984.TMP

This message suggests that you have run out of space on the drive where TimeWise stores temporary files: usually the drive where TimeWise is installed. If you modified the CONFIG.FPW file (TimeWise for Windows) or CONFIG.FPM file (TimeWise for Macintosh) to reassign where temporary files reside, it could refer to a local hard drive or RAM drive. Choose Cancel and free some space.
  

Not enough memory to USE DATABASE

Refer to Insufficient Memory.
 

Not a database file

The file that TimeWise is attempting to use contains an improper header, probably indicating  file corruption. Restore from your most recent Backup Set.
 

Not a numeric expression

An attempt was made to use the SUM command on a non-numeric field.
 

Not enough disk space for "<file name>"

The operating system has returned an error to TimeWise indicating that there is no room on the disk to contain the data from the latest WRITE command. This is also erroneously returned under certain versions of Novell when you try to extend a file that has no owner.
 

[top]



One User in Two Places At Once

On a network, TimeWise does not allow the same user logged onto more than one session at a time. If a session ends unexpectedly (such as due to turning off a computer without leaving TimeWise first), the record of logged on users becomes inaccurate. Correct this with the First Aid command.
 

Open error in XXXXXXXXXX:XXXXXXXXXXXXXXX; YYYYYYYY.YYY DOS nn

If this message (recognizable by the letters DOS followed by two digits at the extreme right) occurs predictably, then the value of nn suggests the nature of the problem:

3 Cannot find a directory YYYYYYY (such as INVOICE) that should exist
32 Sharing violation (someone else is using the file you have requested)
33 Lock violation (someone else is using the file record you have requested)
36 Sharing buffer overflow
50 Network request not supported
51 Remote computer not listening
52 Duplicate name on network
53 Network name not found
54 Network busy
56 Network BIOS command list exceeded
57 Network adapter hardware error
58 Incorrect response from network
59 Unexpected network error
60 Incompatible remote adapter
61 Print queue full
62 Not enough space for print file
63 Print file deleted (not enough space)
64 Network name deleted
65 Access denied to the file YYYYYYYY.YYY
66 Network device type incorrect
67 Network name not found
68 Network name limit exceeded
69 Network BIOS session limit exceeded
70 Temporarily paused
71 Network request not accepted
72 Print or disk redirection paused
88 Network device fault
 

OS/x86: Cannot find operating system kernel

On a network, this suggests that the file FOXD250A.ESO or FOXDX25A.ESO is not marked as read only, as it should be.

[top]



Position Is Off The Screen

This message can be caused by a TrueType font that TimeWise assumes is present in the operating system not being available, typically Arial or Arial Bold. If so, the computer substitutes another font for the missing font, and if the missing font is larger there is not enough room in the window to display the message TimeWise is attempting to display, thus causing the error. See the message Arial Bold font not available above for additional details.

In Windows, another possible cause of this message is a problem with the video driver installed on your computer. To test for this, try resetting the video driver to standard VGA and see if the message goes away. If the message goes away, the problem is related to the video driver. Check with the manufacturer to see if an updated driver is available...this may remedy the problem. If not, contact TimeWise Technical Support.
 

Printer not ready

This error can occur anytime in the printing process when TimeWise is unable to send information to the printer.

This can be due to the printer being off, out of paper, not on-line or not properly connected. A problem with a print spooling program that is running concurrently can cause this message as well.

If this message appears regarding a network printer, read the section Printing On A Network in the Appendix B, Specific Installations.

The printer device specified is currently not accessible or the printer is timing out. The TIME parameter in the CONFIG.FPW (TimeWise for Windows) or CONFIG.FPM (TimeWise for Macintosh) file may need to be increased. If this occurs while an invoice or estimate is being drafted, the INVOICE folder of the TimeWise folder is likely missing.

TimeWise offers to Retry. If you choose Retry, TimeWise tries to send information to the printer. If you choose Ignore, the entire print operation is cancelled and you continue from where you were before making the request.

If the message appears while TimeWise is drafting an invoice or estimate (not printing, but drafting), it suggests that the INVOICE directory that should be in your TimeWise directory cannot be found.

If the message appears while TimeWise is in the midst of creating an editable report, it suggests a technical problem with your hard disk. The printer is fine but the hard disk requires servicing.
 

Program too large

Refer to Run/! Command Failed.
 

Program too large

The program which TimeWise is attempting to load will not fit into memory. The largest program TimeWise can load is one containing 65,000 bytes.
 

[top]



Record is not in index

A key field of the database in use has been modified without the index having been active. To correct this, perform First Aid.
 

Record is out of range

The record which you are attempting to access is beyond the actual number of records contained in the current database. This could indicate a corrupt information file. Perform First Aid. If that doesn't alleviate the problem, reinstall TimeWise.
 

Recursive macro definition

You have created a macro which breaks a rule regarding referring to other macros.
 

Re-organizing...

This is not necessarily a problem. It is caused by either TimeWise detecting a corrupt index file or TimeWise not finding an index file that should exist.

When this happens, TimeWise displays the message and proceeds to recreate the index or indexes. You need not intervene: TimeWise continues after recreating the index.

The first time you launch TimeWise after running INSTALL, this message appears as TimeWise rebuilds index files.

Note that this does not take care of all the possible problems associated with corrupt index files. A corrupt index file may not cause an error message, though information files will not act as expected. Performing First Aid (from the Tools menu) fixes all corrupted index files.
 

Report file invalid

A report description contains an error.
 
 

Resource Manager internal consistency error

This indicates a possible memory conflict. If using TimeWise for Windows or TimeSave for Windows, try loading Windows with the parameter /D:SVXF on the WIN command line. If your autoexec.bat file does not have a WIN line already, then add the line WIN /D:SVXF to your autoexec.bat file. If you do not have an autoexec.bat file already then create a text file called autoexec.bat and put this one line in it and put in the root directory of drive C.
 

Run/! command failed

This error occurs when TimeWise cannot run an external program required to perform the desired activity. Besides TimeWise having not performed the requested command, everything else is OK.

This message suggests a shortage of available memory. It is likely that other programs loaded into memory before running TimeWise are using so much RAM that TimeWise does not have enough. Re-start your computer and try again.

Another possible memory hog is the CONFIG.SYS file in the root directory of the hard disk running Windows 3.x. It likely contains a line that reads BUFFERS = 8 or another number. If this number is high, it consumes more conventional memory. Therefore, a potential solution is to reduce this number.

Another possible cause is the environment variable COMSPEC. If it is not set properly, TimeWise cannot carry out command prompt commands properly, as it cannot find and load COMMAND.COM .

If this error occurs during Backup, TimeWise does not switch from Backup Set A to B or vice versa since the Backup was unsuccessful.
 

top]



Screen file invalid

Re-install TimeWise.
 

Sector not found

There is a physical problem in using your hard disk or floppy disk drive. Consult your computer dealer for assistance. TimeWise offers to Retry. If you choose Retry, TimeWise tries again, continuing operation from where you were when the message appeared. If you choose Cancel, TimeWise forces you to leave the program. Do not choose Ignore, as information could become damaged.
 

Sharing violation reading Drive C

This message suggests that a multiuser edition of TimeWise is not installed properly. The trial edition is not a multiuser edition.

On a peer-to-peer network, such as LANtastic or Windows For Workgroups, this message suggests that the Network Install option was not selected during installation of TimeWise. If installing on a server drive, you must choose Network Install, even if you do not intend to use TimeWise on more than one station. Also, make sure SHARE is installed properly.

On a server-based network, such as NetWare, this message suggests more than one station using TimeWise when files that should have shareable attributes do not. On NetWare, use the FLAG command with an S parameter to achieve this. For example:
FLAG F:\TIMEWISE\*.* S

Make the directory shareable with the FLAGDIR command:
FLAGDIR F:\TIMEWISE S

It can also be caused by SHARE being loaded when it should not be. Try removing SHARE. If that proves to be the problem, and you must have SHARE loaded, try increasing the L and F parameters of SHARE.

One other possible cause of this message is that if you are using Microsoft FoxPro or another program that has been compiled with Microsoft FoxPro, and because of this you have a FOXCFG environment variable set that is pointing to another CONFIG.FPW file specific to the other program, TimeWise will be looking at this CONFIG.FPW file rather than it's own. This can cause a number of problems. You must find a way to have each program access it's own CONFIG.FPW file... if it is not obvious to you how to achieve this, please contact our Technical Support.
 

Since XXXXXX cannot be found in ARCUST01.DBF, SBT's records cannot be updated

This message shows TimeWise cannot find an SBT customer associated with the TimeWise client. If you do not see this message and TimeWise offers a printed report during Open Client Profile, either the ARCUST01.DBF file in the SBT directory is missing (a problem worth investigating) or the Bookkeeper is not set to SBT in Financial Preferences.
 

Someone Else Is Using TimeWise

According to the program's records, someone else on the network is still using TimeWise, which is not allowed when using the Backup command. If this is inaccurate, perform First Aid to correct the user record.
 

Syntax Error

This message can indicate a corrupt PREF.DBF file, which is the file that contains your preferences, especially if it appears upon launching TimeWise.  Restore from your most recent backup.

If you are an advanced computer user and wish to attempt to avoid having to entirely restore from your most recent backup, consider this additional information. Since PREF.DBF contains your preferences, this file can typically be restored independently of other TimeWise files without causing any trouble (of course, this assumes that PREF.DBF is the only damaged file). You can selectively restore it from a backup made with the TimeWise for Windows Backup command by using PKUNZIP to restore just the PREF.DBF file from the TIMEWISE.ZIP file that the Backup command creates. Since you likely do not change your Preferences every day, there is a high likelihood that you can take this approach and not have lost any information. After restoring the one file, use the Preferences Wizard in TimeWise to walk through the Preferences and confirm that they look okay. If you do not have a backup of the file, you can attempt to hand-fix the PREF.DBF using TimeTool™, removing any obvious corruption while comparing the file's structure to the original PREF.DBF file that is located in the ORIGINAL folder of your TimeWise folder (on the Macintosh, the Original folder in the Resouce folder of your TimeWise folder). For diagnostic purposes, you can choose to Ignore the message, and see how many additional Syntax Errors result...each one indicates a corrupt record in PREF.DBF.
 

System integrity error

If this message appears while running TimeWise from Windows, it indicates a shortage of conventional RAM, or that the F parameter of SHARE is not large enough.
 

System resource exhausted

This message can appear when the operating system SHARE command is run when not on a network. Restart the machine without running SHARE, if feasible. If it is important to load SHARE for the benefit of other software, configure TimeWise as if you are using a multiuser edition.

If this message appears when choosing Help and TimeWise is situated in a directory that is not directly off the root directory, try moving TimeWise to a directory directly off the root directory.
 

[top]



The application has quit due to an error type 11

There are several possible reasons why you would see this error messages:

·A path name that exceeds the 256-character limit is being used. Move the TimeWise folder to a location that will result in a shorter path or rename the folder with a shorter name.

·The 'Setting of selected monitor' in the Monitors Control Panel is set to 'Millions' or 'Thousands' of colors. Change the number of colors to 256 or 16.

 

The application has quit due to an error type -192

This message indicates that the PowerPC version of TimeWise is being run on a 68K Macintosh. To remedy this, drag the TimeWise For PPC file from the TimeWise:Resources folder into the Trash and empty the Trash. If TimeWise will still not launch, run the Install program again to re-install the proper edition of TimeWise on the 68K Macintosh (Install automatically detects that the Macintosh is a 68K machine and installs the correct edition.)

It is possible that an original 68K Macintosh may have a PowerPC board installed in it. If Install is run while the PPC board is active, the PPC version of TimeWise could be undesirably installed. Therefore, if you have a PowerPC board installed and there is a possibility it will be disabled at some point, deactivate it before running Install so that the 68K edition of TimeWise will be installed.FoxPro.
 

This beta version of TimeWise has expired

This message indicates that you are using a beta version that had an expiry date. To remedy this problem, download the latest patch for your plat from our patch page.
  

Too many files open

On NetWare, ensure that the SHELL.CFG or NET.CFG is set up and located as described in Chapter 2, Installation, and try using VLM drivers instead of NLM drivers.
 

Too many READs in effect

You may have found a bug in our software. Please contact TimeWise Technical Support.
 

Too many variables open

Ensure all copies of CONFIG.FPW, or CONFIG.FPM include a setting of at least MVCOUNT=610..
 

Total label width exceeds maximum allowable size

You may have found a bug in our software. Please contact TimeWise Technical Support.
 

[top]



Unable to create temporary work file(s)

This is caused by a full folder or a permissions problem concerning access to the temporary files folder.
 

Unable to locate desired version

The version of TimeWise requested is not on the designated path specified in CONFIG.FPW (TimeWise for Windows) or CONFIG.FPM (TimeWise for Macintosh).
 

Unable to locate FoxPro support library

This message indicates that the file FOXW2600.ESL is missing. Reinstall TimeWise for Windows.
 

Unrecoverable error in line nnn

This message suggests an anomaly in the INSTALL program. Please contact us.
 

Use of transgressed handle

This message suggests a hardware failure of some sort.
 

[top]



Variable ["<variable>"] not found

The specified variable could not be found.
 

Variable NEXTASSIGN not found

Basic:

This message indicates that the file STUDIO.DBF is damaged or missing.
First, make a backup of your current TimeWise files before proceeding.
If you are using TimeWise for Windows, use the Restore option from the TimeWise Backup command (on the Tools menu) to restore your data from your most recent backup.
If you are using TimeWise for Macintosh, restore the file STUDIO.DBF from your most recent backup, overwriting the STUDIO.DBF file in your TimeWise Resource folder.

Advanced:

If you'd prefer to just restore this one file from a backup (so that you don't have to lose other data accumulated since the last time you backed up), this is feasible, however STUDIO.DBF contains certain counters which could be out of sync with the rest of your data. Therefore, if you choose this route, you may have to follow the instructions below to modify STUDIO.DBF by hand (or you can hire us to do it for you).

If you are using the Backup command in TimeWise for Windows, it yields a file called TIMEWISE.ZIP, which is a standard ZIP file: you can use the PKUNZIP utility shipped with TimeWise or any other Zip utility (such as WinZip) to restore just the one file from your last Backup Set. Here is how you would accomplish that using PKUNZIP: Put the first (and possibly only) disk of Backup Set A in the floppy disk drive, and then at a Command Prompt type
C:\TIMEWISE\PKUNZIP A:\TIMEWISE STUDIO.DBF
(This example assumes that TimeWise is located in C:\TIMEWISE and that the Backup Set is on floppy drive A.)

Once you have isolated the STUDIO.DBF file from your most recent backup, read on to see if you have to hand-modify it...

STUDIO.DBF contains counters, so it is possible that since you restored from an earlier version of STUDIO.DBF that these counters will now be out of date.

You can correct these counters through TimeWise, or by using TimeTool™. To launch TimeTool™, click the TimeTool™ icon in your TimeWise folder. (in fact, if you cannot locate a recent backup containing STUDIO.DBF, you can probably use TimeTool™ to correct a current damaged copy of the file).


These are the counters in STUDIO.DBF:

Next Job Number
You can reset it to the proper number using the Next Job Number command from the Tools menu.

Or you can set it in TimeTool™ by typing these commands:
RESTORE FROM C:\TIMEWISE\STUDIO.DBF
NEXTASSIGN=1000
SAVE TO C:\TIMEWISE\STUDIO.DBF

(This example assume TimeWise is located in C:\TIMEWISE and the Next Job Number should be 1000.)


Next Purchase Order Number
You can reset it to the correct number by simply specifying the correct number the next time you do a purchase order.

Or you can set it in TimeTool™ by typing these commands:
RESTORE FROM C:\TIMEWISE\STUDIO.DBF
NEXTORDER="1234-5678"
SAVE TO C:\TIMEWISE\STUDIO.DBF


Other Counters
The remaining counters will take care of themselves. Thus you only need concern yourself with them if you are using TimeTool™ to mend a damaged STUDIO.DBF. If so, type these TimeTool™ commands to ensure that the remaining counters are fixed if they were damaged.

RESTORE FROM C:\TIMEWISE\STUDIO.DBF
NEXTINVOIC=2
NEXTBACKUP="A"
NEXT_DATE={01/01/98}
NEXTBACKDA={01/01/98}
SAVE TO C:\TIMEWISE\STUDIO.DBF

[top]



WATCOM Win 386 Read error
 

If you get a WATCOM error when launching TimeWise for Windows, make sure that your TimeWise folder does not have a name that is longer than 8 characters (by default, the TimeWise folder is called "TimeWise", however you may have chosen a longer name during installation).
 

If that does not solve the problem....

In your the directory that contains TimeWise, you will find a text file called CONFIG.FPW. Using any text editor change the MEMLIMIT line to read:

MEMLIMIT      = 50,2048,8192

If your network administrator has set up separate CONFIG.FPW files for each user, you will want to make the change to each one.

This line sets how much RAM is available to TimeWise...the second number is the minimum RAM TimeWise takes while the third is the maximum. If the problem persists, increase the second and third numbers in increments of 1024, being careful not to exceed the amount of available RAM in your computer.
 

If the problem still persists, then please try the following:

Try starting Windows with WIN /D:XVSF.  (In Windows 95, add a C:\AUTOEXEC.BAT file if one does not already exist and add this line as the
last line of the AUTOEXEC.BAT file).

The X in the /D:XVSF option excludes the upper memory area and is equivalent to placing the command EMMExclude=A000-EFFF in the SYSTEM.INI file.  If the error does not occur anymore, the problem is due to a conflict in the upper memory area. Refer to the Getting Started with Microsoft Windows manual for more information on using EMMExclude.

The V option gives the hard drive, rather than Windows 386 Enhanced mode, control over how hard disk interrupts are processed. The S option makes the System ROM Break Point=False. The F option turns 32-Bit Disk Access (FastDisk) off.
 

[top]



You are about to start job or estimate number 12345 and yet the last one started was 12347. If this doesn't make sense, ASSIGN.DBF may be corrupt. If so, answer no and restore from your most recent backup. Do you wish to start number 12348 instead?

This message indicates that the suggested number for the new job or estimate does not follow sequentially after the last job number started. This is normal if you have just changed the next job number through the Next Number command (from the Setup menu). If this condition is a surprise, then the file ASSIGN.DBF is probably damaged and you will likely have to restore from your last Backup Set. If you would like to attempt to fix the database with some other computer program, the file in question is ASSIGN.DBF.

If this is inaccurate, then it can indicate a corrupt database or something strange we've never seen before.
 

You cannot proceed because TimeWise cannot open the ASSNTIME.DBF file.  You cannot proceed until all other users leave TimeWise or TimeSave.

This message typically appears on a network, when someone else is using a TimeWise feature that must have complete control over a certain file (which is pretty rare). It can also occur after a network crash on any version of TimeWise where the file locking on the network server wrongly is still reporting the file as locked or read-only.
 

You cannot proceed because TimeWise cannot open the ASSIGN.DBF file. The file is in use by another user, corrupt, or accidentally read-only.

If a message like this one appears when trying to run a multiuser version of TimeWise for the first time or after a network upgrade, try this alternate installation method:

1. Install to a local hard drive on the network using the Install program.

2. Create the server directory or folder you wish to hold TimeWise.

3. Copy all files from the local hard drive to the new server directory or folder. Be sure to include all subdirectories or subfolders.

4. On a server-based network operating system, such as NetWare, all files must be marked shareable. Use the commands specific to your network to achieve this.

On NetWare, use the FLAG command with an S parameter. For example,

FLAG F:\TIMEWISE\*.* S

Make the directory or folder shareable with the FLAGDIR command:

FLAGDIR F:\TIMEWISE S

5. If using LANtastic 6, set Share Locks to 70 times the maximum number of simultaneous TimeWise and TimeSave users expected. This command is found in the Internal Share section of Server Startup Parameters in NET_MGR.

6. These files must have a read only status (or locked on a Macintosh):
*.EXE (Windows only)
*.ES?
*.BAT (Windows only)
*.COM (Windows only)
CONFIG.FPM (Macintosh only)
CONFIG.FPW (Windows only)
*.FR?
*.BMP
*.LB?
*.DLL (Windows only)
TWHELP.*
TWUSER.*

Windows: Set the read only attribute with the Properties command in Windows or the ATTRIB +R command at a Command Prompt. All other files should be read/write. You can achieve this by launching READONLY.BAT from your TimeWise folder.

Macintosh: Use Get Info to Lock the files on the network volume.

7. Delete the files from the local folder or directory.

8. Ensure all network users that will use TimeWise have rights to the folders or directories in which TimeWise is installed and all its folders or  subdirectories. If unsure of whether rights are causing a problem, have the user log in as the network supervisor and see if the problem is alleviated.
 

You cannot proceed because the NET.TXT file is missing.

This indicates that TimeWise cannot find a file it needs. If the file is a system file, you must reinstall TimeWise. If the file is an information file, restore from your most recent Backup Set. If the file is NET.TXT, TimeWise likely cannot find any files, because it is somehow looking in the wrong directory. Check that the file is present in the TimeWise directory using Windows Explorer, the Macintosh Finder, or Command Prompt commands. If it is, try installing TimeWise in another directory or drive.
 

Your TimeWise trial license has expired. Call David Berman Developments for your Unlocking Key.

This message appears after your 30 day trial license has expired. Contact David Berman Developments (800-665-1809) or sales@timewise.net or your authorized TimeWise reseller to purchase an Unlocking Key for a full license to TimeWise.
 



Other Windows Error Messages or Problems

Freezes

If your Windows computer often freezes when you try to launch TimeWise for Windows, try this:

Go to the Start menu of the computer that is freezing and choose Settings | Control Panels | Display | Settings | Advanced | Performance | and lower the setting from Full to None and see if that solves the problem.

If that doesn't solve it, reset the above to its original state, then try this:

Put a shortcut to the utility file c:\timewise\twstart.exe (assuming TimeWise in located on drive C in folder TimeWise) in the Startup group of the computer that is freezing, OR put a shortcut to TimeWise itself (timeww.exe) in the Startup group so that TimeWise will launch whenever you start your computer.

 

Wrong Country/Region
If the opening screen or About screen in TimeWise refers to the proper region (e.g., United States), then this setting is fine. If it refers to the wrong country, then you must use TimeTool™ to fix the problem.

Set it in TimeTool™ by typing these commands:
USE PREF.DBF
Change Region field to be the country you wish (it must be spelled exactly like the choices on the Region screen

Other messages

Any other message that appears likely concerns the use of the printer, disk drive, or other connected device. For instance, TimeWise may want to use a device that is not ready. Examples include an open disk drive door, an unconnected printer cable, or a high-density floppy disk in a low density drive. Windows recognizes that there is a problem and issues a message identifying the device. Windows then asks:

Abort, Retry, Ignore?

Usually, you can continue your use of TimeWise by fixing the problem and then pressing R for Retry. For instance if your printer was off and Windows says:
 

Write fault error writing device PRN   Abort, Retry, Ignore

What it means to say is Where's the printer I'm supposed to talking to? You can then turn the printer on, press R, and TimeWise resumes where you left off.

If you cannot fix the problem, then press A for Abort, and restart the computer.

Never press I for Ignore or F for Fail. This could make matters worse.

If this message appears while using the Backup command, there is a problem with either the disk drive or the floppy disk. Ensure the floppy disk is in the drive with the label side up and the disk drive latch closed. Then Retry. If the error message persists, the floppy disk could be faulty. To check the floppy disk, try reformatting it with the Command Prompt FORMAT command and try again. If that does not help, try a floppy disk you know is healthy. If the problem persists, there is a problem with your disk drive. Contact your computer dealer.
 

If you see an error message that is not satisfactorily explained here, consult the Error Messages section of Help if possible to see if an explanation of the message appears there. Otherwise, contact us.

A printout of the display is helpful when troubleshooting. If using TimeWise for Windows, capture a picture of the screen by pressing Alt and PrtScreen keys at the same time, then Paste into a word processor or a new email message. Also note what you were doing when the problem occurred.
 

Network Note

If TimeWise is on a local area network, any number of unexpected messages can appear on a station that loses contact with the file server (the main computer). If you see unexplainable errors on a network station, ensure the network connection is sound, restart the station and see if the problem goes away. If the problem persists, call us.

Some error messages appear centered in a box with the choice to Cancel or Ignore. After you have read the message, choose Cancel to leave TimeWise, unless instructed by this documentation or our technical support staff to choose Ignore. If you choose Ignore, you are essentially telling TimeWise to continue even though something is wrong... kind of like running a red light: you may get away unharmed, or you could get really damage something.

If you do not find the error message you seek here, look in the Error Messages--Additional help topic of the TimeWise Help

Sometimes TimeWise can fix a problem automatically, in which you also have the choice to Retry, so you can attempt to continue from where you were.

Whenever you wish to turn off your computer, always leave TimeWise first, if possible. By turning off your computer with TimeWise running, you risk damaging your information files.

Some error messages originate from Windows or your Macintosh. For these, you can consult your operating system documentation for additional information.

Still stuck? Contact support@timewise.net.


TimeWise Home

 

Copyright © 1997-2004 David Berman Developments Inc. Certain names, logos, designs, titles, words or phrases on this page may constitute trademarks, servicemarks, or tradenames of other entities which may be registered in certain jurisdictions.
Reviewed August 2004