I get the following error after a few seconds, or even minutes, when trying to install an app from the store (AppManager).
The wso2carbon.log file doesn't show any error message.
I'm using the WSO2 EMM version 3.3.0 and the device is an Android 8.
It does enroll correctly, and even receives device operations such as: send ring device, and send message.
I looked for enabling debug message log, but I didn't find it for the version of wso2 iot server that I am testing.
Where can I find some clues to solve this issue?
How can I enable debug message logging for the AppManager?
The issue is not on the EMM server but rather on the EMM Android Agent. The server just receives an "ERROR" status from the EMM agent upon failure.
I recommend you run the EMM agent in debug on the device to see what is causing the issue.
I have run into many "INSTALL_APPLICATION" errors, it could be any or none of these:
Download location differs on the device
Network issues during download
Volley issues (HTTP library) - was mostly version issues
Server not allowing HTTP calls (only HTTPS) which is the default for installing apps
Device Owner/Device Admin not set correctly
Missing permissions
What you can see on the HTTP access logs is whether the install is occurring but looking to see whether the APK is downloading, log entry will look like this:
[21/Jun/2019:14:48:19 +0200] "GET /store/api/mobileapp/getfile/6THVwGRMTAG5wD7.apk HTTP/1.1" 200 3803551 "-" "Mozilla/5.0 ( compatible ), Android"
If you see the APK being downloaded then you know for sure the issue is NOT on the server.
Related
when I trying to start WSO2 IoTs Server and go to https://localhost:9443/devicemgt, I'm getting the error
HTTP Status 500 - Cannot call method getUIPermissions of undefined.
I'm using MySQL and run WSO2 IoTs alone on localhost.
Carbon Logs here
This issue is raised when you try to start the pack with a -Dsetup. You can execute the database scripts that are available in the dbscripts folder manually and then run the product. This issue has been fixed after the alpha release.
I made the configurations as per the Documentation. But as I try to subscribe the app from the android mobile,I get the error as ERROR - MDMOperationsImpl Cannot connect to Token API Endpoint
ERROR - MDMOperationsImpl No OK response received form the API. Is there any other configurations to be done to make this work.
Can you explain the scenario you are trying to perform and the EMM version that you use.
EMM 2.0.0 now has in built AppM features which allow EMM to be used without integrating with AppM, in case publishing of only mobile applications is required. If you need to publish both web and mobile applications you will have to integrate AppM with EMM.
In the document you have refered above , section [1] applies to EMM 2.0.0 and above and section [2] applies to versions below 2.0.0
From the error you have mentioned, the issue seems to be related to the following property.
<Property name="TokenApiURL">https://localhost:9448/oauth2/token</Property>
Can you check whether this URL contains the correct host and port ( 9443 + port offset) of EMM .
[1] https://docs.wso2.com/display/APPM100/Integrating+a+Mobile+Device+Manager#IntegratingaMobileDeviceManager-IntegratingWSO2MDM
[2] https://docs.wso2.com/display/APPM100/Integrating+a+Mobile+Device+Manager#IntegratingaMobileDeviceManager-IntegratingWSO2EMM
I am setting up a new WSO2 EMM server and, in order to maintain my organization's PCI DSS certification, I have to disable support for any encryption protocol lower than TLSv1.1 before I can put it into production (see this for more information on PCI 3.1).
I edited the file /repository/conf/tomcat/catalina-server.xml as per the documentation. Here is what I tried:
I changed the attribute sslEnabledProtocols from TLS to TLSv1.1,TLSv1.2, but this generates the error
ERROR {org.wso2.carbon.tomcat.internal.CarbonTomcat} -
LifeCycleException while starting tomcat connector
{org.wso2.carbon.tomcat.internal.CarbonTomcat}
in my wso2carbon.log and I'm unable to log into the EMM web console.
Does anyone know how to disable TLSv1.0 without breaking my installation?
cheers,
Found it!
you have to get rid of sslProtocol attribute and replace it with sslEnabledProtocols, they look very similar.
I downloaded and installed the WSO2 API Manager version 1.4.0 yesterday and I cannot login to the web management console (https://localhost:9443/carbon) using the default credentials (i.e. admin/admin)
I can login to the API store and API publisher and the error comes only for the management console.
Note that I performed the default install (unzip and ran ./wso2server.sh from the bin folder)
Following is part of the error stacktrace
2013-06-03 15:42:13,095] INFO - CarbonAuthenticationUtil 'admin#carbon.super [-1234]' logged in at [2013-06-03 15:42:13,095+1000]
[2013-06-03 15:42:13,112] ERROR - AuthenticationHandler System error : 0 active authenticators registered in the system. The system should have at least 1 active authenticator service registered.
java.lang.RuntimeException: System error : 0 active authenticators registered in the system. The system should have at least 1 active authenticator service registered.
at org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.isAuthenticated(AuthenticationHandler.java:144)
at org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:83)
Further down the stacktrace, I also get the below
[2013-06-04 11:42:15,860] ERROR - AxisEngine Authentication failure
org.apache.axis2.AxisFault: Authentication failure
at org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:110)
at org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.invoke(AuthenticationHandler.java:55)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
I also get the following two warning messages on startup
[2013-06-04 11:14:05,489] WARN - ValidationResultPrinter Swap Memory size (MB): 64 of the system is below the recommended minimum size :2048
[2013-06-04 11:14:15,444] WARN - LandingPageWebappDeployer Product landing page not found.
#nuwandias Hi Nuwan.
I identified the issue. When I was evaluating the previous 1.3.1 version, I injected the Authorization header with the Bearer token via my Firefox browser plugin.
That was what caused the problem with the 1.4.0 version. Once I disable it it works fine.
All good now and I am looking forward to doing a deep dive evaluation of this product.
Thanks a lot for your support.
I have just downloaded the zip from the website and tried the same and it worked fine. Can you please provide the following information.
What is the environment that you are trying this on (OS)?
What is the md5sum value of the zip archive? Mine is fea68eaadd17daa5e6fa0aff3d973601.
Do you see any errors/warnings on startup? If so, could you share the startup logs too?
Thanks,
Nuwan.
Looking at this log message...
Swap Memory size (MB): 64 of the system is below the recommended minimum size :2048
It seems like your hard drive (or partition) has filled up. I'm wondering whether this could have caused any errors when you unzipped the zip file (if the hard disk has no free space).
If this is the case, can you free up some space (>200MB) in your partition, unzip the archive again and retry?
I'm on Windows 7 Ultimate x64 IIS 7.5
I have deployed the services to the web server and when I try them in IE like this: MyService.svc?wsdl I get the 400 "Bad Request" page
I should get the description of the web service instead, anybody knows how to fix this ?
You might need to do the following on the server:
cd c:\windows\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\
followed by
ServiceModelReg -i
This should register the .SVC extension as a WCF service, if not already registered.
Just an update: When using v4.0 on a 64-bit machine, you need to run go to
c:\windows\microsoft.net\framework64\v4.0.30319\
before running
ServiceModelReg.exe -r
If you go to
c:\windows\microsoft.net\framework\v4.0.30319\
and do the same thing, we found that it doesn't work correctly and we keep getting:
Unhandled Exception: System.ServiceModel.EndpointNotFoundException: The message could not be dispatched because the service at the endpoint address 'net.tcp://localhost/Elephant/Tiger.svc' is unavailable for the protocol of the address.