Login failed for user (null). Reason: Not associated with a trusted SQL Server connection.

Anyone,

I have a user "john" whose machine is part of the "job" domain. He is
trying to establish an odbc connection to an MS SQL 2000 server on the
"school" domain. He uses Windows authentication to establish the odbc
connection however it gives the error "Login failed for user '(null)'.
Reason: Not associated with a trusted SQL Server connection."

I am guessing that the odbc connection is trying to pass the
credentials of job\john to the sql server. And since the sql server
is on the school domain it expects the credentials of school\john. Is
there anyway to specify the username and password so that this will
work even though the servers are on different domains without having
to trust the domains? Thanks in advance for
any help on this!!

TonyTo log into SQL Server, the user needs a SQL Server login. If your SQL
Server is set up to use NT Authentication or mixed mode authentication on
the Schools domain, then give John a login on the Schools domain and have
him login using those credentials.

"TBone" <tony.despain@.gmail.com> wrote in message
news:64b1ef71.0411261033.1044c9e9@.posting.google.c om...
> Anyone,
> I have a user "john" whose machine is part of the "job" domain. He is
> trying to establish an odbc connection to an MS SQL 2000 server on the
> "school" domain. He uses Windows authentication to establish the odbc
> connection however it gives the error "Login failed for user '(null)'.
> Reason: Not associated with a trusted SQL Server connection."
> I am guessing that the odbc connection is trying to pass the
> credentials of job\john to the sql server. And since the sql server
> is on the school domain it expects the credentials of school\john. Is
> there anyway to specify the username and password so that this will
> work even though the servers are on different domains without having
> to trust the domains? Thanks in advance for
> any help on this!!
> Tony|||Hi

The school domain needs to trust the job domain to allow this to occur. You
could use SQL Server authentication instead if you don't want this trust to
occur.

John

"TBone" <tony.despain@.gmail.com> wrote in message
news:64b1ef71.0411261033.1044c9e9@.posting.google.c om...
> Anyone,
> I have a user "john" whose machine is part of the "job" domain. He is
> trying to establish an odbc connection to an MS SQL 2000 server on the
> "school" domain. He uses Windows authentication to establish the odbc
> connection however it gives the error "Login failed for user '(null)'.
> Reason: Not associated with a trusted SQL Server connection."
> I am guessing that the odbc connection is trying to pass the
> credentials of job\john to the sql server. And since the sql server
> is on the school domain it expects the credentials of school\john. Is
> there anyway to specify the username and password so that this will
> work even though the servers are on different domains without having
> to trust the domains? Thanks in advance for
> any help on this!!
> Tony

Logging output in a transaction

We have a publish job that we are trying to automate, the problem is getting the output back to the app. or a file. Originally we had print statements, this worked great when we manually ran the proc in QA and could capture the output, now that we are automating it from an application I am not sure how to capture these Print statements - ideally I would like to find this out.

The App. is doing a Try-Catch block so using something like isql.exe will not do the trick otherwise that is the route we would go.

I tried logging everyting to a table but those inserts get rolled back with XACT_ABORT. What about the xp proc that logs it to the event log? Thought of that but that would make a real mess of the event log with all of our status messages.

Now we are considering using xp_cmdshell that calls a batch file to output our status text, is this my best option? I would prefer to capture all of the print statements so if anyone knows how to do this that would be preferable!

Thanks!:bump:

wrong forum? Should I try in an App Dev forum, perhaps?

Logging of SSIS package doesnt work when executed as a job

I am having the same problems as those in another post. SSIS package works fine when executed in BIDS and through execute package utility but it doesnt work when executed as a step in a job.

The other problem is that the logging also doesnt work when i try executing it as a job. So I have no clue about what to do without knowing what error it is. When I run the job it simply says the step has failed.

I have tried most of the solutions posted in other websites most of them to do with using proxies with credentials but havent hit a solution. I would love to get any input on what to do.

Thanks

Look at my post

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=328057&SiteID=1

I have the same problem, but have also do some research and as I think the problem lays in something more complicated than running SSIS package as a job - it is only a symptom.

I have also found some roundtrip (not the best...) but it works on my development machine.

If you will have some new thoughts how to solve it please write!

Przemo

|||

Have Sql Agent run a command processor batch job that calls DtExec. If your package runs fine in DtExec it seems it would run fine when DtExec is called from a batch file?

Ken

|||

Look again at my post. There is a solution for the problem which helped me.

Now I use "Windows Integrated Security" in my sql connection string, so there is no problem with encrypting passwords. When I use SQL Login it must be used together with password encrypting SSIS, so I can provide the password at command line in SQL Job.

Przemo

|||

Hi,

Thanks for the reply , I have tried all what you replied it still dint work.

I am running a 32 bit SQl on a 64 bit machine and also have imports from an Excel source, if that can make things different. I know that there can be two problems why it doesnt work.

1) I developed the package in BIDS with my login and I am trying to deploy it in SQl server. The sql server agent is using proxies of my credentials to run. Is ther a different way it should be done?

2) Since i am running on a 64 bit machine, I set Run64BitRuntime to false, thinking that the providers (especially jet is 32 bit). I dont have program files(x86) on my computer. Should that be on the Sql server? If that is the case please let me know how to point to a different dtexec(32 bit).

Please let me know the exact settings that I need to do. One last question will the problem vanish if I use a 64 bit SQl server?

Thanks

|||I finally figured it out. It was a combination of the above two plus some authentication problems. The logging problem was due to pointing at a file outside of sql server.