I have a web service and a deployment project. Inside the deployment
project, is a custom action to create some database related items such as
stored procedures. I have this packaged as an msi, and can run the
deployment on win2k, win2k server, and winxp without problems. The database
related part of the custom deployment action uses integrated security to
login (SSPI). When tracing the deployments using sql profiler from any of
the machines, I see the login to the database as the user running the msi
package.
When using the same deployment package on win2003 server, the database
connection now uses "domain\machinename$" instead of the logged in user
running the package. This then fails because the domain\machinename$ does
not have any permissions to the database. The install is being done thru
terminal services and the logged in user is a domain admin.
I am pulling my hair out trying to figure out how to get this to use the
logged in user. I do not want to put in the sa password and log in that way,
because the web service will be deployed to different servers and databases.
Right now I have one service and a deployment package that can be deployed
anywhere (except win2003).
Any help or recommendations on where to look would be greatly
appreciated, or if there is a better user group to post to.
Thanks,
Jeff
