Showing posts with label authorization. Show all posts
Showing posts with label authorization. Show all posts

Friday, March 9, 2012

'Invalid authorization specification' from IDBInitialize::Initialize (c++)

Hi

I've been trying to connect to my local SQL Server instance (SQL Server 2005) using the SQLNCLI interface from c++ without success. I consistently receive an 'Invalid authorization specification' error (SQL state 28000 and SQL error number 0) when I call IDBInitialize::Initialize to connect to the database. I was hoping someone here could shed some light on this and help me out.

The strange thing is that I get no error if I leave the user blank (L"" in vValue.bstrVal) and try to connect. Also, IDBProperties::SetProperties returns 0 when the user is blank but 40eda when the user is set. This seems to be a message from the pipeline facility but I haven't found the description of the code (0xeda).

The user in the database is configured with no password and I can successfully connect to the server and open the database using that user through Management Studio.

I've also tried using the SQLOLEDB provider with the same results.

Suspecting that I'm setting the properties wrong I include a code snippet below showing how I'm setting the properties:

for (int i = 0; i < sizeof(dbprop) / sizeof(dbprop[0]); i++)
VariantInit(&dbprop[ i ].vValue);

// Server name
dbprop[0].dwPropertyID = DBPROP_INIT_DATASOURCE;
dbprop[0].vValue.vt = VT_BSTR;
dbprop[0].vValue.bstrVal = SysAllocString(L"localhost");
dbprop[0].dwOptions = DBPROPOPTIONS_REQUIRED;
dbprop[0].colid = DB_NULLID;

// Database
dbprop[1].dwPropertyID = DBPROP_INIT_CATALOG;
dbprop[1].vValue.vt = VT_BSTR;
dbprop[1].vValue.bstrVal = SysAllocString(L"test");
dbprop[1].dwOptions = DBPROPOPTIONS_REQUIRED;
dbprop[1].colid = DB_NULLID;

// Username
dbprop[2].dwPropertyID = DBPROP_AUTH_INTEGRATED;
dbprop[2].vValue.vt = VT_BSTR;
dbprop[2].vValue.bstrVal = SysAllocString(L"jph");
dbprop[2].dwOptions = DBPROPOPTIONS_REQUIRED;
dbprop[2].colid = DB_NULLID;

Cheers,
JPProblem solved.

A little bit embarrasing, since I, somehow, misinterpreted the DBPROP_AUTH_INTEGRATED parameter. It should have been DBPROP_AUTH_USERID (of course) instead.

The username propertie now looks like this:

// Username
dbprop[2].dwPropertyID = DBPROP_AUTH_USERID;
dbprop[2].vValue.vt = VT_BSTR;
dbprop[2].vValue.bstrVal = SysAllocString(L"jph");
dbprop[2].dwOptions = DBPROPOPTIONS_REQUIRED;
dbprop[2].colid = DB_NULLID;

and works like a charm.

JP

invalid authorization specification error? Frontpage DB wizard

I have searched high and low to find out what this means... and I can't. My
connection to the SQL server from Frontpage 2003 database wizard worked then
suddenly didn't. What did I inadvertently change... if anything... Sounds
like an SQL isn't letting me retrieve..but I have no idea why...
Help"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>I have searched high and low to find out what this means... and I can't. My
> connection to the SQL server from Frontpage 2003 database wizard worked
> then
> suddenly didn't. What did I inadvertently change... if anything... Sounds
> like an SQL isn't letting me retrieve..but I have no idea why...
> Help
What error message is being reported back by Frontpage?
Is the SQL Server running?
Did you install any service packs, upgrades, other software?
Rick Sawtell
MCT, MCSD, MCDBA|||That was what the browser was reporting: invalid authorization specification
in the database results wizard... Yet, when I coded my own connection instea
d
of using the wizard on a page.. It worked fine...
When I changed the authentication method on the server to send in clear text
as per:
http://support.microsoft.com/defaul...Q24793
1
It seemed to start to work again... Yet I recalled re-setting nothing of the
sort...
I was lead here by changing trusted_connection to yes and following the
message from there...
"Rick Sawtell" wrote:

