Authentification problem with SQL Server 2000

Do you have TCP/IP enabled on the SQL Server as an allowed connection type?
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
news:O56wq5lQIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Hello !
> We use SQL Server 2000 (standard edition) under Windows 2003 Server.
> Due to a hardware failure, we have fully set up the server after having
> formating the hard drives. After having installed Windows Server 2003, we
> have installed SQL Server 2000, then we have restored the databases from
> our last night SQL backup.
> Curiously : all our Windows XP users can connect to the server, but not
> our Windows 2000 users! We have tried to create an ODBC data source with
> Windows authentication : failure. With SQL authentication : failure.
> But the same user, with his same userid, on another PC under Windows XP :
> no problem.
> And it was working well before the crash. Can anybody give us an
> explanation ? a solution ? a help ?
> Thank you,
> Gilbert
>
http://technet.microsoft.com/en-us/library/ms174212.aspx
You need to use the SQL Server configuration manager which has an option for
viewing which connections are allowed...
Its under your start menu programs in the same group as SQL Server...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
news:uiXkOQvQIHA.2208@.TK2MSFTNGP06.phx.gbl...
> Hi Warren,
> Thank you for your answer. Could you tell us where to look at, to answer
> your question ?
> Gilbert
> "Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
> news: eUKerPpQIHA.5980@.TK2MSFTNGP04.phx.gbl...
>

Authentification problem with SQL Server 2000

Hello !
We use SQL Server 2000 (standard edition) under Windows 2003 Server.
Due to a hardware failure, we have fully set up the server after having
formating the hard drives. After having installed Windows Server 2003, we
have installed SQL Server 2000, then we have restored the databases from our
last night SQL backup.
Curiously : all our Windows XP users can connect to the server, but not our
Windows 2000 users! We have tried to create an ODBC data source with Windows
authentication : failure. With SQL authentication : failure.
But the same user, with his same userid, on another PC under Windows XP : no
problem.
And it was working well before the crash. Can anybody give us an explanation
? a solution ? a help ?
Thank you,
GilbertDo you have TCP/IP enabled on the SQL Server as an allowed connection type?
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
news:O56wq5lQIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Hello !
> We use SQL Server 2000 (standard edition) under Windows 2003 Server.
> Due to a hardware failure, we have fully set up the server after having
> formating the hard drives. After having installed Windows Server 2003, we
> have installed SQL Server 2000, then we have restored the databases from
> our last night SQL backup.
> Curiously : all our Windows XP users can connect to the server, but not
> our Windows 2000 users! We have tried to create an ODBC data source with
> Windows authentication : failure. With SQL authentication : failure.
> But the same user, with his same userid, on another PC under Windows XP :
> no problem.
> And it was working well before the crash. Can anybody give us an
> explanation ? a solution ? a help ?
> Thank you,
> Gilbert
>|||Hi Warren,
Thank you for your answer. Could you tell us where to look at, to answer
your question ?
Gilbert
"Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
news: eUKerPpQIHA.5980@.TK2MSFTNGP04.phx.gbl...
> Do you have TCP/IP enabled on the SQL Server as an allowed connection
> type?
> --
> /*
> Warren Brunk - MCITP,MCTS,MCDBA
> www.techintsolutions.com
> */
> "Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
> news:O56wq5lQIHA.4476@.TK2MSFTNGP06.phx.gbl...
>|||http://technet.microsoft.com/en-us/...y/ms174212.aspx
You need to use the SQL Server configuration manager which has an option for
viewing which connections are allowed...
Its under your start menu programs in the same group as SQL Server...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
news:uiXkOQvQIHA.2208@.TK2MSFTNGP06.phx.gbl...
> Hi Warren,
> Thank you for your answer. Could you tell us where to look at, to answer
> your question ?
> Gilbert
> "Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
> news: eUKerPpQIHA.5980@.TK2MSFTNGP04.phx.gbl...
>|||Hi Warren,
Sorry to be a bit late, but : Thank you !
And a Happy New Year,
Gilbert
"Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
news: OJDKPu5QIHA.5288@.TK2MSFTNGP04.phx.gbl...
> http://technet.microsoft.com/en-us/...y/ms174212.aspx
> You need to use the SQL Server configuration manager which has an option
> for viewing which connections are allowed...
> Its under your start menu programs in the same group as SQL Server...
> --
> /*
> Warren Brunk - MCITP,MCTS,MCDBA
> www.techintsolutions.com
> */
>
> "Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
> news:uiXkOQvQIHA.2208@.TK2MSFTNGP06.phx.gbl...
>

Authentification problem with SQL 2k, IIS and Linked Server

Hello,

I have successfully created an Exchange 2000 linked server in Microsoft SQL server 2k. When I use my NT login, I can query it.

