Identifying Analytics errors - Analytics Troubleshooting Level 1.5

     If basic troubleshooting of the service finds no problems you will need to check the Windows Event Viewer to determine exactly what error the analytics package is throwing. The below walkthough assumes you are running Windows Server 2003 or 2008. If you are running Windows Server2012 simply search for 'EventVwr' from the Windows Start menu to access the application and otherwise proceed as below. The below also assumes you are using the service to run the process, which is the standard way to install per our walkthough (and DGI's).. There are workarounds available for clients where the service will not operate properly, if you have one of these (hint: if you have more than one production DB that CEO Juice is monitoring, you have a workaround) the below will not work for you. Please contact us for direct help.



     You need to be working on the server where analytics was installed and is running, presumably your production server (per DGI recommendations) but it is possible you installed elsewhere on your network. Windows Event Viewer is (primarily) available from the Administrative Tools. you can usually find that directly off the START menu, as per the screenshot below, but on older builds of Server 2003 you may have to look int Administrative Tools in the Control Panel. you can also search for the executable directly, it is named 'eventvwr.exe'. Below is a screenshot of the most straightforward method of opening Event Viewer.



     The data you are interested in is located in the Application Log. Your system may or or may not show all the options in the screenshot below, depending on your exact OS, but one of them should be plainly labeled 'Application' as in the left-hand pane. Once that is open you can either search for 'da_DataProcess' or simply scroll down to the entries from early this morning or late last night and find them the old-fashioned way. The right-hand pane in the illustration below shows you exactly what you're looking for. You want the entry specifically marked as Type='Error'.



     Once you have the located the error entry double-click on it to open it to display the 'full' text (it actually does not show the full error text but 98% of the time it gives us enough to know exactly what your problem is and how to fix it). Please send this to us at either by copy/paste or screenshot and we can tell you exactly how to proceed from here.


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk