Web Reports 8.0.584 - HELP - Report failing since upgrade to v8

Usage and Config Platform
1

(imported topic written by nberger91)

After upgrading to the latest release of Server/Webreports, a previous report returning standard RP’s is now failing. If i (re)create the report by selecting ‘Explore Data’ --> ‘Edit Columns’ then select approx 20 Properties. I get the following error displayed in red font. If i reduce the number of columns (properties) it works. Any Ideas ?

JavaScript Error

“Failed GET request to sort=R-Computer%20Name&dir=asc&startIndex=0&results=50&c=R-Computer%20Name&c=C%2FOS%2520Type%2FYul2G0xJ9gmKgvWj9tWRvZFGvYM&c=C%2FOpen%2520Port%2520Query%2520-%2520VNC%2F4SRHuV9gUcRaZ1mxtPgnJAZpg6E&c=C%2FOpen%2520Port%2520Query%2520-%2520SNMP%2FuNiQdJwtbqdmgnSbFybhVrfo4NU&c=C%2FOpen%2520Port%2520Query%2520-%2520SMTP%2FJdlBqQkYsLU8qublEpj0tkcnTPg&c=C%2FOpen%2520Port%2520Query%2520-%2520POP3%2F30LXGST2dV4BPUmb2V%252fYg6LTFLY&c=C%2FOpen%2520Port%2520Query%2520-%2520HTTP%2FZdDZ56iSYElAU7NPz0awA2%252f2jkk&c=C%2FOpen%2520Port%2520Query%2520-%2520FTP%2FetU%252fT9XZff3JFMvEJv5mYHBLe2s&c=C%2FOpen%2520Port%2520Query%2520-%2520FINGER%2FoWeVatDxofDx2hYckpIcvk%252f%252brrY&c=C%2FNumber%2520Of%2520Relevant%2520Moderate%2520Hotfixes%2FwuXdrM0%252fSxIBGhqxxW1J%252br8aomk&c=C%2FNumber%2520Of%2520Relevant%2520Low%2520Hotfixes%2FMtCfQOPTtNQw3MMXVUfehksY2BQ&c=C%2FNumber%2520Of%2520Relevant%2520Important%2520Hotfixes%2FiYpmqn%252bYk7koSG69uBc7EugZT7k&c=C%2FNumber%2520Of%2520Relevant%2520Critical%2520Hotfixes%2FmzDTLRoVPLO7KDgoFqdPAvZ%252b2rU&c=C%2FNon-Windows%2520Computers%2FGKhl%252bY70E3jl9lpbaTO69cE3DE0&c=C%2FLast%2520Logged%2520in%2520User%2F16ERdfoBavN0yAKiApxPYwS5y5k&c=C%2FIs%2520Laptop%2FCYriq15OLjdl%252fCemWQ3BP39XacY&c=C%2FIM%2520Connected%2520Backup%2520Agent%2520Installed%2FB%252b1CJbo97yUtjikMjQbtMkuBVzg&c%2FFree%2520Space%2520on%2520System%2520Drive%2FDbC2t%252boHeBfa5Ij2MK%252b5xLmeM%252f0&c=C%2FFile%2520System%2520Type%2FND1VlwMmxTJcyarjp%252fimL3avtg8&c=C%2FEncryption%2520Status%2FwycRuV791sdyytTy43HsSwr3tz8&c=C%2FComputer%2520Type%2FwUzFAyQPtWOfCeKEuIRlQ5r0S90&c=C%2FComputer%2520Serial%2520Number%2FOBNQx9g4PeAGoZ%252fIB2E0EzDMlEA&c=C%2FComputer%2520Model%2FwUzFAyQPtWOfCeKEuIRlQ5r0S90&c=C%2FAltiris%2520Agent%2520Service%2520Status%2FYGsiufIRma%252b3laexkJY6y%252bdMzSE&c=R-Active%20Directory%20Path&c=C%2F64bit%2520OS%2520Type%2F2DBQH3DljdAVjzyc%252fvCEA3aVBoc&c=R-IP%20Address&c=R-OS&c=R-CPU&c=R-Last%20Report%20Time: Internal Server Error”

2

(imported comment written by nberger91)

Can anyone recreate this frustrating issue ?

BTW… my server is a 2003 Ent. VM running SQL 2005 32bit.

Thanks …

3

(imported comment written by MikeOttum)

Hi nberger,

I think this might be an issue with browser truncation of GET requests. What browser type and version are you using?

Thanks,

Mike Ottum

Platform Infrastructure Manager - BigFix

4

(imported comment written by nberger91)

It fails on Win7 IE8.0.7600.16385, Win2003 IE IE8.0.600.18702, and Firefox 3.6.8

Attached screenshot. Occurs when between 25 and 30 random column are added

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)

Timestamp: Wed, 18 Aug 2010 07:05:50 UTC

Message: Exception thrown and not caught

Line: 1

Char: 34

Code: 0

URI: http://servername.companyname.corp/JavaScript/Util/Run-min.js?modified=3363956366

Thanks.

5

(imported comment written by MikeOttum)

We’ve been investigating this issue and have found a workaround. If you use filters in any way, it will avoid this error. If you don’t want to filter anything, you can simply click the “-” button to remove the filter template and you should be able to build your report from there. For any existing reports, you will need to use the filter workaround and rebuild the report.

I’m very sorry you encountered this bug. We are working hard to get a permanent fix implemented.

Please let me know if the workaround doesn’t solve your problem.

6

(imported comment written by nberger91)

Hi Mike, this workaround doesnt work for me. Ive tried adding a filter, and removing the filter on a new report. Exactly the same error.