Client Setup: "The requested item does not exist"

HCL Domino Domino Forum
1

I’ve registered a new user and after running the installation (Java client) I then ran the user set-up. After inputting the user name and server and supplying the user’s password, Notes throws this error “The requested item does not exist” and the set-up cannot proceed beyond this point.

I’m not using the ID vault.

Does anyone know what the requested item might be and how I can get around this issue?

Thanks,

Gary

2

Subject: Workaround

I copied the users Id file to his PC and edited the notes.ini to point to this new file.

3

Subject: Requested item not found

What does your notes.ini say is your keyfilename? Did that file exists?

4

Subject: Follow-up query

Hi Gary,Can you provide more details about the options you selected during user registration.

For example, did you select the ID Vault?

If you look in your client’s log.nsf you might have additional information there, if so please post it as well.

5

Subject: The requested item does not exist

We experienced the above error in the following scenario:

We were setting up Lotus Notes 8.5.2 (Standard Conf) for a new user. After entering the password we got the message that the certificate had not been signed yet.

Closed he client, went to sign the certificate.

Restarted the client setup, entered the password and then received the error “The requested item does not exist”.

Upon inspection of the Notes.ini we found that the KeyFileName as already set

KeyFilename=user.id

However, with the certificate not signed at the first setup attempt, the ID file could not have been downloaded yet…

I removed the user.id from KeyFileName ie.

KeyFilename=

then restarted the client setup, which completed fine.

6

Subject: Client Setup: “The requested item does not exist”

Add server name in the host file.Then client will connect and get the file.

or copy the user id file into local PC.

regards,

siva

7

Subject: possible solution

We encounterd the same problem.

Apperantly we where adding a already existing user. This user was deleted and placed in the Deny-access group.

Removing him from this group solved al login problems.