PureEngage On-Premises

Hi all,

Reporting server won't start with the following error:

>>
GVP Reporting Server initialization error, please verify your configuration. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mfService' defined in class path resource [mf.config.xml]: 9 constructor arguments specified but no matching constructor found in bean 'mfService' (hint: specify index and/or type arguments for simple parameters to avoid type ambiguities)
Related cause: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'mfService' defined in class path resource [mf.config.xml]: Unsatisfied dependency expressed through constructor argument with index 2 of type [int]: Could not convert constructor argument value of type [java.lang.String] to required type [int]: Failed to convert value of type [java.lang.String] to required type [int]; nested exception is java.lang.NumberFormatException: For input string: ""
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mfService' defined in class path resource [mf.config.xml]: 9 constructor arguments specified but no matching constructor found in bean 'mfService' (hint: specify index and/or type arguments for simple parameters to avoid type ambiguities)
Related cause: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'mfService' defined in class path resource [mf.config.xml]: Unsatisfied dependency expressed through constructor argument with index 2 of type [int]: Could not convert constructor argument value of type [java.lang.String] to required type [int]: Failed to convert value of type [java.lang.String] to required type [int]; nested exception is java.lang.NumberFormatException: For input string: ""
<<<

Anyone have an idea what the "mfservice" error represent?

Hello:

A couple customers had this same problem, and one customer rebooted their server and the error went away.  Another customer had connectivity problems to their Configuration Server, and once that was resolved this error went away.  

If these two suggestions do not resolve your issue please open a case and provide logs and details to Genesys Customer Care.

Thank you,

Kevin Haselhuhn