Notes/Domino XPages Development Forum - can not open *any* xpages in one database

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

~Maria Mintooverflar

May 28, 2014, 7:14 PM

18 Posts

can not open any xpages in one database

Category: Other
Platform: Windows
Release: 8.5.3
Role: Developer
Tags:
Replies: 1

I'm making changes to a database I've been working on for some time. I clean it often (sometimes several times a day) and have backups. For some reason yet unknown, now I cannot open ANY xPages in this database anymore. I can open xPages in other databases on the same server, but not this one.

I did install the Extension Library today in my Designer client, but am not using any elements of it yet. I was trying something in a computed field that may have gone into a loop, so I removed that computed field. But that's just on ONE xPage, and NONE of them will open in a browser now. I can open views and forms of this database in a browser, so it's just the xPages.

I've already tried cleaning it, rebuilding it, removing it from Designer, removing all the local xsp files, cleaning again, but so far, no luck whatsoever. I can go back to my last backup, but I'd really like to know what's causing this.

Has this ever happened to you?

~Cheryl Elhipigenlen

May 28, 2014, 7:43 PM

366 Posts

Some things to check

Make sure that the under Application Configuration / Page Generation in the XPages Libraries section that the box to use the ext lib did not get checked. If this is checked and the ext lib is not installed on the server then no pages will load as the application can not load.

Check the specific XPage that you added the custom control to and ensure the the ext lib namespace did not get added to the top.

Finally you can check the console log or error log in the C:\IBM\Domino\data\IBM_TECHNICAL_SUPPORT folder. Sort by date/time and see what error the application / page is throwing.