IBM MobileFirst Analytics Error - mobilefirst-analytics

I am keep getting below error frequently in messages.log on for IBM MF Analytics server 8.0 deployed on Liberty server 8.5.5.9.
ibm.mobile.analytics.server.processors.v1.ProcessorUtilityV1 W MSAN239W: Could not populate stackTrace using the key $stacktrace, returning null.
Anyone let me know what could be the issue?

This is a known APAR: http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1PI70463
To resolve, go to IBM Fix Central and download the latest iFix for IBM MobileFirst Foundation 8.0.

Related

Azure Functional App 2.0 Sql Not Supported Error

I am trying to connect to Azure SQL Server from function App 2.0 using .NET core.
After i have added the SQL Data client reference and run the app i am getting not supported error can you please help on this.
You need to import SQL version 4.4.0 to make it work latest nuget update is breaking the changes,

Power Query Connection to mySQL running on Parallels - The handshake failed due to an unexpected packet format

Trying to connect to mySQL instance hosted on AWS RDS via Power Query and/or Power BI Designer. Getting the error
"The handshake failed due to an unexpected packet format"
in both applications.
I am running Office 365/Power Query & Power BI Designer on Windows 8.1 on a VM via Parallels.
I am able to connect to the database using the same credentials using Tableau or MySQL workbench or other applications, however Power Query/Power BI appears to have fallen over in the past couple of weeks after being fine for months before that.
Have tried reinstalling everything (Office, Power Query, Windows, Drivers, MySQL NET connectors) but no success.
Any ideas for to get the handshake to work?
Problems resolved. Thanks Curt & Alejrandro. Server-side changes appeared to have been the issue. AWS apparently changed their certificates and we hadn't rebooted our server instance in a while. Rebooting our server to allow the AWS certificate changes to take hold corrected the handshake issue.
Lukasz, ODBC source did work the whole time, but it was more a matter of not wanting to rebuild the model I'd built using the MySQL connector and I wasn't confident enough with M to manually change the source to ODBC.
Power BI Designer and Power Query now support ODBC data sources.
https://support.powerbi.com/knowledgebase/articles/471643-data-sources-in-power-bi-designer
Perhaps that would work on your system? Could you let me know if it resolves the issue? Won't be as good as the .Net connector, but it probably will get you going.
HTH,
-Lukasz
http://dev.powerbi.com
http://blogs.msdn.com/powerbidev
Make a feature request: https://support.powerbi.com/forums/265200-power-bi
Sign up for Power BI: http://www.powerbi.com

IBM Worklight: failed to upload a package using Worklight Console - jpa.entity.ProjectEntity

I got the error while uploading a package to Worklight using Worklight Console site.
Object
'com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-'
is not managed by this context
I just saw this error message using Browser Developer Tools to investigate Request and Response Network activity.
PS: There isnĀ“t any JPA class in my project and package.
My environment:
IBM MobileFirst 6.3 (Worklight)
IBM WebSphere Liberty 8.5.5
MySQL
Windows Server 2008 R2
Hybrid App with Android Environment
Full error message:
{"id":147,"type":"UPLOAD_APPLICATION","status":"PENDING","project":{"name":"project1"},"timeCreated":"2015-02-05T19:37:08.000Z","userName":"user1","appServerId":"Liberty","description":{"appVersionsDeployed":[{"applicationName":"App1","environment":"android","version":"1.0"},{"applicationName":"App1","environment":"common","version":"1.0"}],"appVersionsAlreadyDeployed":[],"filename":"App1-all.wlapp"},"errors":[{"date":"2015-02-05T19:37:08.655Z","phase":"VALIDATE","code":"FAILURE","exception":"ArgumentException","details":"Object \"com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-2\" is not managed by this context."}],"warnings":[],"productVersion":"6.3.0.00-20141127-1357"}
The problem is the file size (.wlapp).
I got the error when the file is bigger than 7MB.

SQL adapter in Worlight?

I am new to IBM Worklight,and i found a way to connect to the MySQL using the SQL adapter.
the configuration as below:
<dataSourceDefinition>
<driverClass>com.mysql.jdbc.Driver</driverClass>
<url>jdbc:mysql://localhost:3306/worklight_training</url>
<user>Worklight</user>
<password>Worklight</password>
</dataSourceDefinition>
Since the adapter are compile together with the app, just wondering, is it safe? is there a possibility of someone decompiling my apk or ipa to view the adapter connection thus acquire the user and password to my mysql database.
A hacker decompiling your .apk or .ipa file will not find the database username/password there, for the simple reason that the adapter is not compiled "together with the app" and is not part of any artifacts that you install in a device.
An adapter is a server-side entity, not client-side.
The adapter is an object stored in the memory of the running application server.
Adapters are Server side code andare not part of the apk or ipa files.
You can check/confirm this information in Worklight documentation. The details about adapters, under "Developing the server side of a Worklight Application" are at:
http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.dev.doc/devref/c_overview_of_ibm_worklight_adap.html
You can also check the Server Side Development of MobileFirst Platform Getting Started Modules
https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-6-3/server-side-development/
(MobileFirst Platform is the new name of Worklight)
In worklight, you usually have the application (apk/ipa) communicating with a server side component (the adapters) running in a worklight server. The adapters are used to communicate with backend systems (like a mysql server). There are a few different types of adapters to communicate with different types of backends (like sql, http and SAP)
Please, let us know what documentation/guide caused you the understanding that adapters are part of the client apk/ipa. If that is really stated in any documentation, it is wrong and must be corrected.
Edit:
To connect to a MySQL DB (no matter if it is a standalone MySQL or in XAMP, LAMP or whatever package) you can follow this geting started tutorial
https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-6-3/server-side-development/sql-adapter-communicating-sql-database/
Also note that, if you are using MobileFirst Studio (previously Worklight Studio) downloaded for free from Developer Works you have a developer version of the WOrklight Server running inside Studio so that you can create and deploy adapters and use it during development as your server. But when you go to production you are required to purchase licenses of Worklight because you don't have the worklight server available for free.
So if you have Studio, you have the server available but only for development purposes.

Installing the SSRS Data Connector for CRM 2011

I have installed Microsoft Dynamics CRM 2011, Update roll-up 14 in my VPC.
While I try to install Microsoft Dynamic CRM Reporting Extensions using SetupSrsDataConnector.exe, I get an error saying,
Setup cannot proceed because an error occurred while copying installer files to the local system: The upgrade cannot be installed
by the Windows Installer service because the program to be upgraded
may be missing, or the upgrade may update a different version of the
program. Verify that the program to be upgraded exists on your
computer and that you have the correct upgrade For additional details
see logfile.
Does anyone know what is wrong? I tried several instances but they all don't work either. I can access my SSRS server by going to http: //SSRS-Server/Reports and it will give a list of all services running there.
Any help would be much appreciated.
Thanks!
Is there enough disk space for the installation?
Are you installing the update on the SQL machine or the CRM machine?
Are you installing the correct version? CRM 2011, CRM 2013? 64bit, 32bit?
Could you post the results from the log file?
C:\Users\<LoginName>\AppData\Roaming\Microsoft\MSCRM\Logs