Do i ned a Windows Server for MSDE with windows authentification ?

Hi
From the local PC windows authentication seems to work, but from remote pc's
te client seems to logon as guest.
Do i need to install MSDE on a windows server edition to get the windows
authentication working ?
SQL Authentication works from remote machines, but becorse the password is
sent as cleartext over the network i would like to use the Windows
authentication.
Can someone give me an answer on this ? ( i want to move some app from using
acces to sql server).
Hope someone helps me.
Johan.
Hi,
no you don=B4t need a Windows Server to use Windows Authentication. As
long as the machine is in the same domain and uses a service account
which is able to check the identity of the user on the domain
controller you are able to use Windows Authentication.
If you are using WIndows XP you have to disbale "Simple FIle and
Printer Sharing"
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
sql

DML against remote tables (MSSQL to DB2)

I created a linked server to a DB2 database and I can pull data fine, but when I try to insert/update/delete it tells me "SQL0471N Invocation of routine "SYSIBM.SQLTABLES" failed due to reason "00E7900C"" when trying: DELETE FROM DB2LinkedServer..SPACENAME.TABLENAME

I believe I need to send a clear string to DB2 that doesn't get compiled on the sql server side. Is there something like openquery that I can use for DML statements in SQL Server?Upon further review I found this site: http://support.microsoft.com/kb/270119/EN-US/

It shows how to use openquery to execute DML statements. nifty.

'distributor_admin' is not defined as a remote login at the server

We have set up one of the clustered instance as a remote distributor and
replication has been working properly. However, on the event log of the
active node, I saw the following error appeared every few minutes:
Could not connect to server 'REPLICATIONSQL\DISTRIBUTOR' because
'distributor_admin' is not defined as a remote login at the server. Verify
that you have specified the correct login name. [CLIENT: 10.1.1.28].
REPLICATIONSQL\DISTRIBUTOR is the name of the clustered instance configured
as a remote distributor and it is running on active node; the client
(10.1.1.28) is the passive node of the cluster. our environment is windows
2003 and sql server 2005 with sp2.
I wonder if anyone has any idea how to get rid of this error from my server.
Thanks in advance.
Zack.
I wonder if it is a managed news group by Microsoft, if not, someone knows
the managed news group since I was told that it is a managed group and
Microsoft will reply every post?
thanks for your kind reply because I really need to fix this error and don't
want to pay MS for this kind of error. We have paid too much to MS already
for support.
Zack.
m
"dp" wrote:

> We have set up one of the clustered instance as a remote distributor and
> replication has been working properly. However, on the event log of the
> active node, I saw the following error appeared every few minutes:
> Could not connect to server 'REPLICATIONSQL\DISTRIBUTOR' because
> 'distributor_admin' is not defined as a remote login at the server. Verify
> that you have specified the correct login name. [CLIENT: 10.1.1.28].
> REPLICATIONSQL\DISTRIBUTOR is the name of the clustered instance configured
> as a remote distributor and it is running on active node; the client
> (10.1.1.28) is the passive node of the cluster. our environment is windows
> 2003 and sql server 2005 with sp2.
> I wonder if anyone has any idea how to get rid of this error from my server.
> Thanks in advance.
> Zack.
>

distributor_admin error

Hi,
When i try to configure publisher, distributor, subscriber on the same remote server, i am getting the following error:
SQL Server Enterprise Manager could not configure '90.168.XX.XXX' as the distributor for '90.168.xx.xxx'
Error: 18483: could not connect to server 'different name' beacuse 'distributor_admin' isn ot defined as a remote login at the server
I changed the MSSQLSERVER and the SQL Server Agent and a dependant file to run froma domain account, i gave that domain account all the privileges on the database and the master database aswell. but i keep getting the error.
Also why is the error showing diffetent server name than the '90.168...' name?
Will i have problems later if i donot set up alias names rather than ip address. If so, how can i set up alias names for SQL Server's
I am quite new to all this, any detailed answer could really help.
thanks
stummalaGot that fixed by re registering the server name to the result of @.@.SERVERNAME

Distribution agent failed but didn't ?

Hi There

I have the following setup.

Server A transactionally replicates to Server B , using Server C as remote distributor.

Now the distribution agent runs on Server B, under distribution agents in replication monitor the distribution agent is the same job as the job on Server B defined as REPL-Dsitributor, correct ?

Now this morning at 4am under distribution agents on the remote distributor the job was marked as failed (error: no response in 10 minutes), but the "same job" on Server B, was not failed ?

The replication agent failure alert did not fire, neither did the notification failure alert on the job it self ?

What the %#$&#% happened ? This is a production environment so it is very worrying ?

Only according to the distribution agent on the remote distributor did the job fail, but not the job itself on the subscriber ?

Firstly what happened here ?
Secondly how can i make the agent keep retrying ? Once it failed it stayed failed, can i configure it to keep trying ?

Thanx
How can i make this agent keep retrying ?As for your case, distribution agent may not run on B but C (remote distributor) and replmonitor actually monitor agent job on C.

If your subscription is push, distribution agent will run under C. But if your subscription is pull, it will run under B.

About your another question, if agent job can keep retrying if it fails. That's depends, if it fails to access some meta data or subscription database, some access issue, it will retry five times and fail. Other problem cause the agent job fail, it just fail, until your solve the problem and restart it again. Otherwise, it won't run.

Hope it will help you some.

-Yunjing

distributed transaction problem on remote server

I am getting a problem in executing this distributed query



CREATE PROCEDURE [sp_ec2fetch] AS



set XACT_ABORT on

begin distributed tran



select * from OPENDATASOURCE(

'SQLOLEDB',

'Data Source=[ip];User ID=[uid];Password=[pass]'

).dml.dbo.act where code like '4010101000'

