could not execute sp_replcmds on server - need help

I have been getting this message in the past couple of hours. I
rebooted publisher and subscriber. Even if I restart the agent - it
doesn't help. I rebuilt transactional replication from scratch and I
still got this error message. I set for the agent to output to the
file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
>>The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.<<
Try creating a new Profile for your log reader agent with a smaller number
for the -ReadBatchSize parameter, and/or a longer -LoginTimeout value
Could be you have a very large transaction stuck in the t-log of the
published database
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"tolcis" <nytollydba@.gmail.com> wrote in message
news:70357b88-b169-4b21-83b4-ddc5a00b6ad0@.q77g2000hsh.googlegroups.com...
>I have been getting this message in the past couple of hours. I
> rebooted publisher and subscriber. Even if I restart the agent - it
> doesn't help. I rebuilt transactional replication from scratch and I
> still got this error message. I set for the agent to output to the
> file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}

could not execute sp_replcmds on server - need help

I have been getting this message in the past couple of hours. I
rebooted publisher and subscriber. Even if I restart the agent - it
doesn't help. I rebuilt transactional replication from scratch and I
still got this error message. I set for the agent to output to the
file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}>>The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.<<
Try creating a new Profile for your log reader agent with a smaller number
for the -ReadBatchSize parameter, and/or a longer -LoginTimeout value
Could be you have a very large transaction stuck in the t-log of the
published database
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"tolcis" <nytollydba@.gmail.com> wrote in message
news:70357b88-b169-4b21-83b4-ddc5a00b6ad0@.q77g2000hsh.googlegroups.com...
>I have been getting this message in the past couple of hours. I
> rebooted publisher and subscriber. Even if I restart the agent - it
> doesn't help. I rebuilt transactional replication from scratch and I
> still got this error message. I set for the agent to output to the
> file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}

could not execute sp_replcmds on server - need help

I have been getting this message in the past couple of hours. I
rebooted publisher and subscriber. Even if I restart the agent - it
doesn't help. I rebuilt transactional replication from scratch and I
still got this error message. I set for the agent to output to the
file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}>>The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.<<
Try creating a new Profile for your log reader agent with a smaller number
for the -ReadBatchSize parameter, and/or a longer -LoginTimeout value
Could be you have a very large transaction stuck in the t-log of the
published database
--
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"tolcis" <nytollydba@.gmail.com> wrote in message
news:70357b88-b169-4b21-83b4-ddc5a00b6ad0@.q77g2000hsh.googlegroups.com...
>I have been getting this message in the past couple of hours. I
> rebooted publisher and subscriber. Even if I restart the agent - it
> doesn't help. I rebuilt transactional replication from scratch and I
> still got this error message. I set for the agent to output to the
> file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}

could not execute sp_replcmds

I am working on SQL Server 2000 SP4
I am getting a very strange error on one of my instances;

The process could not execute 'sp_replcmds' on #SERVERNAME#

