Dear all

I refer a dll in my windows application project , in that dll i make all the db connection and dbrelated operations. I can connect to the sql server from my development pc , but when i make the setup project and install it in another pc i cannot connect to the same sql server. the sql server is in different machine not in my development pc. what may be the problem?
how can i over come this?

You have a design / architectural issue that is best solved by having the user run this as a configuration step after the install. The issue is that custom actions run with the LocalSystemn account, and usually that aacount has no network access privileges. The alternative is is to modify your MSI file (with Orca) so that your custom action runs with impersonation:

http://msdn.microsoft.com/en-us/library/aa368069(VS.85).aspxand see msidbCustomActionTypeNoImpersonate

but then on Vista and later it won't run with admin privileges.

---

Phil Wilson

You have a design / architectural issue that is best solved by having the user run this as a configuration step after the install. The issue is that custom actions run with the LocalSystemn account, and usually that aacount has no network access privileges. The alternative is is to modify your MSI file (with Orca) so that your custom action runs with impersonation:

http://msdn.microsoft.com/en-us/library/aa368069(VS.85).aspxand see msidbCustomActionTypeNoImpersonate

but then on Vista and later it won't run with admin privileges.

---

Phil Wilson