> "Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
> news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>
> What error message is being reported back by Frontpage?
> Is the SQL Server running?
> Did you install any service packs, upgrades, other software?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Hmmm..
Glad you got it working again.
I wonder if you have automatic updates turned on and it installed a service
pack for IIS or IE that may have reset that value...
Rick
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:FFA1F56D-C150-4665-AB3F-D4FDEC749002@.microsoft.com...[vbcol=seagreen]
> That was what the browser was reporting: invalid authorization
> specification
> in the database results wizard... Yet, when I coded my own connection
> instead
> of using the wizard on a page.. It worked fine...
> When I changed the authentication method on the server to send in clear
> text
> as per:
> http://support.microsoft.com/defaul...Q247
931
> It seemed to start to work again... Yet I recalled re-setting nothing of
> the
> sort...
> I was lead here by changing trusted_connection to yes and following the
> message from there...
> "Rick Sawtell" wrote:
>

invalid authorization specification error? Frontpage DB wizard

I have searched high and low to find out what this means... and I can't. My
connection to the SQL server from Frontpage 2003 database wizard worked then
suddenly didn't. What did I inadvertently change... if anything... Sounds
like an SQL isn't letting me retrieve..but I have no idea why...
Help"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>I have searched high and low to find out what this means... and I can't. My
> connection to the SQL server from Frontpage 2003 database wizard worked
> then
> suddenly didn't. What did I inadvertently change... if anything... Sounds
> like an SQL isn't letting me retrieve..but I have no idea why...
> Help
What error message is being reported back by Frontpage?
Is the SQL Server running?
Did you install any service packs, upgrades, other software?
Rick Sawtell
MCT, MCSD, MCDBA|||That was what the browser was reporting: invalid authorization specification
in the database results wizard... Yet, when I coded my own connection instead
of using the wizard on a page.. It worked fine...
When I changed the authentication method on the server to send in clear text
as per:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q247931&ID=kb;en-us;Q247931
It seemed to start to work again... Yet I recalled re-setting nothing of the
sort...
I was lead here by changing trusted_connection to yes and following the
message from there...
"Rick Sawtell" wrote:
> "Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
> news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
> >I have searched high and low to find out what this means... and I can't. My
> > connection to the SQL server from Frontpage 2003 database wizard worked
> > then
> > suddenly didn't. What did I inadvertently change... if anything... Sounds
> > like an SQL isn't letting me retrieve..but I have no idea why...
> >
> > Help
>
> What error message is being reported back by Frontpage?
> Is the SQL Server running?
> Did you install any service packs, upgrades, other software?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Hmmm..
Glad you got it working again.
I wonder if you have automatic updates turned on and it installed a service
pack for IIS or IE that may have reset that value...
Rick
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:FFA1F56D-C150-4665-AB3F-D4FDEC749002@.microsoft.com...
> That was what the browser was reporting: invalid authorization
> specification
> in the database results wizard... Yet, when I coded my own connection
> instead
> of using the wizard on a page.. It worked fine...
> When I changed the authentication method on the server to send in clear
> text
> as per:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q247931&ID=kb;en-us;Q247931
> It seemed to start to work again... Yet I recalled re-setting nothing of
> the
> sort...
> I was lead here by changing trusted_connection to yes and following the
> message from there...
> "Rick Sawtell" wrote:
>> "Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
>> news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>> >I have searched high and low to find out what this means... and I can't.
>> >My
>> > connection to the SQL server from Frontpage 2003 database wizard worked
>> > then
>> > suddenly didn't. What did I inadvertently change... if anything...
>> > Sounds
>> > like an SQL isn't letting me retrieve..but I have no idea why...
>> >
>> > Help
>>
>> What error message is being reported back by Frontpage?
>> Is the SQL Server running?
>> Did you install any service packs, upgrades, other software?
>>
>> Rick Sawtell
>> MCT, MCSD, MCDBA
>>

