Strange behaviour

HCL Domino Domino Forum
1

We are experiencing a strange situation.

We have users that go from one site to another with a laptop. On each site where they connect, they use a different Server, but, each server has the same replicas of our applications.

Whenever they open a document, on certain databases, they get errors like:

1 - illegal parenthesized reference:

2 - not a sub or function:

3 - Error 28363: user defined error

4 - Unable to locate field

5 - the linked document cannot be found in view `

When the user gets one of those errors, he can’t open the document.

Those applications are also accessed by non-roaming users. They never experience such problems.

We tried a lot of administration tools: compact, fixup, etc. nothing seems to work. The only thing that seems to temporarily solve the problem is to delete the windows profile (local and on server), where the notes data directory of the user is stored.

Oddly, this error seems to be linked to a particular site, depending on the user. So if user 1 goes from A to B and C, once he gets the error on B, he will experience it until we fix his windows profile. If he tries to connect (veeeery slow) to A or C from B, everything’s ok. And user 2 might experience the same on C… or not at all.

If anyone has any good idea to help us solve this situation, please, you’re welcome :slight_smile:

2

Subject: Strange behaviour

What do you do when you ‘fix his windows profile’?

I suspect there is something about what your doing that points to the root problem.

Do your lotus functions point to servers? Any chance there’s something screwy about these users and they’re trying to connect to a server they can’t see which is causing the functions to fail until you ‘fix’ their profile?

Have you tried running these apps with the debugger turned on so you can see why the code is failing?

3

Subject: RE: Strange behaviour

What I mean when I say ‘fix his windows profile’ is completely erasing it.

Some functions do point to servers, but always with @server or session.currentdatabase.server. We can’t afford to put a the name of a server in our code as we have tons of servers.

I’ve done some debbugging and the problem is that the error pops even before the debugger starts, so it looks like some code loading problem (hence the many compile errors - that shouldn’t appear at that moment, these kind of errors only appears at compile time).

By the way the users access servers they see because some databases fail, some others don’t, and they all reside on the same server. And the server they are trying to connect to is the right one.

We only have the error when opening documents.

Thanks.