I'm getting the message "Logging: Couldn't initialize from PropertyFile; activating fallback ..." on a fresh install of Domino 9.0.1 FP8 with the latest OpenNTF Domino API 4.0.0. There's another question with the same issue, but the solution was a fresh install.
After the Domino install we created the updatesite.nsf, imported the OpenNTF Domino API 4.0.0. Clicked, Action, Sign All Content, then added the OSGI_HTTP_DYNAMIC_BUNDLES=updateSite.nsf to the notes.ini and rebooted the server.
With a little more digging it seems the IBM_TECHNICAL_SUPPORT/org.openntf.domino.logging.logconfig.properties file is missing from the OpenNTF install or not being created.
There are no applications running on this server, other than the basic Domino default applications you would have from a fresh install.
Also, this isn't a fresh re-install. This is a brand new Win 2008 R2 server with a new Domino 9.0.1 FP8 install.
Related
At present one of our ACI (SonarQube 7.7 community edition) is running with Azure SQL Server DB. Now I need to map existing Azure SQL Server database to a new ACI (SonarQube 7.9.6 community edition). I had done but ACI is not running properly and some times events/logs are not stored, and I even tired with to stop & deleted ACI (SonarQube 7.7 community edition) as well.
At our end my main priority is need to upgrade SonarQube version 7.7 to 7.9.X or newer.
Is it possible to upgrade the sonarqube image in the same ACI?
Yes, it is possible to upgrade the sonarqube and here ate the steps to upgrade the Snoarqube.
Download and unzip the SnorQube distribution.
If you're using third-party plugins, manually install plugins that are compatible with your version of SonarQube.
Update the contents of sonar.properties and wrapper.conf files
Stop your old server and start your new server.
Browse to http://yourSonarQubeServerURL/setup and reanalyze your projects to get fresh data.
Here are the links which can give you complete information regarding SonarQube upgradation.
Before you Upgrade.
Upgrade Guide.
I recently installed Liberty Core server, created a new Profile, installed MobileFirst Platform Server and deployed a MobileFirst runtime environment with the Server Configuration Tool in MacBook.
Instead of installing in default directory(Application/ibm/*) I choose to install under custom directory (Users/username/LibertyCore).
I started the server manually installed adapters and *.wlapp from worklight console.
Instead of doing this manual deployment I want to do it from command line? My understanding is I have to use MFP command line utility.
I installed MFP CLI utility then parsed to the App Project folder to build and deploy to currently installed Liberty Core server I see issue with MFP PUSH it says server is not started though server is running.
So when I do MFP Info I found that CLI is pointing to completely different set up. How can I make CLI to point to currently installed Liberty Server.
Note that you can run "mfp help" to see all available CLI commands.
There is the command "mfp server". Using this command you can add additional server definitions: "mfp server add". Run the command and follow the on-screen instructions to add a server definition for your remote server...
Once you've added it, you can use "mfp push your-remote-server-name" to push the artifacts to the remote server.
Whenever I try to install SQL Server 2012 Express with Advanced Services I am getting this error:
I have tried both version (32-bit/64-bit) and re-downloaded multiple times.
How can I solve it ?
Check if you have .Net framework 4 installed at your machine. If not - download it and install it and then try again with SQL Server.
Also check this bug at Microsoft site about .Net framework 4 (there is workaround explained in the bug).
FWIW, I just downloaded and installed SQLEXPRADV_x86_ENU.exe from HERE on a vanilla Win7Pro/64 VirtualBox virtual machine and encountered no errors.
Edit
I also installed SQLEXPRADV_x64_ENU.exe from that same location on an older Vista machine. The SQL Server installer told me that it needed some new .NET components, then it proceeded to download and install them. I didn't need to manually install anything ahead of time.
Also perhaps worth noting:
Both of the machines on which my installs were successful had no anti-virus software installed. (They are development boxes behind a firewall and I don't do email or web surfing on them.)
I have downloaded the IBM Worklight Enterprise Server, trying to install Worklight server with Apache Tomcat and deploy my worklight application in my remote server.
It is mentioned in the readme file, that I need "IBM installation Manager" to install the "IBM Worklight Server".
I downloaded the IBM installation Manager and followed the steps in the readme file and installed the Worklight server in my local machine.
Installed Apache Tomcat in my remote machine and copied the worklight- jee-library.jar to the $TOMCAT_HOME/lib directory.
Is this the right way to install IBM Worklight server ?, or is there any other way to install "IBM Worklight Enterprise Server" in my remote machine from the command line ?
I am stuck at this place
Any help would be greatly appreciated.
Thanks
Suren
No, it is not the right way. Specifically, you should not copy anything into Tomcat. The installation does it for you.
The steps to follow are
Install the IBM Installation Manager version 1.5.2 and onward (available on the web). This is a one time step.
Download the Worklight server package from IBM
Point the IBM Installation Manager to the Worklight server package (File - Preferences in main screen).
Start the installation.
The installation will ask you for a path to Tomcat and will install everything that is needed inside Tomcat.
If your server does not have a GUI, the steps 3 and 4 are replaced by the so-called silent installation.
Quite often you won't have access to the server GUI but you can simply redirect the X display output to your desktop and launch IM. Ie. if you are running Linux export DISPLAY=xxx.xxx.xx:0.0
If you are running Windows just use Exceed.
I'm having problems migrating a PowerBuilder application from XP to Windows 7.
We've built the application in PowerBuilder on Windows XP, and when we attempt to install components in to component services on Windows 7 machines, we get compatibility errors. Everything works great on Windows XP. But I think because the DLL's on 7 are so different, it's having problems.
If the program was built using a PowerBuilder IDE in a Windows 7 environment, would that possibly fix the problem?
The application is divided into
- a server component running on Server 2003
- a client component which installs sucessfully on Win7
- proxy components that are generated into an MSI when the server components are installed.
The problem is only the proxy. The MSI doesn't want to work on Windows 7.
Without the proxy installed on the client desktops, the client can't communicate with the server.
When I run the MSI in compatibility mode on Windows 7, I get some details of the error. Here they are
Program Compatibility Issues found Incompatible Application Fix
application CCS_Proxy_XP_Exports
Issues found Incompatible Application CCS_Proxy_XP_Exports is
incompatible.
Fix application CCS_Proxy_XP_Exports Provides steps to fix the
incompatible application. CompatMode CompatMode UserVerifySolution
User Verification of Solution Verify_NO
Detection details Collection information Computer Name: ##########
Windows Version: 6.1 Architecture: amd64 Time: Wednesday, November
14, 2012 11:56:36 AM
Publisher details Program Compatibility Make older programs run in
this version of Windows. Package Version: 1.5 Publisher: Microsoft
Windows
Program Compatibility Make older programs run in this version of
Windows. Package Version: 1.0 Publisher: Microsoft Corporation
If I view more details on the event log, I get the following
“Product: Client Communications (Application Proxy) -- Error 1928.
Error registering COM+ Application. Contact your support personnel
for more information.”
General idea
Actually dll on the win7 platform are not different from previous ones. There can be differences related to the multiple and different C runtimes that live now in the WinSxS dll-hell directories but this should not impact powerbuilder (as I can say from my 11.5 classic release experience).
I suspect that you might have some problems related to the UAC and or ACL management. I recently upgraded some legacy PB applications by adding compatibility to the Vista / Win7 specifications.
In short : the application must run without needing administrative privileges, and must not try to modify data in privileged places like c:\ or c:\windows.
Thus everything must no more be installed in program files directory. The application binaries can be deployed in program files but if the application need to create / modify some files they must be deployed in a ProgramData subdirectory for user-shared datad and / or in the local user data files for the private data. The application has to be modified to create or find the files in the correct directories. If you do not comply to the standard, the file virtualization mechanism can hide a lack of rights and can simulate the files in a VirtualStore directory in the user local data but is just a workaround and it provides some other problems.
Com+ error
Given you error messages, if the proxy is also a PB application, given the fact that PB only produce 32bits binaries and that your system is a 64bits one, maybe that the tips to register a 32b COM+ onto a Win2008 could help you?
Thought, your proxy exe/dll file does not have manifest or manifest does not contains compatibility section. Try to add compatibility info to manifest.