invalid authorization specification error? Frontpage DB wizard

I have searched high and low to find out what this means... and I can't. My
connection to the SQL server from Frontpage 2003 database wizard worked then
suddenly didn't. What did I inadvertently change... if anything... Sounds
like an SQL isn't letting me retrieve..but I have no idea why...
Help
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>I have searched high and low to find out what this means... and I can't. My
> connection to the SQL server from Frontpage 2003 database wizard worked
> then
> suddenly didn't. What did I inadvertently change... if anything... Sounds
> like an SQL isn't letting me retrieve..but I have no idea why...
> Help
What error message is being reported back by Frontpage?
Is the SQL Server running?
Did you install any service packs, upgrades, other software?
Rick Sawtell
MCT, MCSD, MCDBA
|||That was what the browser was reporting: invalid authorization specification
in the database results wizard... Yet, when I coded my own connection instead
of using the wizard on a page.. It worked fine...
When I changed the authentication method on the server to send in clear text
as per:
http://support.microsoft.com/default...;en-us;Q247931
It seemed to start to work again... Yet I recalled re-setting nothing of the
sort...
I was lead here by changing trusted_connection to yes and following the
message from there...
"Rick Sawtell" wrote:

> "Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
> news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>
> What error message is being reported back by Frontpage?
> Is the SQL Server running?
> Did you install any service packs, upgrades, other software?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||Hmmm..
Glad you got it working again.
I wonder if you have automatic updates turned on and it installed a service
pack for IIS or IE that may have reset that value...
Rick
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:FFA1F56D-C150-4665-AB3F-D4FDEC749002@.microsoft.com...[vbcol=seagreen]
> That was what the browser was reporting: invalid authorization
> specification
> in the database results wizard... Yet, when I coded my own connection
> instead
> of using the wizard on a page.. It worked fine...
> When I changed the authentication method on the server to send in clear
> text
> as per:
> http://support.microsoft.com/default...;en-us;Q247931
> It seemed to start to work again... Yet I recalled re-setting nothing of
> the
> sort...
> I was lead here by changing trusted_connection to yes and following the
> message from there...
> "Rick Sawtell" wrote:

Invalid authorization specification connecting to Sql Server 2000

I have a vb 6 program that has been running for several years against a 6.5 db. I convert the db to 2000, and now when I repoint the software to the 2000 db, I get "Invalid Authorization Specification" when I try to open the connection. The connection string is:
Dim conn As ADODB.Connection
Set conn = New ADODB.Connection
conn.Open "Provider=SQLOLEDB" & _
";Data Source=" & sServer & _
";Initial Catalog=" & sDB & _
";User Id=" & goProcess.UserID & _
";Password=" & goProcess.Password & ";"
All of the variables are filled out correctly, when I go against a 6.5 it works, Sql Server 2000 doesn't.Did you set up the user in SQL 2000? and give persmissions for the database you are querying against?
|||I used the "sa" user to try to eliminate any issues. I'm able to use several C# programs to connect to the server in the same way (except vb uses ado, and C# uses ado.net).

Invalid authorization specification

Hi:

I'm trying to connect to a data base of "sql server 2005 enterprise" named BCR.
The server name is "server1"
I'm using Windows Authentication to connect to server
The operating system is Windows Server 2003 Enterprise Edition Service Pack 1

When I run the aspx I get this error at line 21

System.Data.OleDb.OleDbException: Invalid authorization specification Invalid connection string attribute at System.Data.OleDb.OleDbConnection.ProcessResults(Int32 hr) at System.Data.OleDb.OleDbConnection.InitializeProvider() at System.Data.OleDb.OleDbConnection.Open() at ASP.pruebaLeeSqlServer_aspx.__Render__control1(HtmlTextWriter __output, Control parameterContainer) in Z:\Digital\pruebaLeeSqlServer.aspx:line 21

This is my code:

