Notes/Domino XPages Development Forum

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

~Hal Opwesterynds

Jan 6, 2013, 2:30 PM

6 Posts

Resolved

Exception

Category: Server Side JavaScript
Platform: Windows
Release: 8.5.3
Role: Developer
Tags: Exceptions Crashes
Replies: 1

Hi,

I have read version 8.5.1 have a bug in which the following error uses to occur:

[TypeError] Exception occurred calling method NotesSession.getDatabase(string, string) null

But my current version is 8.5.3 and I have faced this error too.

The code below is on Value property of a ListBox on a ComputedItens block.

1: var dbName:NotesDatabase = session.getDatabase("myServerName", "aplicat/cad.nsf");

2: var v:NotesView = dbName.getView("sysFuncAbb").getColumnValues(0);

3: return v;

There is two situations.

The error occurs at line 1 of code when the second parameter of getDatabase method have a slash, as demonstrated 'aplicat/cad.nsf".

The same error occurs at line 2 of code when the second parameter of getDatabase method have a backslash, as "aplicat\cad.nsf". Line 1 doesnt rise an error in this case.

Important: This issue occurs only on navigator, on web, but it doesnt occur on client of Notes.

Is it really a bug?

Thank you all.

~Hal Opwesterynds

Jan 6, 2013, 2:57 PM

6 Posts

Re: Exception

Unbelievable!

Im not sure yet, but I think I solved this issue.

The ACL of the database had an Anonymous entry with Author rights to it. This entry is necessary in order to a local database can be tested in a navigator as it would be accessed on web.

I was testing the database on local access and the error did not occur, but when I copyed it to the server that error occurred.

I removed this entry and the error did not appears anymore! The Xpage works on client and web now perfectly.