Xpages HTTP Web Server: Command Not Handled Except

Question

Problem

I have an Xpage working properly on the test Domino server. On production Domino server it can not be opened, Http 500 error displayed.

The two servers has different access control settings in the server document, but the signer of the application (production server) is listed in all programmability restrictions field except "Sign script libraries to run on behalf of someone else" field.

Server log

[25A4:0014-1604] 2012.11.07 14:06:30 HTTP JVM: SEVERE: CLFAD0141E: Error processing XPage request

[25A4:0014-1604] 2012.11.07 14:06:30 HTTP JVM: SEVERE: CLFAD0211E: Exception thrown [25A4:0014-1604] 2012.11.07 14:06:30 HTTP JVM: SEVERE: CLFAD0246E: Exception occurred servicing request for: /applications/application.nsf/xpage.xsp - HTTP Code: 500

[25A4:0014-1604] 2012.11.07 14:06:30 HTTP Web Server: Command Not Handled Exception [/applications/application.nsf/xpage.xsp] CN=First Last/O=Company/C=Country Code

Question

I have searched the net including IBM pages and forums for possible fix this error, but I have not found useable solution. Does anyone now how to fix this error?

Answer 1

Have a look at the latest xpages_exc_*.log file in the data/IBM_TECHNICAL_SUPPORT folder on the server for a more detailed explanation of the error.

If you don't have access to the file system on the server, then install and use the XPages Log File Reader from OpenNTF for easy access to the server log files.

Answer 2

I got this same error when I included the extlib.relational.library with the extlibx.library in the page generations property section of the Xpage property window. If I uncheck the relational library it works fine.

Answer 3

Here I found a fix for the same problem

" The resolution was discovered! We had added some Crystal Reports jar files to the C:\Lotus\Domino\jvm\lib\ext directory. It appears as if Domino and XPages did not like that. Instead, we had to put them in a directory external to Domino and then needed to reference those jar files in the "JavaUserClassesExt" line of the notes.ini. After this was completed, Xpages worked! "

Answer 4

I also had this problem earlier this week on a production 8.5.1 server (without extlib) and it was resolved by restarting the Domino server.

Answer 5

Besides server security settings etc the issue can also be related to application specific settings. E. g. Fulltext index, database properties etc. It might be a good idea to compare these things too. Furthermore I also recommend using the Log Reader for easy access to the XPages log files...