Replication failure. File 'T:\shiloh\sql\ntdbms\srvrepl\src\replicat.cpp',
line 1677.
(Source: #SERVERNAME# (Data source); Error number: 18759)

In microsoft http://support.microsoft.com/kb/308865 it tells you to apply
SQL SP4, which i have done and re did just incase it wasn't applied properly,
it made no difference to the situations. Ive restarted the intance and the
server and still to no avail.

Last month we did have a situation where our master database went suspect
and this is the first time anything has had to be replicated on that server
since then. The publisher and subscriber database are on the same server.

Thanks.

Was this post helpful to you?

Why should I rate a post?I have a recollection with replication that you have to enable replication before applying SP4 (or re-apply SP4 after enabling replication). You must do this on both the publisher and the distributor. If I recall the sequence correctly, you must do the distributor first and then then publisher.

I know that you said you re-applied SP4, did you do it in accordance with the steps outlined above?

Regards,

hmscott

Could not establish trust relationship with remote server.........

Please....help....I've to go live with the production environment - next
week...
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?&guid=&sloc=en-us&dg=microsoft.public.sqlserver.reportingsvcs&p=1&tid=a80ed727-334a-47c9-a6c8-2b76dfc141cd
Many thanks...Bye the way...I'm using the Reporting Service Developer Edition on my Test
serverâ?¦
"Dominic" wrote:
> Please....help....I've to go live with the production environment - next
> week...
> http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?&guid=&sloc=en-us&dg=microsoft.public.sqlserver.reportingsvcs&p=1&tid=a80ed727-334a-47c9-a6c8-2b76dfc141cd
> Many thanks...|||Hi Dominic,
I had exactly the same problem as you described. I'm also using the
Reporting Server Developer Edition too on our test system. After alot of
effort I tracked it down to the SSL certificate we have on our test server
not been written to the "Trusted Certificated List". To Fix this I used
selfSSL with the option /T see below this fixed it with no other changes
required. If I missed out the /T option I got exactly the same error as you.
Regards,
Microsoft (R) SelfSSL Version 1.0
Copyright (C) 2003 Microsoft Corporation. All rights reserved.
Installs self-signed SSL certificate into IIS.
SELFSSL [/T] [/N:cn] [/K:key size] [/S:site id] [/P:port]
/T Adds the self-signed certificate to "Trusted Certificates"
list. The local browser will trust the self-signed
certificate
if this flag is specified.
/N:cn Specifies the common name of the certificate. The computer
name is used if not specified.
/K:key size Specifies the key length. Default is 1024.
/V:validity days Specifies the validity of the certificate. Default is 7 days.
/S:site id Specifies the id of the site. Default is 1 (Default Site).
/P:port Specifies the SSL port. Default is 443.
/Q Quiet mode. You will not be prompted when SSL settings are
overwritten.
I ran selfssl on the command line with the following options
selfssl.exe /T /N:CN=EDGE /K:1024 /V:365 /S:1 /P:443
"Dominic" wrote:
> Bye the way...I'm using the Reporting Service Developer Edition on my Test
> serverâ?¦
>
> "Dominic" wrote:
> > Please....help....I've to go live with the production environment - next
> > week...
> >
> > http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?&guid=&sloc=en-us&dg=microsoft.public.sqlserver.reportingsvcs&p=1&tid=a80ed727-334a-47c9-a6c8-2b76dfc141cd
> >
> > Many thanks...

Could not establish trust relationship with remote server.

I am trying to setup SQL Server 2000 Reporting services with an SSL
connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
have tried setting up Certificates from both and Stand-Alone and Enterprise
CA. I have tried several combinations of the Issue To name (server |
server.company | server.company.local) I have modified the
rsWebApplication.config and rsReportServer.config to match the certificateâ's
Issue to exactly. I have tried installs with both Domain Accounts and NT
AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
to work but I have had no luck with the report manager
https://server/reports. How do I fix this error?
ThankyouThe most likely reason this is failing is that your Report Server does not
trust the Root Certificate Authority that created the certificate you are
using.
If you go to https://machine/ReportServer and IE says "this certificate is
not valid are you sure you want to accept it?" then you will know that the
certificate is not 100% trusted and that is why you are receiving the error.
You will need to export the Trusted Root Authority certificate from the
issuing server and import it on the Report Server.
--
SQL Server Developer Support Engineer
"vbchewie" wrote:
> I am trying to setup SQL Server 2000 Reporting services with an SSL
> connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
> Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
> have tried setting up Certificates from both and Stand-Alone and Enterprise
> CA. I have tried several combinations of the Issue To name (server |
> server.company | server.company.local) I have modified the
> rsWebApplication.config and rsReportServer.config to match the certificateâ's
> Issue to exactly. I have tried installs with both Domain Accounts and NT
> AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
> to work but I have had no luck with the report manager
> https://server/reports. How do I fix this error?
> Thankyou
>|||I went to the stand alone root certificate authority and exported the
certificate for that server. I then imported it into both the SQL Server and
Reporting Server. Now when I type the FQDN
(https://machine.domain.local/Reports ) I no longer get a certificate error,
but I do still get â'The underlying connection was closed: Could not establish
trust relationship with remote server.â'
Is there something else I can do? Does it have to be an Enterprise Root
Certificate Authority in order to work?
Thank You.
"Chris Alton [MS]" wrote:
> The most likely reason this is failing is that your Report Server does not
> trust the Root Certificate Authority that created the certificate you are
> using.
> If you go to https://machine/ReportServer and IE says "this certificate is
> not valid are you sure you want to accept it?" then you will know that the
> certificate is not 100% trusted and that is why you are receiving the error.
> You will need to export the Trusted Root Authority certificate from the
> issuing server and import it on the Report Server.
> --
> SQL Server Developer Support Engineer
>
> "vbchewie" wrote:
> > I am trying to setup SQL Server 2000 Reporting services with an SSL
> > connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
> > Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
> > have tried setting up Certificates from both and Stand-Alone and Enterprise
> > CA. I have tried several combinations of the Issue To name (server |
> > server.company | server.company.local) I have modified the
> > rsWebApplication.config and rsReportServer.config to match the certificateâ's
> > Issue to exactly. I have tried installs with both Domain Accounts and NT
> > AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
> > to work but I have had no luck with the report manager
> > https://server/reports. How do I fix this error?
> >
> > Thankyou
> >|||You also need to make sure that the SSL certificate you are using matches
the machine name you are accessing it by EXACTLY. You will also need to
make sure that in the Reporting Services configuration tool that you have
checked the "Require Secure Socket Layer (SSL) Connections" and put the
same name you are accessing the server by in the "Certificate Name" field.
So in your example you would put "machine.domain.local" in the Certificate
Field and the certificate should be issued to "machine.domain.local".
The easiest way to tell if the certificate is valid is to open up
https://machine.domain.local/ReportServer from the web server and if IE
complains about the certificate at all then it will not work.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.|||In RSReportServer.config I have my "SecureConnectionLevel" Value="3" and my
<UrlRoot>https://machine.domain.local/ReportServer</UrlRoot>
in RSWebApplication.config
I have
<ReportServerUrl>https://machine.domain.local/ReportServer</ReportServerUrl>
When I go to IIS on the Reporting Server and right click on Default Web Site
> Properties > Directory Security.
And click on 'View Certificate...' it says Issued to: machine.domain.local I
also checked the friendly name it also has machine.domain.local.
When I click 'Edit...' under 'Secure communications' both Require secure
channel(SSL) and Require 128-bit encryption are checked.
When I click 'Edit...' Under 'Authentication and access control' Enable
anonymous access is unchecked.
The same is true for my Virtual Directories 'Reports' and ReportServer'
When I go to https://machine/domain.local/Reports there are no certificate
errors. It goes straight though to a page that says
"The underlying connection was closed: Could not establish trust
relationship with remote server."
You mentioned Reporting Services Configuration Tool. This is Reporting
Services for SQL Server 2000. Is there a Reporting Services Configuration
Tool for this version? I thought that was for 2005.
Iâ'm not sure what I am missing. Any other ideas?
Thank you
"Chris Alton [MSFT]" wrote:
> You also need to make sure that the SSL certificate you are using matches
> the machine name you are accessing it by EXACTLY. You will also need to
> make sure that in the Reporting Services configuration tool that you have
> checked the "Require Secure Socket Layer (SSL) Connections" and put the
> same name you are accessing the server by in the "Certificate Name" field.
> So in your example you would put "machine.domain.local" in the Certificate
> Field and the certificate should be issued to "machine.domain.local".
> The easiest way to tell if the certificate is valid is to open up
> https://machine.domain.local/ReportServer from the web server and if IE
> complains about the certificate at all then it will not work.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||I didn't know you were using SQL 2000. The only thing I can think of is
that you need to install the Root CA Certificate in the Certificate Store
of the Machine account. What account do you have the SRS Windows Service
and the IIS Application Pool running under?
If it is LocalSystem or Network Service you can install the certificate by
following these steps:
a. Click Start->Run
b. Type mmc and hit enter.
c. Click File->Add/Remove Snap-in
d. Click the "Add" button.
e. Select "Certificates" from the list
f. Click the "Add" button.
g. Click the "Computer Account" radio button.
h. Click "Next"
i. Make sure "Local Computer" is selected and click "Finish"
j. Click "Close"
k. Click "Ok"
l. Branch down on Certificates.
m. Right click Trusted Root Certification Authorities->All
Tasks->Import...
n. Click "Next" and browse to the certificate you are importing.
o. Click "Next" and make sure the "Place all certificates in the
following store" is selected and "Trusted Root Certification Authorities"
is listed in the "Certificate Store" box. If not browse to it by clicking
the "Browse" button.
p. Click "Next" and then click "Finish"
q. The Trusted Root Authority Certificate should now be imported and
available to web application/service.
Hopefully that should get it now.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.|||It works!!!
SRS is running under a domain\account. In order to get Kerberos to function
properly I used setspn to allow the domain\account to use the http service.
So I am not running under LocalSystem or Network Service.
I logged into the computer with the domain\account that is running both the
SRS Service and the ReportingServices Application Pool. I followed your
directions exactly with only one variation. Instead of picking "Computer
Account" at g. I chose "My Account". It looks like it is working now.
To recap for anyone else that runs into this issue:
SQL Server 2000 is on machine1
SharePoint and Reporting Services are on machine2 and are running under a
domain\account (very limited rights).
SSL Certificate was issued from a Stand-Alone Root Certificate Authority.
Thank you very much for your help,
"Chris Alton [MSFT]" wrote:
> I didn't know you were using SQL 2000. The only thing I can think of is
> that you need to install the Root CA Certificate in the Certificate Store
> of the Machine account. What account do you have the SRS Windows Service
> and the IIS Application Pool running under?
> If it is LocalSystem or Network Service you can install the certificate by
> following these steps:
> a. Click Start->Run
> b. Type mmc and hit enter.
> c. Click File->Add/Remove Snap-in
> d. Click the "Add" button.
> e. Select "Certificates" from the list
> f. Click the "Add" button.
> g. Click the "Computer Account" radio button.
> h. Click "Next"
> i. Make sure "Local Computer" is selected and click "Finish"
> j. Click "Close"
> k. Click "Ok"
> l. Branch down on Certificates.
> m. Right click Trusted Root Certification Authorities->All
> Tasks->Import...
> n. Click "Next" and browse to the certificate you are importing.
> o. Click "Next" and make sure the "Place all certificates in the
> following store" is selected and "Trusted Root Certification Authorities"
> is listed in the "Certificate Store" box. If not browse to it by clicking
> the "Browse" button.
> p. Click "Next" and then click "Finish"
> q. The Trusted Root Authority Certificate should now be imported and
> available to web application/service.
> Hopefully that should get it now.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||If the Windows Service and Application Pool all run under a domain account
then you really don't have to go through all those convoluted steps to
import the cert. That is only if you are using LocalSystem/Network Service
since those are considered the "Machine" account.
If you can log on to the account in an interactive session all you really
have to do to import the certificate is logon and then double click the
cer file and follow the prompts :)
Glad its working for you now though, those SSL issues with SRS can be quite
complicated sometimes.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> Thread-Topic: Could not establish trust relationship with remote server.
> From: <vbchewie@.discussions.microsoft.com>
> Subject: RE: Could not establish trust relationship with remote server.
> Date: Tue, 2 Oct 2007 14:18:01 -0700
> It works!!!
> SRS is running under a domain\account. In order to get Kerberos to
function
> properly I used setspn to allow the domain\account to use the http
service.
> So I am not running under LocalSystem or Network Service.
> I logged into the computer with the domain\account that is running both
the
> SRS Service and the ReportingServices Application Pool. I followed your
> directions exactly with only one variation. Instead of picking "Computer
> Account" at g. I chose "My Account". It looks like it is working now.
> To recap for anyone else that runs into this issue:
> SQL Server 2000 is on machine1
> SharePoint and Reporting Services are on machine2 and are running under a
> domain\account (very limited rights).
> SSL Certificate was issued from a Stand-Alone Root Certificate Authority.
> Thank you very much for your help,
>
> "Chris Alton [MSFT]" wrote:
> > I didn't know you were using SQL 2000. The only thing I can think of is
> > that you need to install the Root CA Certificate in the Certificate
Store
> > of the Machine account. What account do you have the SRS Windows
Service
> > and the IIS Application Pool running under?
> >
> > If it is LocalSystem or Network Service you can install the certificate
by
> > following these steps:
> >
> > a. Click Start->Run
> > b. Type mmc and hit enter.
> > c. Click File->Add/Remove Snap-in
> > d. Click the "Add" button.
> > e. Select "Certificates" from the list
> > f. Click the "Add" button.
> > g. Click the "Computer Account" radio button.
> > h. Click "Next"
> > i. Make sure "Local Computer" is selected and click "Finish"
> > j. Click "Close"
> > k. Click "Ok"
> > l. Branch down on Certificates.
> > m. Right click Trusted Root Certification Authorities->All
> > Tasks->Import...
> > n. Click "Next" and browse to the certificate you are importing.
> > o. Click "Next" and make sure the "Place all certificates in the
> > following store" is selected and "Trusted Root Certification
Authorities"
> > is listed in the "Certificate Store" box. If not browse to it by
clicking
> > the "Browse" button.
> > p. Click "Next" and then click "Finish"
> > q. The Trusted Root Authority Certificate should now be imported
and
> > available to web application/service.
> >
> > Hopefully that should get it now.
> > --
> > Chris Alton, Microsoft Corp.
> > SQL Server Developer Support Engineer
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
>

Could not establish trust relationship with remote server.

Error comes up when I try to deploy RS to my web server, "The underlying
connection was closed: Could not establish trust relationship with remote
server." Web server has valid certificate, and I'm using https in my
connection.
OverwriteDataSources: True
TargetFolder: Reports
TargetServerURL: https://webserver/ReportServer
I'm able to see https://webserver/ReportServer through IE, and I see the
folder Reports. I clicked on Reports and I see my old RS files.I also tried without the s in https, but I still get the same error message.
http://webserver/ReportServer
"Mike L" wrote:
> Error comes up when I try to deploy RS to my web server, "The underlying
> connection was closed: Could not establish trust relationship with remote
> server." Web server has valid certificate, and I'm using https in my
> connection.
> OverwriteDataSources: True
> TargetFolder: Reports
> TargetServerURL: https://webserver/ReportServer
> I'm able to see https://webserver/ReportServer through IE, and I see the
> folder Reports. I clicked on Reports and I see my old RS files.
>|||Hello Cadel,
You may try the following steps to disable SSL on report server to test:
1. Within the RSReportServer.config file you'll find in "\Program
Files\Microsoft SQL Server\MSSQL.X\Reporting Services\ReportServer",
set secureconnectionlevel to 0.
Change
<UrlRoot>https://webserver/ReportServer</UrlRoot>
<UrlRoot>http://webserver/ReportServer</UrlRoot>
2. within C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager, change
<ReportServerUrl>https://webserver/ReportServer</ReportServerUrl> to
<ReportServerUrl>http://webserver/ReportServer</ReportServerUrl>
Note: Please backup above files to safe place before you try to modify
them. You may need to restart IIS if it is not take effect
After that, you may want to configure deploy server to
http://webserver/ReportServer in VS to test the situatioin.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Could not establish trust relationship with remote server.
>thread-index: AcYgX/vgGz1j0C1/RduYsSVDkkJvAQ==>X-WBNR-Posting-Host: 204.87.106.66
>From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
>References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
>Subject: RE: Could not establish trust relationship with remote server.
>Date: Mon, 23 Jan 2006 13:00:04 -0800
>Lines: 18
>Message-ID: <A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67357
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>I also tried without the s in https, but I still get the same error
message.
>http://webserver/ReportServer
>"Mike L" wrote:
>> Error comes up when I try to deploy RS to my web server, "The underlying
>> connection was closed: Could not establish trust relationship with
remote
>> server." Web server has valid certificate, and I'm using https in my
>> connection.
>> OverwriteDataSources: True
>> TargetFolder: Reports
>> TargetServerURL: https://webserver/ReportServer
>> I'm able to see https://webserver/ReportServer through IE, and I see the
>> folder Reports. I clicked on Reports and I see my old RS files.
>|||1. I set "secureconnectionlevel" to zero, the URLRoot was already
"<UrlRoot>http://WEBSERVER/ReportServer</UrlRoot>", so I didn't change that.
2. RSReportServer.config in ReportManager, already had
"<ReportServerUrl>http://WEBSERVER/ReportServer</ReportServerUrl>"
When I tried to deploy in VS, I made sure the TargetServerURL was
"http://webserver/ReportServer", and the TargetFolder was "Reports".
I now get the error, "c:\intranet\Claims.rds The permissions granted to user
'WEBSERVER\IUSR_WEBSERVER' are insufficient for performing this operation."
"Peter Yang [MSFT]" wrote:
> Hello Cadel,
> You may try the following steps to disable SSL on report server to test:
> 1. Within the RSReportServer.config file you'll find in "\Program
> Files\Microsoft SQL Server\MSSQL.X\Reporting Services\ReportServer",
> set secureconnectionlevel to 0.
> Change
> <UrlRoot>https://webserver/ReportServer</UrlRoot>
> <UrlRoot>http://webserver/ReportServer</UrlRoot>
> 2. within C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager, change
> <ReportServerUrl>https://webserver/ReportServer</ReportServerUrl> to
> <ReportServerUrl>http://webserver/ReportServer</ReportServerUrl>
> Note: Please backup above files to safe place before you try to modify
> them. You may need to restart IIS if it is not take effect
> After that, you may want to configure deploy server to
> http://webserver/ReportServer in VS to test the situatioin.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> >Thread-Topic: Could not establish trust relationship with remote server.
> >thread-index: AcYgX/vgGz1j0C1/RduYsSVDkkJvAQ==> >X-WBNR-Posting-Host: 204.87.106.66
> >From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
> >References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
> >Subject: RE: Could not establish trust relationship with remote server.
> >Date: Mon, 23 Jan 2006 13:00:04 -0800
> >Lines: 18
> >Message-ID: <A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67357
> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >
> >I also tried without the s in https, but I still get the same error
> message.
> >
> >http://webserver/ReportServer
> >
> >"Mike L" wrote:
> >
> >> Error comes up when I try to deploy RS to my web server, "The underlying
> >> connection was closed: Could not establish trust relationship with
> remote
> >> server." Web server has valid certificate, and I'm using https in my
> >> connection.
> >>
> >> OverwriteDataSources: True
> >> TargetFolder: Reports
> >> TargetServerURL: https://webserver/ReportServer
> >>
> >> I'm able to see https://webserver/ReportServer through IE, and I see the
> >> folder Reports. I clicked on Reports and I see my old RS files.
> >>
> >
>|||Hello Cadel,
It seems your report server is configured to allow anonymous
authentication. Please check the following settings:
1. Run Inetmgr, right click Reportserver virtual
directory->Properties->Directory Security tab
2. Click Edit, and uncheck "Enable anonymouse access", make sure
"Integrated Windows authentication" is checked.
3. Restart IIS to test
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Could not establish trust relationship with remote server.
>thread-index: AcYhHcfqfQzv5KrkRySdCQqp8f5RKg==>X-WBNR-Posting-Host: 204.87.106.66
>From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
>References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
<A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.microsoft.com>
<Kuu46qKIGHA.1236@.TK2MSFTNGXA02.phx.gbl>
>Subject: RE: Could not establish trust relationship with remote server.
>Date: Tue, 24 Jan 2006 11:38:41 -0800
>Lines: 111
>Message-ID: <38F8AA05-20C3-4BDB-B64F-6629EB127703@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67414
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>1. I set "secureconnectionlevel" to zero, the URLRoot was already
>"<UrlRoot>http://WEBSERVER/ReportServer</UrlRoot>", so I didn't change
that.
>2. RSReportServer.config in ReportManager, already had
>"<ReportServerUrl>http://WEBSERVER/ReportServer</ReportServerUrl>"
>When I tried to deploy in VS, I made sure the TargetServerURL was
>"http://webserver/ReportServer", and the TargetFolder was "Reports".
>I now get the error, "c:\intranet\Claims.rds The permissions granted to
user
>'WEBSERVER\IUSR_WEBSERVER' are insufficient for performing this operation."
>
>
>
>"Peter Yang [MSFT]" wrote:
>> Hello Cadel,
>> You may try the following steps to disable SSL on report server to test:
>> 1. Within the RSReportServer.config file you'll find in "\Program
>> Files\Microsoft SQL Server\MSSQL.X\Reporting Services\ReportServer",
>> set secureconnectionlevel to 0.
>> Change
>> <UrlRoot>https://webserver/ReportServer</UrlRoot>
>> <UrlRoot>http://webserver/ReportServer</UrlRoot>
>> 2. within C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportManager, change
>> <ReportServerUrl>https://webserver/ReportServer</ReportServerUrl> to
>> <ReportServerUrl>http://webserver/ReportServer</ReportServerUrl>
>> Note: Please backup above files to safe place before you try to modify
>> them. You may need to restart IIS if it is not take effect
>> After that, you may want to configure deploy server to
>> http://webserver/ReportServer in VS to test the situatioin.
>> Best Regards,
>> Peter Yang
>> MCSE2000/2003, MCSA, MCDBA
>> Microsoft Online Partner Support
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================>>
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>> --
>> >Thread-Topic: Could not establish trust relationship with remote server.
>> >thread-index: AcYgX/vgGz1j0C1/RduYsSVDkkJvAQ==>> >X-WBNR-Posting-Host: 204.87.106.66
>> >From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
>> >References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
>> >Subject: RE: Could not establish trust relationship with remote server.
>> >Date: Mon, 23 Jan 2006 13:00:04 -0800
>> >Lines: 18
>> >Message-ID: <A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.microsoft.com>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.sqlserver.reportingsvcs:67357
>> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >
>> >I also tried without the s in https, but I still get the same error
>> message.
>> >
>> >http://webserver/ReportServer
>> >
>> >"Mike L" wrote:
>> >
>> >> Error comes up when I try to deploy RS to my web server, "The
underlying
>> >> connection was closed: Could not establish trust relationship with
>> remote
>> >> server." Web server has valid certificate, and I'm using https in my
>> >> connection.
>> >>
>> >> OverwriteDataSources: True
>> >> TargetFolder: Reports
>> >> TargetServerURL: https://webserver/ReportServer
>> >>
>> >> I'm able to see https://webserver/ReportServer through IE, and I see
the
>> >> folder Reports. I clicked on Reports and I see my old RS files.
>> >>
>> >
>>
>