Quickie: SMTP config for attachments

I can configure a working subscription to e-mail through my SMTP server when
sending only the LINK to a report but not if I attach the report to the
e-mail in say excel or xml format.
Any suggestions?
Thanks
TravisSomeone must have an idea... please! :-)
I have tested using a command line SMTP utility and have been able to send
both a plain text message and a plain text message wth and attachment so I
know the Mail server will accept it.
Someone, Anyone?
Thanks
Travis
"REM7600" <rem7600@.hotmail.com> wrote in message
news:eumyP3OdEHA.1692@.tk2msftngp13.phx.gbl...
> I can configure a working subscription to e-mail through my SMTP server
when
> sending only the LINK to a report but not if I attach the report to the
> e-mail in say excel or xml format.
> Any suggestions?
> Thanks
> Travis
>|||Here's the error from the log... I can't make much of it... Other than the
part that says please see the log files...
ReportingServicesService!emailextension!728!07/29/2004-07:32:05:: Error
sending email.
Microsoft.ReportingServices.Diagnostics.Utilities.RSException: The Report
Server has encountered a configuration error; more details in the log
files -->
Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorEx
ception: The Report Server has encountered a configuration error; more
details in the log files
at
Microsoft.ReportingServices.Authorization.Native.GetAuthzContextForUser(IntP
tr userSid)
at Microsoft.ReportingServices.Authorization.Native.IsAdmin(String
userName)
at
Microsoft.ReportingServices.Authorization.WindowsAuthorization.IsAdmin(Strin
g userName, IntPtr userToken)
at
Microsoft.ReportingServices.Authorization.WindowsAuthorization.CheckAccess(S
tring userName, IntPtr userToken, Byte[] secDesc, ReportOperation
requiredOperation)
at Microsoft.ReportingServices.Library.Security.CheckAccess(ItemType
catItemType, Byte[] secDesc, ReportOperation rptOper)
at
Microsoft.ReportingServices.Library.RSService._GetReportParameterDefinitionF
romCatalog(CatalogItemContext reportContext, String historyID, Boolean
forRendering, Guid& reportID, Int32& executionOption, String&
savedParametersXml, ReportSnapshot& compiledDefinition, ReportSnapshot&
snapshotData, Guid& linkID, DateTime& historyDate)
at
Microsoft.ReportingServices.Library.RSService._GetReportParameters(String
report, String historyID, Boolean forRendering, NameValueCollection values,
DatasourceCredentialsCollection credentials)
at
Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(Catalog
ItemContext reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effectiveParameters)
at
Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext
reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effectiveParameters, String[]&
secondaryStreamNames)
at
Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute()
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
at
Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RS
Service rs, CatalogItemContext reportContext, ClientRequest session,
JobTypeEnum type, Warning[]& warnings, ParameterInfoCollection&
effectiveParameters, String[]& secondaryStreamNames)
at Microsoft.ReportingServices.Library.ReportImpl.Render(String
renderFormat, String deviceInfo)
at
Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.ConstructMes
sageBody(IMessage message, Notification notification, SubscriptionData data)
at
Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.CreateMessag
e(Notification notification)
at
Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.Deliver(Noti
fication notification)

Queue Reader - remote procedure call failed

