Intermittent SQLSERVERAGENT error "unable to send job completion..

A batch job that executes once daily is configured to send job completion
notification on success or failure. Usually it works. Twice in the past
week it didn't, and this message is in the Application Log:
Event Type:Error
Event Source:SQLSERVERAGENT
Event Category:Job Engine
Event ID:210
Date:8/8/2005
Time:11:10:07 PM
User:N/A
Computer:xxxxxxx (name withheld to protect the guilty)
Description:Unable to send job completion notification email to operator
'DBA - SQLExec' for job 'Maintenance and backup'.
Both before and after the occurence of the problem, I am able to
successfully send mail with a 'test' of the operator 'DBA - SQLExec'.
Our environment is as follows:
SQL Server 2000 SP3a on Windows 2000 Server.
Outlook 2000 on the SQL Server box.
WAN; and the SQL box is geographically remote from the Exchange server.
MS Exchange email system (newly implemented).
Any ideas would be appreciated. Thanks in advance.
Hi,
Thanks for your post.
From your descriptions, I understood your SQLAgent intermittently failed to
report the error message that unable to send job completion notification
email to operator 'DBA - SQLExec' for job. If I have misunderstood your
concern, please feel free to point it out.
I have noticed that this issue will not happen all the time and and based
on my knowledge it is most possible that the Exchange server is unavailable
at that time of name resolution the above error will occur. Check logs of
exchange server to go further for this loss of connectivity between the
MAPI client and Exchange server
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
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.

Intermittent SQLSERVERAGENT error "unable to send job completion..

A batch job that executes once daily is configured to send job completion
notification on success or failure. Usually it works. Twice in the past
week it didn't, and this message is in the Application Log:
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 210
Date: 8/8/2005
Time: 11:10:07 PM
User: N/A
Computer: xxxxxxx (name withheld to protect the guilty)
Description:Unable to send job completion notification email to operator
'DBA - SQLExec' for job 'Maintenance and backup'.
Both before and after the occurence of the problem, I am able to
successfully send mail with a 'test' of the operator 'DBA - SQLExec'.
Our environment is as follows:
SQL Server 2000 SP3a on Windows 2000 Server.
Outlook 2000 on the SQL Server box.
WAN; and the SQL box is geographically remote from the Exchange server.
MS Exchange email system (newly implemented).
Any ideas would be appreciated. Thanks in advance.Hi,
Thanks for your post.
From your descriptions, I understood your SQLAgent intermittently failed to
report the error message that unable to send job completion notification
email to operator 'DBA - SQLExec' for job. If I have misunderstood your
concern, please feel free to point it out.
I have noticed that this issue will not happen all the time and and based
on my knowledge it is most possible that the Exchange server is unavailable
at that time of name resolution the above error will occur. Check logs of
exchange server to go further for this loss of connectivity between the
MAPI client and Exchange server
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
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.

Intermittent SQLSERVERAGENT error "unable to send job completion..

A batch job that executes once daily is configured to send job completion
notification on success or failure. Usually it works. Twice in the past
week it didn't, and this message is in the Application Log:
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 210
Date: 8/8/2005
Time: 11:10:07 PM
User: N/A
Computer: xxxxxxx (name withheld to protect the guilty)
Description:Unable to send job completion notification email to operator
'DBA - SQLExec' for job 'Maintenance and backup'.
Both before and after the occurence of the problem, I am able to
successfully send mail with a 'test' of the operator 'DBA - SQLExec'.
Our environment is as follows:
SQL Server 2000 SP3a on Windows 2000 Server.
Outlook 2000 on the SQL Server box.
WAN; and the SQL box is geographically remote from the Exchange server.
MS Exchange email system (newly implemented).
Any ideas would be appreciated. Thanks in advance.Hi,
Thanks for your post.
From your descriptions, I understood your SQLAgent intermittently failed to
report the error message that unable to send job completion notification
email to operator 'DBA - SQLExec' for job. If I have misunderstood your
concern, please feel free to point it out.
I have noticed that this issue will not happen all the time and and based
on my knowledge it is most possible that the Exchange server is unavailable
at that time of name resolution the above error will occur. Check logs of
exchange server to go further for this loss of connectivity between the
MAPI client and Exchange server
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
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.

Intermittent Login failure at boot

