Ver Mensaje Individual
  #2 (permalink)  
Antiguo 16/07/2002, 01:21
jjlallana
 
Fecha de Ingreso: enero-2002
Ubicación: Zaragoza
Mensajes: 144
Antigüedad: 23 años, 4 meses
Puntos: 0
Re: Microsoft JET Database Engine error '80004005'

Por si te sirve (1):
Problems Accessing Remote Machines
Common symptoms
"Microsoft OLE DB Provider for ODBC drivers error '80004005'" error received when attempting to open an Active Data Objects (ADO) connection.


ASP code that worked fine when the database was located on the IIS Server no longer works when the Microsoft SQL Server or Microsoft Access database is moved to a remote machine.
Description
One of the most common types of problems occurs when ASP attempts to access resources located on remote machines. A good example of this is using ADO to access either Microsoft SQL Server on a remote machine or a Microsoft Access .mdb file located on another Windows NT machine. The problems stem from the fact that ASP is operating in the context of the IUSR_MACHINE account. On servers that are not primary or backup domain controllers, the IUSR_MACHINE account is a local account. Since this local account is not recognized on the remote machine, access is denied to the database.