HPE Software Products: Mobile Center
Share |

Hp mobile center authentication issueOpen in a New Window

I have succesfully installed the trial version of HP mobile center in my local machine but could not logoin . It says the username or password incorrect. PLease help me with the authentication issue what credentials to be given.

 

HPE Sprinter: A Run session cannot be startedOpen in a New Window

Hello All,

I am getting this error "Failed to lock the mobile device" when I am trying to to connect Mobile Center Server using Sprinter.

Please help me.

 

Defect Tracking System Settings in Sprinter for JIRA.Open in a New Window

Error:- Failed to login to DTS with given project settings User does not have permissions to create issues.

I am trying to connect JIRA Defect Tracking System using Sprinter and i am facing this issue please help me for this error.

 

 

Failed connecting to mobile server through Sprinter.Open in a New Window

Timeout occurred , unable to complete an operation (checking connection to HPE Mobile Center ) within the allotted time (90 second).

Please help me on this error.

 

 

Mobile Center AWS DeviceFarm Integration - Error Code 2036Open in a New Window

Hi,

I am trying to solve this almost for one whole week. I would really appreciate any kind of help :-).

I am using HPE Mobile Center, HPE UFT and AWS DeviceFarm to test apps.

To build my infrastructure I followed the official tutorials which can be found here: http://mobilecenter.hpe.com/Content/AWS%20installation.htm

My IP-Adress of HPE MC is whitelisted and it can connect to AWS DeviceFarm. 

All of my tests work perfectly without AWS DeviceFarm. However, If I follow the tutorial to run a test on one of the emulated devices on AWS DeviceFarm, I receive the error code 2036. The odd thing is, that the connection between UFT -> MC -> AWS DeviceFarm works, but right before the test is started, I receive that error.

I attached a screenshot of that error this post.

What does that error code 2036 mean?

Thank you!! 

Best Regards,

mk_1992

 

Exception occurred on Open application in HPE mobile centerOpen in a New Window

I got exception when I click "OK" button after finishing required fields on "Open application in HPE mobile center" popup window, please see details as below:

 

at PackageServicesLib.IPackageServices3.ExeService(Guid& ServiceGroup, UInt32 ServiceID, Object& ServiceParams, Object& Result)
at HP.QTP.BackEndServices.Services.Mobile.MobileService.ExecuteMobilePackageService(UInt32 serviceId, Object data)
at HP.QTP.BackEndServices.Services.Mobile.MobileService.ConvertMobileHR2Str(Int32 hr)
at HP.QTP.MobileCenterSettings.Dialog.MobileCenterSettingsViewModel.HandleLaunchAppServiceComExceptionHResult(Int32 hResult)
at HP.QTP.MobileCenterSettings.Dialog.MobileCenterSettingsViewModel.SetAndSaveSettings()
at HP.QTP.MobileCenterSettings.Dialog.MobileCenterSettingsControl.OkAction()
at HP.QTP.MobileCenterSettings.Dialog.MobileCenterSettingsDialog.OkAction(CustomDialog obj)
at HP.Utt.UttDialog.DialogButtonInfo.DialogButtonContinueCommandExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.Input.CommandBinding.OnExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.Input.CommandManager.ExecuteCommandBinding(Object sender, ExecutedRoutedEventArgs e, CommandBinding commandBinding)
at System.Windows.Input.CommandManager.FindCommandBinding(CommandBindingCollection commandBindings, Object sender, RoutedEventArgs e, ICommand command, Boolean execute)
at System.Windows.Input.CommandManager.FindCommandBinding(Object sender, RoutedEventArgs e, ICommand command, Boolean execute)
at System.Windows.Input.CommandManager.OnExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.UIElement.OnExecutedThunk(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.Input.ExecutedRoutedEventArgs.InvokeEventHandler(Delegate genericHandler, Object target)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated)
at System.Windows.Input.RoutedCommand.ExecuteCore(Object parameter, IInputElement target, Boolean userInitiated)
at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
at System.Windows.Controls.Primitives.ButtonBase.OnClick()
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.UIElement.OnMouseLeftButtonUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

 