I have a Windows Service middleware application that depends on SQL
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
Thanks
Go through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:

>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thanks

Intermittent Login failure at boot

I have a Windows Service middleware application that depends on SQL
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
ThanksGo through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:

>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thankssql

Intermittent email issue

We are having a problem with a report that is scheduled to be emailed
only works sometimes. Other time it fails with a "Reporting Services
Failure sending mail: Cannot access a closed file" error message.
The report is running off a snapshot that is generated every half hour
and a subscription is setup to email the report to some users. The
snapshot is generated even when the email fails.
It seems the problem is pointed to by userName: [DOMAIN\username]not
found in the database. This seems to be a security problem - but why
would it work sometimes? The log file is below for reference. The user
in question is in the same domain as the report service is running
under.
Environment:
Report service SP2 running on a Windows 2003 EE with SQL Server 2000
Active Director Domain server running on Windows 2003 EE
The report server service is running under a domain account that is in
the local administrator group on the local server.
Has anyone seen this problem?
Thanks
ReportingServicesService!library!2b4!09/02/2005-09:09:38:: i INFO:
Initializing EnableExecutionLogging to 'True' as specified in Server
system properties.
ReportingServicesService!session!2b4!09/02/2005-09:09:38:: i INFO:
LoadSnapshot: Item with session: tc2ixx55bnczhjifyjr2z42q, reportPath:
/Company Reports/MyReport, userName: [DOMAIN\username]not found in the
database
ReportingServicesService!chunks!2b4!09/02/2005-09:09:38:: i INFO: ###
GetReportChunk('MyReport_style', 1), chunk was not found!
this=38c10bb1-1bae-4d41-a03e-f56437fc3c86
ReportingServicesService!emailextension!2b4!09/02/2005-09:09:38:: Error
sending email. System.ObjectDisposedException: Cannot access a closed
file.
at System.IO.__Error.FileNotOpen()
at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32
count)
at
Microsoft.ReportingServices.Library.PartitionFileStream.Read(Byte[]
buffer, Int32 offset, Int32 count)
at
Microsoft.ReportingServices.Library.MemoryUntilThresholdStream.Read(Byte[]
buffer, Int32 offset, Int32 count)
at Microsoft.ReportingServices.Library.RSStream.Read(Byte[] buffer,
Int32 offset, Int32 count)
at
Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.EmbedReport(IMessage
message, RenderedOutputFile[] reportData, Notification notification,
SubscriptionData data)
at
Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.ConstructMessageBody(IMessage
message, Notification notification, SubscriptionData data)
at
Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.CreateMessage(Notification
notification)
at
Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.Deliver(Notification
notification)
ReportingServicesService!notification!2b4!09/02/2005-09:09:38::
Notification 2180101f-6faa-41b7-b1a0-b3217c5d630e completed. Success:
False, Status: Failure sending mail: Cannot access a closed file.,
DeliveryExtension: Report Server Email, Report: MyReport, Attempt 0
ReportingServicesService!dbpolling!2b4!09/02/2005-09:09:38::
NotificationPolling finished processing item
2180101f-6faa-41b7-b1a0-b3217c5d630ejmbackup1024@.gmail.com wrote:
> We are having a problem with a report that is scheduled to be emailed
> only works sometimes. Other time it fails with a "Reporting Services
> Failure sending mail: Cannot access a closed file" error message.
> The report is running off a snapshot that is generated every half hour
> and a subscription is setup to email the report to some users. The
> snapshot is generated even when the email fails.
> It seems the problem is pointed to by userName: [DOMAIN\username]not
> found in the database. This seems to be a security problem - but why
> would it work sometimes? The log file is below for reference. The user
> in question is in the same domain as the report service is running
> under.
> Environment:
> Report service SP2 running on a Windows 2003 EE with SQL Server 2000
> Active Director Domain server running on Windows 2003 EE
> The report server service is running under a domain account that is in
> the local administrator group on the local server.
> Has anyone seen this problem?
> Thanks
> ReportingServicesService!library!2b4!09/02/2005-09:09:38:: i INFO:
> Initializing EnableExecutionLogging to 'True' as specified in Server
> system properties.
> ReportingServicesService!session!2b4!09/02/2005-09:09:38:: i INFO:
> LoadSnapshot: Item with session: tc2ixx55bnczhjifyjr2z42q, reportPath:
> /Company Reports/MyReport, userName: [DOMAIN\username]not found in the
> database
> ReportingServicesService!chunks!2b4!09/02/2005-09:09:38:: i INFO: ###
> GetReportChunk('MyReport_style', 1), chunk was not found!
> this=38c10bb1-1bae-4d41-a03e-f56437fc3c86
> ReportingServicesService!emailextension!2b4!09/02/2005-09:09:38:: Error
> sending email. System.ObjectDisposedException: Cannot access a closed
> file.
> at System.IO.__Error.FileNotOpen()
> at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32
> count)
> at
> Microsoft.ReportingServices.Library.PartitionFileStream.Read(Byte[]
> buffer, Int32 offset, Int32 count)
> at
> Microsoft.ReportingServices.Library.MemoryUntilThresholdStream.Read(Byte[]
> buffer, Int32 offset, Int32 count)
> at Microsoft.ReportingServices.Library.RSStream.Read(Byte[] buffer,
> Int32 offset, Int32 count)
> at
> Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.EmbedReport(IMessage
> message, RenderedOutputFile[] reportData, Notification notification,
> SubscriptionData data)
> at
> Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.ConstructMessageBody(IMessage
> message, Notification notification, SubscriptionData data)
> at
> Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.CreateMessage(Notification
> notification)
> at
> Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.Deliver(Notification
> notification)
> ReportingServicesService!notification!2b4!09/02/2005-09:09:38::
> Notification 2180101f-6faa-41b7-b1a0-b3217c5d630e completed. Success:
> False, Status: Failure sending mail: Cannot access a closed file.,
> DeliveryExtension: Report Server Email, Report: MyReport, Attempt 0
> ReportingServicesService!dbpolling!2b4!09/02/2005-09:09:38::
> NotificationPolling finished processing item
> 2180101f-6faa-41b7-b1a0-b3217c5d630e
Experiencing a very similar issue, running SP1. I created a
parameterized report, from which 93 link reports point to. Those 93
linked reports are set to run nightly at 2:00 am by generating a
snapshot (for historical purposes). All 93 snapshots were created
within about 3 mintutes of 2:00 am. The subscription is suposed to
fire an email whenever it is updated, but only half or so are
successful. On those that are unsuccessful, I get no error message at
all.
It seems timed subscriptions work just fine. Perhaps what I will do is
send the email based only on a timed subscription and also create a
snapshot for historical purposes...I would much rather not have to do
double the processor work, as many more reports are needed for
conversion.

