-
Runtime Error 53, 61, 70, 75 or 76 with Windows 2000 Professional or Windows XP Professional
Versions: 32-bit Lifebase™
Problem Explanation:
When attempting to use Lifebase™ on a computer with Windows 2000 Professional
or Windows XP Professional installed as the operating system, a "Runtime
Error XX" message is displayed where XX could is one of the following:
-
53 - File not found
-
61 - Disk full
-
70 - Permission denied
-
75 - Path/file access error
-
76 - Path not found
Solutions:
You have insufficient security rights to run the Lifebase™ system on this computer.
Contact your system administrator have them perform the following:
-
Grant "Write" access permission to the Lifebase™ program directory for your local user
account. This directory varies by company and is in the format XXXLBASE, where
XXX is a three letter code abbreviation for the company.
-
Grant "Write" and "Modify" access permission to the LBREPORT directory for your local
user account.
If the "Security" tab is not visible for either folder, make sure that "Simple File
Sharing" has been disabled. This option can be found in Windows Explorer under
the Tools menu, Folder Options menuitem, View tab on the Folder Options dialog box.
Network Microdesigns is currently investigating a permanent fix for Lifebase™
that will put all data that requires read/write/delete access into the Documents and
Settings folder for Windows 2000 and Windows XP.
- Web Update System Requirements
Versions: 32-bit Lifebase™
In general, the following is required to use Lifebase™ Web Update:
- Your Home Office has contracted with us to provide the Web Update service.
- You have a Windows 98 or better machine that meets the general
system requirements for Lifebase™.
- You have Internet
Explorer version 4.0 or better installed and properly configured. If you
don't have Internet Explorer 4.0 installed, the latest version of Internet
Explorer can be downloaded and installed for free from Microsoft website
here.
- You have a working
Internet connection installed and properly configured.
- >You have kept current
with critical updates to your operating system. These updates are available
for free from Microsoft at the Microsoft Windows Update
website here.
-
Web Update is not Enabled on Tools Menu in Lifebase™
Versions: 32-bit Lifebase™
Problem Explanation:
Web update is visible on the Tools
menu in Lifebase™, but is not enabled or "greyed out".
Solutions:
We have recently discovered that
a variety of settings on a computer, with regards to Internet connectivity, can give
us conflicting results as we try to determine the status of your Internet connection.
This has been especially true with broadband (DSL/cable) connections that use network
cards or a USB interface. Instead of trying to accommodate the determination of every
connection scenario possible, we've removed the checking that is responsible for enabling/disabling
this tool.
In early March 2003, we started
distributing a new version of Lifebase™ that resolve this issue. In the meantime, there
are workarounds to resolve this issue.
-
If you've recently received a release
from your home office, it's possible that the program folder for Lifebase™ that exists
in your Start->Programs menu has a shortcut directly to Web Update, bypassing the
need to launch Live Update from the Tools menu within Lifebase™.
-
If you do not have this shortcut
in your Lifebase™ program folder, contact your home office for information on how to
obtain this shortcut as well as the latest version of Lifebase™ and Web Update.
-
If you are comfortable in doing
so, you may wish to apply the latest updates to your operating system from the Microsoft
Windows Update website here.
These updates are provided freely from Microsoft. This may resolve the issue, in some
cases.
-
Web Update cannot connect to the Web Update server or similar error message
Versions: 32-bit Lifebase™
Problem Explanation:
When launching Web Update, an error
message is encountered that states "No internet connection could be found" or "Lifebase
Web Update could not establish a connection to the Internet" or "Lifebase Web Update
could not establish a connection to the Web Update server.".
Solutions:
If you have a dial-up connection,
AOL, or some other non-standard means of connecting to the Internet, check that you
have established a connection with your Internet service provider before you try to
launch Web Update. A non-standard connection is any connection that does not make
an entry in the Windows Dialup Networking folder. Some non-standard connection software
includes AOL, SBC Yahoo and some smaller Internet Service Providers (local area service
only, cooperatives, etc.). Also check with your home office to make sure you have
the latest version of the Web Update program. As of March 2003, we have implemented
a fix that should allow Web Update to bypass the problem with non-standard connections,
provided you are connected to the Internet before attempting a Web Update.
-
Crystal Report Error 997 or 998
Versions:32-bit Lifebase™
Problem Explanation:
Crystal Reports is encountering
problems processing Microsoft Word embedded objects on the output report.
These objects can appear on the cover page, which may contain a watermark
or company logo, or within illustrations or presentations that contain a large
amount of static text or clip art that was created in Microsoft Word. This
error can also occur with in reports that contain Crystal Reports graphs or
charts in the output as well.
Solutions:
This problem is caused
by Norton Antivirus, Version 2001 and up. A feature of Norton Antivirus, called
Script Blocking, incorrectly determines embedded Microsoft Word objects as
a virus and disables their functionality in the Crystal Report when you attempt
to display or print the report. This feature not only effects Lifebase™ and
Crystal Reports but all Microsoft Office products (all versions) that use
embedded objects in their documents.
If you encounter this
error and are running Norton Antivirus, you need to disable the "Script Blocking"
feature. This feature prevents Crystal Reports from printing or displaying
embedded Word objects or Crystal Reports charts and graphs correctly. To disable
"Script Blocking", follow the steps outlined by one of the following links:
Symantec
Support - Disable Script Blocking for Norton Antivirus Version 2002, 2003, 2004
Microsoft
- Disable Script Blocking for Norton Antivirus Version 2001, 2002, 2003, 2004
If you are having trouble locating
where or how to disable the "Script Blocking" feature, contact Symantec Support (makers
of Norton Antivirus) to find out how to disable the "Script Blocking" feature with
your particular version of Norton Antivirus. Where and how to disable this feature
can vary based on the version, updates and operating system in question.
Symantec
Support for Home Office/Small Business
If you are not running Norton Antivirus
or the above steps do not resolve the error, contact your home office, report the
problem, and request that the report be forwarded to us. When reporting this error,
take note as to whether you have an anti virus program installed that is active and
the name of that anti virus program.
-
Crystal Reports Error 545
Versions: 32-bit Lifebase™
Indications:
Crystal Reports cannot determine
the default output device or default output options to use with the report it is currently
processing.
Solutions:
Write down the entire error given
to you by Lifebase™, including the filename that Crystal Reports failed to process.
Call your home office, report the problem, and request that the report be forwarded
to us. Typically we can modify the report and have the problem fixed immediately.
We'll post the updated report on Web Update. If you don't have access to Web Update,
the report file can be emailed or sent to you via parcel post.
-
Crystal Reports Error 500 - Not Enough Memory for Operation
Versions: 16-bit and 32-bit Lifebase™
Indications:
The machine does not have enough
resources to launch Crystal Reports and process the requested output. Typically this
error is encountered when Lifebase™ abnormally terminates for an unrelated reason and
the user tries to start a new Lifebase™ session with Crystal still in memory from the
last session.
Solutions:
If youve recently encountered an
error and Lifebase™ terminated abnormally, take note of the error(s) prior to the termination
of the program and convey them back to the home office so that Network Microdesigns
can investigate. Reboot your machine to avoid the Crystal Report Error 500. If this
does not resolve the error 500, or you feel that you did not encounter any other errors,
check the system requirements to make sure that your machine meets these requirements.
Crystal Reports does require a large amount of system resources to run. Even though
your machine may have a large amount of memory and free disk space, if you are using
up those resources with other applications it is possible to get this error. Try running
Lifebase™ with fewer or no applications loaded. Check the system tray in the lower
right hand corner of the screen and terminate or remove any unnecessary applications.
Make sure that you dont have two sessions of Lifebase™ up at once.
-
Crystal Reports Error 501 - Invalid Job Number
Versions: 32-bit Lifebase™
Indications:
The Crystal Reports print engine
does not recognize the job number passed to it as a valid job.
Solutions:
Network Microdesigns has made significant
changes to the processing of print jobs in the 32-bit system during the month of November,
2001. Updates will be released to most companies starting in December 2001. If you
have not received an update, contact your home office for anticipated dates.
-
Printing an Illustration takes an excessive amount of time.
Versions: 32-bit Lifebase™
Indications:
Printing a NAIC compliant illustration takes times in excess of 5 to 15 minutes.
Solutions:
The new output forms for the 32-bit
version of Lifebase™ contain shading, graphics, and font characteristics designed to
combine into a professional looking presentation. Most printers that are designed
for office work can handle these characteristics. If you are using a slow or older
printer that typically takes a long time to print a graphic, you are going to have
problems. Network Microdesigns has designed within the Crystal Report an economy mode.
This economy mode removes all shading and graphics. Contact your home office to see
whether your company has opted for the black and white print mode. You might also
try altering the properties of your printer so that it prints in draft or economy
mode. This will enhance the speed but degrade the look of the output.
-
Lifebase™ does not print properly on a newer printer using a PCL6 printer driver.
Versions: 16-bit and 32-bit Lifebase™
Indications:
Lifebase™ hangs while trying to
print, or you get a large white error box indicating that something caused an error
within the printer driver dll. This tends to happen with newer HP LaserJet printers
that utilize a PCL6 version printer driver. 2000 series and 4000 series.
Solutions:
We are hoping that our upgrade
to Crystal Reports 8.5 is going to resolve some of these issues. Until then, either
use a PCL5 version of the printer driver or use a more generic version of driver for
that printer family. At least while printing through Lifebase™.
-
Letters or numbers missing from output. Whole sections of output missing from a page.
Versions: 16-bit and 32-bit Lifebase™
Indications:
Sentences will be missing letters
or entire words. Words may be jumbled together and the spacing may not be quite right.
Numbers may be missing from the tabular detail. Weve encountered this problem on Canon
equipment, in particular a multifunction machine.
Solutions:
Since there are not many alternative
printer drivers for this equipment, its not practical that the user do anything besides
try to use the most up to date driver possible. We suggest that you contact Canon
technical support to see if they have encountered any problems in printing graphics
from programs such as Crystal Reports. We are hoping that our upgrade to Crystal Reports
8.5 will alleviate some of these issues.
-
HP Deskjet Printers and Pure Virtual
Function Call
Versions: 16-bit and 32-bit Lifebase™
Indications:
While trying to print or preview,
the user will get an error message from the printer driver in a large white rectangular
box stating that a Pure Virtual Function Call occurred.
Solutions:
HPs own website offers
us our only insight into this problem. After reading the information that
is offered, the bottom line is that the machine is out of print resources.
View this link
for more information. Youll see that most of the suggestions involve freeing
up resources. Trying a different print driver is also an option. Try the Microsoft
version that is supplied on the OS CD as opposed to the one offered by HP.
Or vice versa.
-
Problems with HP Printer Drivers
Versions: 16-bit Lifebase™
Indications:
While trying to print or preview
an illustration, an error occurs that indicates that there were problems with the
printer or printer driver. This was most prevalent on the 16-bit Lifebase™ system and
involved mostly HP DeskJet series printers.
Solutions:
We always suggest that
you first check to see that you are using the latest printer driver for your
hardware. With the exception of PCL6 drivers, download the latest driver for
your HP printer.
If this does not resolve the issue, or if your current printer driver is a
PCL6 driver (usually appears in the title or version information) try downloading
an older driver for the printer family you are working with.
-
InstallShield error 115 while installing Lifebase™
Versions: 16-bit and 32-bit Lifebase™
Indications:
User encounters error 115 from
InstallShield while attempting to install Lifebase™. Installation process terminates.
Lifebase™ does not install.
Solutions:
Error 115 from the InstallShield
help reads as follows: "Specified file cannot be opened as write. An attempt was made
to overwrite a locked file belonging to a file group that does not have the Potentially
Locked or Shared property set to Yes; an attempt was made to install a file with a
long file name (or to a folder with a long path name) in a 16-bit setup; or the path
to the target folder is invalid."
Since Lifebase™ does not utilize
long file names, the error is referring to a problem opening a file that is already
open and locked. Check your machine to make sure that you do not already have a Lifebase™
session up and running. Check to make sure that you dont have any other applications
open and running while trying to install Lifebase™. Reboot the machine if necessary
and try the installation again.
-
InstallShield error 119 while installing Lifebase™
Versions: 16-bit and 32-bit Lifebase™
Indications:
User encounters error 119 from
InstallShield while attempting to install Lifebase™. Installation process terminates.
Lifebase™ does not install.
Solutions:
Error 119 indicates that InstallShield
was unable to register a control or process necessary for Lifebase™ to function properly.
Most frequently this occurs when a virus protection program determines that a process
is trying to alter the registry of the machine when it should not be doing so. The
solution is to temporarily disable the virus protection program for the duration of
time it takes to install Lifebase™ and for InstallShield to properly register the controls.
Reboot the machine if prompted upon completion of install. Remember to reactivate
the virus protection software once Lifebase™ is properly installed.
-
Codebase Error 70
Versions: 16-bit and 32-bit Lifebase™
Indications:
During startup of Lifebase™, user
is presented with a Codebase Error 70, followed by a filename that Lifebase™ is unable
to access. Lifebase™ then terminates
Solutions:
Error 70 indicates that the database
engine is having problems accessing a file. Check to make sure that the file is not
locked by another process. Make sure two sessions of Lifebase™ are not running at the
same time. In a network environment, make sure that all of the files within the Lifebase™
installation that are shared, are flagged properly as sharable with read / write capabilities
for all users. In a network environment, make sure that your users have the proper
rights to the directories in which you installed Lifebase™.
-
Runtime Error 13 Type Mismatch
Versions: 16-bit and 32-bit Lifebase™
Indications:
During the entry of data or display
of a dialog box, a Visual Basic runtime error 13 Type Mismatch is displayed on the
screen. Lifebase™ terminates.
Solutions:
Type mismatch indicates that Lifebase™
tried to set a data field to a value that the field was not meant to represent. Many
times, this data involves dates or currency values. Be sure to check your regional
settings. If it is not set to English (United States) or Spanish, it is possible that
your date or currency representation is causing the problem. Make sure dates are set
to dates involving 4 digit years, just to be sure. Contact your home office if this
does not resolve the issue.