Reports and databases
proCube Publisher creates a database in SQL that stores all markups and reports as XML files in separate tables. These tables store information about every choice or selection you made during the markup and report configuration processes.
Re-starting SQL server
SQL Server must be running in order to use Publisher. If SQL Server is not running, an error message opens.
To manually start the SQL Server:
Select Start, Settings, Control Panel, Administrator Tools, Services. The following dialog appears:
Select the MSSQL$PUBLISHER service.
When you right-click on this service, a drop-down menu appears. Select Start to restart the SQL server.
Launch reports (log files)
When you launch a report, error messages are generated in the XML file, which is located in the C:\Temp\ directory (or other directory designated when Publisher was installed). This XML file captures every detail about the report, including when it was sent, who received it, the members and dimensions that were selected, the types of outputs and who received them, the report options selected, and any errors that occurred when the report was launched.
Common error messages
The following table lists some of the common error messages that you may receive:
in the XML file generated after launching a report (in Temp file)
as message boxes while configuring a report
in an E-mail
Unless otherwise noted, when you receive a warning message, you will find these errors listed in the report’s XML file, which is located in the C:\Temp\ directory (or other directory designated when Publisher was installed).
Avoiding Excel errors
The following recommendations will help you avoid Excel errors when using Publisher:
You cannot have a cell or a sheet that is referenced to a different spreadsheet in your workbook.
If your macro has a reference to a cell in a specific spreadsheet, the cell must be specified with the sheet name. (This concerns only workbooks that contain multiple spreadsheets).
If your workbook has a macro runtime error, no errors are displayed, and when you generate the report, the VB debug window opens up.