intermitent connection failure

We have written a thread to monitor whether the database connection is still
alive or not.
This monitoring thread executes a stored procedure, sp_TestDB, with ADO
_CommandPtr every 3 seconds.
Most of the time we have no problems executing it. However, we receive the
following error randomly:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
(WrapperWrite()). Msg:Unspecified error
We are convinced that the machine where the database server is installed is
definitely alive as we ping it all the time and there is no request time out
.
We want to know what other problems could cause this error to happen randoml
y?
The development language we use is Visual C++.
The database server we use is :
Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
ScottHi Scott,
Since this is an unspecified error on the client side, In this case, please
try to use SQL profiler to start a trace to see what is actually happening
on the server. The trace log might show more information on this error.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."|||Excuse me, but I have the same problem, could you tell me how can I fix ?
I will appreciate it.
Thanks
Bruno Martinez
MCDBA
BMartinez@.cosapisoft.com.pe
"scottrm" <scottrm@.newsgroup.nospam> escribi en el mensaje
news:AD41E055-5B53-4015-B73E-88086A949CE4@.microsoft.com...
> We have written a thread to monitor whether the database connection is
> still
> alive or not.
> This monitoring thread executes a stored procedure, sp_TestDB, with ADO
> _CommandPtr every 3 seconds.
> Most of the time we have no problems executing it. However, we receive the
> following error randomly:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
> (WrapperWrite()). Msg:Unspecified error
> We are convinced that the machine where the database server is installed
> is
> definitely alive as we ping it all the time and there is no request time
> out.
> We want to know what other problems could cause this error to happen
> randomly?
> The development language we use is Visual C++.
> The database server we use is :
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>
>
> --
> Scott

intermitent connection failure

