Forum Moderators: DixonJones
I'm running Webtrends 5.5c and am having problems reconfiguring some of my profiles. I'm trying to get stats for specific directories from logs pulled from a server cluster.
I have a dedicated machine running Webtrends and the log directories look like this:
E:\logs\mysite\server1
E:\logs\mysite\server2
E:\logs\mysite\server3
E:\logs\mysite\server4
The profiles I'm trying to update need to point to the 4 logfile directories above. Currently, they point to similar but different locations (note that the directory structures on the web sites themselves remain the same, basically we just moved all of the content off of servers 5 and 6 and dumped it onto 1-4):
E:\logs\myOLDsite\server5
E:\logs\myOLDsite\server6
I have gone into one of my profiles and updated the logfile locations, but it doesn't seem to give me an accurate report. Basically, when I run the profile, it seems to look at the server1 directory for a second or 2, then generates a report showing garbage data (just shows data for december 31 on a report for full month of december).
I noticed when modifying the profile it made mention of a fasttrends database that is in use and gives me the option of deleting it or continuing to use it. I have a total of 200ish profiles and 1/2 of them are working fine (pointing at other servers/locations) so I'm afraid if I delete the database and attempt to rebuild it that might screw up the working profiles.
Any thoughts on this? Huge thanks in advance if you can assist :).
But that may have nothing to do with your situation. Maybe changing the locations of the raw data is causing WT to think that something more drastic has changed, and it's asking you if you want to start all over.
To try to trouble shoot this, I would first create a completely new profile that points to the new log setup. (Maybe you're already done this.) If it still can't cope with the multiple log locations, I'd suspect something else, like 1) the logs really aren't there, 2) the path to the logs is wrong, 3) you have some kind of "start report on x date" limitation in place that you've forgotten about, 4) permissions aren't right and the WT machine isn't allowed into those folders. The best way to check is to sign on to the WT machine and see if you can browse to and read those logs.
All this may not help at all but it's the best I can offer right now. There's a processing error log somewhere in the GUI that will allow you to see a lot of the errors that WT experiences, so if you try to find that it could help.
Stop using FastTrends on the profiles and delete the data already stored, then you should be fine.
