Databases Reference
In-Depth Information
Like a typical log file, each contains information about Report Server events, warnings, and errors.
There's a separate trace log file that's created for each day. The log file contains all the entries for that
day, beginning at midnight. The local time of the computer is used to determine when midnight is and is
also used to name the file. It's good to know that Reporting Services doesn't remove any previously gen-
erated log files, but that can also be a problem as disk space gets used up. Figure 11-4 shows a typical
Report Server log file.
Figure 11-4
From the developer perspective, you can get a lot of troubleshooting information from a combination of
the log files and the stack trace. If you're a local administrator and are running Internet Explorer on the
server, stack trace info is available by right-clicking the error page in the browser window and selecting
View Source.
You can also tweak how log entries are made and kept. Changing those settings can have an effect on
how your server behaves. You'll read about what settings to change and how to set them later in this
chapter, in the section “Exploring the Execution Log.”
Delivery Settings
Reporting Services includes a delivery extension so reports can be distributed by e-mail. The delivery
settings include a Simple Mail Transfer Protocol (SMTP) server address and an e-mail address for the
From: field. This typically occurs when a subscription has been created and the user requests e-mail
delivery. The e-mail itself can contain the actual report in static HTML or can contain a link to the report
in Report Manager.
The delivery setting must be the valid hostname of an SMTP server. If you're using Microsoft Exchange,
use the name of the SMTP gateway; don't use the name of the Exchange server here or you'll get errors
during subscription processing. Use an IP address like 192.168.0.1 or other DNS-resolvable name.
Remember to include the domain name if necessary.
Search WWH ::
Custom Search