Distribution agent schedule

Hi,
1. I need to configure automatic stop of the distribution agent for
transactional replication and start in 3 hours in order guys could run their
reports on the replicated site. This means that distribution agent should run
all the time except the time 7.00-10.00, stop automatic at 7.00 and start at
10.00. How can I configure that through the schedule in the distribution
agent job settings (agent’s properties)?
2. What another solution could be suggested to run queries without
interrupting continuous work of distribution agent for transactional
replication (pull subscriber)?
1) Right click on your distribution agent, select agent properties,
schedules, and create a reoccurring daily schedule which starts at 10:00 and
stops at 7:00.
2) Have them look at Reporting Services or Analysis Services. These products
may be what they are looking for depending on their requirements.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Elena" <Elena@.discussions.microsoft.com> wrote in message
news:7CFF7D5E-F884-4885-8459-6D396E644796@.microsoft.com...
> Hi,
> 1. I need to configure automatic stop of the distribution agent for
> transactional replication and start in 3 hours in order guys could run
> their
> reports on the replicated site. This means that distribution agent should
> run
> all the time except the time 7.00-10.00, stop automatic at 7.00 and start
> at
> 10.00. How can I configure that through the schedule in the distribution
> agent job settings (agent's properties)?
> 2. What another solution could be suggested to run queries without
> interrupting continuous work of distribution agent for transactional
> replication (pull subscriber)?
>
|||1) But what shall I choose in the hours option?
2) Reporting guys are already using Reporting Services. But not in the right
way I guess. Some Reports use multiple joins of huge tables.
"Hilary Cotter" wrote:

> 1) Right click on your distribution agent, select agent properties,
> schedules, and create a reoccurring daily schedule which starts at 10:00 and
> stops at 7:00.
> 2) Have them look at Reporting Services or Analysis Services. These products
> may be what they are looking for depending on their requirements.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Elena" <Elena@.discussions.microsoft.com> wrote in message
> news:7CFF7D5E-F884-4885-8459-6D396E644796@.microsoft.com...
>
>
|||1) In the schedules table, select reoccurring. Click Change, Click daily,
and I'd select occurs every 5 minutes. With a start at 10:00 pm and stop at
7:00 am. Its not clear to me when you want it to start and stop. Can you use
am and pm or military times?
2) I can't comment if they are using it correctly or not. If you/they are
concerned about it, I would post to
microsoft.public.sqlserver.reportingservices
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Elena" <Elena@.discussions.microsoft.com> wrote in message
news:2950DC12-CE3B-48A7-B679-19872DD907C2@.microsoft.com...[vbcol=seagreen]
> 1) But what shall I choose in the hours option?
> 2) Reporting guys are already using Reporting Services. But not in the
> right
> way I guess. Some Reports use multiple joins of huge tables.
> "Hilary Cotter" wrote:

distributed transaction on win 2003 server failed

Hi Guys,
I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
win2k working fine.
but the same transaction not working in win2k3.
i am getting the following error.
Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
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].
NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
NETWORK ACCESS.
MY CODE IS LIKE THIS.
CREATE PROCEDURE P2( @.NO INT)
AS
BEGIN DISTRIBUTED TRAN
INSERT INTO TESTB VALUES(1,'GH')
EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
COMMIT TRAN
pls advice me
On a Windows 2003 cluster you have to manually create a MSDTC cluster
instance.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"bijupg" <bijupg@.hotmail.com> wrote in message
news:0dbe01c503b2$665adce0$a601280a@.phx.gbl...
> Hi Guys,
> I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
> win2k working fine.
> but the same transaction not working in win2k3.
> i am getting the following error.
> Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
> 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].
> NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
> NETWORK ACCESS.
> MY CODE IS LIKE THIS.
> CREATE PROCEDURE P2( @.NO INT)
> AS
> BEGIN DISTRIBUTED TRAN
> INSERT INTO TESTB VALUES(1,'GH')
> EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
> COMMIT TRAN
> pls advice me

distributed transaction giving error on win2003

Hi Guys,
I AM USING DISTRIBUTED TRANSACTION WITH 2 sql server 2000
on
win2k and is working fine.
but the same transaction not working in win2003.
i am getting the following error.
Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
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].
NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
NETWORK ACCESS.
MY CODE IS LIKE THIS.
CREATE PROCEDURE P2( @.NO INT)
AS
BEGIN DISTRIBUTED TRAN
INSERT INTO TESTB VALUES(1,'GH')
EXEC server2.PUBS.DBO.P1 @.NO
COMMIT TRAN
pls advice meTry taking a look over this
http://blogs.msdn.com/florinlazar/a...1/02/47239.aspx
Message posted via http://www.droptable.com

