Issues setting up users to authenticate via NT group into MSSQL

I have a NT Group of users that need to connect to MSSQL db using integrated auth and run a stored proc. I have got this concept to work for individual windows users but not a group.

Does anyone have any ideas?

(Win XP, MSSQL 2000 SP3, Windows Group = "SQLUsers", member is "User2")

-- TSQL --

USE master
GO
sp_grantlogin 'pc\SQLUsers'
GO
sp_defaultdb 'pc\SQLUsers', 'theDB'
GO
USE theDB
GO
sp_grantdbaccess 'pc\SQLUsers', 'SQLUsers'
GO
GRANT EXECUTE ON [dbo].[uspThing] TO SQLUsers
GO

-- Trying to connect with OSQL.EXE:

> osql -d theDB -E
Login failed for user 'pc\User2'.

BUT....

runing it for the individual user:

--TSQL

USE master
GO
sp_grantlogin 'pc\User2'
GO
sp_defaultdb 'pc\User2', 'theDB'
GO
USE theDB
GO
sp_grantdbaccess 'pc\User2', 'SQLUsers'
GO
GRANT EXECUTE ON [dbo].[uspThing] TO SQLUsers
GO

-- now trying to connect with OSQL.EXE as User2:

>osql -d theDB -E
1> exec uspThing
2> go
3> data...

all is fine.....

I can't use the user method - to much admin... any ideas!?

PKOk, get this... because I was using "runas /user:User2 cmd.exe" sessions for testing the different users integrated security (osql -E -d dbName) etc the group changes I was making were not reflected until I logged out of the command session.

I have been officially driven mad by this one...

Issues on setting the table visibility using an expression

Hi team,

I'm working on Reporting service 2005. When I give an expression for visibility of a table in a report based on a parameter, the contents are coming in a single page and it is not based on the interactive size of the report. I want the data to be coming on different pages based on the interactive size of the page. If the visibility is set directly it works. Could you please help me to solve this issue?

Thanks in advance,

Minu

Hello,

I couldnt resolve this issue. Can you please tell whether its a known issue in reporting service?

Thanks,

Minu

issues deploying snapshot for merge replication.

I'm having issues setting up merge replication and the errors I'm getting are inconsistent but lead me to believe there is a bigger underlying issue than what they actually indicate.

Issue: unable to initialise subscriber with snapshot for merge replication. Fails for various reasons regardless of environment and setup. Previously this has deployed fine but now it is not.

Publisher is SQL 2005 (9.0.2047), Subscribers are SQLExpress or SQL Dev

The various errors I get are as follows:

These come mixed together generally... Unable to INSERT ... cannot insert NULL into column rowguid. [This error comes up on different tables for different snapshots, including ones with no records] bcp (Bulk Copy) error 20253 batch send failed Unspecified error Failed to send batch after max errors end of file reached, terminator missing or field data incomplete

Actions I have taken so far, all to no effect:

Adjusted Agent Profile to increase timeout values and decrease packet sizes Took new snapshots (tables where errors occured changed but still ame errors) Created a local subscription database on the server to remove any network related issues (using merge sync over VPN) Deleted and recreated Publication Created second publication with different articles on same database to find same errors in different locations again

I've tried reinitializing subscriptions (before subscribers were dropped and I tried recreating) but the DROP command fails due to FK constraints so if I reinitialize any subscriptions they will fail to be applied. Have tried editing the properties to just delete data and not drop tables but that still failed.

I've tried setting up subscriber without snapshot - created publication and snapshot, backed up db, copied to subscriber and restored there. See this article: https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=689428&SiteID=1 This bloke suffered same results and the response from MS was to change the help files, not functionality. Doesn't help us dealing with subscribers via satellite AND unable to deploy snapshots...

I've checked the service pack releases to see if any issues like this are addressed and found nothing relevent.

My gut feeling is that the snapshot is not being generated correctly for some reason - system stored procedure errors perhaps.

So far my experience with replication has been good, with the odd issue or frustrating limitation in older versions, but this is really killing me...

Barry

