|
The following Technical Notes are useful in assisting
some common occurences which may happen in MSA. If you
do not see an answer to one of your own issues in the
Notes below, please feel free to submit your own issue
to support@miracleservice.com
and we will do our best to add them here for future
use. Also, Check out our
•
NEW!
Searchable Knowledgebase •
Can't find what you are looking
for here? Email
us! Status
Codes
Errors
General Issues
| Status
30 when running Pervasive Server Engine |
| | Engine not started
(ctrl+alt+del with W32MKDE confirms this). On server ensure
both Pervasive services are started.
|
| Status
30 with Pervasive.SQL 2000 Server
|
|
|
Check for \windows\system\wbtrv32.dll
- if it exists, delete it
|
| Status
85, Unable to open keys table
|
| | A client which
does not have Pervasive installed is attempting to or
has accessed MSA (conflicting btrieve drivers). Need to
install Pervasive on the client machine
|
| Status
87, 'file handle table full', logging into Accent |
|
|
Using the Pervasive.SQL
Server, increase the 'file handles' and 'open files' values
using the pervasive utilities
|
| Status
94 with Pervasive.SQL 2000 server for NT.
|
|
|
Ensure
the group everyone has been added to has the permissions
for the AccentDB share with 'full control'
Set the Pervasive services to log in as Administrator
|
| Licence
key status codes
|
|
|
|
| | Also:
53 - mixed drive mapping, run dbrouter.exe from
exact same location on all clients (i.e. via Network Neighborhood
or mapped drive)
|
| Pervasive.SQL
2000 status 3006 (This error occurs when the network connection
to the Pervasive server is broken or interrupted).
|
|
|
On each client
workstation, perform the following:
-click Start, Programs, Pervasive, Pervasive control centre
-Expand the computer name (this should be the name of
the local workstation)
-Expand Configuration
-Expand Client
-Click on Communication protocols
-On the right hand side, you should see an option for
Enable Auto Reconnect
-Double-click this and change it from Off to On
-Exit the control centre, save the changes, then restart
the workstation.
On the server (whether a genuine Pervasive.SQL 2000
server or a workgroup engine acting as the server, do
the following):
-click Start, Programs, Pervasive, Pervasive control centre
-Expand the computer name (this should be the name of the server)
-Expand Configuration
-Expand Server
-Click on Communication protocols
-On the right hand side, you should see an option for Enable Auto Reconnect
-Double-click this and change it from Off to On
-Exit the control centre and save the changes. If this
is a workstation running -Pervasive.SQL Workgroups,
restart the workstation. If it is an NT server running
-Pervasive.SQL Server, stop and restart the two Pervasive services
|
Back
to top
|
| Run-time
error 48 when running reports
|
|
|
Check that \windows\system\crwrap32.dll exists
Check that \windows\system\sscsdk32.dll exists (only for
graphed reports), also returns 'unknown error'
|
| Runtime
error 13 (escalation, or any date/time based form)
|
|
|
Check
that the c:\windows\win.ini [intl] settings match a working
client PC
In particular, check all date settings, plus 'itime' which should be set to '1'
Can also mean that the database is not compatible with
the application version
|
| Accent
returns messages like 'bad or missing entry in ini file'
or 'message 999.0001 missing from resource file'
|
| | The file 'accent.ini'
or 'resource.ini' may be locked. Check via the server
and remove any existing ownerships.
|
| Printer
missing in reports (W9x)
|
|
|
Look
in WIN.INI under [Devices]. If it is missing here, see
if it under [PrinterPorts], and if it is, copy and paste
to the [Devices] section
|
| Runtime
error 367, 'can't load or register customer control acbtrv32.ocx'
|
| | Re-instate file
wbtrv32.dll to the local \windows\system folder or equivalent
Go to the Dos/Command prompt
Change to the c:\program files\service accent directory
Type regsvr32 acbtrv32.ocx
After successful registration, rename or remove wbtrv32.dll
|
| Can't
start Pervasive Server Engine, Error 1069, login failure
|
| | If services are
logging in as administrator, ensure administrator password
is correct on both.
|
| Runtime
error 31037
|
| | Caused by some
runtime files missing/out of date. Files to check include (\windows\system or system32)
· Olepro32.dll
· Oleaut32.dll
· Comcat.dll
· Comctl32.ocx
If older than 1997, they need updating
|
| Licence
error - OLE automation server cannot create objects
|
|
|
Start > Run
> regsvr32 "c:\program files\miracle service accent\vw_lic.dll"
this will register the license properly
|
Back
to top
|
| Accent
installation onto NT machine hangs searching for the database:
|
|
|
Delete
wbtrv32.dll from winnt\system32 folder
Check path to make certain pvsw.bin is in it
|
|
Notepad appearing pressing an F on the keyboard
|
|
|
Press and release
the ctrl and alt keys to force Windows to clear them.
This is a bug in Windows 95.
|
| Hotfix
requests an ugrade when logging into Accent, even though
the latest update has been loaded
|
|
|
NT
can sometimes append file names. Find the latest msa-???.exe
in the accentdb and or \accentdb\updates folder and rename it
Find all local files named 'accent.exe' and use 'properties'
to check the version - it may be out of date
If find returns multiple files, make sure the Accent shortcuts
refer to the latest version
Try copying 'accent.exe' from a working client
|
| Conflict
of the International settings on an NT machine
|
|
|
Go to Regedit,
the HKEY_CURRENT_USER\Control Panel\International. Reset
sDate and/or sShortDate.
|
| Crystal
reports errors
|
|
|
Three main areas these fall into:
'Invalid file name (507)' - the report file is not in
\accentdb\reports.
'Unable to link file XXX' - the table link(s) in the Crystal
report file are broken. Report needs to be opened in Crystal
Reports 7, link recreated and saved.
''btrieve error on XXX.btr' - report structure is out
of date compared to the database. Report needs to be verified
in Crystal reports and saved.
|
Also
available: Frequently
Asked Questions
Back to top
|
|