commit tran

GO



When I run it with a local LAN IP it works fine, but when I use a public ip my analyzer hangs and doesnt give me any output. I am using a dedicated dialup 64kbps connection. I have tried this query without begin distributed trans and commit trans and it worked fine, may be there are extra overheads with transactions, if so let me know



As an alternate I have tried registering server with sp_addlinkedserver and then executing a query with direct server reference, but had the same problem with it.Ensure MSDTC is started on both the servers.

distributed transaction failure

Im attempting to insert the result set from a remote query into a local table and Im getting the following error:

Msg 8501, Level 16, State 1, Line 1
MSDTC on server 'REMOTESVR' is unavailable.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d01c].
Msg 7391, Level 16, State 1, Line 1

The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.

MSDTC is running on both servers. Has anyone ever seen this or have any insight into the cause?


The code that Im trying to run is:

create table msver
(
[Index] int,
[Name] varchar(30),
Internal_Value varchar(20),
Character_Value varchar(512)
)

insert into msver
exec ('exec [REMOTESVR].master.dbo.xp_msver')

Note that the remote query works fine.

Thanks!
EricMake sure MSDTC is started on both the servers.|||I might be wrong, but I don't think you're going to get xp_msver to work this way. Run it as:

insert msver
exec [REMOTESVR].sp_executesql 'exec master.dbo.xp_msver'

See if that works. I don't have my laptop hooked up, or I would test it really quick at the lab. :)|||Check on the 'remoteserver' SQL server error log for #
"... server Attempting to initialize Distributed Transaction Coordinator..."

distributed transaction error - help urgent

i have two remote servers connected to each other through the linked servers.

i can run querries or even perform inserts as far as its not inside a transaction
but when i am trying to run distribted transaction but it keeps on returning the same msg.

Server: Msg 7391, Level 16, State 1, Line 3
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].

i have configured the firewall, made sure the DTC service is started on both and enabled. they both have the same Sp packs, same config.http://www.experts-exchange.com/Databases/Microsoft_SQL_Server/Q_20888629.html

Go Google the error...there are probably a lot of reasons...|||1)are u using Microsoft Windows Server 2003 as OS? if it is,check this site,

http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql

Distributed transaction error

Hi,
I have written a procedure as below. I'm connected to a remote server server1 with valid

login id and permissions. When I run the procedure, I get the following error.

Server: Msg 7391, Level 16, State 1, Procedure procAddMissingAssociates, Line 09
The operation could not be performed because the OLE DB provider 'SQLOLEDB' does not support

distributed transactions.
[OLE/DB provider returned message: Distributed transaction error]

MSDTC is enabled on both the server, the local as well as the remote ones.
In the example below ASSOCIATE_ID in table2 is a primary key.

Please help,
Thanks
P.C. Vaidyanathan

CREATE PROCEDURE procAddMissingAssociates
AS
DECLARE @.USERID INT

BEGIN
SET TRANSACTION ISOLATION LEVEL repeatable read

BEGIN DISTRIBUTED TRANSACTION
SET XACT_ABORT ON

DECLARE MISSING_CURSOR CURSOR FOR
SELECT USR_ID
FROM SERVER1.DB1.DBO.TABLE1
WHERE USR_ID NOT IN (SELECT COLUMN2
FROM TABLE2)

OPEN MISSING_CURSOR
FETCH FROM MISSING_CURSOR
INTO @.USERID

WHILE (@.@.FETCH_STATUS=0)
BEGIN
INSERT INTO TABLE2 (ASSOCIATE_ID,
REDEEM_POINTS,
UPDATED_DATE)
VALUES (@.USERID,
0,
GETDATE())
FETCH NEXT FROM MISSING_CURSOR
INTO @.USERID
END
CLOSE MISSING_CURSOR
DEALLOCATE MISSING_CURSOR
COMMIT TRANSACTION
END
GOif your servers connect to each other trough the Firewall, check that all necessary ports are open in both directions. As usually it is 1433 and 134|||SERVER1.DB1.DBO.TABLE1

are both sql servers on the same network and starting as the same user? how are you authenticating with server1? linked server?

the above post is right, if you are on seperate networks, you'll need to have access to the other machine thru the firewall.

if you cant/dont want to setup a linked server, you can also use OPENROWSET in an encrypted view.

if thats not the problem.. from another forum

"To work around this problem, set XACT_ABORT to ON before the transaction. This causes SQL Server to terminate the surrounding transaction when an error occurs while processing the data modification statement. If SET XACT_ABORT is ON, SQL Server does not require nested transaction support from the OLE DB Provider. "

Also, try the following:

http://dbforums.com/t361216.html

Distributed Transaction

I want to do distributed queries in a transaction, I'm using win XP pro, then I connect to a remote server (win 2003 standard), the remote server has sql server standard edition and my computer has sql server personal edition.
when I try to do this
begin tran
select * from rafael.tcadbcoi.dbo.invlin
commit tran
I get this error
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].
without "begin tran" , the sicript works ritght> when I try to do this
> begin tran
> select * from rafael.tcadbcoi.dbo.invlin
> commit tran
> I get this error
> The operation could not be performed because the OLE DB provider
'SQLOLEDB' was unable to
> begin a distributed transaction. [OLE/DB provider returned message: New
transaction cannot enlist in
> the specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction
> returned 0x8004d00a].
> without "begin tran" , the script works right
--
Error 0x8004d00a is an issue with MSDTC. On the Windows 2003 server, verify
whether "Enable DTC for remote access" is turned on, reboot and try again.
For more information, consult the "Configuring an application server"
documentation of Windows 2003 online help.
Hope this helps,
--
Eric Cárdenas
SQL Server support