File System Archiving (FSA) Reporting scan on FSA Agent server fails to start properly. Client.GetConfigurationParameters function errors with Exception.

Article:TECH59075  |  Created: 2008-01-03  |  Updated: 2011-03-23  |  Article URL http://www.symantec.com/docs/TECH59075
Article Type
Technical Solution

Product(s)

Environment

Problem



File System Archiving (FSA) Reporting scan on FSA Agent server fails to start properly. Client.GetConfigurationParameters function errors with Exception: Server was unable to process request. ---> Unexpected end of file while parsing Name has occurred. Line 1, position 2048.


Error



Exception: Server was unable to process
request. ---> Unexpected end of file while parsing Name has occurred. Line 1, position 2048.


Solution



During the File System Archiving Reporting data gathering process, the first step for the FSA Agent server is to get the configuration parameters from the Enterprise Vault server. This process will current fail if the configuration parameters exceed 2048 characters.

Dtrace of the FSAReportingservice process on affected FSA Agent servers will show:

(FSAReportingService)  <5316>  EV-H       {CLIENT.EN_US} Exception: Server was unable to process request. ---> Unexpected end of file while parsing Name has occurred. Line 1,
position 2048. Info: Diag: Type:System.Web.Services.Protocols.SoapException ST:  at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean asyncCall)|   at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName,
Object[] parameters)|   at
FSAReportingClient.ReportingServer.ReportingServer.GetConfigurationParameters(String
strDomainName, String strServerName)|   at
FSAReportingClient.Client.GetConfigurationParameters(String DomainName, String
ServerName)

Invocation of the GetConfigurationParameters function from the FSA Reporting Web Service page:
http://EVServer_Name/FSAReporting/FSAReporting.asmx will result in the same error.

System.Xml.XmlException: Unexpected end of file while parsing Name has occurred.
Line 1, position 2048.

  at System.Xml.XmlTextReaderImpl.Throw(Exception e)
  at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
  at System.Xml.XmlTextReaderImpl.Throw(Int32 pos, String res, String arg)
  at System.Xml.XmlTextReaderImpl.ParseQName(Boolean isQName, Int32
startOffset, Int32& colonPos)
  at System.Xml.XmlTextReaderImpl.ParseAttributes()
  at System.Xml.XmlTextReaderImpl.ParseElement()
  at System.Xml.XmlTextReaderImpl.ParseElementContent()
  at System.Xml.XmlTextReaderImpl.Read()
  at System.Xml.XmlWriter.WriteNode(XmlReader reader, Boolean defattr)
  at System.Xml.XmlReader.ReadOuterXml()
  at
KVS.EnterpriseVault.FSAReportingServerWebService.ReportingServer.GetConfiguratio
nParameters(String strDomainName, String strServerName)

Workaround
1. Volumes for the FSA Agent Server currently selected for reporting will need to be de-selected. Enough volumes must be de-selected to get under the 2048 character limit.

2. The volumes de-selected in step 1 will also need to be removed from the ROConfiguration table in the EnterpriseVaultFSAReporting database.

3. Internet Information Services (IIS) on the Main Enterprise Vault server will need to be cycled.


Solution:
This issue has been addressed as part of the following release:

Symantec Enterprise Vault 2007 Service Pack 3 (SP3)
 http://entsupport.symantec.com/docs/304217
 

Supplemental Materials

Value1189561
Description

FSAReporting - select getconfigurationparameters FSAReporting.asmx error: Unexpected end of file while parsing Name has occurred



Legacy ID



302098


Article URL http://www.symantec.com/docs/TECH59075


Terms of use for this information are found in Legal Notices