Hi!
I created a simple task that just run a SQL text script. I created a connection to my SQL 2005 machine using integrated security (I am a trusted user) and when I tested the connection I was successful. However, when I run the task using this connection and my credentials I get the failure below. I guess VC can't find my user for whatever reason. What am I doing wrong? Thanks!

Result:Login failed for user ''. The user is not associated with a trusted SQL Server connection.

Did you specificy a Credential in the SQL Task (not just the Connection)? The main reason is that you need a successful login to the system first as your service probably runs as SYSTEM account.

---

Yes, I selected my credentials from first drop down and then connection from second. Is there any other setting even at server level I have to set? It is very strange that in the message no user is found.

When I select no credentials and run it I actually get this message:
Result:Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
But when I use myself I get the empty string. I am using my NT credential info with my domain name in fromt of my username. And of course, my NT windows password

Could be that the login fail in some way.

1. what if you try a local user on that SQL server? (where domain name is servername)
2. Can you use your existing credential for launching a process (background) with success?

---

I can't use a sql server user, we use NT user that have permissions to the SQL Server DBs. We ussually impersonate in our apps. Also, my execution context is always Background since I am using your server mode (localhost). For what it's worth, with my connection I can actually go to tools> SQL Explore and see all my DB, Tables, SPs, etc...

Still failing task.

Thanks!

But can you please confirm that the current Credential works for example launching notedpad.exe hidden in the background. If you then see it in Task manager running as your user it works. Otherwise it might be some detail that is wrong like password.

---

One final option, if the Credential works, would be to remove the Credential and change the username that runs the Service to this user - and test again.

---