Xpages can't load, Error 500; java.util cannot be resolved - xpages

I recently moved a couple of applications to a server that is running Domino 9.0.1FP8 (JVM version: JRE 1.8.0 Windows Server 2008 R2 amd64-64). Since I did this I've been unable to load any, but the most basic of Xpages. I get the "Error 500 HTTP Web Server: Command Not Handled Exception" page.
Via the ...IBM\Domino\data\IBM_TECHNICAL_SUPPORT\xpages_exec I get Exceptions such as:
The type java.util.Comparator cannot be resolved. It is indirectly referenced from required .class files
The type java.util.Map$Entry cannot be resolved. It is indirectly referenced from required .class files
The import java.util.Arrays cannot be resolved
I'm also getting the following Errors in the "Problems" tab in Designer:
"The project was not built since its build path is incomplete. Cannot
find the class file for java.util.Comparator. Fix the build path then
try building this project"
"The type java.util.Comparator cannot be resolved. It is indirectly
referenced from required .class files"
Is there a reason the java.util is failing in Java 1.8? Is there anything I can do? Thanks for any help.
Dan

This problem occurs when Domino Designer 9.0.1 FP8 attempts to compile against a Java8 JRE. The version of eclipse in that Designer install does not know how to parse some of the runtime jar files in Java8. The workaround is to compile against a Java6 JRE instead. There were changes in the Domino Designer installation as part of SPR#BGLN9PXEVM to change the configuration of the preferences in Designer to point to a Java6 JRE instead of using the default JRE. If there was some install problem or you manually modified your preferences, you may need to manually re-apply the workaround as follows.
In Domino Designer, menu File, Preferences, Java, Installed JREs.
There should be 2 listed JVMs with paths like so:
[x] jvm C:\Notes\jvm1.6\
[ ] Notes 8.5.1 VM (locked) C:\Notes\jvm
If your entry named "jvm" is incorrectly pointing to the C:\Notes\jvm\ folder instead of the jvm1.6 folder, then you will need to edit it to point to the jvm1.6 folder instead.
On the Domino Designer team we are investigating potentially upgrading the eclipse version in Designer, so that it might be possible to compile against a Java8 JRE.

It sounds like the installer has not installed successfully. There's no reason java.util packages should be failing. I would recommend running the installer again, making sure all services are stopped prior to running it. That will ensure that anything that needs replacing isn't locked by another process.

Related

Compile error in java script library for Xpages

Notes 10.0.1 FP3 causing below compile errors, but Notes 9.0.1 FP10 SHF81 doesn't have the same issue. Is there a way to resolve this without having 9.0.1 installed?
1) Cannot nest 'IBM/Notes/framework/rcp/eclipse/plugins/org.eclipse.swt.win32.win32.x86_3.105.3.20190810-1410'
2) Container 'IniVariable Java Library' references non-existing library 'IBM\Notes\Data\SwPDFC\java\ver6.20.000\swpdfc-2.0.0.jar'
It looks like your using the SWING PDF Converter. Maybe you should try to reinstall the Converter or maybe you have to look if there's a newer version that is compatible with Notes version 10. As stwissel pointed out Notes version 10 uses Java8 and OpenJDK, so maybe a newer version of the SWING PDF Converter is the solution.
When you create a new blank database it automatically includes 'Plug-in Dependencies' which appear to pull in everything in the 'Notes\framework\rcp\eclipse\plugins' folder which includes the referenced plug-in shown in the error message. The problem is when you add a new variable classpath entry and select ECLIPSE_HOME, then navigate to the same 'Notes\framework\rcp\eclipse\plugins' location.
If you select a different folder for your new variable classpath entry or remove either the 'ECLIPSE_HOME' or 'Plug-in Dependencies' from your Build Path Libraries the error goes away. I have included the below screenshot showing what I mean.
Since the Extension Library was rolled into the Notes core it must now be part of the Plug-in Dependencies causing a conflict when being added via the IniVariable option for those using 10.0.1. I still need to confirm the build path with a co-worker who has Notes 9.0.1 FP10 SHF81.

Getting "Gradle sync failed: Please use JDK 8 or newer" under version 3.3

