Hi there,



I am having a hard time setting up a trusted connection from an ASP 3 

application to SQL 7. As far as I know, all I need to do is use the 

following connectionstring:



"Provider=SQLOLEDB;Server=MachineName;Database=DatabaseName;Trusted_Connect

ion=yes"



The website is (under Windows 2000) setup like this:



- Application runs in Medium isolation (pooled) or in Low isolation,

- App doesn't use custom components (script only),

- SQL Server is on the same machine as IIS and ISR_MachineName has been 

added as a user for the database,

- Anonymous Access is the only way allowed to connect to this server,

- Webserver runs under the context of IUSR_MachineName.



Now on some pages, I receive an "Login failed for 

user 'MachineName\IWAM_MachineName' message.



Indeed IWAM is not a user of the SQL database.



How is this possible?? Why does IIS impersonate IWAM instead of IUSR. IWAM 

should only be used for out-of-process websites, right?? And it's even 

weirder: this only seems to happen the first time a page is hit. After 

that, apparently the connection is re-used and no error is raised. The 

page is not cached by IIS, because datadriven content is updated on the 

page.



Any suggestions????





Imar