HPMC service start failedOpen in a New Window

1. Install HPMC on an Amazon EC2 t2.large with file MC220_Linux_Server.iso by sudo command

2. At the end of installation, the installation console shows 

Congratulations! The HPE Mobile Center Server has been successfully installed
in the following location:
/opt/hpmc
Do you want to start the service [Y/n] (Default: Y): Y

Start Mobile Center Server service
Wait for service to be up.............Service running !

Server is up and running !

Configuration completed
-----------------------

The modification of the configuration of HPE Mobile Center Server has been
completed with success.

PRESS <ENTER> TO ACCEPT THE FOLLOWING (Exit):

 

Try to connect the MC server by the DNS:8080, browser shows

can't establish a connection

Then use "netstat -an |grep LISTEN", NONE 8080 port is found. Only PGSQL.5432 is there.

Clear all the files and folders under /tmp, use "sudo service hpmc restart"

Stopping HPMC Server
HPMC Server Stopped
Starting HPMC Server:
....................................................................................................................................................................................
http_code: 000
ERROR: Failed to start Server.

Use "sudo service hpmc start" has the same result.

 

1. AWS EC2 security group (port 22, 8080, 8081, 5432, 8443, 3000 are open) and IAM role - ADF- are correctly set.

2. Installation log and server log files attached on goolge drive.

https://drive.google.com/file/d/0BwjL0YRJPKF1MnVfZjcwWGdoYU0/view?usp=sharing
https://drive.google.com/file/d/0BwjL0YRJPKF1Z3JNN2pFVjFxYzQ/view?usp=sharing

3. Empty /tmp folder - done.

4. Tried change port from 8080 to 3000, same error result.

 

Any guidance or help? Really apprieciate. 

 

 

Blog: New Release - Mobile Center 2.2 and Four Reasons to Get Excited about Mobile Testing!Open in a New Window

We are pleased to announce the release of Mobile Center 2.2 this week.. Ease of use and flexibility are the core themes for this release. From developers to test automation engineers, mobile administrators and business/application owners, Mobile Center 2.2 has made their respective tasks easier. 

Read more

 

 

Blog: Mobile World Congress 2017 Wrap-up from Barcelona #MWC17Open in a New Window

Silvia Siqueira, WW Sr. Product Marketing Manager for Performance testing solutions, provides a wrap-up of Mobile World Congress.

Read the blog

 

 

how to fix " failed to install local postgers database" when install HP mobile center serverOpen in a New Window

Hi guys

Im trying to execute install HP mobile center server but I always get an error " failed to install local postgers database". (Attached image)
Can everyone tell me how to fix the above error?
Thank.

 

 

HPE Mobile Center Error 2049Open in a New Window

I have been trying to run a sample mobile application via HPE Mobile Center but after selecting the Mobile device and the application and on clicking on OK the application is throughing this following error:

"Unexpected error from HPE Mobile Center.[Error 2049]"

I have attached the screenshot of the error code.

Help me out. What should I do.

Thanks

 

 

Best of Show on Tour 2017: March 28 - Apr 6 in GermanyOpen in a New Window

Join us for the  Best of Show on Tour where we will present the latest trends and developments in Application Delivery Management. Providing high-quality applications quickly and reliably, creating a positive digital user experience – these are the declared goals of IT and development departments. These can be achieved with Continuous Testing, agile development and DevOps. We will show you how on the Best of Show on Tour. At the same time, we would like to take the opportunity to kick off the HPE German Testing Community – a format which is already well received in Switzerland and which we would like to offer our German customers as a platform for knowledge exchange, best practice sharing, networking and collaboration among peers. Don’t miss this opportunity in a city near you and register now! (The events will be conducted in German language.)

Agenda & registration

 

