Data Warehouse Analytics System Issues
For the latest version of Commerce Server 2007 Help, see the Microsoft Web site.
This topic describes various issues that apply to the Data Warehouse.
Data Warehouse and Analytics reports
The following Data Warehouse and Analytics reports require date range entry input in MM/DD/YYYY format:
Advertising_Reports/Ad_Reach_and_Frequency_by_Advertiser.rdl
Advertising_Reports/Ad_Reach_and_Frequency_by_Date.rdl
Advertising_Reports/Campaign_Event_Summary.rdl
Advertising_Reports/Campaign_Item_Summary.rdl
Diagnostic_Reports/Bandwidth_Summary.rdl
Diagnostic_Reports/Bandwidth_Trends.rdl
Diagnostic_Reports/Hits_by_HTTP_Status.rdl
Diagnostic_Reports/Hits_by_Win32_Status.rdl
Product_Sales_Reports/Buyer_Browse_to_Purchase.rdl
Product_Sales_Reports/Customer_Sales.rdl
Product_Sales_Reports/Order_Events.rdl
Product_Sales_Reports/Product_Sales.rdl
Product_Sales_Reports/Shopping_Basket_Events.rdl
Query_String_Reports/Query_Strings_Multi_Value.rdl
Query_String_Reports/Query_Strings_Single_Value.rdl
User_Reports/Distinct_Users_by_Time.rdl
User_Reports/New_Registered_Users.rdl
User_Reports/Registered_User_Properties.rdl
User_Reports/Registered_Users_by_Date_Registered.rdl
User_Reports/User_Days_To_Register.rdl
User_Reports/User_Registration_Rate.rdl
User_Reports/User_Trends.rdl
Visit_Reports/Entry_Pages.rdl
Visit_Reports/Exit_Pages.rdl
Visit_Reports/General_Activity_Statistics.rdl
Visit_Reports/User_Visit_Trends.rdl
Web_Usage_Reports/Activity_By_Browser.rdl
Web_Usage_Reports/Directories.rdl
Web_Usage_Reports/Entry_Path_Analysis.rdl
Web_Usage_Reports/Top_Referring_Domains_by_Request.rdl
Web_Usage_Reports/Top_Requested_Pages.rdl
Web_Usage_Reports/Usage_Summary_by_Day_of_Week.rdl
Web_Usage_Reports/Usage_Summary_by_Hour_of_Day.rdl
Web_Usage_Reports/Usage_Summary_by_Week_of_Year.rdl
Web_Usage_Reports/Usage_Trends.rdl
Multilingual reports
By default, if you view the Data Warehouse and Analytics reports in a locale other than English, French, German, or Japanese, the Relative Date: drop-down list that appears on most reports will appear in English. You can change this value by editing the RelativeDate table in the Data Warehouse and Analytics database. The column named Other contains the values that you can change for any new locale that you want.
Prepare Reports failure with SQL Server 2000
When you run the Reports preparation DTS task with SQL Server 2000, you may receive the following error message:
"Level Directory
Processing error [Source data contains no rows] ‘Level Directory’S’"
This error occurs when there is no data in the Level 5 Directory dimension. You can safely ignore this error because it does not affect functionality.
Enclose Profile ID GUIDs with braces {} when passing to Data Warehouse methods from the user interface
The Profile ID is a string type and not a GUID type. You must enclose the Profile ID with braces {} when you pass the Profile ID to any methods that call the Data Warehouse from the user interface. The method will recognize the Profile ID as a string-based GUID and will not throw an exception.
Circular catalog hierarchy causes Report Preparation DTS task to fail
Catalogs can be set up in such a way that one catalog points to another, which causes a circular hierarchy. The Report preparation DTS task will fail in this case.
For example, if you add three catalogs in the following configuration, there is a circular hierarchy:
Parent |
Child |
|---|---|
C1 |
C2 |
C2 |
C3 |
C3 |
C1 |
To reproduce the circular catalog hierarchy
Create a category definition, such as CategoryDefinition1.
Create a Catalog with default value, such as Catalog1.
Create three categories in the Catalog1 with default values, such as C1, C2, and C3.
Edit category C1 to add C2 as the child category of C1.
Edit category C2 to add C3 as the child category of C2.
Edit category C3 to add C1 as the child category of C3.
Given these reproduction steps, there should be a Catalog Manager error, or the three categories should be displayed successfully in the Catalog Manager. The categories do not appear when you click Refresh in the Catalog Manager. However, the three categories disappear from the Catalog Manager, but actually exist in the database.
As soon as the Data Warehouse has entered this state, the following steps are necessary to return the Data Warehouse catalog to working order.
To repair the Data Warehouse catalog
Remove the category loop from the catalog.
Export the catalog.
Delete and purge the catalog.
Re-create or re-import the catalog (now without the looping categories).
Run a full DTS catalog import.
Reprocess the cubes.