Certificate table does not contain enough valid certificates

We are having some trouble migrating an LEI server to a new host. As a way to get the application working again, we are trying to use a development server as a temporary measure. The problem is that the development server is just a server sitting under someone’s desk and not at all incorporated into the corporate hierarchy. The id that we need the LEI server to use was issued from one of the corporate servers.

I put the needed id on the dev server and tried to open a db using the client. I got an error message:

“The certificate table does not contain enough valid certificates to verify the public key of its owner. Do you want to access the server anyway? Yes/No”

So, I clicked Yes and got this message:

“Server Error: The certificate table does not contain enough valid certificates to verify the public key of its owner.”

And, would not open the server’s data directory to list the databases.

I switched back to the server’s admin id, opened the admin client and cross-certified the id. But, I am still getting the same errors when I try to open a db on the server using the other id.

Any one have any ideas about what I should do to allow the id access to the dev server?

Thanks,

Steve

Subject: certificate table does not contain enough valid certificates

Please post the hierarchical names of the server and the active user. Did you create the cross certificate in the server’s address book or locally?

Subject: RE: certificate table does not contain enough valid certificates

I’m sorry I didn’t include this.

The server name is chem1/aaa.

The user id is App Admin/Raleigh/AAA.

I considered after I posted that it might be because the domains are the same except in different case.

When I cross certified it, I was on the server using the server’s id on the admin client. I opened the server and clicked cross-certify on the right-hand menu bar. I don’t see a user in the address book on the server after cross-certifying.

Subject: RE: certificate table does not contain enough valid certificates

As suspected, your problem is that both certifiers have the same name (names are case insensitive). You should choose a different root certifier name for your test environment.