Anyone else having a problem with Urchin this morning?

When I log in and click on my reports, all I get is:
"Content-type: text/HTML Urchin CGI Report. Error Encountered (1007). Invalid Report Number. "

I logged a ticket a couple of hours ago.

No problem here, was on earlier and just checked again

We have the same error as above.

Me too. Same error.

Thanks for the responses...at least Im not alone.
Hopefully it'll be resolved soon (my ticket is in "assigned" status).

This helped me out..

http://forum.ev1servers.net/showthread.php...&highlight=1007

but I'm still looking for another resolution, the 5.7 update have also knock my direct link report off.

Hey hsmcache.
Thanks for the info, but I'm not quite sure thats a workable solution on our end as users?
My ticket is still in "assigned" status...yikes.


UPDATE: Lost some older data, but got it fixed...perhaps I missed something before but...
I am now also seeing stats from TODAY!!! Yeeee Haaaaa!!!

Any update on this? I'm still getting the error.

I suppose I need to create a ticket.

Hey cctvgirl...
See my post above. It was fixed within a few hours once I submitted a ticket.

I'm not getting the error but I'm not seeing stats from today either. Is it supposed to show current stats, including the current day?

We have no stats listed for this past Thursday. All other days are OK.
As far as I can tell, we only see stats the following day. I never saw stats for the current day.
That would be really cool though.
Ben N

Ok, perhaps I jinxed myself, or it was a glitch when fixed my stats, but I was seeing stats from the current day.
I just checked it a moment ago ...no more current days stats

If I was able to get them for a day (or so), why not constantly???

?

Did anyone else lose all their historical data? I am very angry that they blew away everything from prior months when they supposedly "fixed" the database. This now prevents year over year, seasonal and trend analysis on traffic. I am having a hard time understanding how they can just trash our historical data so cavalierly. This is the 3rd time we've been screwed over by their server programmers. The first time they blew away a weeks worth of e-mail when the e-mail server was clogged by a spammer. The second time was the monstermarketplace debacle where they set my pages (and a lot of others) to "do not index", and now this. I don't know if I can handle much more of their supposed "technical support". I'm very afraid they are going to lose our more valuable data such as past and pending orders. I would not recommend these guys for data protection. Be forewarned.

Yup...us too.
Hey Jim, I feel your pain.

Im a firm believer in backing up.
We export our reports regularly...after the first time I saw a blue screen of death and a DOA hard drive (on a local machine), I've been backing up like its a religion (been many years now).
If it's important, I keep copies of copies of copies of copies in multiple places.
It's certainly no excuse for the Urchin dump, but as I understand it, it was an issue with an Urchin upgrade or patch, and mons*er was just responding to the recommended fix.
I feel your pain.
Chant: back up the data...back up the data...

Yes, we lost everything too. No warning even. I would have at least printed out reports for the records had I known over a years worth of data was just going to be dumped with no warning. Unfortunately, I do not know how to back up Urchin stats either. Not that it will do me any good at this point!

The first year we were on , everything went great. 3 months into year two and things are not going so great.

Even if you can back up the data, I don't know how much value there would be since there is apparently no way to upload it back. Current and past data would always be in separate databases requiring downloading before every analyis. Plus you probably wouldn't be able to recreate all the cool data maniupation features like the calendar, etc. without being a database whiz. I would agree MC seems to be going through a rough patch right now.

Agreed 100%, but it's better than nada.
Im not sure this issue rests wholly on though...I really think it was an issue with Urchin. There are a number of techie threads on the web about this issue happening to a bunch of hosts that provide Urchin stats.
I have no issue taking a responsible party to task (or taking blame myself), but on this one...well...