Page History
...
- Verify that the EventCollector web application can be accessed from the your SharePoint front-ends (WFEs), and that it is not blocked by a FW/Proxy in the organizationfirewall or proxy, by browsing to http://[CardioLog server name:port]/EventCollector/caCached.aspx (edit the Input your CardioLog server name and port). The expected result is a an XML response. To see which ports are used View the ports used by CardioLog Analytics click here.
- Verify that the CardioLog database is up and running, and the CardioLog application pool user account can account is assigned a db_owner role, and can connect to itthe database.
- Check for server errors in personalizing content.
- Configure the default timeout for content personalization in the JavaScript tracking code.
- Verify the CardioLogAgent web application can be accessed from your workstation, and it is not blocked by a FW/Proxy in the organizationfirewall or proxy. This is done by browsing to http://[CardioLog server name:port]/CardioLogAgent/ca.aspx (edit the Input your CardioLog server name and port). View the ports which are used View the ports used by CardioLog Analytics.
- Send the JavaScript error
- message by opening a new support ticket.
- Remove the tracking code from your SharePoint website.
- For more information see Uninstall Procedure.
| Anchor | ||||
|---|---|---|---|---|
|
In order to configure detailed server errors for the tracking agent, edit the "KeywordForShowingErrors" key in the following files: [CardioLog Installation Folder]\CardioLogAgent\Web.config and and [CardioLog Installation Folder]\EventCollector\Web.config:
...
Each customer must set his own unique value for "kfse".
When using a valid "kfse" URL parameter, page caching and timeouts are ignored and one you can view the server error. In order to overcome avoid caching, modify the "kfse" parameter value with every call time so it contains the original value, for example, if "kfse" is "test", then use "test1", "test2", "testabc", etc. each time you browse to the page.
In order to turn on message logging to trace the tracking agent, add the "Message" switch to the "logType" key to the [CardioLog Installation Folder]\EventCollector\web.config file -
<add key="logType" value="Message,Warning,Error" />
| Anchor | ||||
|---|---|---|---|---|
|
...
Server Errors in Tracking Usage Data
To view the server error, browse the following page and add the "kfse" URL parameter (the . The "kfse" URL parameter value must correspond to the "KeywordForShowingErrors" keyword):
- http://[CardioLog server name:port]/CardioLogAgent/tunnel.aspx?kfse=[keyword]
Example error message: "Error caught in tunnel: Request timed out"
Solution: Verify that the EventCollector web application can be accessed from the SharePoint front-ends, and that it is has not been blocked by a FW/Proxy in the organizationfirewall or proxy. This is done by browsing to http://[CardioLog server name:port]/EventCollector/monitor.aspx (edit the Input your CardioLog server name and port). The expected result is an XML response. View the ports which are used View the ports used by CardioLog Analytics.
| Anchor | ||||
|---|---|---|---|---|
|
...
Server Errors in Storing Usage Data
To view the server error, browse to the following page and add the "kfse" URL parameter (the . The "kfse" URL parameter value must correspond to the "KeywordForShowingErrors" keyword):
- http://[CardioLog server name:port]/EventCollector/monitor.aspx?kfse=[keyword]
To view
...
a detailed log of the data collection process, open the [CardioLog Installation Folder]/CardioLogScheduleServices\Logs\EventCollector.log file.
| Anchor | ||||
|---|---|---|---|---|
|
Server Errors in Personalizing Content
To view the server error, browse to the following pages and add the "kfse" URL parameter (the . The "kfse" URL parameter value must correspond to the "KeywordForShowingErrors" keyword).
Note: these files are cached by default, in order to overcome avoid caching and display the error message, modify the "kfse" parameter value with every call time so it contains the original value. For example, if "kfse" is "test", then use "test1", "test2", "testabc", etc. each time you browse to the page.
- http://[CardioLog server name:port]/CardioLogAgent/ca.aspx?kfse=[keyword]1
- http://[CardioLog server name:port]/EventCollector/caCached.aspx?kfse=[keyword]1 1
Example error message: