Avaya Attendant Console Bedienungsanleitung PDF herunterladen (Seite 56)

56 Chapter 8 Troubleshooting

P0936570 03

Reports could not connect to the chosen

database.

This error occurs if the Reports component fails to create a

DAO record set from the database selected. This can be

because:

• The file is not found.

• The file cannot be locked because it is in a write protected

area.

• The file is not readable for some other reason.

This error can also result if DAO is not properly installed.

The Reports component was unable to

generate the listing from the database

specified.

Make sure that the database selected is created by the server.

This error occurs if a user tries to use the Employee or

Customer directories after connecting to a database that is not

a Attendant Console database. The error is usually preceded

by a message from the Microsoft Jet database engine that

says: “The Microsoft Jet database engine cannot find the input

table or query ‘People’. Make sure that it exists and that its

name is spelled correctly.”

The animation file used to indicate that a

report is running could not be found. It

might be missing or corrupted. As a

consequence, no animation plays while the

reports are running.

This error occurs during Reports start if the “run.avi” file is not

found in the Reports path. Check that the file is installed

correctly and is not deleted. The component runs, but the

animation does not play while generating reports.

The maximum number of selections

allowed in any single category is 100. Limit

your selections or cancel the selection and

choose the All option.

The maximum number of selections from the Customers or

Employee categories is 100 each. Trying to click OK from a

directory dialog box with more than 100 selections causes this

error and returns the user to the directory dialog box, from

which they must reduce the number of selections.

The report could not find the necessary

data in the specified database. Make sure

the specified database is a valid system

database:

This error occurs if a report is run, but the database selected is

not a valid Attendant Console database. The colon is followed

by a new line on which a more specific error message from the

Crystal Reports Engine is displayed. This message is usually

“Unable to connect: incorrect table location”.

Reports could not find the needed report

(.rpt) file. Make sure all the “.rpt” files are

installed correctly.

This occurs when generating a report, if the appropriate “.rpt”

file is not found in the Reports directory. Either the file is

deleted, moved, not installed correctly or corrupted. When

corrupted the Crystal Engine can no longer recognize it as

a.rpt file even though the name indicates it is.

The report file has somehow become

corrupted. The following statement in

English is more detailed information useful

for troubleshooting.

This error occurs if the needed “.rpt” file is found but does not

contain the correct parameters or information. The Extension

Directory Report (using ExtDir.rpt) does not produce this error

because it does not require any parameters.

The “statement which follows” part occurs on the next line and

is a message from the Crystal Reports Engine. The message

is most often “No Error”.

Error message / Log message Meaning / Action required

1 2 ... 51 52 53 54 55 56 57 58 59 60 61 62 63

Kommentare zu diesen Handbüchern

Keine Kommentare

Avaya Attendant Console Bedienungsanleitung Seite 56

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Datenbanksoftware Avaya Attendant Console