I checked every thread related to that error. But I couldn't find the appropriate answer. I have additional error too. Check out the screenshots.
Posts I came across recommending fixing JDK pathing issues through "Switch IDE book JDK..." or "Project Structure".
For me, in Android Studio 3.0, "Project Structure" would no longer open, so I upgraded to 3.1. Afterwards, it still had the JDK version error, but now it let me open "Project Structure" from the "File" menu, where I was able to correct the JDK, SDK, and NDK locations and versions.
There were still several build errors after that, but clicking the recommended fix in the build output window eventually installed everything I needed. Once it managed to synchronize correctly, it also upgraded Gradle to version 4.4. That then required new build tools and so forth.
Though instructions directly, may not help everyone, but it points to configuration corruption. So, if you cannot just upgrade to get around it, I recommend making backup copies of your Android Studio settings (generally in your user's home directory like ~/.AndroidStudioX.Y), as well as your project .idea (generally in the root of your project), then deleting the originals. If that is still not enough, purge the configurations again and reinstall Android Studio.
Note: I was going back into an old project so several warnings about deprecated features being removed in 2018 had to be dealt with.
error window
Here's what worked for me!
1. First verify that your JDK is indeed higher than JDK8
jdk version
2. Press "Ctrl+Alt+Shift+S" to open project structure
enter image description here
3. Then I selected "Use the embedded JDK"
4. Click OK and retry it.
That should solve it.
I was facing same problem, getting these two kinda errors:
SDK path should not contain white space.
Gradle sync failed. Please use JDK 8 or newer.
Solution for me was to set proper SDK path with no white space in path first and than choose JDK path. After setting path I've synced the project and tada it worked...
Thanks.

orchard cms: module package not installing

Setup:
I have created a module that works fine in the solution where it was created, ie, the orchard source code. I then package it up using package create.
Edit: I now realize that the problem appeared IMMEDIATELY after installing visual studio 2012.
Problem:
If I now install the module on a different app using the package and install from file, all the alerts show the module is installed, it appears in the features list, it is enabled... but there are no menu items, no entry in the migrations table, nothing.
Edit: Nothing appears in the logs. The files are, however, installed correctly in the modules folder of the site.
Question:
What could be going wrong that stops the module being properly installed using the package given that the module works fine in the source code solution where it was created??
Any suggestions?
Edit:
How could installing visual studio 2012 have affected Orchard?
I notice that installing visual studio 2012 resulted in various bits of sql server 2012 being installed at the same time. Could this be relevant? EG, is this why the migrations code never runs?
Edit on the basis of Bertrand Le Roy's comments (see below this question):
BertrandLeRoy says that having ASP.NET MVC 4 installed in the GAC, as well as Razor 2 (both of which came with VS 2012), is the problem.
He suggests upgrading to Orchard 1.5.x.
However:
I have tried using a new install of Orchard 1.5.1, and the problem is the same:
Creating a new module using VS 2012 and Source Code for Orchard 1.5.1 and the module appears correctly when running the orchard site from VS.
Creating a package and then installing that into an Orchard 1.5.1 site, eg, using WebMatrix, running and then installing the package has the following effect:
2.1. The alerts in the dashboard tell me that the package has installed correctly.
2.2. However, enabling the feature does nothing.
2.3. This is hardly surprising, as installing the package has not even run the migrations.
The last test I can do is to see if the package runs on a web server that doesn't have asp.net mvc4 installed. I will post back once that is done.
However, the main point is that using Orchard 1.5.1 produces the exact same result. So, if the problem really is the fact that MVC 4 and Razor 2 are on the machine, then Orchard 1.5.1 is not solving it.
Ie, what will happen when I install mvc 4 on the web server as I will inevitably have to for other, non Orchard apps?
I experienced the same thing on version 1.8.1. That is, the module appeared to install fine, but it didn't actually perform migrations or load correctly.
Initially, I saw nothing in the log to indicate a problem. However, after adjusting the /Config/log4net.config file to log ALL instead of just ERROR messages. I got this:
... Orchard.Environment.Extensions.Loaders.PrecompiledExtensionLoader -
- Extension "Transformalize" will not be loaded as pre-compiled extension
because one or more referenced extension is dynamically compiled
The part saying my module "will not be loaded as pre-compiled extension because one or more referenced extension is dynamically compiled" seemed to explain why my module wasn't loading. So, I Googled and found this documentation regarding the Orchard module loader and dynamic compilation. It's a bit complicated at 2 AM, but what I gathered is my module's reference to another module (Orchard.Autoroute in this case) caused the log message (above) in the production environment. I removed my module's reference and dependency on Orchard.Autoroute, and then it installed fine.
The documentation explains how modules are dynamically compiled and how the settings in /Config/HostComponents.config can change how things work.

Problems creating a Java Mobile Application project

I have installed the Netbeans 6.7 IDE with Java ME included, but cannot create a Mobile Application project from the Java ME category. When I select the project type the wizard stops at "Finding Feature" with the message:
Not all requested modules can be enabled:
[StandardModule:org.netbeans.modules.mobility.end2end.kig jarFile:C:\Program Files\NetBeans 6.7\mobility8\modules\org-netbeans-modules-mobility-end2end-kit.jar.
I am attempting to run this on Vista Home Premium. I have tried to run the IDE as Administrator with no luck.
I am at a loss for where to go next as I cannot seem to find any information regarding this issue. Even if you don't have the solution any insight into this error message would be helpful.
I am unable so far to get the project running via the Netbeans IDE install. I have, for the time being, installed the Java ME SDK which includes a very stripped down version of the Netbeans IDE for mobile development.
I originally had some issues starting the SDK as well on Vista. The IDE reported that it could not connect to the device manager on localhost. After some searching I found this link: Java ME SDK Startup Problem which suggests changing the hosts file localhost entry from IPv6 to IPv4. The fix worked perfectly and I can now compile and run code in the emulator.
This is not an optimal solution as the SDK does not include the visual design tools, however I am able to get a basic project going in the mean time.
I have given up on the 6.7 version and have instead located and installed 6.5.1. This previous version has been working just fine and seems to do everything I need.
I ran into the exact same error today while installing NB 6.8 beta. To resolve it we need to install two plugins:
Java Web Applications (as mentioned by Ali above) and
Sun Java System Web Server 7.0
Note that these two are part of the Category called "Java Web and EE" hence the confusion that we need to install Glassfish App Server. But we need these two plugins because they are required for debugging using breakpoints in emulator. Netbeans runs a web server when we do breakpoint based debugging.
Also note that the Java Web applications needs SOAP Web Services and JavaScript Debugger plugins to run and so these plugins are also installed when you try to install it.
You also need to install "Java Web Applications" plugin.
Tools->Plugins->Available Plugins
If the module is present, you should try unzipping it to check its content makes sense.
You should also be able to rebuild it from Netbeans sources.
You can also try to figure out why this happens by debugging the module loader inside Netbeans from its sources, using another IDE, presumably the latest version of Netbeans you can find without the issue.
If the module is missing, you might want to get the missing jar file from an installation of a previous version of Netbeans, see if it is compatible.
6.5.1 isn't missing any module.
back in version 5.5, the mobility module had to be downloaded and installed separately from the main IDE.
If you want to consider using Eclipse for developing your J2ME app...I've written a post related to that some time ago: here.

Error: The Side-by-Side configuration information in "BLAH.EXE" contains errors

This is the error Dependency Walker gives me on an executable that I am building with VC++ 2005 Express Edition. When trying to run the .exe, I get:
This application has failed to start because the application configuration
is incorrect. Reinstalling the application may fix this problem.
(I am new to the manifest/SxS/etc. way of doing things post VC++ 2003.)
EDIT:
I am running on the same machine I am building the .exe with. In Event Viewer, I have the unhelpful:
Faulting application blah.exe, version 0.0.0.0, faulting module blah.exe,
version 0.0.0.0, fault address 0x004239b0.
Open the properties sheet for your project, go to the Configuration Properties -> C/C++ -> Code Generation page, and change the Runtime Library selection to /MT or /MTd so that your project does not use the DLL runtime libraries.
The C/C++ DLL runtimes used by VS2003 and up are not automatically distributed with the latest version of the OS and are a real pain to install and get working without this kind of problem. statically link the c-runtime and just avoid the total mess that is manifests and version specific runtime dlls.
I've had this problem. The solution has two steps:
1. Compile your program in "Release" mode instead of "Debug" mode (there's usually a combo-box in the toolbar)
2. Download from Microsoft their Redistributable Package of runtime components. Make sure to download the x86 edition for 32-bit computers and the x64 edition for 64-bit computers/OSes. Install this package on the target computer, and your application should run fine
P.S. This is a SxS thing
P.P.S. Alternatively, use a different compiler (like GCC, for example with Dev-Cpp) to compile your program's source, and your headaches will disappear.
Sorry to bump an old question, but I was able to get around this exact issue and thought I'd post a solution in case someone else needs it...
Even after installing Microsoft's redistributable DLLs I was getting this error, the fix was to copy the
C:\Program Files\Microsoft Visual Studio 8\VC\redist\x86\Microsoft.VC80.CRT
folder into the application's directory on the target PC. After that, no more problems.
BTW, the DLL that was giving me issues was a 3rd-party DLL that had never had problems before on over 100 other computers... go figure.
Run Event Viewer: it'll have more information.
Probably you've attempted to run your program on a machine that doesn't have the VC redistributables installed, or you're attempting to run a debug build on a machine that doesn't have Visual Studio installed (the debug libraries aren't redistributable).
I have had the same issue with VS 2008-built debug binaries on other winxp sp3 machines.
I first tried installing the client machine with vc redist package,as it seemed sensible. Annoyingly, it didn't work.
I tried copying all the dependent dlls to the application's directory - still didn't work
After being struck over this issue for hours, I found that the latest VS builds require manifests and policies to link with the dlls. After copying them into their respective "C:\WINDOWS\WinSxS\" folders, I got it working.
The problem was caused due to the fact that the vc redist package did not install debug versions of dlls, they somehow thought its up to the programmer to figure out.

Resources