Symptom
- Error message: "Invalid minute field value" appears in the e2emai.0.log file when enabling "Advanced" options in the Collection Interval for the Metric SSL Server Certificate Expiry Data collection.
- Metric remains gray and does not collect values.
- Error trace includes: "com.sap.smd.server.exec.strategy.cron.CronField.validate(CronField.java:149)" and "com.sap.smd.mai.configuration.parser.AdvancedSchedulerBuilder.buildAdvancedScheduler".
- we can see the following error in the e2emai.0.log file and the metric remains gray
[Thread[Thread-5,5,main]] Error [MetricConfigurationParser.parseConfiguration] Could not resolve metric group definition 00000000000000000001, entry is skipped.
[EXCEPTION]
com.sap.smd.mai.configuration.parser.ScheduleDefinitionException: [MetricConfigurationParser.buildAdvancedScheduler] invalid scheduler definition.
at com.sap.smd.mai.configuration.parser.AdvancedSchedulerBuilder.buildAdvancedScheduler(AdvancedSchedulerBuilder.java:114)
at com.sap.smd.mai.configuration.parser.MetricConfigurationParser.buildScheduler(MetricConfigurationParser.java:155)
at com.sap.smd.mai.configuration.parser.MetricConfigurationParser.buildMetricGroup(MetricConfigurationParser.java:140)
at com.sap.smd.mai.configuration.parser.MetricConfigurationParser.parseConfiguration(MetricConfigurationParser.java:104)
at com.sap.smd.mai.configuration.MetricConfigurationMgr.loadConfiguration(MetricConfigurationMgr.java:128)
at com.sap.smd.mai.MAIService.load(MAIService.java:120)
at com.sap.smd.mai.MAIService.init(MAIService.java:99)
at com.sap.smd.mai.MAIServiceFactory.getInstance(MAIServiceFactory.java:108)
at com.sap.smd.mai.MAIServiceFactory.getService(MAIServiceFactory.java:102)
at com.sap.smd.core.plugin.service.ServiceEntityHandle.getObjectAs(ServiceEntityHandle.java:191)
at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.getObjectAs(PseudoEntityHandle.java:140)
at com.sap.smd.om.impl.broker.ObjectProxyImpl._getObjectAs(ObjectProxyImpl.java:627)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.getObjectAs(ObjectProxyImpl.java:574)
at com.sap.smd.core.plugin.service.ServiceContextImpl.getService(ServiceContextImpl.java:62)
at com.sap.smd.mai.MAIServiceFactory.init(MAIServiceFactory.java:60)
at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:114)
at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:234)
at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:308)
at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:146)
at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:468)
at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:366)
at com.sap.smd.core.runtime.Runtime.run(Runtime.java:57)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.runStarterPlugin(SMDAgeletsRuntimeContext.java:110)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.startApplications(SMDAgeletsRuntimeContext.java:158)
at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:573)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:241)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:483)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:282)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:759)
at java.lang.Thread.run(Thread.java:836)
Caused by: java.lang.IllegalArgumentException: Invalid minute field value
at com.sap.smd.server.exec.strategy.cron.CronField.validate(CronField.java:149)
at com.sap.smd.server.exec.strategy.cron.CronField.<init>(CronField.java:79)
at com.sap.smd.server.exec.strategy.cron.CronMinuteField.<init>(CronMinuteField.java:32)
at com.sap.smd.server.exec.strategy.cron.CronEntry.<init>(CronEntry.java:148)
at com.sap.smd.mai.configuration.parser.AdvancedSchedulerBuilder.computeTimeExpression(AdvancedSchedulerBuilder.java:419)
at com.sap.smd.mai.configuration.parser.AdvancedSchedulerBuilder.buildWeeklyInterval(AdvancedSchedulerBuilder.java:370)
at com.sap.smd.mai.configuration.parser.AdvancedSchedulerBuilder.buildWeeklyScheduler(AdvancedSchedulerBuilder.java:340)
at com.sap.smd.mai.configuration.parser.AdvancedSchedulerBuilder.buildAdvancedScheduler(AdvancedSchedulerBuilder.java:101)
Read more...
Environment
- SAP Solution Manager 7.2
Product
SAP Solution Manager 7.2
Keywords
invalid minute field value, advanced scheduler, collection interval, metric configuration, SSL Server Certificate Expiry, e2emai.0.log, gray metric, data collection error, advanced options, SAP Web Dispatcher 7.1 and higher. , KBA , SV-SMG-MON-ALR-CFG , Alert / Metric Configuration , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview