My 32bit Windows 7 server is running Pentaho bi server ce 7.0.
Everything seemed to install fine, but I'm having trouble getting the server to run.
Attempt 1
Everything seems OK after running start-pentaho.bat and accessing localhost:8080, however accessing localhost:8080\Pentaho\login returns an error.
Attempt 2
I am unable to access the site after running start-pentaho.bat and accessing localhost:8080.
Can anybody help?
It seems that the BI Server is only supported on 64-bits OSes all the way back to version 5.1. The documentation for 4.4 is already gone from the Pentaho support site.
https://help.pentaho.com/Documentation/7.0/0D0/160/000
Related
Since Oracle Database cannot be installed on Apple Silicon, I decided to take a workaround, but now I do not understand how to connect to the Oracle Database, which I installed on a Windows 11 virtual machine through Parallels.
I understand that this makes little sense, since in fact you can use Oracle from Windows 11 and do whatever you want with it.
But as an experiment, I wanted to try connecting to an already deployed HR database in my Windows 11 virtual machine using DataGrip on my Apple Silicon (M1) computer.
I know that there are other ways to use Oracle on a Mac (using Docker for example) but maybe we can come up with some other alternative, or maybe there already is, but I don't know about it.
I hope I wrote as clear as possible. Sorry, I'm using a translator.
I used this instruction to install Instant Client (as I understand it, this tool helps us connect to the Database server, be it a virtual machine or a remote server), I spent several hours installing everything. In Datagrip, when connecting, I specified different settings, wrote the path to the installed instantclient, however, I constantly get an error when connecting (whatever settings I choose), I googled this error, but I still did not understand how I can apply them It is for M1 and not Windows computers.
The error looked like this:
Failed DBMS: Oracle (no ver.) Case sensitivity: plain=mixed, delimited=exact Native library cannot be loaded. no ocijdbc21 in java.library.path: /Users/malkhaz/instantclient_19_8:/Users/malkhaz/lib:/Users/malkhaz/instantclient_19_8.
I wrote a QT tool using WebSockets with SSL. When I roll it out to an other Windows 10 machine it doesn't connect but produces a QAbstractSocket::UnsupportedSocketOperationError on Client side. On server side I don't get any notification that a new client has connected.
The tool "Dependencies" shows no difference in dll's, a test without SSL worked fine as well as connecting from same network with my developer machine.
As is works fine with my developer machine I assume something is wrong/missing on the other Windows 10 machine. I have installed OpenSSL 1.1.0f on it but I have no idea what else to look for.
I found out that this was an encryption problem from QT. I solveded it by downloading the dll's (libcrypto-1_1-x64.dll, libssl-1_1-x64.dll) together with precompiled(!) MySql driver for my QT version from https://github.com/thecodemonkey86/qt_mysql_driver/releases and stored it into the application root folder. Additional I copied into here the "tls"-folder from qt/6.3.0/plugins/.
I've upgraded the Windows 10 to 1809 for test purposes and now the SCCM client has the problem that it needs a very long time until it starts and then aborts with the error:
Loading Software Center returned error code 0x80041001 (-2147217407).
Unfortunately I do not really find much under the error message, are there any solutions for that?
If I reset the Windows installation and then install the SCCM client everything works fine again ...
System information:
Version 1810
Console version: 5.1810.1075.2000
Site version: 5.0.8740.1000
Small addendum, after I did the following everything seems to work again:
SCCM Upgrade
SCCM client deinstallation
WMIRepair (Roger Zander)
Reinstall SCCM client
We recently implemented MobileFirst 7.0 IF201609291531 iFix and started experiencing a windows 8 app connection issue when a new runtime is created on the server and a windows8 app uploaded:
The windows8 App is deployed on a device via App Center
When the windows8 app attempts to connect, the server log records the message:
FWLSE0332E: The application some_app for the environment windows8 does not exist on the server. Cannot register this client.
I double checked that the app was in fact deployed on the server, I confirmed the version number, app id, and server details in the wlclient.properties file. The same build process also deployed an Iphone and Android app, both of which works and connects correctly.
I decided to change the windows8 application access to "Active, notifying" just as a test. The console did not save the message, and when I looked at the log, it recorded:
000000e5 com.ibm.worklight.admin.actions.BaseTransaction E Result: newruntime: mobileFirstServer///XX.xx.X.xx: There is no deployed application with name 'some_app-windows8-2.0.25'
I managed to set the application access for both the iPhone and Android apps without any problems.
This behaviour is only evident on any new runtimes created since the ifix was installed. When I upload the windows8 app to a runtime that existed before the ifix it connects as expected.
I've tried this on multiple MobileFirst servers with the ifix loaded and the behaviour is consistent across all of them.
My build setup is as follows:
The binaries are built using MobileFirst CLI (initially with IF201607241420, and then with IF201609291531) using Jenkins
The binaries are then uploaded and deployed to the MobileFirst server using the worklight_build.xml ant script
Server OS: RHEL 7.0
MobileFirst configuration: standard Liberty profile
DBMS: MySQL
Has anyone experienced this before? Could it be a database or permission issue?
Our sys admin is planning on removing the ifix on Monday, after which I'll run another test to see if it resolves the issue. I'll post the result of the test here.
It's clear you are experiencing some kind of a regression with the latest iFix. I suggest then that you'll just open a PMR. This is not a question for Stack Overflow.
I have found a work-around for the issue.
It seems the issue occurs if a new runtime is deployed via the ant scripts, and the application is also deployed via ant scripts (no manual deployment was done). When I manually deployed the application via the web console it resolved the issue. This manual upload seems to only be required once, after that the app continued to connect as expected even with subsequent ant uploads.
I have installed Moodle 2.4 server on machine with window 7 by downloading the package available in moodle.org which includes XAMPP server .It is installed properly and is accessible from all client machines with windows operating system. The problem is that when we try to access the server from machines having Ubuntu it is not accessible. Pl help what to do.
You should not use that XAMPP package to install Moodle on a production server. That package is only suitable for "localhost" test installations of Moodle.
Windows 7 is also not suitable as a server operating system.
Also, check that you've got the correct '$CFG->wwwroot' value in your Moodle config.php file. "localhost" won't work.
Please explain what happens when a Ubuntu user tries to access that Moodle site. What happens? Do they get an error message?