IMPORTANT NOTICE: As of 21 February, anything posted in this community WILL NOT BE MIGRATED to our new community site. We have pulled all user information and data from this site and are now in an approximately week long process of importing users, roles, and data to our new site. We are leaving this site open and active so you can post and hopefully get a response until the migration is complete. Once complete, the URL that currently takes you to this site will take you to our new site so your bookmarks will work as always. Please read the information on a New Login Process
When running the Batch Refresh Process (BRP) in Enterprize Analyzer, the following error occurs ...
Unhandled Exception : System.FormatException: Input String was not in a correct format.
at System.Number.StringToNumber<String str, NumberStyles options, NumberBuffer& number, NumberFOrmatInfo info, Boolean parseDecimal>
at System.Number.ParseInt32<String s,NumberStyles style, NumberFormatInfo info>
at runBRP.Context.LoadParamsFromFile<String sFile>
at runBRP.Program.Main<String args>
What is the cause of this and how can it be rectified?
When the BRP is configured from the Enterprise Analyzer Administration tool, the BRP.ini file is generated using the User Interface.
The contents of an example BRP.ini , from the Spanish customer, is below and contains an invalid entry (highlighted) which caused the failure reported.
Debug = 1
RMWInstallPath = C:\Program Files (x86)\Micro Focus\Enterprise Analyzer
BRPInstallPath = M:\MFA\BRP_LCMM
BRPRunType = Master
Site = client Workspace
Dir = M:\MFA\LCMM
ObsoleteProcessing = 0
RunIMSAnalysis = 0
RestoreIndices = 1
RunExecReport = 0
RunWebGen = 0
LaunchHCC = 1
DropInd = Auto
WaitHCCBefore = No
WaitHCC = 15
ExtraHCC = 1
GeneratePCF = both
The problem entry is "CleanQueue =Verdadero"
The entry should contain either "CleanQueue =True" or "CleanQueue =False"
Although "Verdadero" is Spanish for True, the process objects and the BRP batch run fails.
Correct the entry to either "CleanQueue =True" or "CleanQueue =False" and re-run the BRP process again
Incident # 2618495