Dim str2 As String = "Provider=SQLNCLI; Server = server1; Database = BCR"
Dim cnn2 As OleDbConnection = New OleDbConnection(str2)
Dim cmd2 As New OleDbCommand()
Dim drd2 As OleDbDataReader
Try
cnn2.Open()
cmd2.Connection = cnn2''''line 21
cmd2.CommandText ="SELECT LastName FROM Employees"
drd2 = cmd2.ExecuteReader
Do While drd2.Read
%>
<%=drd2.GetString(0)%><br>
<%
Loop
drd2.Close()
Catch exc1 As Exception
%>
<%=exc1.ToString()%>
<%
Finally
cnn2.Close()
End Try

What could be wrong?
Do I need enable permission for asp.net in sql server?
how I can do it?

Thanks!!

You should be using the objects in the System.Data.SqlClient namespace to connect to MS SQL Server, not System.Data.OleDb. That should fix your issue given that there is no problem with your connection string.

HTH,
Ryan

|||thanks Ryan. It works!

I are right, I had to use System.Data.SqlClient namespace instead of System.Data.OleDb. And I just change my connection string to

"Server=server1; Database=BCR; Trusted_Connection=True;"

Thanks!

Invalid authorization specification

MS OLE DB Provider for SQL Server Error: Invalid authorization specification
This is a basic 3-tier system, front end, data broker, database. The front
end software is written in VB 6. There are many front end users. This
error is coming up on one computer only. No users can access the database
through the software from this machine. But, all users can access the
database through the software from all other machines. This machine is WinXP.
Any ideas where to look? The software and connection code is the same on
all machines. What could have changed on this one machine (because it did
work before) that would cause only it to stop working properly?
Thanks.
Does your application use a DSN to connect to SQL Server? If so ensure this
DSN is setup correctly on the client machine.
This error is similar to the "login failed for user <usr>" Thus you should
troubleshoot it similarly. For instrance, try connecting from this client
using both SQL and NT authentication. To simplify troubleshooting, try
taking your application out of the picture by testing UDL file connections
and from odbc administrator(test dsn). Is the same error displayed when
testing connectivity using these client tools?
Also see KB: How to troubleshoot connectivity issues in SQL Server 2000 -
ID: 827422 9available at http://support.microsoft.com)
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Invalid authorization specification

Hi,
I am trying to run some queries across the servers.
I have admin rights on both the boxes, I have linked the server.
But whenever i run a query on the remote server, I get the following error
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Invalid authorization specification]
The query is a basic one like
SELECT distinct [name] FROM remoteserver.sms_rdm.dbo.v_r_system.
Any suggestions pls ?
Hi Arun,
Possible reasons...
* Check whether you have added your login id in the remote sql server. If
you haven't added the login id, use sp_addremotelogin system stored procedure
to add your local login in the remote server and give appropriate access
rights.
"Arun" wrote:

> Hi,
> I am trying to run some queries across the servers.
> I have admin rights on both the boxes, I have linked the server.
> But whenever i run a query on the remote server, I get the following error
> --
> Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Invalid authorization specification]
> --
> The query is a basic one like
> SELECT distinct [name] FROM remoteserver.sms_rdm.dbo.v_r_system.
> Any suggestions pls ?
|||Shri,
Thanks for the reply. But i can run the query successfully when i dirctly
connect to remoteserver via q/a. and have full rights on the remoteserver.
Arun
"Shri.DBA" wrote:
[vbcol=seagreen]
> Hi Arun,
> Possible reasons...
> * Check whether you have added your login id in the remote sql server. If
> you haven't added the login id, use sp_addremotelogin system stored procedure
> to add your local login in the remote server and give appropriate access
> rights.
> "Arun" wrote:
|||The issue was simple ( now that i figured it out ;))
I was getting the error below because the security tab of the linked server
was set to 'connection to be made without security context' once it was
changed to 'use current context' it worked fine
Thanks for the reply
Arun
"Arun" wrote:
[vbcol=seagreen]
> Shri,
> Thanks for the reply. But i can run the query successfully when i dirctly
> connect to remoteserver via q/a. and have full rights on the remoteserver.
> Arun
> "Shri.DBA" wrote:

Wednesday, March 7, 2012

Invalid authorization specification

MS OLE DB Provider for SQL Server Error: Invalid authorization specification
This is a basic 3-tier system, front end, data broker, database. The front
end software is written in VB 6. There are many front end users. This
error is coming up on one computer only. No users can access the database
through the software from this machine. But, all users can access the
database through the software from all other machines. This machine is WinX
P.
Any ideas where to look? The software and connection code is the same on
all machines. What could have changed on this one machine (because it did
work before) that would cause only it to stop working properly?
Thanks.Does your application use a DSN to connect to SQL Server? If so ensure this
DSN is setup correctly on the client machine.
This error is similar to the "login failed for user <usr>" Thus you should
troubleshoot it similarly. For instrance, try connecting from this client
using both SQL and NT authentication. To simplify troubleshooting, try
taking your application out of the picture by testing UDL file connections
and from odbc administrator(test dsn). Is the same error displayed when
testing connectivity using these client tools?
Also see KB: How to troubleshoot connectivity issues in SQL Server 2000 -
ID: 827422 9available at http://support.microsoft.com)
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Invalid authorization specification

Hi,

We are testing our product on Windows Vista with SQL Server 2005 SP2 and are encountering an "invalid authorization specification". We make the connection through a Windows service using a standard ADO connection. I have tried changing the provider in the connection string to SQLNCLI without any success. The application is written in Delphi 5 and has worked on previous versions of Windows running SQL Server 2005.

Thanks.

Steven
Can you post the connection string ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

Hi,

My connection string is: Provider=SQLNCLI;Database=TESTDB;Server=STEVENV;UID=sa;PWD=test

Steven

|||

What's the exect error msg?

Can you check this page http://msdn2.microsoft.com/en-us/library/ms188670.aspx to ensure that SQL Authentication is turned on? (although I noticed that the title mentioned authorization) Thanks,

|||

We actually managed to get this issue resolved.

What was happening is that we were setting the previously posted connection string on our ADO connection object and when we requested the connection string off that object for a different connection object, for some reason it was adding a whole lot of other connection string parameters that obviously don't work on Windows Vista but do work on Windows XP. This must just be some strange behaviour in the ADO connection object that we're using, a pretty legacy ADO object in Delphi 5. We resolved the issue by always using the original connection string instead of the one off the first ADO connection.

Thanks for the help.

Steven

Invalid authorization specification

Hi,
I am trying to run some queries across the servers.
I have admin rights on both the boxes, I have linked the server.
But whenever i run a query on the remote server, I get the following error
--
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Invalid authorization specification]
--
The query is a basic one like
SELECT distinct [name] FROM remoteserver.sms_rdm.dbo.v_r_system.
Any suggestions pls ?Hi Arun,
Possible reasons...
* Check whether you have added your login id in the remote sql server. If
you haven't added the login id, use sp_addremotelogin system stored procedure
to add your local login in the remote server and give appropriate access
rights.
"Arun" wrote:
> Hi,
> I am trying to run some queries across the servers.
> I have admin rights on both the boxes, I have linked the server.
> But whenever i run a query on the remote server, I get the following error
> --
> Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Invalid authorization specification]
> --
> The query is a basic one like
> SELECT distinct [name] FROM remoteserver.sms_rdm.dbo.v_r_system.
> Any suggestions pls ?|||Shri,
Thanks for the reply. But i can run the query successfully when i dirctly
connect to remoteserver via q/a. and have full rights on the remoteserver.
Arun
"Shri.DBA" wrote:
> Hi Arun,
> Possible reasons...
> * Check whether you have added your login id in the remote sql server. If
> you haven't added the login id, use sp_addremotelogin system stored procedure
> to add your local login in the remote server and give appropriate access
> rights.
> "Arun" wrote:
> > Hi,
> > I am trying to run some queries across the servers.
> > I have admin rights on both the boxes, I have linked the server.
> > But whenever i run a query on the remote server, I get the following error
> > --
> > Server: Msg 7399, Level 16, State 1, Line 1
> > OLE DB provider 'SQLOLEDB' reported an error.
> > [OLE/DB provider returned message: Invalid authorization specification]
> > --
> > The query is a basic one like
> > SELECT distinct [name] FROM remoteserver.sms_xxx.dbo.v_r_system.
> >
> > Any suggestions pls ?|||The issue was simple ( now that i figured it out ;))
I was getting the error below because the security tab of the linked server
was set to 'connection to be made without security context' once it was
changed to 'use current context' it worked fine
Thanks for the reply
Arun
"Arun" wrote:
> Shri,
> Thanks for the reply. But i can run the query successfully when i dirctly
> connect to remoteserver via q/a. and have full rights on the remoteserver.
> Arun
> "Shri.DBA" wrote:
> > Hi Arun,
> >
> > Possible reasons...
> >
> > * Check whether you have added your login id in the remote sql server. If
> > you haven't added the login id, use sp_addremotelogin system stored procedure
> > to add your local login in the remote server and give appropriate access
> > rights.
> >
> > "Arun" wrote:
> >
> > > Hi,
> > > I am trying to run some queries across the servers.
> > > I have admin rights on both the boxes, I have linked the server.
> > > But whenever i run a query on the remote server, I get the following error
> > > --
> > > Server: Msg 7399, Level 16, State 1, Line 1
> > > OLE DB provider 'SQLOLEDB' reported an error.
> > > [OLE/DB provider returned message: Invalid authorization specification]
> > > --
> > > The query is a basic one like
> > > SELECT distinct [name] FROM remoteserver.sms_xxx.dbo.v_r_system.
> > >
> > > Any suggestions pls ?

Invalid authorization specification

Hi,
I am trying to run some queries across the servers.
I have admin rights on both the boxes, I have linked the server.
But whenever i run a query on the remote server, I get the following error
--
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Invalid authorization specification]
--
The query is a basic one like
SELECT distinct [name] FROM remoteserver.sms_rdm.dbo.v_r_system.
Any suggestions pls ?Hi Arun,
Possible reasons...
* Check whether you have added your login id in the remote sql server. If
you haven't added the login id, use sp_addremotelogin system stored procedur
e
to add your local login in the remote server and give appropriate access
rights.
"Arun" wrote:

> Hi,
> I am trying to run some queries across the servers.
> I have admin rights on both the boxes, I have linked the server.
> But whenever i run a query on the remote server, I get the following error
> --
> Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'SQLOLEDB' reported an error.
> [OLE/DB provider returned message: Invalid authorization specification
]
> --
> The query is a basic one like
> SELECT distinct [name] FROM remoteserver.sms_rdm.dbo.v_r_system.
> Any suggestions pls ?|||Shri,
Thanks for the reply. But i can run the query successfully when i dirctly
connect to remoteserver via q/a. and have full rights on the remoteserver.
Arun
"Shri.DBA" wrote:
[vbcol=seagreen]
> Hi Arun,
> Possible reasons...
> * Check whether you have added your login id in the remote sql server. If
> you haven't added the login id, use sp_addremotelogin system stored proced
ure
> to add your local login in the remote server and give appropriate access
> rights.
> "Arun" wrote:
>|||The issue was simple ( now that i figured it out ;))
I was getting the error below because the security tab of the linked server
was set to 'connection to be made without security context' once it was
changed to 'use current context' it worked fine
Thanks for the reply
Arun
"Arun" wrote:
[vbcol=seagreen]
> Shri,
> Thanks for the reply. But i can run the query successfully when i dirctly
> connect to remoteserver via q/a. and have full rights on the remoteserve
r.
> Arun
> "Shri.DBA" wrote:
>