IP Change of Mobile Center ServerOpen in a New Window

Hi,

Mobile Center can be installed using FQDN or IP Address.

In case that customer choosed to use IP address, need to take into account that this IP can be changed.

Iin the event of IP change, Mobile Center will stop functioning (since it is configured for specific address).

In this case, there is a need to run Modification Wizard that helps to reconfigure MC server and use correct address - it is located in root directory of MC installation.

Please note that in case of remote connectors usage, those must be reconfigured also (same Modification Wizard exsists for MC Connectors as well). On top of that, there is a need to clean up MC DB from old data issued for old IP adress (otherwise the connector will still try to use old data). Please run the following commands (terminal) on MC server to achieve that:

cd <mc installation>\Schema

 java -cp hp4m-database-jar-with-dependencies.jar com.hp.db.MasterCreator -db hp4m -s <NEW IP>  -u postgres -p password -port 5432 -path ..\

(please change "password" to postgres user password - the one supplied during MC install). 

After that, run Modify Confuguration Wizard on the connectors.

Hope this helps, 

 

ALM Integration with Mobile Center - Incorrect Login - SolutionOpen in a New Window

Hi,

I thought it worth posting this as it wasn't that intuitive imo.  To use the ALM Integration with Mobile Center, which allows the selection of the device from the test set, it is necessary to have the right version of ALM and perform the configuration from the help.  The COMMUNITY_SECURITY_PASSPHRASE for Mobile Center must be set to the same as in ALM.  There is one of those notes there.... but the section begins with an If, and talks about Single Sign-On tokens.  I ignored because of not using SSO...... this was wrong.  Set the value in Mobile Center to the same value as in ALM.

Paul

 

WEBVIEW is not available for hybrid appOpen in a New Window

I am trying to test an hybrid app (cordova, crosswalk build) in a real android device. I am using Appium in order to use selenium. I am able to launch the app in the device but its not possible to switch to the WEBVIEW, the reason is only one context is available that is NATIVE_APP.

But I can debug the app using chrome remore debug & can inspect the elements.

Here is the capabilities I am setting. 

capabilities.setCapability("platformName", "Android");
capabilities.setCapability("uuid", "3300f358d02c5297");
capabilities.setCapability("userName", "user");
capabilities.setCapability("password", "pass");
capabilities.setCapability("appPackage", "package");
capabilities.setCapability("appActivity","activity");
AndroidDriver driver = new AndroidDriver(new URL("mobile center url"), capabilities);

Without the WEBVIEW its really hard to inspect the elements. Can anyone tell me what can be the reason of not getting the WEBVIEW context?

 

Error 2049Open in a New Window

I get the error message 2049 " unexpected error from HPE Mobile Center" after wich i make in "open application in HPE Mobile Center" settings. I would like to know what is this error.

 

Mobile center connection with win 10 mobileOpen in a New Window

We need to automate a win10 miobile app which interacts with win10 PC (in which mobile connector is installed), using UFT and mobile center. Does mobile center provide support for the same  (win10 mobile app)? [Note: Same has been achived for combination of android and win10 PC, using UFT and mobile center]

 

New Release - Mobile Center 2.2 with immediate effect!Open in a New Window

Ease of use and flexibility are the core themes for this latest release of Mobile Center 2.2. From developers to test automation engineers, mobile app administrators and business/application owners, MC 2.2 has made their respective tasks easier. Some of the new features of interest to customers include video/camera sensor simulation, support of LDAP/Active Directory for ease of management, quick ad hoc, exploratory testing on the go and most importantly, 4 new licensing options to cater to every customers’ needs. Read on here to learn more about what’s new in MC2.2.

Lastly, save the date and come join us in one of these webinars:

  • Feb 2nd: Supporting the Idea Economy in the world of finance

This is a re-run of Discover London session. Prospective customers will be interested to learn how WorldPay support the idea economy and achieved high return on investment through its use of HPE UFT and Mobile Center. Check out link here.

 

