Error rendering macro 'rw-search'

null

Downloads

Versions Compared

Old Version 17

changes.mady.by.user franz walder [panagenda]

Saved on

compared with

New Version 18

changes.mady.by.user franz walder [panagenda]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Security access issues (server access, database access, database access level)
  • Network access issues
  • DXL Exporter issues


Troubleshooting Access and Network Issues

Security and network issues should be relatively easy to solve, because they are in direct control of the personnel who administers the Domino servers and the network. After troubleshooting, the databases need to be re-scanned manually using the re-scan options on the same page.

Network Access Issues

To scan the application design, the Notes ID with which iDNA runs needs access to the server the database resides on. The Domino server must be accessible over the network from the appliance. In an optimal scenario, the server's common name can be pinged from a console in the appliance to avoid name resolution issues.

Common problems are:

  • "Unable to find path to server" / Error 2051

  • "Server not responding" / Error 2055

  • "You are not authorized to use the server" / Error 2350 or 18734

  • "Remote system no longer responding" / Error 2562

  • "Network operation did not complete in a reasonable amount of time" / Error 2567

  • "The remote server is not a known TCP/IP host" / Error 7267

  • "The connection has been reset by the remote TCP host" / Error 7285

  • "The connection has timed out" / Error 7286

  • "The server is not responding" / Error 18439


The solution for these issues is to make sure the iDNA has a stable network connection to the server and name resolution works flawlessly. However, sometimes network hick-ups occur, so in many cases a simple re-scan of databases with these errors might solve the issue.

Sometimes, what seems like network errors can in reality be access issues. An example here is the well known behavior of the Notes Client saying "Server not responding", when in reality a server access issue exists (see next paragraph).


Security Access Issues

To scan the application design, the Notes ID with which iDNA runs needs access to the server and the database in question. In the DBs ACL it should at least have Designer rights.

Common problems are:

  • "Insufficient access level [EDITOR/READER/AUTHOR]": the Notes ID can access the DB, but does not have required Designer rights in ACL
  • "Insufficient permission access resource" / Error 4060: the Notes ID can access the server, but cannot access the DB at all
  • "Unable to access server" / Error 4271: the Notes ID does not have access to the server

  • "You are not authorized to perform that operation" / Error 4067: general access error. The Notes ID has insufficient access.


The solution for both issues is to modify server security settings or the database ACL and add the Notes ID with Designer rights. Alternatively, if that is not possible, the Notes ID will utilize Full Access Administrator if available.



Troubleshooting DXL Exporter Issues

...