I would check the IIS config and make sure that ASP.NET v2 is set to allowed and not prohibited.

I checked it and it is "Allowed".

Hello,

Has anyone else had this problem? We are currently seeing the same thing and I was wondering who else may have some ideas?

thanx,

Travis

I will admit that FSA Reporting is a challenge to get working properly. What I would suggest is that your firstly take a look at the following troubleshooting document and if you get no further that raise a case with support:-

ftp://exftpp.symantec.com/pub/support/products/Enterprise_Vault_File_System_Archiving/288460.pdf

Also try registering the FSAReporting virtual directory by following command and then with restarting IIS:-  <System Drive>\Windows\Microsfot.NET\Framework\v2.0.50727\aspnet_regiis –s “W3SVC/1/Root/FSAReporting”

Are you running SQL 2005 SP3 by chance?  It's not supported just yet.

A coworker just told me of a problem he has with FSA reporting and he discovered that his issue was caused by the SQL 2005 server being patched to SP3.  He backed up his DBs, uninstalled then reinstalled SQL 2005 and patched to SP2, then restored the DBs and that solved his problems.

Hey Guys,

Thanks for the info, I did check and we are running SQL 2005 sp2. The only big diff between the prod and dev sites is that reporting server in dev is 32 bit and the prod is 64 bit OS. Which brings me to another question, I know that the 64 bit reporting svr needs to run the x32 .net2 but does is also have to have x32 .net 1.1? At this time it only has x32 .net 2.0... So to recap when I try to enable collections for fsa reporting the mmc usually crashes and when it doesnt crash it just does not retain the settings.

Thanks,

Travis

Hi Paul

I will look into this as well. We currently have an open case which has been sent to back line but we are not hearing back as of yet.  So I thought that I would poke around a bit in the meantime.

Thanks,

Travis