Can not Access to Content Manager

• Time it when you restart Apache Tomcat service and open Content Manager so easily point out errors
  • Restart Apache DDHHMM
  • Open Content Manager DDHHMM

1. Disable Antivirus software.
2. Access CM from server locally. Ex. http://localhost:8080/ContentManager
   • Default:C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Scala Enterprise Content Manager
   • Click on Access Scala Enterprise Content Manager.

1. Check Performance. Access to the server>Task Manager>Performance>Open Resource Monitor

• If CPU utilization is high like 100%, check which process is high.

1. Open Event Viewer>Check Errors in Administrative Events and System.
   • Find HDD, SSD and memory related issues.

1. Open Services. Check Status of Apache Tomcat, PostgreSQL (Microsoft SQL server) and Scala Transmission Server service. Status should be "Running".

• If you can not start Apache Tomcat service, Check Can not start Apache after Java update.

1. ContentManager logs.
   • Check ContentManager logs
     • If a player sends a wrong password, users which are behind a router will be banned.
       • Data user 'player_XXX' provided wrong password. IP-address = 203.156.XXX.XXX (attempt #794)
         • IPBlacklister : User with IP [203.156.XXX.XXX] banned for 4770 seconds
         • Did you change the player username or password? Please change it to the previous settings.

• Restart Apache Tomcat Service. (It will take a while)
• Check Tomcat logs. C:\Program Files\Apache Software Foundation\Tomcat 7.0\logs
• Check newest errors in below logs
  • --- catalina.xxxx-xx-xx
  • --- commons-daemon.XXXX-XX-XX.log
  • --- localhost.xxxx-xx-xx
  • --- tomcat7-stderr.xxxx-xx-xx
  • --- tomcat7-stdout.xxxx-xx-xx

1. Re-run the Content Manager installer or updater (Your current CM version)>Next>Use existing installation settings>Confirm access

1. If you are in the middle of an update installation where there is a database update pending you need remove the Content Manager config.xml file. Restart the Apache Tomcat, and Scala Transmission Server services.
   1. Windows XP or Windows Server 2003: (default path) C:\Documents and Settings \All Users\Application Data\Scala\InfoChannel Content Manager 5\Conf\Config.xml
   2. Windows 7 or Windows Server 2008 R2: (default path) Select Computer > Local Disk (C) > ProgramData > Scala > InfoChannel Content Manager 5 > Conf > Config.xml
2. Corrupted database
   1. Restore the database in a test environment.
      • if it does not work, restore an old database which was working fine.
   2. Send database backups to support.

Content Manager indeed implements an account lockout policy.

• Restarting Apache Tomcat resets the lockout. If a player is the problem, disconnect the player from network.
  • If a player sends a wrong password, users which are behind a router will be banned.
• Content Manager adds a 30-second hold-off after 5 successive failures. This increases by 30 seconds after every five additional failures. This amounts to 2.5 minutes for 10 failures, 15 minutes for 20 failures, and over an hour for 40 failures, and almost 8 hours for 100 failed attempts. An attempt is not counted if the same incorrect password is used as the previous attempt.
• Also, the logic is not to count repeated attempts with the same bad password. This is important so that Players that are misconfigured (therefore repeatedly try the same wrong password) don’t get banned. However, that exception is not really needed for user-logins, and can lead a penetration-tester to conclude that we don’t in fact have anti-breakin defenses.
  • REL11.01 change: Repeat attempt to login with the same login/password on a user account will go towards a lockout. However, for a player account, they will not be locked out as long as they repeat the same login/password sequence.
  • REL11.05 planned change: add the IP address in the logging message.Sep 6