RE: problem connecting to dbase from webservice with impersonation

Thanks for your followup Nadav,

Seems the problem has been quite narrowed. So it is only when performing
query against the SQLMembershipProvider 's database table does the error
occur. Are you currently put the membership's database tables in the same
database with your other application data?

I think you can run SQL profiler at SQLServer side to see what is output
when the Validateuser is called at client-side, you can also compare it
with your normal database access to see what's the difference between them
in SQL profiler trace.


Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.