Broken Fixlets after BES 8 Upgrade

Reporting
1

(imported topic written by MattBoyd)

It looks like some of our Web Reports filters were broken after the upgrade to BES 8. Particularly, I’m seeing errors for filters that are by group. The filters show this error:

Unknown Group: bes.server.com/ActionSite (bes.server.com)/21083

Any ideas as to what happened?

Edit: Sorry for the misleading title… I meant Filters.

2

(imported comment written by MikeOttum)

Hi boyd,

I’m sorry you’re running into this error. By chance, did you change the database name in Web Reports when you upgraded?

Thanks,

Mike

3

(imported comment written by MattBoyd)

Hey Mike,

I don’t think the database name changed… it’s still BESReporting in our SQL instance, which I believe is the default. The server address/DNS name definitely didn’t change. However, we are hosting Web Reports on a separate server from the BES root server. I swapped out the real DNS name with bes.server.com in the example I provided.

Another thing I discovered today is that the “restrict view by console operator” behavior has changed. As far as I can tell, you could always get to the property results of a locally activated analysis in 7.2, regardless of what user activated the analysis. However, now it looks like the results aren’t available unless the analysis was activated by the console operator account that you’re using to restrict a user’s view.

Since we create one console operator account for multiple users that need web reports access, this is kind of a bummer. It looks like we’ll be able to create a filtered view that will work, but this seems counter-intuitive…

4

(imported comment written by MikeOttum)

Hi boyd,

I think that changing the server name in the Web Reports database entry caused this problem. Web Reports uses the database name (from the “Edit Database” page in Web Reports, not “BESReporting” or “BFEnterprise”) as part of the ActionSite identifier. It is the “bes.server.com” portion of “bes.server.com/ActionSite (bes.server.com)/21083”. So, if “bes.server.com” changed when you migrated to the new server (as I assume it did), then that would explain this error. This is a known bug in Web Reports.

To fix this problem, you can either rename your database in Web Reports by removing it and re-adding it with the old name, or you can delete the problematic filter(s) and recreate them.

Please let me know whether this fixes your problem or not.

Again, sorry that you’re running into this error. I hope we can get you working again quickly.

Mike

5

(imported comment written by MattBoyd)

Hey Mike,

I just checked and that database name did not change. The only thing that may have changed was the casing (maybe it was capitalized instead of lowercase?). Is there any way I can verify this, since we don’t have Web Reports 7.2 anymore?

6

(imported comment written by MikeOttum)

boyd,

If you send me your email address (via the email link under my name) I can send you a Perl script that will detect which database names are being used in your BESReporting database. This will let us know definitively whether that is the problem or not.

Thanks,

Mike

7

(imported comment written by MikeOttum)

Hi boyd,

Are you still having this problem?

Thanks,

Mike

8

(imported comment written by MattBoyd)

Hey Mike,

Sorry for not contacting you yet. Yes, we’re still seeing the issue, and I’d still like to take you up on your offer to send me that script to detect what the database names are.

Could you send me your e-mail address? It looks like it’s listed as private in your profile.

Thanks,

Matt