I'm now developping a website (ASP.NET in IIS 5). I have successfully created a web page querying my database. But now, I would like to query my linked server via my SQL server. I have try various authentification settings but I always got this error : OLE DB provider 'Exoledb.DataSource.1' reported an error. Authentication failed.

I know it is because the IIS process don't have any rights on the Exchange server but I would like to know what is the way to get around this without given rights to the IIS process (and creating huge security holes).

Thank a lot

Felix Pageau
fpageau@.str.cadid you try distributed queries ?

for example :
INSERT INTO [Database1name].[Owner].[Table]
SELECT *
FROM OPENQUERY ([LinkedServerName], SELECT Database2name.Table.* FROM Database2Name.Table)|||Hello,

this is exactly what I'm trying to do... I would like to know if it is possible to "impersonate" an Exchange Linked Server (with a user defined in the domain...) ?

Thank|||Review information from this KBA (http://support.microsoft.com/default.aspx?scid=kb;EN-US;285833) to go with Linked server authentication.|||Hello,
this is working fine with access but Exchange is using Active Directory login... Those example use plain text login & password. I have already try this way.

Thank a lot

Felix Pageau

Auhtentification problem with Remote Data Access

Hello

I try to make a pull operation from an SQL SERVER 2005 database to a SQL Mobile 2005. I set Integrated authentification on IIS and SQL SEvrer authentification in the database. It passes the IIS authentification, but not the sql Server one. In addition, I tried to connect directlly to the sql with the same connection string anf it works.

Can you help me with this? Do i have to extra configure that dll(the agent) in the virtual directory, or sometihng llike that?

This is my code:

// Connection String to the SQL Server

//

string rdaOleDbConnectString = "Data Source=Sql07;Initial Catalog=AdventureWorks; " +

"User Id=sa;Password = sql250";

SqlConnection conn = new SqlConnection(rdaOleDbConnectString);

conn.Open();

// Initialize RDA Object

//

SqlCeRemoteDataAccess rda = null;

try

{

// Try the Pull Operation

//

rda = new SqlCeRemoteDataAccess(

"http://192.168.0.79/SqlMobileReplication/sqlcesa30.dll",

"assolutions\\dan.popescu",

"password",

"Data Source=\\my documents\\Baza.sdf");

rda.Pull("Employees", "SELECT * FROM DimEmployee", rdaOleDbConnectString,

RdaTrackOption.TrackingOnWithIndexes, "ErrorTable");

// or, try one of these overloads:

//

// rda.Pull("Employees", "SELECT * FROM DimEmployee", rdaOleDbConnectString,

// RdaTrackOption.TrackingOnWithIndexes);

//

// rda.Pull("Employees", "SELECT * FROM DimEmployee", rdaOleDbConnectString);

}

catch (Exception ex)

{

// Handle errors here

//

}

finally

{

// Dispose of the RDA object

//

rda.Dispose();

}

You can see that I have tried the connection first, and it really works. Isn't it the same thing it's doing at replication?

What is the error you are getting?
Also are you sure that the server has the table DimEmployee in the database?

Auhtentification problem with Remote Data Access

Hello

I try to make a pull operation from an SQL SERVER 2005 database to a SQL Mobile 2005. I set Integrated authentification on IIS and SQL SEvrer authentification in the database. It passes the IIS authentification, but not the sql Server one. In addition, I tried to connect directlly to the sql with the same connection string anf it works.

Can you help me with this? Do i have to extra configure that dll(the agent) in the virtual directory, or sometihng llike that?

This is my code:

// Connection String to the SQL Server

//

string rdaOleDbConnectString = "Data Source=Sql07;Initial Catalog=AdventureWorks; " +

"User Id=sa;Password = sql250";

SqlConnection conn = new SqlConnection(rdaOleDbConnectString);

conn.Open();

// Initialize RDA Object

//

SqlCeRemoteDataAccess rda = null;

try

{

// Try the Pull Operation

//

rda = new SqlCeRemoteDataAccess(

"http://192.168.0.79/SqlMobileReplication/sqlcesa30.dll",

"assolutions\\dan.popescu",

"password",

"Data Source=\\my documents\\Baza.sdf");

rda.Pull("Employees", "SELECT * FROM DimEmployee", rdaOleDbConnectString,

RdaTrackOption.TrackingOnWithIndexes, "ErrorTable");

// or, try one of these overloads:

//

// rda.Pull("Employees", "SELECT * FROM DimEmployee", rdaOleDbConnectString,

// RdaTrackOption.TrackingOnWithIndexes);

//

// rda.Pull("Employees", "SELECT * FROM DimEmployee", rdaOleDbConnectString);

}

catch (Exception ex)

{

// Handle errors here

//

}

finally

{

// Dispose of the RDA object

//

rda.Dispose();

}

You can see that I have tried the connection first, and it really works. Isn't it the same thing it's doing at replication?

What is the error you are getting?
Also are you sure that the server has the table DimEmployee in the database?