distributed transaction giving error on win2003

Hi Guys,
I AM USING DISTRIBUTED TRANSACTION WITH 2 sql server 2000
on
win2k and is working fine.
but the same transaction not working in win2003.
i am getting the following error.
Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
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].
NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
NETWORK ACCESS.
MY CODE IS LIKE THIS.
CREATE PROCEDURE P2( @.NO INT)
AS
BEGIN DISTRIBUTED TRAN
INSERT INTO TESTB VALUES(1,'GH')
EXEC server2.PUBS.DBO.P1 @.NO
COMMIT TRAN
pls advice me
Try taking a look over this
http://blogs.msdn.com/florinlazar/ar.../02/47239.aspx
Message posted via http://www.sqlmonster.com

distributed transaction giving error on win 2003

Hi Guys,
I AM USING DISTRIBUTED TRANSACTION WITH 2 sql server 2000
on
win2k and is working fine.
but the same transaction not working in win2003.
i am getting the following error.
Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
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].
NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
NETWORK ACCESS.
MY CODE IS LIKE THIS.
CREATE PROCEDURE P2( @.NO INT)
AS
BEGIN DISTRIBUTED TRAN
INSERT INTO TESTB VALUES(1,'GH')
EXEC server2.PUBS.DBO.P1 @.NO
COMMIT TRAN
pls advice me
.Hi
Did you check out
http://support.microsoft.com/defaul...kb;en-us;329332 or possible
firewall issues?
John
"bijupg" wrote:

> Hi Guys,
> I AM USING DISTRIBUTED TRANSACTION WITH 2 sql server 2000
> on
> win2k and is working fine.
> but the same transaction not working in win2003.
> i am getting the following error.
> Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
> 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].
> NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
> NETWORK ACCESS.
> MY CODE IS LIKE THIS.
> CREATE PROCEDURE P2( @.NO INT)
> AS
> BEGIN DISTRIBUTED TRAN
> INSERT INTO TESTB VALUES(1,'GH')
> EXEC server2.PUBS.DBO.P1 @.NO
> COMMIT TRAN
> pls advice me
> ..
>

distributed transaction failed on win 2003

Hi Guys,
I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
win2k working fine.
but the same transaction not working in win2k3.
i am getting the following error.
Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
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].
NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
NETWORK ACCESS.
MY CODE IS LIKE THIS.
CREATE PROCEDURE P2( @.NO INT)
AS
BEGIN DISTRIBUTED TRAN
INSERT INTO TESTB VALUES(1,'GH')
EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
COMMIT TRAN
pls advice mecontrol panel, addr emove perograms, add/remove win components, application
server, enable network COM+ access
"bijupg" wrote:
> Hi Guys,
> I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
> win2k working fine.
> but the same transaction not working in win2k3.
> i am getting the following error.
> Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
> 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].
> NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
> NETWORK ACCESS.
> MY CODE IS LIKE THIS.
> CREATE PROCEDURE P2( @.NO INT)
> AS
> BEGIN DISTRIBUTED TRAN
> INSERT INTO TESTB VALUES(1,'GH')
> EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
> COMMIT TRAN
> pls advice me
>|||check "Allow other SQL Servers to connect remotely to this SQL Server using
RPC" and "Enforce distributed transactions"
"Aleksandar Grbic" wrote:
> control panel, addr emove perograms, add/remove win components, application
> server, enable network COM+ access
> "bijupg" wrote:
> > Hi Guys,
> >
> > I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
> > win2k working fine.
> > but the same transaction not working in win2k3.
> >
> > i am getting the following error.
> >
> > Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
> > 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].
> >
> > NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
> > NETWORK ACCESS.
> >
> > MY CODE IS LIKE THIS.
> > CREATE PROCEDURE P2( @.NO INT)
> > AS
> > BEGIN DISTRIBUTED TRAN
> > INSERT INTO TESTB VALUES(1,'GH')
> > EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
> > COMMIT TRAN
> >
> > pls advice me
> >|||even after this not working.
>--Original Message--
>check "Allow other SQL Servers to connect remotely to
this SQL Server using
>RPC" and "Enforce distributed transactions"
>"Aleksandar Grbic" wrote:
>> control panel, addr emove perograms, add/remove win
components, application
>> server, enable network COM+ access
>> "bijupg" wrote:
>> > Hi Guys,
>> >
>> > I AM USING DISTRIBUTED TRANSACTION WITH sql server
2000 on
>> > win2k working fine.
>> > but the same transaction not working in win2k3.
>> >
>> > i am getting the following error.
>> >
>> > Server: Msg 7391, Level 16, State 1, Procedure P2,
Line 5
>> > 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].
>> >
>> > NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED
FOR
>> > NETWORK ACCESS.
>> >
>> > MY CODE IS LIKE THIS.
>> > CREATE PROCEDURE P2( @.NO INT)
>> > AS
>> > BEGIN DISTRIBUTED TRAN
>> > INSERT INTO TESTB VALUES(1,'GH')
>> > EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
>> > COMMIT TRAN
>> >
>> > pls advice me
>> >
>.
>

distributed transaction failed on win 2003

Hi Guys,
I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
win2k working fine.
but the same transaction not working in win2k3.
i am getting the following error.
Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
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].
NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
NETWORK ACCESS.
MY CODE IS LIKE THIS.
CREATE PROCEDURE P2( @.NO INT)
AS
BEGIN DISTRIBUTED TRAN
INSERT INTO TESTB VALUES(1,'GH')
EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
COMMIT TRAN
pls advice me
control panel, addr emove perograms, add/remove win components, application
server, enable network COM+ access
"bijupg" wrote:

> Hi Guys,
> I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
> win2k working fine.
> but the same transaction not working in win2k3.
> i am getting the following error.
> Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
> 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].
> NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
> NETWORK ACCESS.
> MY CODE IS LIKE THIS.
> CREATE PROCEDURE P2( @.NO INT)
> AS
> BEGIN DISTRIBUTED TRAN
> INSERT INTO TESTB VALUES(1,'GH')
> EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
> COMMIT TRAN
> pls advice me
>
|||check "Allow other SQL Servers to connect remotely to this SQL Server using
RPC" and "Enforce distributed transactions"
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> control panel, addr emove perograms, add/remove win components, application
> server, enable network COM+ access
> "bijupg" wrote:
|||even after this not working.
>--Original Message--
>check "Allow other SQL Servers to connect remotely to
this SQL Server using[vbcol=seagreen]
>RPC" and "Enforce distributed transactions"
>"Aleksandar Grbic" wrote:
components, application[vbcol=seagreen]
2000 on[vbcol=seagreen]
Line 5[vbcol=seagreen]
DB[vbcol=seagreen]
cannot[vbcol=seagreen]
0x8004d00a].[vbcol=seagreen]
FOR
>.
>

distributed transaction failed on win 2003

Hi Guys,
I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
win2k working fine.
but the same transaction not working in win2k3.
i am getting the following error.
Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
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].
NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
NETWORK ACCESS.
MY CODE IS LIKE THIS.
CREATE PROCEDURE P2( @.NO INT)
AS
BEGIN DISTRIBUTED TRAN
INSERT INTO TESTB VALUES(1,'GH')
EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
COMMIT TRAN
pls advice mecontrol panel, addr emove perograms, add/remove win components, application
server, enable network COM+ access
"bijupg" wrote:

> Hi Guys,
> I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
> win2k working fine.
> but the same transaction not working in win2k3.
> i am getting the following error.
> Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
> 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].
> NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
> NETWORK ACCESS.
> MY CODE IS LIKE THIS.
> CREATE PROCEDURE P2( @.NO INT)
> AS
> BEGIN DISTRIBUTED TRAN
> INSERT INTO TESTB VALUES(1,'GH')
> EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
> COMMIT TRAN
> pls advice me
>|||check "Allow other SQL Servers to connect remotely to this SQL Server using
RPC" and "Enforce distributed transactions"
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> control panel, addr emove perograms, add/remove win components, applicatio
n
> server, enable network COM+ access
> "bijupg" wrote:
>|||even after this not working.
>--Original Message--
>check "Allow other SQL Servers to connect remotely to
this SQL Server using
>RPC" and "Enforce distributed transactions"
>"Aleksandar Grbic" wrote:
>
components, application[vbcol=seagreen]
2000 on[vbcol=seagreen]
Line 5[vbcol=seagreen]
DB[vbcol=seagreen]
cannot[vbcol=seagreen]
0x8004d00a].[vbcol=seagreen]
FOR[vbcol=seagreen]
>.
>