Reporter 9.1.2.1

[ArtBahrs]

Hi All,
Anyone using this yet? Issues? Evaluations?

Thanks,
Art

[ReddBull]

I just completed the upgrade from 9.1.1.2 64-bit to 9.1.2.1 64-bit...upgrade was quick (less than 5 min) and flawless (no problems).

[ArtBahrs]

Glad to hear it went ok... may I ask about your environment?
- How many databases?
- How much disc?
- Freespace?
- How many Lines of Log file Data?
- How many Users
- Scheduled Reports - do you?

thanks,
Art

[CuseHokie]

I've been having many issues.

After rebuilding the database from scratch, it worked fine for a few days...

Now I notice my whole dashboard reports got blown away.

Apparently restarting the service does this?

I also cannot send files with an SR#, it attempts to bypass proxy settings on the windows server.


And when I choose to edit reports under different roles, it does not show the column of the value for the attribute you're viewing... i.e. cannot see requests/pageviews/bytes/etc.

[ReddBull]

I'm noticing the same issue with customized dashboard being reset. I've opened a support case...will let you know if there is a "fix" or workaround.

[ReddBull]

So far only our LDAP users are having the issue of re-set dashboard and 'lost' customized reports. Local accounts do not appear to exhibit the loss of customized content when the service is restarted...

[ArtBahrs]

Hi All,
Ok... I "installed" 9.1.2.1 last week since 9.1.1.2 was killing us!!! We had "user ID's" losing there ability to "access" databases even tho other users could see and use the databases. And numerous other issues I had on escalated status

Also, We had problems with 'scheduled' reports becoming "undefined" - thus wouldn't run... 9.1.2.1 dosn't have a fix for this... and the scheduled "Daily Use by Category" I set up and schedueld to run daily at 5:59 hrs local .... well I built it yesterday... it went undefined... then this morning? It is gone completely from the "scheduled" tasks window!!!!

Anyone here willing to start a "Open Ticket" Thread so if one of us sees someone has opened a ticket for a problem we can call Tech Support and have ourselves added to the ticket? This way BlueCoat can 'see' how many people are having the same problems?I would hope that BlueCoat would give increased effort to tickets that have lots of us chiming in on ...

Thanks,
Art

[ReddBull]

These are the same issues that I reported to Blue Coat when I opened my support ticket. I got a response this morning that there is a 'known' bug (# 123134)...they are working on a 'fix', but no ETA.

[clott]

I recently upgraded 9.1.1.3 to 9.1.2.1 and found my report server down from friday at 10am until monday lunchtime.
The upgrade looked to have worked but failed to add a folder called updates and therefore would not run the program.

Once the site was working again, Every report that was scheduled became Undefined and will no longer run.
also, the custom group and all of my reports went AWOL so I have to spend the best part of a week recreating these reports from scratch (again).

btw,
I have also logged a service request to be able to have other users run my reports, to save everyone creating the same reports individually, which they no longer want to do
because they get trashed during every upgrade. After all Version 8 allowed us to all see reports created by an administrator.

[ArtBahrs]

Hullo,
I didn't know about (or encounter) the Updates Directory SNAFU....but yah... the reporter becoming "Undefined" is a known issue that I reported and had escalated about 2 rev's back...

Note there is a work around.... go to your "reports" screen ... the report will be there.... run it and schedule it again.... seems that after scheduling a report a second time it 'sticks'....

Now, having done the debuging without access to the source what I found was that during the scheduling process (read "code module" here) the report is placed into the schedule.cfg file with a "temporary" value for the report identifier rather than the actual report identifer... this means that the system does not think the report is to be run more than once at a "later date/time" than you created the report.

This is supposed to be fixed in 9.1.2.2 or later...I honestly have lost track of the current and pending versions... since I have had to upgrade the dang thing so often to fix the major things.

Art

[clott]

Hi Art,
I have just been given the same workaround you had, and they also mention the fix in is 9.1.2.2, sadly no ETA yet.

The trouble is that all of my reports were in a custom group, this group does not exist any longer and neither do the reports.
Therefore the only place you can see reference to the report is in the Scheduled reports group. each one being listed as undefined, the format and time scheduled.
If I try to run the report nothing happens.
The choices I have are View, Delete from schedule or Hide in group.

thanks for the info though.
Chris

[ReddBull]

9.1.3 should incorporate many fixes, and is tentatively due out mid to late August

[ArtBahrs]

Hi All,
Ok... I was told by my Escalation Manager that 9.1.3.x was released late yesterday...

On the issue of reports located in a group that no longer is there.... Did you get "down and dirty" in the command line? I found things by digging around in the command line that the GUI Interface no longer showed as existing.

Art

[ReddBull]

Just upgraded to 9.1.3.1 with no issues…so far. Reporter checks out healthy and the issues we had in the past *seem* fixed. Still testing...will update the board if I stumble upon a problem.

[ArtBahrs]

Hello All,
I wanted to let all know that we had a situation where when a user report was run/running that produced an extremely large (>47mb) PDF we had the actual program 'modified'!

The Roles Management Module (my term) was corrupted so that we were unable to get to the screen where we could Add/Edit/Delete Roles within Reporter 9.1.3.1. This also caused something to be changed in the user interface as users could no longer see any of the data!... We got back to "walking wounded" status, as I called it, by making everyone who *HAD* to use the Reporter an "Administrator".

Solution was a complete removal of Reporter 9.1.2.1 and reinstall from scratch - This was after first attempting to upgrade from 9.1.3.1 - our SE and Tech Support thought the upgrade would 'replace' the sections of the Reporter system that had been 'corrupted'.

Art