Errors in report field of WSUS.

I'm not the most qualified to answer this question, but it seems it may be an issue with the accounts associated with generating the reports. I believe the reports are generated and stored by a sql database that WSUS works with, so check the SQL groups to make sure they have proper administrative rights.
To that extent, I'm not positive but it could also be the rights of the user your logged in as on the machine, but I think that is unlikely.

Ok, now I can't even connect to the server in the WSUS admin console.  I should have said this earlier but this is on a DC.  When I try to connect to the server in WSUS snap in I get the following pop up window.

Cannot connect to 'FV-GR'.  You do not have the permissions required to access this WSUS server.

I'm a member of the security group who is a member of WSUS Admin and WSUS reporters groups.  I've also added my user account to both of those WSUS groups.  So I should not be getting this error.  I've read some forums that say accounts need to be added to those WSUS groups in the local account but its a DC so I don't have that option.

side question...does sql server need to be installed on this machine?  I don't see it as a requirement but it seems like it would need to be on there.

Well I resolved the second issue (found it at this link about 3/4 of the way down http://forums.techarena.in/showthread.php?s=551a4348b1ad16263e8d1a47a13f47da&t=811268), but I am still unable to view the reports.  Still getting the;
An error occurred during local report processing.
An error occurred during rendering of the report.
An error occurred during rendering of the report.
Font 'Arial' does not support style 'Regular'

andrewc...I'm not that familiar with sql...are they sql groups located in AD?  The SQL groups I have are below.

SQLServer2005MSSQLUser$FV-GR$MICROSOFT##SSEE
SQLServer2005MSFTEUser$FV-GR$MICROSOFT##SSEE

I've added both of these users to the WSUS admin and reporters to see if this will help.

Also I don't have a MSSQL$WSUS service, its not even listed.  So I'm assuming I'm missing a piece of the install or SQL needs to be installed.

I'm doing some research on it right now, I'm sorry that I'm not the most qualified but I'm gonna try to help anyway. Have you attempted to run a report while logged in as a domain admin? This may come down to a re-install also so make sure you have the latest release (since you just installed it I'm assuming that to be true)

I'll get back to you when I find out some more info.

You probably chose to use Microsoft's free database "MSDE" when you installed. You do not need to install SQL.

How about some more info. Was this a clean install or did you upgrade from WSUS 2.0? Is your account a domain admin/local admin?

After snooping around a bit, I think I'm on the right track with the initial error. It has popped up in other programs too. Check out: http://forums.visualtour.com/showthread.php?p=1591
I think the fix they have is only for that specific software though, so I'm searching for one that will fix it in MSDE/WSUS

Don't worry about not being the most qualified because I'm obviously not qualified to even run this app. This is a clean install and not an upgrade.  My account is a member of the domain admins group and I also threw myself in the WSUS admins group just to see if that would work.
I ran that font fix, it requires a reboot.  I'll have to reboot it tonight.  

Ah ok. Well hopefully that fix does the same thing, but it may not be designed for your version of windows. Either way if you do copy over the Arial.ttf file, you will need to reboot before it takes affect.

Holy crap...you have to be kidding me.  There was an arial.ttf shortcut that was linked to a folder on a network drive that isn't there any more.  I recreated that folder and copied the arial.ttf file from my computer over to that folder.  Went into WSUS console and the reports started running like a dream.  Who would've thought a stupid little font file would hose a whole application.  

Thanks a lot for your help, If I was near you I'd give you a high 5.

Digital high 5!

Haha no problem. That was a fun one! We bounced from security to database problems .... to a simple font fix. Good reference for future problems of that sort.