The following symptoms are commonly seen in conjunction with this scenario:
- SEPM scheduled reports and notification conditions don't generate, and aren't sent to my Administrator as expected
- Custom notification conditions don't trigger
- When I log into the SEPM manager, it's successful but yet I still see the following errors:
The administrator's user name or password is incorrect. Type a valid user name or password.
You cannot access this server from this IP address.
From SEPM > Monitors > System > Server Activity, the following can be seen:
...
8/13/2025 11:55 Error An unexpected exception has occurred The administrator's user name or password is incorrect. Type a valid user name or password. Authentication failure, please retry. Authentication failure, please retry. "com.sygate.scm.server.util.ServerException: The administrator's user name or password is incorrect. Type a valid user name or password. at com.sygate.scm.server.task.ScheduledReportingHelper.doReportingLogin(ScheduledReportingHelper.java:558) at com.sygate.scm.server.task.ScheduledReportingTask.execute(ScheduledReportingTask.java:462) at com.sygate.scm.server.task.MonitoredTimerTask.run(MonitoredTimerTask.java:56) at java.base/java.util.TimerThread.mainLoop(Timer.java:556) at java.base/java.util.TimerThread.run(Timer.java:506) "
8/13/2025 11:55 Error Scheduled reporting failed The administrator's user name or password is incorrect. Type a valid user name or password.
8/13/2025 11:55 Error An unexpected exception has occurred You cannot access this server from this IP address. You cannot access this server from this IP address. Admin access denied. "com.sygate.scm.server.util.ServerException: You cannot access this server from this IP address. at com.sygate.scm.server.consolemanager.SRAuthenticator.authenticate(SRAuthenticator.java:99) at com.sygate.scm.server.consolemanager.requesthandler.LoginHandler.doLogin(LoginHandler.java:876) at com.sygate.scm.server.consolemanager.requesthandler.LoginHandler.getCredential(LoginHandler.java:271) at com.sygate.scm.server.consolemanager.requesthandler.LoginHandler.handleRequest(LoginHandler.java:187) at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:354) at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:170) at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:151) at javax.servlet.http.HttpServlet.service(HttpServlet.java:555) at javax.servlet.http.HttpServlet.service(HttpServlet.java:623) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) at com.sygate.scm.pool.HttpResponseFilters.doFilter(HttpResponseFilters.java:129) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) at com.sygate.scm.server.servlet.ConsoleFilter.doFilter(ConsoleFilter.java:86) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) at org.apache.catalina.core.StandardWrapperValve.invoke(S"
...
scm-server-x.log:
On Prem SEPM Manager (SEPM) 14.3 RU8 and later
Starting with 14.3 RU8, server's with multiple NICs "present" hosting the SEPM manager have observed issues with SEPMs ScheduledReportingTask.
Disable any extra NICs that are "present" AND currently "not connected" or "down" to force the SEPM manager to use the NIC that is "up" instead for best results.
CRE-19154 / CRE-18521