We have written a thread to monitor whether the database connection is still
alive or not.
This monitoring thread executes a stored procedure, sp_TestDB, with ADO
_CommandPtr every 3 seconds.
Most of the time we have no problems executing it. However, we receive the
following error randomly:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
(WrapperWrite()). Msg:Unspecified error
We are convinced that the machine where the database server is installed is
definitely alive as we ping it all the time and there is no request time out.
We want to know what other problems could cause this error to happen randomly?
The development language we use is Visual C++.
The database server we use is :
Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Scott
Hi Scott,
Since this is an unspecified error on the client side, In this case, please
try to use SQL profiler to start a trace to see what is actually happening
on the server. The trace log might show more information on this error.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
|||Excuse me, but I have the same problem, could you tell me how can I fix ?
I will appreciate it.
Thanks
Bruno Martinez
MCDBA
BMartinez@.cosapisoft.com.pe
"scottrm" <scottrm@.newsgroup.nospam> escribi en el mensaje
news:AD41E055-5B53-4015-B73E-88086A949CE4@.microsoft.com...
> We have written a thread to monitor whether the database connection is
> still
> alive or not.
> This monitoring thread executes a stored procedure, sp_TestDB, with ADO
> _CommandPtr every 3 seconds.
> Most of the time we have no problems executing it. However, we receive the
> following error randomly:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
> (WrapperWrite()). Msg:Unspecified error
> We are convinced that the machine where the database server is installed
> is
> definitely alive as we ping it all the time and there is no request time
> out.
> We want to know what other problems could cause this error to happen
> randomly?
> The development language we use is Visual C++.
> The database server we use is :
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>
>
> --
> Scott
sql

Integrity Check Job Failure

Hi,
Psoted this is in Reporting Services, but no response:
I have the AdventureWorks2000 database (part of reporting services)
installed on a couple of servers. I have created a maintenance plan to run
the integrity check on all user servers. The job ran fine until the
AdventureWorks2000 db was installed. The jobs fails only on this db and work
s
just fine on other db's . Here is the
output from the maintenance plan:
Starting maintenance plan 'Master Server - All DB Integrity Check Job' on
4/10/2005 9:30:01 PM
[1] Database AdventureWorks2000: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options
have
incorrect settings: 'QUOTED_IDENTIFIER'.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed becau
se the
following SET options have incorrect settings: 'QUOTED_IDENTIFIER'.
I tried setting different options, but nothing appears to solve the problem.
Any suggestions/ideas?
TIA,
DeeJay PuarLook here, your problem is described there:
http://support.microsoft.com/kb/q301292/
HTH, Jens Smeyer.
http://www.sqlserver2005.de
--
"DeeJay Puar" <DeeJayPuar@.discussions.microsoft.com> schrieb im Newsbeitrag
news:197CD201-850D-447C-A461-C01EBD987657@.microsoft.com...
> Hi,
> Psoted this is in Reporting Services, but no response:
> I have the AdventureWorks2000 database (part of reporting services)
> installed on a couple of servers. I have created a maintenance plan to run
> the integrity check on all user servers. The job ran fine until the
> AdventureWorks2000 db was installed. The jobs fails only on this db and
> works
> just fine on other db's . Here is the
> output from the maintenance plan:
> Starting maintenance plan 'Master Server - All DB Integrity Check Job' on
> 4/10/2005 9:30:01 PM
> [1] Database AdventureWorks2000: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
[ODBC
> SQL
> Server Driver][SQL Server]DBCC failed because the following SET option
s
> have
> incorrect settings: 'QUOTED_IDENTIFIER'.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed bec
ause the
> following SET options have incorrect settings: 'QUOTED_IDENTIFIER'.
> I tried setting different options, but nothing appears to solve the
> problem.
> Any suggestions/ideas?
> TIA,
> DeeJay Puar
>|||Hit the Nail on the Head...Thanks Jen.
I was only looking the Reporting Services Documentation.
DeeJay Puar
"Jens Sü?meyer" wrote:

> Look here, your problem is described there:
> http://support.microsoft.com/kb/q301292/
> HTH, Jens Sü?meyer.
> --
> http://www.sqlserver2005.de
> --
> "DeeJay Puar" <DeeJayPuar@.discussions.microsoft.com> schrieb im Newsbeitra
g
> news:197CD201-850D-447C-A461-C01EBD987657@.microsoft.com...
>
>