(Sorry that author is "Anonymous" - must have messed that up)

Hey Barry it sounds like you have some problems there.

I would check a few things, maybe you have already done it but perhaps not.

Check that the snapshot is not getting corrupted by something when it is getting transferred accross the network / internet. You could try copying it via FTP and applying manually to the subscriber and see if that helps. Could also look into compressed snapshots for that too. Do a CRC check on the snapshot file and make sure it matches on both ends. You can get a util for that here: http://www.kmrconsulting.com/free_download.html

For that table with the null problems check that the default value for rowguid is set to newid() or newsequential() even though there is no data in there i suspect replication is doing some testing when it sets up the subscription to make sure things are running.

It sounds like your failure is with the bcp so perhaps after the tables are extracted try adding a few triggers on the troublesome tables that will record what replication is trying to insert or update. That will at least give you more info on what it is trying to do on the table.

Also take a look at the procedures that get run when the subscriber is applying the snapshot. Try running them one by one manually and issolate the problem more.

Good Luck!

Martin

issues deploying snapshot for merge replication.

I'm having issues setting up merge replication and the errors I'm getting are inconsistent but lead me to believe there is a bigger underlying issue than what they actually indicate.

Issue: unable to initialise subscriber with snapshot for merge replication. Fails for various reasons regardless of environment and setup. Previously this has deployed fine but now it is not.

Publisher is SQL 2005 (9.0.2047), Subscribers are SQLExpress or SQL Dev

The various errors I get are as follows:

These come mixed together generally... Unable to INSERT ... cannot insert NULL into column rowguid. [This error comes up on different tables for different snapshots, including ones with no records] bcp (Bulk Copy) error 20253 batch send failed Unspecified error Failed to send batch after max errors end of file reached, terminator missing or field data incomplete

Actions I have taken so far, all to no effect:

Adjusted Agent Profile to increase timeout values and decrease packet sizes Took new snapshots (tables where errors occured changed but still ame errors) Created a local subscription database on the server to remove any network related issues (using merge sync over VPN) Deleted and recreated Publication Created second publication with different articles on same database to find same errors in different locations again

I've tried reinitializing subscriptions (before subscribers were dropped and I tried recreating) but the DROP command fails due to FK constraints so if I reinitialize any subscriptions they will fail to be applied. Have tried editing the properties to just delete data and not drop tables but that still failed.

I've tried setting up subscriber without snapshot - created publication and snapshot, backed up db, copied to subscriber and restored there. See this article: https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=689428&SiteID=1 This bloke suffered same results and the response from MS was to change the help files, not functionality. Doesn't help us dealing with subscribers via satellite AND unable to deploy snapshots...

I've checked the service pack releases to see if any issues like this are addressed and found nothing relevent.

My gut feeling is that the snapshot is not being generated correctly for some reason - system stored procedure errors perhaps.

So far my experience with replication has been good, with the odd issue or frustrating limitation in older versions, but this is really killing me...

Barry

(Sorry that author is "Anonymous" - must have messed that up)

Hey Barry it sounds like you have some problems there.

I would check a few things, maybe you have already done it but perhaps not.

Check that the snapshot is not getting corrupted by something when it is getting transferred accross the network / internet. You could try copying it via FTP and applying manually to the subscriber and see if that helps. Could also look into compressed snapshots for that too. Do a CRC check on the snapshot file and make sure it matches on both ends. You can get a util for that here: http://www.kmrconsulting.com/free_download.html

For that table with the null problems check that the default value for rowguid is set to newid() or newsequential() even though there is no data in there i suspect replication is doing some testing when it sets up the subscription to make sure things are running.

It sounds like your failure is with the bcp so perhaps after the tables are extracted try adding a few triggers on the troublesome tables that will record what replication is trying to insert or update. That will at least give you more info on what it is trying to do on the table.

Also take a look at the procedures that get run when the subscriber is applying the snapshot. Try running them one by one manually and issolate the problem more.

Good Luck!

Martin

Issue when setting up the XML connection to Analysis Services on W

I am using XML For Analysis in a Windows 2000 server in order to access my
OLAP cubes and I'm getting the following error when using the Sample VB app
that comes with the package:
Run-time error '500'
<FaultCode>1198808394</FaultCode>
<Description></Description>
Can some one help me?You may want to ask this question in the analysis services group.
Best regards
Michael
"Carlos La Rovere" <Carlos La Rovere@.discussions.microsoft.com> wrote in
message news:F602ABDF-A418-49A5-B6A3-CA36C3DBE102@.microsoft.com...
>I am using XML For Analysis in a Windows 2000 server in order to access my
> OLAP cubes and I'm getting the following error when using the Sample VB
> app
> that comes with the package:
> Run-time error '500'
> <FaultCode>1198808394</FaultCode>
> <Description></Description>
> Can some one help me?

Issue in setting up the database Mirrioring environment for SQL Server 2005.

Environment:SQL Server 2005 Enterprise in Win2k3 Enterprise on 32(x86) bit machine

I am able to enable the Trace Flag 1400 using DBCC TRACEON (1400) GO. Only then we can able to configure for the ENDPOINTS.

I successfully configured the ENDPOINTS for both the principal server and Mirror server .And then when I started the START MIRRORING.

I got the error message. Please find the Message below.

An error occured while starting mirroring.

additional Information:
:..>Alter failed for Database 'KQDB', (Microsoft SqlServer.Smo)

:..>An exception occured while executing a Transact-SQL statement or batch
[Microsoft SqlServer.Connection.info]

:..>Database mirroring Transport is disabled in the endpoint configuration.
[Microsft SQL Server,Error: 1486]

If anyone have a solution on how to setup a database mirroring environment.Please send.

You must start up the sql service with trace flag 1400. It is not enough to use DBCC TRACE ON.

Thanks,

Mark

|||I've been encountering the same issue. I've set the trace flag on startup, and still have no luck.
I've gone through every step in the online help, verified that BOTH server instances are listening (the pids corresponds to the ports) and I cannot shake this message:

"Database Mirroring Transport is disabled in the endpoint configuration."

The error comes following the command:

alter database AdventureWorks SET PARTNER = 'TCP://10.0.25.72:5022'
go

It does not seem to matter what port I enter, and it doesn't matter what the IP address is. I've tried this on both the Mirror and on the Primary (ie - in every order).

The mirroring endpoints seem be created properly. I've explored all steps in the msdn "Troubleshooting Database Mirroring Setup" document, checking the various system tables for status, etc. but it is to no avail.

I disabled the 'VIA' protocol in the Configuartion Manager, one of the hints I found from the various newsgroups i've browsed.

I am trying to mirror (without a witness) between two instances on the same server. I am well aware that this is not supported, but I need to kick the tires in a testing playground.

Is this a common problem? The lack of postings with this issue indicate that it may not be, but honestly, i'm stymied.

If anyone has encountered and solved this, please respond, and hopefully it will help others as well.

Cheers,

brentj

|||Can you just please tell use how to start the sql service with trace flag 1400.|||

chanmm wrote:

Can you just please tell use how to start the sql service with trace flag 1400.

You don't need the trace flag if you install SP1 which has now released.

Otherwise if SP1 isn't yet an option (which it really should be if you want to use db mirroring), you can add -T1400 as a startup parameter via the SQL Configuration Manager, properties of the SQL Server service -> advanced tab ->Startup Parameters.

it's not particularly well indexed or cross-referenced but BOL has details here :

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c82d19e5-5557-4235-9a70-37983607a1fd.htm

thx, Simon.

|||I'm wondering if the thread started for this post resolved this issue? I have set Trace Flag 1400 "-T1400;..." in startup configuration options, rebooted and restarted servers and still not able to mirror. Also given the error "Database Mirroring Transport is disabled."

Anyone figure this out? Next I install SQL 2005 SP1.|||To update on my experience:
I installed SP1 and interestingly it even strips the Trace Flag 1400 out of the startup options for you so you don't leave that remnant of a failed Mirroring Attempt - good work guys!

I got an asynchronous mirror working after installing SQL 2005 SP1 but have not fully tested it.|||Sample is there in the updated SQL BOL docs. No gotchas except the fact that security configuration is the MOST critical. If you get that done, the rest is a breeze.

Issue in setting up the database Mirrioring environment for SQL Server 2005.

Environment:SQL Server 2005 Enterprise in Win2k3 Enterprise on 32(x86) bit machine

I am able to enable the Trace Flag 1400 using DBCC TRACEON (1400) GO. Only then we can able to configure for the ENDPOINTS.

I successfully configured the ENDPOINTS for both the principal server and Mirror server .And then when I started the START MIRRORING.

I got the error message. Please find the Message below.

An error occured while starting mirroring.

additional Information:
:..>Alter failed for Database 'KQDB', (Microsoft SqlServer.Smo)

:..>An exception occured while executing a Transact-SQL statement or batch
[Microsoft SqlServer.Connection.info]

:..>Database mirroring Transport is disabled in the endpoint configuration.
[Microsft SQL Server,Error: 1486]

If anyone have a solution on how to setup a database mirroring environment.Please send.

You must start up the sql service with trace flag 1400. It is not enough to use DBCC TRACE ON.

Thanks,

Mark

|||I've been encountering the same issue. I've set the trace flag on startup, and still have no luck.
I've gone through every step in the online help, verified that BOTH server instances are listening (the pids corresponds to the ports) and I cannot shake this message:

"Database Mirroring Transport is disabled in the endpoint configuration."

The error comes following the command:

alter database AdventureWorks SET PARTNER = 'TCP://10.0.25.72:5022'
go

It does not seem to matter what port I enter, and it doesn't matter what the IP address is. I've tried this on both the Mirror and on the Primary (ie - in every order).

The mirroring endpoints seem be created properly. I've explored all steps in the msdn "Troubleshooting Database Mirroring Setup" document, checking the various system tables for status, etc. but it is to no avail.

I disabled the 'VIA' protocol in the Configuartion Manager, one of the hints I found from the various newsgroups i've browsed.

I am trying to mirror (without a witness) between two instances on the same server. I am well aware that this is not supported, but I need to kick the tires in a testing playground.

Is this a common problem? The lack of postings with this issue indicate that it may not be, but honestly, i'm stymied.

If anyone has encountered and solved this, please respond, and hopefully it will help others as well.

Cheers,

brentj

|||Can you just please tell use how to start the sql service with trace flag 1400.|||

chanmm wrote:

Can you just please tell use how to start the sql service with trace flag 1400.

You don't need the trace flag if you install SP1 which has now released.

Otherwise if SP1 isn't yet an option (which it really should be if you want to use db mirroring), you can add -T1400 as a startup parameter via the SQL Configuration Manager, properties of the SQL Server service -> advanced tab ->Startup Parameters.

it's not particularly well indexed or cross-referenced but BOL has details here :

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c82d19e5-5557-4235-9a70-37983607a1fd.htm

thx, Simon.

|||I'm wondering if the thread started for this post resolved this issue? I have set Trace Flag 1400 "-T1400;..." in startup configuration options, rebooted and restarted servers and still not able to mirror. Also given the error "Database Mirroring Transport is disabled."

Anyone figure this out? Next I install SQL 2005 SP1.|||To update on my experience:
I installed SP1 and interestingly it even strips the Trace Flag 1400 out of the startup options for you so you don't leave that remnant of a failed Mirroring Attempt - good work guys!

I got an asynchronous mirror working after installing SQL 2005 SP1 but have not fully tested it.|||Sample is there in the updated SQL BOL docs. No gotchas except the fact that security configuration is the MOST critical. If you get that done, the rest is a breeze.

Issue in setting up the database Mirrioring environment for SQL Server 2005.

Environment:SQL Server 2005 Enterprise in Win2k3 Enterprise on 32(x86) bit machine

I am able to enable the Trace Flag 1400 using DBCC TRACEON (1400) GO. Only then we can able to configure for the ENDPOINTS.

I successfully configured the ENDPOINTS for both the principal server and Mirror server .And then when I started the START MIRRORING.

I got the error message. Please find the Message below.

An error occured while starting mirroring.

additional Information:
:..>Alter failed for Database 'KQDB', (Microsoft SqlServer.Smo)

:..>An exception occured while executing a Transact-SQL statement or batch
[Microsoft SqlServer.Connection.info]

:..>Database mirroring Transport is disabled in the endpoint configuration.
[Microsft SQL Server,Error: 1486]

If anyone have a solution on how to setup a database mirroring environment.Please send.

You must start up the sql service with trace flag 1400. It is not enough to use DBCC TRACE ON.

Thanks,

Mark

|||I've been encountering the same issue. I've set the trace flag on startup, and still have no luck.
I've gone through every step in the online help, verified that BOTH server instances are listening (the pids corresponds to the ports) and I cannot shake this message:

"Database Mirroring Transport is disabled in the endpoint configuration."

The error comes following the command:

alter database AdventureWorks SET PARTNER = 'TCP://10.0.25.72:5022'
go

It does not seem to matter what port I enter, and it doesn't matter what the IP address is. I've tried this on both the Mirror and on the Primary (ie - in every order).

The mirroring endpoints seem be created properly. I've explored all steps in the msdn "Troubleshooting Database Mirroring Setup" document, checking the various system tables for status, etc. but it is to no avail.

I disabled the 'VIA' protocol in the Configuartion Manager, one of the hints I found from the various newsgroups i've browsed.

I am trying to mirror (without a witness) between two instances on the same server. I am well aware that this is not supported, but I need to kick the tires in a testing playground.

Is this a common problem? The lack of postings with this issue indicate that it may not be, but honestly, i'm stymied.

If anyone has encountered and solved this, please respond, and hopefully it will help others as well.

Cheers,

brentj

|||Can you just please tell use how to start the sql service with trace flag 1400.|||

chanmm wrote:

Can you just please tell use how to start the sql service with trace flag 1400.

You don't need the trace flag if you install SP1 which has now released.

Otherwise if SP1 isn't yet an option (which it really should be if you want to use db mirroring), you can add -T1400 as a startup parameter via the SQL Configuration Manager, properties of the SQL Server service -> advanced tab ->Startup Parameters.

it's not particularly well indexed or cross-referenced but BOL has details here :

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c82d19e5-5557-4235-9a70-37983607a1fd.htm

thx, Simon.

|||I'm wondering if the thread started for this post resolved this issue? I have set Trace Flag 1400 "-T1400;..." in startup configuration options, rebooted and restarted servers and still not able to mirror. Also given the error "Database Mirroring Transport is disabled."

Anyone figure this out? Next I install SQL 2005 SP1.|||To update on my experience:
I installed SP1 and interestingly it even strips the Trace Flag 1400 out of the startup options for you so you don't leave that remnant of a failed Mirroring Attempt - good work guys!

I got an asynchronous mirror working after installing SQL 2005 SP1 but have not fully tested it.|||Sample is there in the updated SQL BOL docs. No gotchas except the fact that security configuration is the MOST critical. If you get that done, the rest is a breeze.

Issue in setting up the database Mirrioring environment for SQL Server 2005.

Environment:SQL Server 2005 Enterprise in Win2k3 Enterprise on 32(x86) bit machine

I am able to enable the Trace Flag 1400 using DBCC TRACEON (1400) GO. Only then we can able to configure for the ENDPOINTS.

I successfully configured the ENDPOINTS for both the principal server and Mirror server .And then when I started the START MIRRORING.

I got the error message. Please find the Message below.

An error occured while starting mirroring.

additional Information:
:..>Alter failed for Database 'KQDB', (Microsoft SqlServer.Smo)

:..>An exception occured while executing a Transact-SQL statement or batch
[Microsoft SqlServer.Connection.info]

:..>Database mirroring Transport is disabled in the endpoint configuration.
[Microsft SQL Server,Error: 1486]

If anyone have a solution on how to setup a database mirroring environment.Please send.

You must start up the sql service with trace flag 1400. It is not enough to use DBCC TRACE ON.

Thanks,

Mark

|||I've been encountering the same issue. I've set the trace flag on startup, and still have no luck.
I've gone through every step in the online help, verified that BOTH server instances are listening (the pids corresponds to the ports) and I cannot shake this message:

"Database Mirroring Transport is disabled in the endpoint configuration."

The error comes following the command:

alter database AdventureWorks SET PARTNER = 'TCP://10.0.25.72:5022'
go

It does not seem to matter what port I enter, and it doesn't matter what the IP address is. I've tried this on both the Mirror and on the Primary (ie - in every order).

The mirroring endpoints seem be created properly. I've explored all steps in the msdn "Troubleshooting Database Mirroring Setup" document, checking the various system tables for status, etc. but it is to no avail.

I disabled the 'VIA' protocol in the Configuartion Manager, one of the hints I found from the various newsgroups i've browsed.

I am trying to mirror (without a witness) between two instances on the same server. I am well aware that this is not supported, but I need to kick the tires in a testing playground.

Is this a common problem? The lack of postings with this issue indicate that it may not be, but honestly, i'm stymied.

If anyone has encountered and solved this, please respond, and hopefully it will help others as well.

Cheers,

brentj

|||Can you just please tell use how to start the sql service with trace flag 1400.|||

chanmm wrote:

Can you just please tell use how to start the sql service with trace flag 1400.

You don't need the trace flag if you install SP1 which has now released.

Otherwise if SP1 isn't yet an option (which it really should be if you want to use db mirroring), you can add -T1400 as a startup parameter via the SQL Configuration Manager, properties of the SQL Server service -> advanced tab ->Startup Parameters.

it's not particularly well indexed or cross-referenced but BOL has details here :

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c82d19e5-5557-4235-9a70-37983607a1fd.htm

thx, Simon.

|||I'm wondering if the thread started for this post resolved this issue? I have set Trace Flag 1400 "-T1400;..." in startup configuration options, rebooted and restarted servers and still not able to mirror. Also given the error "Database Mirroring Transport is disabled."

Anyone figure this out? Next I install SQL 2005 SP1.|||To update on my experience:
I installed SP1 and interestingly it even strips the Trace Flag 1400 out of the startup options for you so you don't leave that remnant of a failed Mirroring Attempt - good work guys!

I got an asynchronous mirror working after installing SQL 2005 SP1 but have not fully tested it.|||Sample is there in the updated SQL BOL docs. No gotchas except the fact that security configuration is the MOST critical. If you get that done, the rest is a breeze.

Issue in setting up the database Mirrioring environment for SQL Server 2005.

Environment:SQL Server 2005 Enterprise in Win2k3 Enterprise on 32(x86) bit machine

I am able to enable the Trace Flag 1400 using DBCC TRACEON (1400) GO. Only then we can able to configure for the ENDPOINTS.

I successfully configured the ENDPOINTS for both the principal server and Mirror server .And then when I started the START MIRRORING.

I got the error message. Please find the Message below.

An error occured while starting mirroring.

additional Information:
:..>Alter failed for Database 'KQDB', (Microsoft SqlServer.Smo)

:..>An exception occured while executing a Transact-SQL statement or batch
[Microsoft SqlServer.Connection.info]

:..>Database mirroring Transport is disabled in the endpoint configuration.
[Microsft SQL Server,Error: 1486]

If anyone have a solution on how to setup a database mirroring environment.Please send.

You must start up the sql service with trace flag 1400. It is not enough to use DBCC TRACE ON.

Thanks,

Mark

|||I've been encountering the same issue. I've set the trace flag on startup, and still have no luck.
I've gone through every step in the online help, verified that BOTH server instances are listening (the pids corresponds to the ports) and I cannot shake this message:

"Database Mirroring Transport is disabled in the endpoint configuration."

The error comes following the command:

alter database AdventureWorks SET PARTNER = 'TCP://10.0.25.72:5022'
go

It does not seem to matter what port I enter, and it doesn't matter what the IP address is. I've tried this on both the Mirror and on the Primary (ie - in every order).

The mirroring endpoints seem be created properly. I've explored all steps in the msdn "Troubleshooting Database Mirroring Setup" document, checking the various system tables for status, etc. but it is to no avail.

I disabled the 'VIA' protocol in the Configuartion Manager, one of the hints I found from the various newsgroups i've browsed.

I am trying to mirror (without a witness) between two instances on the same server. I am well aware that this is not supported, but I need to kick the tires in a testing playground.

Is this a common problem? The lack of postings with this issue indicate that it may not be, but honestly, i'm stymied.

If anyone has encountered and solved this, please respond, and hopefully it will help others as well.

Cheers,

brentj

|||Can you just please tell use how to start the sql service with trace flag 1400.|||

chanmm wrote:

Can you just please tell use how to start the sql service with trace flag 1400.

You don't need the trace flag if you install SP1 which has now released.

Otherwise if SP1 isn't yet an option (which it really should be if you want to use db mirroring), you can add -T1400 as a startup parameter via the SQL Configuration Manager, properties of the SQL Server service -> advanced tab ->Startup Parameters.

it's not particularly well indexed or cross-referenced but BOL has details here :

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c82d19e5-5557-4235-9a70-37983607a1fd.htm

thx, Simon.

|||I'm wondering if the thread started for this post resolved this issue? I have set Trace Flag 1400 "-T1400;..." in startup configuration options, rebooted and restarted servers and still not able to mirror. Also given the error "Database Mirroring Transport is disabled."

Anyone figure this out? Next I install SQL 2005 SP1.|||To update on my experience:
I installed SP1 and interestingly it even strips the Trace Flag 1400 out of the startup options for you so you don't leave that remnant of a failed Mirroring Attempt - good work guys!

I got an asynchronous mirror working after installing SQL 2005 SP1 but have not fully tested it.|||Sample is there in the updated SQL BOL docs. No gotchas except the fact that security configuration is the MOST critical. If you get that done, the rest is a breeze.

Issue in Merge Replication

Hi Kevin,
I am setting up a SQL Server Database Merge Replication between Publisher
(P) & Subscriber (S) using EXCHANGE_TYPE '1' (Data only needs to be merged
from Subscriber to Publisher - Upload). Publisher priority is maximaum by
default.
However, I am facing this issue:
Under normal scenario, if a row of Data is changed at Subscriber, it is
updated at the Publisher since there is no change at Publisher.
But when same Row of Data in Publication (Table x) is updated at the
Publisher and also at the Subscriber (conflict situation), the row do not
particicipate in Replication when the agent runs and then it never
participates in Replication. Means the Data at Subscriber and Publisher
reamins different for that row. SQL Server do show any conflict that I can
resolve. Kindly help me to find out root cause and how to fix this!
Database : SQL Server 2000 SP3a
OS: Win2003 (No Service Pack)
Hi All,
I found the solution myself . Basically by changing the conflict resolver to
"Subscriber will always win the conflict" resolves the problem.
Cheers!
Vikas
"Vikas Kohli" wrote:

> Hi Kevin,
> I am setting up a SQL Server Database Merge Replication between Publisher
> (P) & Subscriber (S) using EXCHANGE_TYPE '1' (Data only needs to be merged
> from Subscriber to Publisher - Upload). Publisher priority is maximaum by
> default.
> However, I am facing this issue:
> Under normal scenario, if a row of Data is changed at Subscriber, it is
> updated at the Publisher since there is no change at Publisher.
> But when same Row of Data in Publication (Table x) is updated at the
> Publisher and also at the Subscriber (conflict situation), the row do not
> particicipate in Replication when the agent runs and then it never
> participates in Replication. Means the Data at Subscriber and Publisher
> reamins different for that row. SQL Server do show any conflict that I can
> resolve. Kindly help me to find out root cause and how to fix this!
> Database : SQL Server 2000 SP3a
> OS: Win2003 (No Service Pack)