Determining problems with the interface – Cisco OL-20949-01 User Manual

Page 93

Advertising
background image

10-5

Cisco Unified IP Phone Services Application Development Notes

OL-20949-01

Chapter 10 DeviceListX Report

Troubleshooting DeviceListX Reports

Error Message

1001 Too many simultaneous requests for Device List. Please wait at

least 60 seconds and try again.

Explanation

When two or more clients attempt to get the list at the same time, or if the list is long,

overlapping requests can result (first request is processing when the second request attempts
processing).

Recommended Action

Request information only as often as necessary.

Note

Cisco recommends that you wait longer than 60 seconds between requests.

Error Message

1002 Too many consecutive requests for Device List. Please wait at

least 60 seconds and try again.

Explanation

Because the system is busy, it cannot process a Device List.

Recommended Action

Request information only as often as necessary. Because the real-time status of

every device gets checked, Device List represents a CPU-intensive process.

Note

Cisco recommends that you wait longer than 60 seconds between requests.

Determining Problems With the Interface

Use the following procedure to determine whether a problem exists with the interface and determine the
root cause of the problem.

Procedure

Step 1

Check the Windows NT Event Logs for error messages that pertain to the IIS server and the SQL server.

Start > Programs > Administrative Tools > Event Viewer

Step 2

Check for error messages or successful completion of a request in the IIS log files, which are typically
located in

C:\WINNT\System32\LogFiles\W3SVC1

The date of the log provides part of the log name. All times in the log files specify GMT for noted events.
The IIS logs appear in chronological order and can easily be searched by specific query event.

Step 3

Use a web browser, such as IE, to request the URL of the devicelistx.asp web page. A successful request
yields a well-formed XML object of all the device information.

Step 4

Use a Sniffer trace to view the HTTP GET request and response transaction between the third-party
application and the report.

Step 5

If you need further assistance, see the

“Document Conventions” section on page x

.

Advertising