Integrity Check Job Failure

Hi,
Psoted this is in Reporting Services, but no response:
I have the AdventureWorks2000 database (part of reporting services)
installed on a couple of servers. I have created a maintenance plan to run
the integrity check on all user servers. The job ran fine until the
AdventureWorks2000 db was installed. The jobs fails only on this db and works
just fine on other db's . Here is the
output from the maintenance plan:
Starting maintenance plan 'Master Server - All DB Integrity Check Job' on
4/10/2005 9:30:01 PM
[1] Database AdventureWorks2000: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options have
incorrect settings: 'QUOTED_IDENTIFIER'.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed because the
following SET options have incorrect settings: 'QUOTED_IDENTIFIER'.
I tried setting different options, but nothing appears to solve the problem.
Any suggestions/ideas?
TIA,
DeeJay Puar
Look here, your problem is described there:
http://support.microsoft.com/kb/q301292/
HTH, Jens Smeyer.
http://www.sqlserver2005.de
"DeeJay Puar" <DeeJayPuar@.discussions.microsoft.com> schrieb im Newsbeitrag
news:197CD201-850D-447C-A461-C01EBD987657@.microsoft.com...
> Hi,
> Psoted this is in Reporting Services, but no response:
> I have the AdventureWorks2000 database (part of reporting services)
> installed on a couple of servers. I have created a maintenance plan to run
> the integrity check on all user servers. The job ran fine until the
> AdventureWorks2000 db was installed. The jobs fails only on this db and
> works
> just fine on other db's . Here is the
> output from the maintenance plan:
> Starting maintenance plan 'Master Server - All DB Integrity Check Job' on
> 4/10/2005 9:30:01 PM
> [1] Database AdventureWorks2000: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server]DBCC failed because the following SET options
> have
> incorrect settings: 'QUOTED_IDENTIFIER'.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed because the
> following SET options have incorrect settings: 'QUOTED_IDENTIFIER'.
> I tried setting different options, but nothing appears to solve the
> problem.
> Any suggestions/ideas?
> TIA,
> DeeJay Puar
>
|||Hit the Nail on the Head...Thanks Jen.
I was only looking the Reporting Services Documentation.
DeeJay Puar
"Jens Sü?meyer" wrote:

> Look here, your problem is described there:
> http://support.microsoft.com/kb/q301292/
> HTH, Jens Sü?meyer.
> --
> http://www.sqlserver2005.de
> --
> "DeeJay Puar" <DeeJayPuar@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:197CD201-850D-447C-A461-C01EBD987657@.microsoft.com...
>
>

Integrity Check Failure

DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
Log backup and Optimizations are successful. I can’t determine if it’s
failing to run or if it’s running
and finding a problem. The logs are not indicating any reasons for failure.
Integrity check is successful on other DB’s. Thanks for being there to help.
1. Define a report file for the plan and check that report file for error messages.
2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
3. http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
> DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
> Log backup and Optimizations are successful. I can’t determine if it’s
> failing to run or if it’s running
> and finding a problem. The logs are not indicating any reasons for failure.
> Integrity check is successful on other DB’s. Thanks for being there to help.
>
|||Thanks Tibor. Can you direct me to a location that indicates the procedure for
defining a report?
"Tibor Karaszi" wrote:

> 1. Define a report file for the plan and check that report file for error messages.
> 2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
> 3. http://www.karaszi.com/SQLServer/inf...suspect_db.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
>
|||EM, Management, Maintenance Plans, right-click your plan to open it. The right-most ( think) tab has
this option. You can also right-click an existing plan and open (something like) history and try to
find the error messages there. I don't use maint plans, so it is a little bit sketchy...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...[vbcol=seagreen]
> Thanks Tibor. Can you direct me to a location that indicates the procedure for
> defining a report?
> "Tibor Karaszi" wrote:
|||Thanks for your help
"Tibor Karaszi" wrote:

> EM, Management, Maintenance Plans, right-click your plan to open it. The right-most ( think) tab has
> this option. You can also right-click an existing plan and open (something like) history and try to
> find the error messages there. I don't use maint plans, so it is a little bit sketchy...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...
>

Integrity Check Failure

DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
Log backup and Optimizations are successful. I can’t determine if it’s
failing to run or if it’s running
and finding a problem. The logs are not indicating any reasons for failure.
Integrity check is successful on other DB’s. Thanks for being there to hel
p.1. Define a report file for the plan and check that report file for error me
ssages.
2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
3. http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
> DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
> Log backup and Optimizations are successful. I can’t determine if it’s
> failing to run or if it’s running
> and finding a problem. The logs are not indicating any reasons for failure
.
> Integrity check is successful on other DB’s. Thanks for being there to h
elp.
>|||Thanks Tibor. Can you direct me to a location that indicates the procedure f
or
defining a report?
"Tibor Karaszi" wrote:

> 1. Define a report file for the plan and check that report file for error
messages.
> 2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
> 3. http://www.karaszi.com/SQLServer/in..._suspect_db.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
>|||EM, Management, Maintenance Plans, right-click your plan to open it. The rig
ht-most ( think) tab has
this option. You can also right-click an existing plan and open (something l
ike) history and try to
find the error messages there. I don't use maint plans, so it is a little bi
t sketchy...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...[vbcol=seagreen]
> Thanks Tibor. Can you direct me to a location that indicates the procedure
for
> defining a report?
> "Tibor Karaszi" wrote:
>|||Thanks for your help
"Tibor Karaszi" wrote:

> EM, Management, Maintenance Plans, right-click your plan to open it. The r
ight-most ( think) tab has
> this option. You can also right-click an existing plan and open (something
like) history and try to
> find the error messages there. I don't use maint plans, so it is a little
bit sketchy...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...
>

Integrity Check Failure

DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
Log backup and Optimizations are successful. I canâ't determine if itâ's
failing to run or if itâ's running
and finding a problem. The logs are not indicating any reasons for failure.
Integrity check is successful on other DBâ's. Thanks for being there to help.1. Define a report file for the plan and check that report file for error messages.
2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
3. http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
> DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
> Log backup and Optimizations are successful. I canâ't determine if itâ's
> failing to run or if itâ's running
> and finding a problem. The logs are not indicating any reasons for failure.
> Integrity check is successful on other DBâ's. Thanks for being there to help.
>|||Thanks Tibor. Can you direct me to a location that indicates the procedure for
defining a report?
"Tibor Karaszi" wrote:
> 1. Define a report file for the plan and check that report file for error messages.
> 2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
> 3. http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
> > DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
> > Log backup and Optimizations are successful. I canâ't determine if itâ's
> > failing to run or if itâ's running
> > and finding a problem. The logs are not indicating any reasons for failure.
> > Integrity check is successful on other DBâ's. Thanks for being there to help.
> >
>|||EM, Management, Maintenance Plans, right-click your plan to open it. The right-most ( think) tab has
this option. You can also right-click an existing plan and open (something like) history and try to
find the error messages there. I don't use maint plans, so it is a little bit sketchy...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...
> Thanks Tibor. Can you direct me to a location that indicates the procedure for
> defining a report?
> "Tibor Karaszi" wrote:
>> 1. Define a report file for the plan and check that report file for error messages.
>> 2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
>> 3. http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
>> news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
>> > DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
>> > Log backup and Optimizations are successful. I canâ't determine if itâ's
>> > failing to run or if itâ's running
>> > and finding a problem. The logs are not indicating any reasons for failure.
>> > Integrity check is successful on other DBâ's. Thanks for being there to help.
>> >
>>|||Thanks for your help
"Tibor Karaszi" wrote:
> EM, Management, Maintenance Plans, right-click your plan to open it. The right-most ( think) tab has
> this option. You can also right-click an existing plan and open (something like) history and try to
> find the error messages there. I don't use maint plans, so it is a little bit sketchy...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...
> > Thanks Tibor. Can you direct me to a location that indicates the procedure for
> > defining a report?
> >
> > "Tibor Karaszi" wrote:
> >
> >> 1. Define a report file for the plan and check that report file for error messages.
> >>
> >> 2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
> >>
> >> 3. http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> >> news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
> >> > DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
> >> > Log backup and Optimizations are successful. I canâ't determine if itâ's
> >> > failing to run or if itâ's running
> >> > and finding a problem. The logs are not indicating any reasons for failure.
> >> > Integrity check is successful on other DBâ's. Thanks for being there to help.
> >> >
> >>
> >>
>