SUMMARY

Getting Database Name not found error when trying to view application.

CAUSE

The problem with the ASP.NET website not finding the name is due to the fact that private 'Database Names' are stored in the registry on a per-user basis.  The ASP.NET process runs under a different user profile than a Windows executable would when launched on the server.  The database name created by the programmer is stored in a 'private' registry entry accessible only by his user profile, so the IIS process cannot access Database Names configured to be accessible to only one user.

RESOLUTION

The solution to the problem is to create a PUBLIC Database Name. You do that by Prepending the keyword *Public to the name like the following dialog shows.  In this case the program would use the name 'DBASP' (or whatever you called your database).  Because the DB is Public, it is stored in the 'Machine Register' (HKEY_LOCAL_MACHINE). Regular DB Names are kept in the 'Current User' registry (HKEY_CURRENT_USER). Please see the help documentation regarding Public Database Names, especially the security section.

You must now change your AVR applications to reference your database name with the "*Public/" preamble; e.g., DBDESC("*Public/DBASP").