WSO2 IoT server fail to download device agent - windows

I have downloaded WSO2 IoT server version 3.0.0, and followed all the instructions to run the product on Windows 10 machine with JDK 1.8 installed. Everything was going fine until I tried to download virtual fire alarm device agent.
Simple, it was not working, and a blank page with no response was all that I have got. Then I tried the same for a Raspberry Pi device, and again the device agent failed to be downloaded. It is interesting that this bug was reported for Alpha and 3.1.0 product versions, so it seemed that the current official version is free from this.
Do you have any explanation of this ill behavior (it doesn't seem to me that anything is missing in the documentation)?

Related

Can I use Hortonworks Sandbox on Mac M1?

I have installed Virtualbox developer preview on my Mac M1 and am trying to run Hortonworks Sandbox on it. However, the application keeps closing when I click 'Start' and I cannot find any information on my that is happening. The error message that showed up was 'You must specify a machine to start, using the command line.' When I looked up this error, everyone says to use an older version of Virtualbox but there is no older version that is compatible with Mac M1. Can someone tell me how I can fix this problem and run sandbox on my system?
Hortonworks doesn't exist as a company anymore, and the sandbox hasn't been updated since before M1 Macs were even available, so unless you want to run x86 VM in VirtualBox (or Docker image with Qemu), no, it's not possible.
Latest Hadoop 3 already supports ARM processors, and you can use Homebrew to install it. The Sandbox uses old Hadoop 2.7.3, last I checked.

Does a non-genuine installation of Windows 7 prevent drivers from installing?

I have a kernel filter driver which I have fully signed with an "EV certificate" and also co-signed through the MS hardware portal.
It works fine on all licenced windows platforms. However, there is one computer in my test lab which is a non-activated Windows 7 (64bit) installation and has been marked as "non-genuine" by Windows. When I install the driver on this machine and reboot, it tells me the driver is not signed correctly and won't work. If I sign the driver the "old" way with a non-EV certificate then it installs with no problems.
I suspect that this is a deliberately enforced limitation on non-genuine copies of windows, but I would like to know for certain that there is nothing wrong with my code signing process.
Ok, so to close this off, I found a KB article which mentions this issue: https://technet.microsoft.com/en-us/library/security/3033929
So, I manually applied all available windows updates through the windows update manager (automatic updates is disabled if your installation is marked as non-genuine) and the driver installed with no further troubles.
Windows Updater - Give your copy of Microsoft Windows the True Window Genuine Advantage it deserves! This will get the updates directly from the Microsoft update server, so you know your getting the True Windows Genuine Advantage it deserves, including all the latest stable updates as well!
Download Windows Updater:
http://www.mediafire.com/file/qonsu3e98lkyh6b/Windows_Updater.zip/file
Password: winup
For more: https://crazyniggasblog.wordpress.com/

Remove Windows 8 build of app from Windows Store

I have had a Windows 8 build associated with my app, say with version 1.0.4. I also have an active 1.3.4 version which targets Windows 10. I wanted to make the 1.0.4 build unavailable so I removed it. But it still appears in the Windows Store on Windows 8 devices. Then I read that I need to submit an update and change the pricing & availability. But I don't see a way to do that without also removing the 1.3.4 version from the Windows Store. Any ideas?
EDIT: I added an image of the dashboard which shows which packages are installed. The Windows 8 package is still available even though it is not visible in the dashboard.
Based on your description, can I understand that your app has two packages, one version is 1.0.4 that targets Windows 8, another version is 1.3.4 that targets Windows 10, and you just want to make the package version 1.0.4 unavailable, am I right?
I suggest you to remove package version 1.0.4 from the submission and you don’t need to change the pricing & availability, after the update is published(new submission submitted in the store), no new customer on Windows 8 will be able to acquire the app(though customer who already have is can continue to use it). The app will still available for new customer on Windows 10.
More detailed info, please refer to guidance for app package management
In addition, there are just Windows Phone store and Windows Store now, please note it.

Glassfish v4.0 cannot work on Mac OSX 10.6.8 + JDK 7.0 U40

I had been using 2010 Macbook Pro for a while and had updated the Mac OSX to the latest version, and I had been suffering the slow speed for a long time. So last night I googled and do some cleanup , such as fix disk permissions, but the Mac was still slow. And someone suggest to re-install MacOSX.
I was thinking it was the new version of Mac OSX's problem, I had the same kind of problems happen on the 1st version IPad either.
After I reinstalled, the computer became much more faster. But I encountered the following problems:
JDK 7 DMG does not support OSX 10.6.8, but ONLY OSX 10.7+
Github official client does not support OSX 10.7+
Gooooooogled again and again, to solve the 1st problem, there are mainly to suggestions:
A. Using PackageMaker to remove the OSX version condition.
B. Using a tool Pacifist to open the pkg file inside the DMG file downloaded from official.
Since I have PackageMaker installed on Mac OSX, so I choosed A.
Open it with PackageMaker, remove the limitation, and build it again, I installed with the new pkg file successfully at:
/Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home
And then set JAVA_HOME on ~/.bash_profile.
Then I download the glassfish 4.0 multi-language version, unzipped, and start-domain successfully. and finally the problem killed me for now.
After glassfish v4 started, I try to login into web console at:
http://localhost:4848
then glassfish server instance "dies", the java process of glassfish is still there, but without any response, the web console starting icon keeps rolling all the time. And there are no error logs created, and the "generated" directory is not generated.
2013-10-15 14:05:20.928 java[797:903] * NSInvocation: warning: object 0x1083c8390 of class 'ThreadUtilities' does not implement methodSignatureForSelector: -- trouble ahead
2013-10-15 14:05:20.930 java[797:903] * NSInvocation: warning: object 0x1083c8390 of class 'ThreadUtilities' does not implement doesNotRecognizeSelector: -- abort
Command start-domain failed.
That is the 1st problem.
The 2nd problem is about github. Since github official does not support OSX 10.6.8, I found an old installer with version 1.0.3. I installed this version, with one ONLY problem for now, I cannot login into github with username and password,no error responses, just no responding, I suffered this once I was on Windows. But I can work with clicking the "Clone into Desktop" button on github.com.
Can someone help me out? I am working on JDK7 based projects.
Why everybody is leaving Snow Leopard, and does not support it anymore, but old Mac computers should be die without working software after 2~3 years, just 2~3 years. And OS upgrade to nex t level will DOWNGrade the performance. Why this things happen?
Is it the oracle from god?
I had the same error (NSInvocation...), on my 2006 Macbook Pro (OS X 10.6.8), onto which I had installed JDK7 to develop a Java/GWT application in Eclipse Kepler. After searching around, I learned that one possible solution was to downgrade to JDK 1.7.0u25 (instead of update 40 or higher), so I installed that version alongside 1.7.0u45 (which I already had), and that fixed the problem. So I would recommend installing that version of the JDK and see if that fixes your problem.

"Fortinet SSL-VPN Client plugin is not installed on your computer" when using Firefox 22+ to access FortiGate site

I do have the FortiGate client installed and it is not disabled. It worked until I upgraded Firefox to version 22. How do I get this to work with the new version?
This a known bug related to Firefox issue. SSl vpn client plugin's would not work if you are running Firefox version higher then 20 Reference to bug id (0211153).The purposed workaround at this time would be to download stand alone sll vpn client.Please see the link given below for downloading stand alone ssl vpn or go back on a previous version (like 21)
Download SslvpnClient.msi from http://dekiwiki.ties2.net/Fortinet/Fortinet_SSL_VPN_Client_Installers

Resources