I am running transactional repl with an updateable subscription between two servers running SQL Server 2000 SP3, all agents running on the publisher. Every now and then, the Queue reader fails. I enable logging and attempt restart. The output file looks n
ormal to me; several queries for queued data, but then it seems to timeout. It just sits there for 3 minutes, then fails and retries. I can successfully query the other server, so I know it's not a communications problem. The event viewer simply says "the
remote procedure call failed and did not execute". I can't find any other error messages.
Does anyone have any advice? Thank you.
Microsoft SQL Server Replication Queue Reader Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: [MIALDCS-1].9
Trying to Connect to Local Distributor
Connecting to QueueReader 'MIALDCS-1.distribution'
Server: MIALDCS-1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (distribution)'
[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select top 1 id, name from MSqreader_agents
[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select SERVERPROPERTY('IsClustered')
Queue Reader Agent [MIALDCS-1].9 (Id = 3) started
Repl Agent Status: 1
[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: execute dbo.sp_MShelp_profile 3, 9, N''
Opening SQL based queues
[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: exec master.dbo.sp_MSenum_replsqlqueues N'distribution'
Worker Thread 608 : Starting
The Message Queuing service does not exist[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: exec dbo.sp_MShelp_subscriber_info N'MIALDCS-1', N'MIALDCS-2'
The Message Queuing service is not available
Connecting to MIALDCS-2 'MIALDCS-2.Island'
Server: MIALDCS-2
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
MIALDCS-2.Island: {? = call dbo.sp_getsqlqueueversion (?, ?, ?, ?)}
MIALDCS-2.Island: {? = call dbo.sp_replsqlqgetrows (N'MIALDCS-1', N'Island', N'Island')}
[7/30/2004 12:17:31 PM]MIALDCS-1.distribution: exec dbo.sp_helpdistpublisher @.publisher = N'MIALDCS-1'
Connecting to MIALDCS-1 'MIALDCS-1.Island'
Worker Thread 608 : processing Transaction [2LhOShgh_agC2<T]?LH.h-5--09M--] of [SQL Queue]
Worker Thread 608 : Started Queue Transaction
Worker Thread 608 : Started SQL Tran
MIALDCS-1.Island: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Island', 44)}
SQL Command : <exec [dbo].[sp_MSsync_del_Leg_Seat_Map_1] N'MIALDCS-2', N'Island', 'F2', '101', '2004-07-24 00:00:00.000', '1', 0, 0, ' ', ' ', 0, 12632256, ' ', 'Y', ' ', 'N', 'N', '', '', '', '', '', '', '', '', ' ', ' ', ' ', 'E8613112-29DC-4563-B3F0-58
665C4967B9', 1>
(hundreds more records follow)
what command is it failing on?
The problem is probably related to the execution of a single proc, which is
locking on the publisher.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"LeeH" <LeeH@.discussions.microsoft.com> wrote in message
news:055E41A9-DA76-403B-8D93-3F4C32BA6DDE@.microsoft.com...
> I am running transactional repl with an updateable subscription between
two servers running SQL Server 2000 SP3, all agents running on the
publisher. Every now and then, the Queue reader fails. I enable logging and
attempt restart. The output file looks normal to me; several queries for
queued data, but then it seems to timeout. It just sits there for 3 minutes,
then fails and retries. I can successfully query the other server, so I know
it's not a communications problem. The event viewer simply says "the remote
procedure call failed and did not execute". I can't find any other error
messages.
> Does anyone have any advice? Thank you.
> Microsoft SQL Server Replication Queue Reader Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: [MIALDCS-1].9
> Trying to Connect to Local Distributor
> Connecting to QueueReader 'MIALDCS-1.distribution'
> Server: MIALDCS-1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select count(*) from
master.dbo.sysprocesses where [program_name] = 'Queue Reader Main
(distribution)'
> [7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select top 1 id, name from
MSqreader_agents
> [7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select
SERVERPROPERTY('IsClustered')
> Queue Reader Agent [MIALDCS-1].9 (Id = 3) started
> Repl Agent Status: 1
> [7/30/2004 12:17:19 PM]MIALDCS-1.distribution: execute
dbo.sp_MShelp_profile 3, 9, N''
> Opening SQL based queues
> [7/30/2004 12:17:19 PM]MIALDCS-1.distribution: exec
master.dbo.sp_MSenum_replsqlqueues N'distribution'
> Worker Thread 608 : Starting
> The Message Queuing service does not exist[7/30/2004 12:17:19
PM]MIALDCS-1.distribution: exec dbo.sp_MShelp_subscriber_info N'MIALDCS-1',
N'MIALDCS-2'
> The Message Queuing service is not available
> Connecting to MIALDCS-2 'MIALDCS-2.Island'
> Server: MIALDCS-2
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> MIALDCS-2.Island: {? = call dbo.sp_getsqlqueueversion (?, ?, ?, ?)}
> MIALDCS-2.Island: {? = call dbo.sp_replsqlqgetrows (N'MIALDCS-1',
N'Island', N'Island')}
> [7/30/2004 12:17:31 PM]MIALDCS-1.distribution: exec
dbo.sp_helpdistpublisher @.publisher = N'MIALDCS-1'
> Connecting to MIALDCS-1 'MIALDCS-1.Island'
> Worker Thread 608 : processing Transaction
[2LhOShgh_agC2<T]?LH.h-5--09M--] of [SQL Queue]
> Worker Thread 608 : Started Queue Transaction
> Worker Thread 608 : Started SQL Tran
> MIALDCS-1.Island: {? = call dbo.sp_getqueuedarticlesynctraninfo
(N'Island', 44)}
> SQL Command : <exec [dbo].[sp_MSsync_del_Leg_Seat_Map_1] N'MIALDCS-2',
N'Island', 'F2', '101', '2004-07-24 00:00:00.000', '1', 0, 0, ' ', ' ', 0,
12632256, ' ', 'Y', ' ', 'N', 'N', '', '', '', '', '', '', '', '', ' ', ' ',
' ', 'E8613112-29DC-4563-B3F0-58665C4967B9', 1>
> (hundreds more records follow)
>
|||I don't see anything in the log that indicates failure. It seems that the
agent just restarts. The event viewer simply says "the remote procedure call
failed and did not execute".
"Hilary Cotter" wrote:

> what command is it failing on?
> The problem is probably related to the execution of a single proc, which is
> locking on the publisher.
>
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "LeeH" <LeeH@.discussions.microsoft.com> wrote in message
> news:055E41A9-DA76-403B-8D93-3F4C32BA6DDE@.microsoft.com...
> two servers running SQL Server 2000 SP3, all agents running on the
> publisher. Every now and then, the Queue reader fails. I enable logging and
> attempt restart. The output file looks normal to me; several queries for
> queued data, but then it seems to timeout. It just sits there for 3 minutes,
> then fails and retries. I can successfully query the other server, so I know
> it's not a communications problem. The event viewer simply says "the remote
> procedure call failed and did not execute". I can't find any other error
> messages.
> master.dbo.sysprocesses where [program_name] = 'Queue Reader Main
> (distribution)'
> MSqreader_agents
> SERVERPROPERTY('IsClustered')
> dbo.sp_MShelp_profile 3, 9, N''
> master.dbo.sp_MSenum_replsqlqueues N'distribution'
> PM]MIALDCS-1.distribution: exec dbo.sp_MShelp_subscriber_info N'MIALDCS-1',
> N'MIALDCS-2'
> N'Island', N'Island')}
> dbo.sp_helpdistpublisher @.publisher = N'MIALDCS-1'
> [2LhOShgh_agC2<T]?LH.h-5--09M--] of [SQL Queue]
> (N'Island', 44)}
> N'Island', 'F2', '101', '2004-07-24 00:00:00.000', '1', 0, 0, ' ', ' ', 0,
> 12632256, ' ', 'Y', ' ', 'N', 'N', '', '', '', '', '', '', '', '', ' ', ' ',
> ' ', 'E8613112-29DC-4563-B3F0-58665C4967B9', 1>
>
>