MID Server Service Starts but MID Server Status shows as Down - Unable to unsecure parameter mid.instance.password: Problem while decryptingDescriptionMID Server Service Starts but MID Server Status shows as Down. When starting your MID Server you see the following in the agent log: 03/28/19 08:20:53 (707) MIDServer SEVERE *** ERROR *** Unexpected exception, terminating the MID server java.lang.RuntimeException: Unable to unsecure parameter mid.instance.password: Problem while decrypting at com.service_now.mid.services.Config.getProperty(Config.java:509) at com.service_now.mid.services.Config.getProperty(Config.java:535) at com.service_now.mid.services.Config$InstanceConnectionConfig.getUserPassword(Config.java:843) at com.service_now.mid.Instance.getUserPassword(Instance.java:537) at com.service_now.mid.Instance.setupFactory(Instance.java:486) at com.service_now.mid.Instance.init(Instance.java:74) ...at org.tanukisoftware.wrapper.WrapperStartStopApp.run(WrapperStartStopApp.java:405) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalStateException: Problem while decrypting at com.glide.util.AESCodec.decrypt(AESCodec.java:227) at com.service_now.mid.services.config.DefaultMidServerEncrypter.decrypt(DefaultMidServerEncrypter.java:63) at com.service_now.mid.services.config.DefaultMidServerEncrypter.decrypt(DefaultMidServerEncrypter.java:45) at com.service_now.mid.services.config.DefaultSecuredConfigProvider.unsecuredParameterValue(DefaultSecuredConfigProvider.java:54) at com.service_now.mid.services.Config.getProperty(Config.java:506) ... 31 moreRelease or EnvironmentAll currently supported environments.CauseThere is a problem with the password in the config.xml file.ResolutionOpen the config.xml file2. Re enter the user's password. (By default, this will be encrypted after you restart the service) Start or Restart the MID Server service. If you get the same error message after following the above steps, and you are sure the password is correct: Stop the serviceRun agent/bin/UninstallMID-NT.batRun agent/bin/InstallMID-NT.batStart service What you should be seeing from a normal startup without this issue is as follows: 03/26/19 11:37:40 (297) MIDServer Creating injector...03/26/19 11:37:40 (815) MIDServer Using configuration: C:\ServiceNowTemp\agent\config.xml03/26/19 11:37:40 (925) MIDServer Logger config: root=INFO03/26/19 11:37:40 (925) MIDServer Refreshing LoggerFactory cache03/26/19 11:37:41 (018) MIDServer Loaded credentials provider: com.service_now.mid.keypairs.provider.standard.StandardKeyPairsProvider03/26/19 11:37:41 (034) MIDServer ThreadPool-Interactive started with corePoolSize: 10, maxPoolSize: 10, maximumQueueSize: 4003/26/19 11:37:41 (034) MIDServer ThreadPool-Expedited started with corePoolSize: 20, maxPoolSize: 20, maximumQueueSize: 40003/26/19 11:37:41 (034) MIDServer ThreadPool-Standard started with corePoolSize: 25, maxPoolSize: 25, maximumQueueSize: 50003/26/19 11:37:41 (034) MIDServer ExtensionContainer ThreadPool started with corePoolSize: 25, maximumPoolSize: 25, maximumQueueSize: 50003/26/19 11:37:44 (837) MIDServer Setting basic authentication with user admin03/26/19 11:37:45 (134) MIDServer MIDCredentialsConfigProvider initialized with com.service_now.mid.creds.provider.standard.StandardCredentialsProvider03/26/19 11:37:45 (244) MIDServer MID Server starting03/26/19 11:37:45 (275) MIDServer Agent home path: C:\ServiceNowTemp\agent03/26/19 11:37:45 (478) MIDServer MID Server started