Home/ Questions/Q 8728119
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T08:33:42+00:00

Connection String: Server=(local);Database=DigitSite.mdf;Integrated Security=true I’ve tried a bunch of other connection strings and they

  • 0

Connection String: 

Server=(local);Database=DigitSite.mdf;Integrated Security=true

I’ve tried a bunch of other connection strings and they have the same error or one that doesn’t even try to logon to the database I provide. I’m not sure if this is an IIS issue at this point or a sql issue or a connection string issue.

In IIS7 the this app pool is set to local system

I have my virtual directory mapped correctly

For Path credentials I’ve used “Application user(pass-through authentication) and I’ve specified a user and neither has worked, In authentication I’ve turned off anonymous authentication and turned on impersonation

In sql I’ve made sure that the user I’m trying to login as has the proper security for this database as “db owner”. I’ve tried creating a user to sign in to sql as (sql Server 2008R2) but I get errors when trying to log that user in. Any suggestions?

This seems to be a common issue but I’ve literally spent more than 5 hours researching this and screwing with settings so I’m a little at whits end on how to get this to work. Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    SQL Server typically uses logical database name, e.g. you create a database on the server instance (or you attach an existing .mdf file in SQL Server Management Studio and give it a logical database name), and you never really have to deal with file names and such.

    So your connection string should really be something like:

    Server=(local);Database=DigitSite;Integrated Security=true

    using just the logical database name DigitSite – not the actual file name (SQL Server will manage the file(s) for you – don’t mess with that!)

    • 0