Configure MC server to run on privileged port (Linux)Open in a New Window

 

In Linux OS the usage of ports less than 8080 restricted to root user.

The MC is not running as a root. You can easily configure MC to run there on port 8080 or 8443.

But if there is a need to run it on 80 or 443, we can try the following workaround:

1.       Install MC server with 443 port

2.       Run the following command (as root):            

                     setcap CAP_NET_BIND_SERVICE=+eip /usr/sbin/nginx

3.       Start the service

This will allows MC to run on priveleged port (like 80 or 443).

 

 

Connecting Windows Phone - WP-start-hpmc.batOpen in a New Window

I'm using HPE Mobile Phone 2.01 through a connector. I connected Android devices without problems.

This time I'm trying to connect a Windows Phone (8.1 update 2).

I've registered the phone (with the sdk that comes with Visual Studio 2015) and when I connected the phone to the PC the phone is recognized as a new storage unit.

When I connect the phone and execute WP-start-hpmc.bat (with admin priviledges) the phone appears in the Devices section but blurred and with state: disconnected.

As I execute the command WP-start-hpmc.bat the log indicates this:

 

Ejecutando (\\BT-NB-LEMI\ROOT\CIMV2:Win32_Process.Handle="6980")->terminate()
Ejecución correcta del método.
Parámetros de salida:
instance of __PARAMETERS
{
ReturnValue = 0;
};
Ejecutando (\\BT-NB-LEMI\ROOT\CIMV2:Win32_Process.Handle="5576")->terminate()
Ejecución correcta del método.
Parámetros de salida:
instance of __PARAMETERS
{
ReturnValue = 0;
};
nginx: [error] OpenEvent("Global\ngx_reload_6980") failed (2: FormatMessage() error:(15100))
"C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/../jre/bin/java.exe" -Xmx30m -Djna_tmpdir="C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/tmp" -Djava.net.preferIPv4Stack=true -jar "C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/wrapper.jar" -c "C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/wrapper.conf"
YAJSW: yajsw-beta-12.04
OS : Windows 8.1/6.3/amd64
JVM : Azul Systems, Inc./1.7.0_76/C:\Program Files\HPE Mobile Center Connector\connector\jre/64
ene 18, 2017 6:17:44 PM org.apache.commons.vfs2.VfsLog info
INFORMACIËN: Using "C:\Users\LEONAR~1.MIR\AppData\Local\Temp\vfs_cache" as temporary files store.
wrapper|YAJSW: yajsw-beta-12.04
wrapper|OS : Windows 8.1/6.3/amd64
wrapper|JVM : Azul Systems, Inc./1.7.0_76/C:\Program Files\HPE Mobile Center Connector\connector\jre/64
wrapper|create script: C:\Program Files\HPE Mobile Center Connector\connector/wrapper/killRelatedProcesses.groovy
-D{}: {}
io.netty.leakDetection.level
simple
-D{}: {}
io.netty.leakDetection.maxRecords
4
java.nio.ByteBuffer.cleaner: {}
available
java.nio.Buffer.address: {}
available
Platform: Windows
Java version: {}
7
-Dio.netty.noUnsafe: {}
false
sun.misc.Unsafe: {}
unavailable
-Dio.netty.noJavassist: {}
false
Javassist: unavailable
You don't have Javassist in your class path or you don't have enough permission to load dynamically generated classes. Please check the configuration for better performance.
-Dio.netty.tmpdir: {} (java.io.tmpdir)
C:\Users\LEONAR~1.MIR\AppData\Local\Temp
-Dio.netty.bitMode: {} (sun.arch.data.model)
64
-Dio.netty.noPreferDirect: {}
true
Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
wrapper|create script: C:\Program Files\HPE Mobile Center Connector\connector/wrapper/restartRelatedService.groovy
wrapper|create script: C:\Program Files\HPE Mobile Center Connector\connector/wrapper/startRelatedService.groovy
wrapper|create script: C:\Program Files\HPE Mobile Center Connector\connector/wrapper/stopRelatedServices.groovy
wrapper|start from Thread main
wrapper|set state IDLE->STARTING
checkRemainConc C:\Program Files\HPE Mobile Center Connector\connector/wrapper/startRelatedService.groovy 5
wrapper|starting Process
wrapper|starting controller
wrapper|executed script: C:\Program Files\HPE Mobile Center Connector\connector/wrapper/startRelatedService.groovy 5
wrapper|binding to port 15003
-Dio.netty.initialSeedUniquifier: 0x3f3227399ba44943 (took 1 ms)
-Dio.netty.allocator.type: {}
unpooled
-Dio.netty.threadLocalDirectBufferSize: {}
65536
-Dio.netty.maxThreadLocalCharBufferSize: {}
16384
Loopback interface: {} ({}, {})
lo
Software Loopback Interface 1
127.0.0.1
{}: {} (non-existent)
\proc\sys\net\core\somaxconn
200
wrapper|Controller State: UNKNOWN -> WAITING
wrapper|binding successfull
wrapper|controller started
wrapper|working dir C:\Program Files\HPE Mobile Center Connector\connector\jetty
system.env 56
env result 58
wrapper|spawning wrapped process
wrapper|is running: false pid=(-1<=0)
wrapper|exec: "C:\Program Files\HPE Mobile Center Connector\connector\jre\bin\java.exe" -classpath "C:\Program Files\HPE Mobile Center Connector\connector\wrapper\wrapperApp.jar;C:\Program Files\HPE Mobile Center Connector\connector\jetty\start.jar;C:\Program Files\HPE Mobile Center Connector\connector\jetty\start.jar" -XX:MaxPermSize=128m -XX:+UseParallelGC -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=HPHeapDump.txt "-Dconsole.home=C:\Program Files\HPE Mobile Center Connector\connector" "-Djetty.home=C:\Program Files\HPE Mobile Center Connector\connector/jetty" "-Djetty.base=C:\Program Files\HPE Mobile Center Connector\connector/jetty" "-Djetty.pid=C:\Program Files\HPE Mobile Center Connector\connector/jetty/jetty.pid" "-Djetty.state=C:\Program Files\HPE Mobile Center Connector\connector/jetty/jetty.state" "-Djetty.logs=C:\Program Files\HPE Mobile Center Connector\connector/log" "-Dpath=C:\Program Files\HPE Mobile Center Connector\connector/conf" -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Xms512m -Xmx512m "-DJETTY_HOME=C:\Program Files\HPE Mobile Center Connector\connector/jetty" "-DJAVA_HOME=C:\Program Files\HPE Mobile Center Connector\connector/jre" "-DCONSOLE_HOME=C:\Program Files\HPE Mobile Center Connector\connector" -Dwrapper.port=15003 -Dwrapper.key=-8519700503074142639 -Dwrapper.teeName=-8519700503074142639$1484774264934 "-Dwrapper.tmp.path=C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/tmp" "-Djna_tmpdir=C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/tmp" "-Dwrapper.config=C:\Program Files\HPE Mobile Center Connector\connector\wrapper\wrapper.conf" org.rzo.yajsw.app.WrapperJVMMain
wrapper|waiting for termination of process
wrapper|created jva.pid file C:\Program Files\HPE Mobile Center Connector\connector\wrapper\app.pid
wrapper|started process with pid 2820
wrapper|set state STARTING->RUNNING
wrapper|GetExitCodeProcess returned 259
wrapper|getExitCode -2 processINFO==null=false
wrapper|is running: true 2820 -2
wrapper|waitFor -1
wrapper|GetExitCodeProcess returned 259
wrapper|getExitCode -2 processINFO==null=false
wrapper|is running: true 2820 -2
wrapper|1waitFor
wrapper|2waitFor
wrapper|GetExitCodeProcess returned 259
wrapper|getExitCode -2 processINFO==null=false
wrapper|is running: true 2820 -2
wrapper|WaitForSingleObject +
2820/0|[INFO] StandardFileSystemManager - Using "C:\Users\LEONAR~1.MIR\AppData\Local\Temp\vfs_cache" as temporary files store.
2820/0|APP user name=leonardo.miro
2820/0|APP working dir=C:\Program Files\HPE Mobile Center Connector\connector\jetty
2820/0|APP java version=1.7.0_76
2820/0|APP class path=C:\Program Files\HPE Mobile Center Connector\connector\wrapper\wrapperApp.jar;C:\Program Files\HPE Mobile Center Connector\connector\jetty\start.jar;C:\Program Files\HPE Mobile Center Connector\connector\jetty\start.jar
2820/0|APP library path=C:\Program Files\HPE Mobile Center Connector\connector\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\HPE Mobile Center Connector\connector\jre\bin;C:\Program Files\HPE Mobile Center Connector\connector\openssl\bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\HP\Virtual User Generator\strawberry-perl\perl\bin;C:\Program Files (x86)\Skype\Phone\;C:\Users\leonardo.miro\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;.
2820/0|Application args: no args
2820/0|mainClass/jar/script: null/start.jar/null
2820/0|external stop false
2820/0|args:
2820/0|--lib=C:\Program Files\HPE Mobile Center Connector\connector/conf
2820/0|terminated WrapperManager.init()
2820/0|connecting to port 15003
2820/0|WrapperManager: channel connected, sending key
-D{}: {}
io.netty.buffer.bytebuf.checkAccessible
true
2820/0|Controller State: WAITING -> ESTABLISHED
-Dio.netty.recycler.maxCapacity.default: {}
262144
2820/0|Controller State: ESTABLISHED -> LOGGED_ON
2820/0|Correct key
2820/0|app already logged on -> rejecting new connection
2820/0|unexpected connection closed: /127.0.0.1:16056
2820/0|2017-01-18_18:17:48.865 INFO org.eclipse.jetty.util.log - Logging initialized @2704ms
2820/0|2017-01-18_18:17:48.912 WARN o.e.jetty.server.HomeBaseWarning - This instance of Jetty is not running from a separate {jetty.base} directory, this is not recommended. See documentation at http://www.eclipse.org/jetty/documentation/current/startup.html
2820/0|2017-01-18_18:17:49.225 INFO org.eclipse.jetty.server.Server - jetty-9.2.10.v20150310
2820/0|2017-01-18_18:17:49.256 INFO o.e.j.server.AbstractNCSARequestLog - Opened C:\Program Files\HPE Mobile Center Connector\connector\log\2017_01_18.access.log
2820/0|2017-01-18_18:17:49.256 INFO o.e.j.d.p.ScanningAppProvider - Deployment monitor [file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/webapps/] at interval 1
2820/0|app already logged on -> rejecting new connection
2820/0|unexpected connection closed: /127.0.0.1:16057
2820/0|SLF4J: Class path contains multiple SLF4J bindings.
2820/0|SLF4J: Found binding in [jar:file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/webapps/hp4m-connector/WEB-INF/lib/logback-classic-1.0.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2820/0|SLF4J: Found binding in [jar:file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/lib/ext/logging/logback-classic-1.1.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2820/0|SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2820/0|SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
2820/0|18:17:57,006 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
2820/0|18:17:57,006 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
2820/0|18:17:57,006 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/webapps/hp4m-connector/WEB-INF/classes/logback.xml]
2820/0|18:17:57,006 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs multiple times on the classpath.
2820/0|18:17:57,006 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/webapps/hp4m-connector/WEB-INF/classes/logback.xml]
2820/0|18:17:57,006 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/resources/logback.xml]
2820/0|18:17:57,162 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
2820/0|18:17:57,178 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Setting ReconfigureOnChangeFilter scanning period to 5 seconds
2820/0|18:17:57,178 |-INFO in ReconfigureOnChangeFilter{invocationCounter=0} - Will scan for changes in [[C:\Program Files\HPE Mobile Center Connector\connector\jetty\webapps\hp4m-connector\WEB-INF\classes\logback.xml]] every 5 seconds.
2820/0|18:17:57,178 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Adding ReconfigureOnChangeFilter as a turbo filter
2820/0|18:17:57,178 |-INFO in ch.qos.logback.core.joran.util.ConfigurationWatchListUtil@7905e210 - Adding [file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/webapps/hp4m-connector/WEB-INF/classes/logbackInt.xml] to configuration watch list.
2820/0|18:17:57,193 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
2820/0|18:17:57,193 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
2820/0|18:17:57,256 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,256 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]
2820/0|18:17:57,272 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,303 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@713cc682 - No compression will be used
2820/0|18:17:57,303 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/connector.log
2820/0|18:17:57,303 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/connector.log]
2820/0|18:17:57,303 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,303 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [DEVICE_HEALTH_FILE]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@4d0cbae2 - No compression will be used
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[DEVICE_HEALTH_FILE] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/device_health.log
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[DEVICE_HEALTH_FILE] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/device_health.log]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ACCESS_LOGGER]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@7ec172f2 - No compression will be used
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[ACCESS_LOGGER] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/WSaccess.log
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[ACCESS_LOGGER] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/WSaccess.log]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.sift.SiftingAppender]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE-THREAD]
2820/0|18:17:57,334 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.sift.MDCBasedDiscriminator] for [discriminator] property
2820/0|18:17:57,334 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,334 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [DEVICE_CONNECTION_FILE]
2820/0|18:17:57,334 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,334 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@4e61aee1 - No compression will be used
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[DEVICE_CONNECTION_FILE] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/device_connections.log
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[DEVICE_CONNECTION_FILE] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/device_connections.log]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [VNCLAUNCHER]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@6f205dfa - No compression will be used
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[VNCLAUNCHER] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/vncLauncher.log
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[VNCLAUNCHER] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/vncLauncher.log]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [WEBSOCKIFY]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@35fa0115 - No compression will be used
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[WEBSOCKIFY] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/websockify.log
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[WEBSOCKIFY] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/websockify.log]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [AWS]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@305d2562 - No compression will be used
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[AWS] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/aws.log
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[AWS] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/aws.log]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [WS_KEEPALIVE_LOGGER]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@33415dbc - No compression will be used
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[WS_KEEPALIVE_LOGGER] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/connectorKeepAlive.log
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[WS_KEEPALIVE_LOGGER] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/connectorKeepAlive.log]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [device] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [device] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [DEVICE_CONNECTION_FILE] to Logger[device]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [deviceHealth] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [deviceHealth] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [DEVICE_HEALTH_FILE] to Logger[deviceHealth]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [accessLogger] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [accessLogger] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ACCESS_LOGGER] to Logger[accessLogger]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [vncLauncher] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [vncLauncher] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [VNCLAUNCHER] to Logger[vncLauncher]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [websockify] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [websockify] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [WEBSOCKIFY] to Logger[websockify]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [aws] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [aws] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [AWS] to Logger[aws]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [HPMC-WebSocket-KeepAlive] to INFO
2820/0|log4j:WARN No appenders could be found for logger (org.springframework.web.context.ContextLoader).
2820/0|log4j:WARN Please initialize the log4j system properly.
2820/0|log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

 

I checked and saw many problems, many of then maybe warnings. But I can't found what the real problem is.

If you cant give me a hint about this let me know.

Contact Us

Vivit Worldwide
P.O. Box 18510
Boulder, CO 80308

Email: info@vivit-worldwide.org

Mission

Vivit's mission is to serve
the Hewlett Packard
Enterprise User
Community through
Advocacy, Community,
and Education.