Flow Forensics report errors.

Document ID : KB000031754
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:

Whenever we try to use guest account to create a flow forensics report we get an error as below:

Server Error in '/RA' Application.
--------------------------------------------------------------------------------

NQS_BUS_03202: The specified name Flow Forensics Reports is already in used.
Description: An unhandled exception occurred during the execution of the current web request.
Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: NetQoS.Business.i18nEntityPropertyValidationException: NQS_BUS_03202:
The specified name Flow Forensics Reports is already in used.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information
regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[i18nEntityPropertyValidationException: NQS_BUS_03202: The specified name Flow Forensics Reports is already in used.]
NetQoS.ReporterAnalyzer.Business.ReportFolder.Persist() +449
NetQoS.ReporterAnalyzer.WebSite.Ctrls.FlowForensicsReportEdit.SaveReport(Boolean runReport) +255
NetQoS.ReporterAnalyzer.WebSite.Ctrls.FlowForensicsReportEdit.cmdRun_Click(Object sender, EventArgs e) +21
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +111
System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +110
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +36
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1565

Environment:  

All versions of NFA, All versions of Windows

Cause: 

The Guest account that had been created by the client only had User Privileges.

Resolution: 

Changing the Guest account to a Power User resolved the issue and the reports were created successfully.