Issue with the Mid Server Installation. Below are the wrapper logs

Chandresh · ‎11-24-2015

I have double checked the Mid server user's credentials and Instance URL. don't know where is the gap

2015/11/24 12:49:17 | SNC EYNZ2 service installed.

2015/11/24 12:49:17 | Starting the SNC EYNZ2 service...

2015/11/24 12:49:17 | --> Wrapper Started as Service

2015/11/24 12:49:17 | Java Service Wrapper Standard Edition 64-bit 3.5.17

2015/11/24 12:49:17 | Licensed to ServiceNow for MID

2015/11/24 12:49:17 |

2015/11/24 12:49:18 | Launching a JVM...

2015/11/24 12:49:18 | WrapperManager: Initializing...

2015/11/24 12:49:19 | Logger for 'glide' has not been configured by the container, configuring now:

2015/11/24 12:49:19 | Configuring log handler: java.util.logging.FileHandler

2015/11/24 12:49:19 | Setting useParentHandlers=false for Logger 'glide'

2015/11/24 12:49:19 | Overriding formatter to: com.glide.util.DefaultLogFormatter (for handler: java.util.logging.FileHandler)

2015/11/24 12:49:22 | SNC EYNZ2 started.

2015/11/24 12:57:50 | JVM exited unexpectedly.

2015/11/24 12:57:55 | Launching a JVM...

2015/11/24 12:57:56 | WrapperManager: Initializing...

2015/11/24 12:57:57 | Logger for 'glide' has not been configured by the container, configuring now:

2015/11/24 12:57:57 | Configuring log handler: java.util.logging.FileHandler

2015/11/24 12:57:57 | Setting useParentHandlers=false for Logger 'glide'

2015/11/24 12:57:57 | Overriding formatter to: com.glide.util.DefaultLogFormatter (for handler: java.util.logging.FileHandler)

2015/11/24 13:39:55 | Machine is shutting down.

2015/11/24 13:41:23 | --> Wrapper Started as Service

2015/11/24 13:41:23 | Java Service Wrapper Standard Edition 64-bit 3.5.17

2015/11/24 13:41:23 | Licensed to ServiceNow for MID

2015/11/24 13:41:23 |

2015/11/24 13:41:24 | Launching a JVM...

2015/11/24 13:41:25 | WrapperManager: Initializing...

2015/11/24 13:41:27 | Logger for 'glide' has not been configured by the container, configuring now:

2015/11/24 13:41:28 | Configuring log handler: java.util.logging.FileHandler

2015/11/24 13:41:28 | Setting useParentHandlers=false for Logger 'glide'

2015/11/24 13:41:28 | Overriding formatter to: com.glide.util.DefaultLogFormatter (for handler: java.util.logging.FileHandler)

adamtrent · ‎02-29-2016

Did you figure this out?

Chandresh · ‎02-29-2016

Yes, it was because of the company's network security. I used different proxy settings and it is working fine now.