G
Guest
I've got a very simple ASP.NET 2.0 web application that uses some
SpDiscoverParameterSet with my database queries. It works fine when running
or debugging under Visual Studio.
When I try to run it through IIS, like a real web app, I get a
SpDiscoverParameterSet Failed". This is a security issue, but I don't know
how to:
1) Change the setup of the .MDF file so that it will NOT use integrated
security, but accept an sa id and password
AND/OR
2) Specify a connection string that will solve the problem.
Please don't tell me that I "should not be using sa logins" - and please
don't tell me not to use SpDiscoverParameterSet. I don't want to have to
re-write the code just to get this running under IIS.
Arrghhhhhhhhh... this one day project has turned into a 2 day project, just
because of this silly security issue.
SpDiscoverParameterSet with my database queries. It works fine when running
or debugging under Visual Studio.
When I try to run it through IIS, like a real web app, I get a
SpDiscoverParameterSet Failed". This is a security issue, but I don't know
how to:
1) Change the setup of the .MDF file so that it will NOT use integrated
security, but accept an sa id and password
AND/OR
2) Specify a connection string that will solve the problem.
Please don't tell me that I "should not be using sa logins" - and please
don't tell me not to use SpDiscoverParameterSet. I don't want to have to
re-write the code just to get this running under IIS.
Arrghhhhhhhhh... this one day project has turned into a 2 day project, just
because of this silly security issue.