Login failed for user '(null)'...

There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
selected a database on PC2 using Windows authentication and executed the
following query:
select * from PC1.Database1.dbo.Table1
I got this error:
Server: Msg 18452, Level 14, State 1, Line 2
Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection.
Both servers are set to mixed mode authentication and both are linked
using sp_addlinkedserver. Does anybody have a solution to this issue?
--
Best regards,
Vladimir.Vova
When you created linked server what is the login do you specify?
"Vladimir Svrkota" <see@.reply.to> wrote in message
news:1o1fojctigtr3.dlg@.vladimir.svrkota...
> There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
> selected a database on PC2 using Windows authentication and executed the
> following query:
> select * from PC1.Database1.dbo.Table1
> I got this error:
> Server: Msg 18452, Level 14, State 1, Line 2
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
> Both servers are set to mixed mode authentication and both are linked
> using sp_addlinkedserver. Does anybody have a solution to this issue?
> --
> Best regards,
> Vladimir.|||Vladimir Svrkota wrote:
> There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
> selected a database on PC2 using Windows authentication and executed the
> following query:
> select * from PC1.Database1.dbo.Table1
> I got this error:
> Server: Msg 18452, Level 14, State 1, Line 2
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
> Both servers are set to mixed mode authentication and both are linked
> using sp_addlinkedserver. Does anybody have a solution to this issue?
>
Hi
You most likely need to specify a login that can access the remote
server. If you don't specify anything, the server will try to connect
using your NT login which requires that the both servers is set to
delegation.
Try to look up sp_addlinkedsrvlogin in BOL - that will give you more info.
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||"Steen Schlüter Persson (DK)" wrote:
> Try to look up sp_addlinkedsrvlogin in BOL - that will give you more info.
Thanks. I'll take a look.
--
Best regards,
Vladimir.

Login failed for user '(null)'...

There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
selected a database on PC2 using Windows authentication and executed the
following query:
select * from PC1.Database1.dbo.Table1
I got this error:
Server: Msg 18452, Level 14, State 1, Line 2
Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection.
Both servers are set to mixed mode authentication and both are linked
using sp_addlinkedserver. Does anybody have a solution to this issue?
Best regards,
Vladimir.Vova
When you created linked server what is the login do you specify?
"Vladimir Svrkota" <see@.reply.to> wrote in message
news:1o1fojctigtr3.dlg@.vladimir.svrkota...
> There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
> selected a database on PC2 using Windows authentication and executed the
> following query:
> select * from PC1.Database1.dbo.Table1
> I got this error:
> Server: Msg 18452, Level 14, State 1, Line 2
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
> Both servers are set to mixed mode authentication and both are linked
> using sp_addlinkedserver. Does anybody have a solution to this issue?
> --
> Best regards,
> Vladimir.|||Vladimir Svrkota wrote:
> There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
> selected a database on PC2 using Windows authentication and executed the
> following query:
> select * from PC1.Database1.dbo.Table1
> I got this error:
> Server: Msg 18452, Level 14, State 1, Line 2
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
> Both servers are set to mixed mode authentication and both are linked
> using sp_addlinkedserver. Does anybody have a solution to this issue?
>
Hi
You most likely need to specify a login that can access the remote
server. If you don't specify anything, the server will try to connect
using your NT login which requires that the both servers is set to
delegation.
Try to look up sp_addlinkedsrvlogin in BOL - that will give you more info.
Regards
Steen Schlter Persson
Database Administrator / System Administrator|||"Steen Schlter Persson (DK)" wrote:

> Try to look up sp_addlinkedsrvlogin in BOL - that will give you more info.
Thanks. I'll take a look.
Best regards,
Vladimir.sql

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.