Integrated Security: failed

Showing posts with label failed. Show all posts

Monday, March 26, 2012

intermittent connection problems

We are having an intermittent connection problems with some DTS
packages. We get the following error about 1 out of every 15 days
Login failed for user '(null)'. Reason: Not associated
One DTS package connects to remote SQL servers with a linked server,
another package uses a OLE DB provide connection to connect to a remote
server.
Configuration:
Client network configuration TCP/IP NamePipes
Server network configuration TCP/IP NamePipes
SQLServer 2000 service pack 3
Windows 2000 Server.
Authentication is set for both SQL Server and Windows
Has anyone seen this type of problem or have any troubleshooting advice
thanksHi
If SQL Server can not authenticate the user against the Domain Controller,
it has no option but to deny the connection. So you will see this message.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<scott.yoder@.ngc.com> wrote in message
news:1112822349.200542.189700@.g14g2000cwa.googlegroups.com...
> We are having an intermittent connection problems with some DTS
> packages. We get the following error about 1 out of every 15 days
> Login failed for user '(null)'. Reason: Not associated
> One DTS package connects to remote SQL servers with a linked server,
> another package uses a OLE DB provide connection to connect to a remote
> server.
> Configuration:
> Client network configuration TCP/IP NamePipes
> Server network configuration TCP/IP NamePipes
> SQLServer 2000 service pack 3
> Windows 2000 Server.
> Authentication is set for both SQL Server and Windows
>
> Has anyone seen this type of problem or have any troubleshooting advice
> thanks
>

intermittent connection problems

We are having an intermittent connection problems with some DTS
packages. We get the following error about 1 out of every 15 days
Login failed for user '(null)'. Reason: Not associated
One DTS package connects to remote SQL servers with a linked server,
another package uses a OLE DB provide connection to connect to a remote
server.
Configuration:
Client network configuration TCP/IP NamePipes
Server network configuration TCP/IP NamePipes
SQLServer 2000 service pack 3
Windows 2000 Server.
Authentication is set for both SQL Server and Windows
Has anyone seen this type of problem or have any troubleshooting advice
thanks
Hi
If SQL Server can not authenticate the user against the Domain Controller,
it has no option but to deny the connection. So you will see this message.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<scott.yoder@.ngc.com> wrote in message
news:1112822349.200542.189700@.g14g2000cwa.googlegr oups.com...
> We are having an intermittent connection problems with some DTS
> packages. We get the following error about 1 out of every 15 days
> Login failed for user '(null)'. Reason: Not associated
> One DTS package connects to remote SQL servers with a linked server,
> another package uses a OLE DB provide connection to connect to a remote
> server.
> Configuration:
> Client network configuration TCP/IP NamePipes
> Server network configuration TCP/IP NamePipes
> SQLServer 2000 service pack 3
> Windows 2000 Server.
> Authentication is set for both SQL Server and Windows
>
> Has anyone seen this type of problem or have any troubleshooting advice
> thanks
>
sql

Intermittent 401: Not Authorized

The first time I try to access a RS report after an IISreset, I get a
"System.Net.WebException: The request failed with HTTP status 401:
Unauthorized." error. If I try to access it again, I get in without a
problem.
In addition to the "first attempt after the iisreset", which happens
consistently, we also intermittently experience the same error, infrequently.
Any idea what is going on here? Caching of Credentials?
Michael DorfmanHello Michael,
To understand the issue better, I'd like to know the following information:
1. Does the issue only occur with a specific RS report or any RS report
such as sample reports including in RS installation?
2. Do you have anonymous access enabled on Report Manager or Report Server
virtual directories?
Also, this issue might be related to a known issue in .Net framework 1.1
sp1, I suggest that you contact CSS to get 887563 installed hotfix 887563
to see if it helps:
884537 FIX: You may receive a "System.Net.WebException" error message when
you
http://support.microsoft.com/?id=884537
887563 Availability of the .NET Framework 1.1 Post-Service Pack 1 rollup
http://support.microsoft.com/?id=887563
Also, please search if there are multiple copies of security.dll on your
SQL Reporting Services machine. If there are security.dll other than
%windir%\system32 folder, please tempoarily rename them to test the
situation.
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: Intermittent 401: Not Authorized
| thread-index: AcVTuOW2QlsDZxZ1SwW4LqLFvzorxw==| X-WBNR-Posting-Host: 62.97.217.178
| From: =?Utf-8?B?TWljaGFlbCBEb3JmbWFu?= <mercatus2004@.online.nospam>
| Subject: Intermittent 401: Not Authorized
| Date: Sun, 8 May 2005 03:30:04 -0700
| Lines: 11
| Message-ID: <E81A662F-4F37-45EB-8174-9C17787D5295@.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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:43126
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| The first time I try to access a RS report after an IISreset, I get a
| "System.Net.WebException: The request failed with HTTP status 401:
| Unauthorized." error. If I try to access it again, I get in without a
| problem.
|
| In addition to the "first attempt after the iisreset", which happens
| consistently, we also intermittently experience the same error,
infrequently.
|
| Any idea what is going on here? Caching of Credentials?
|
| Michael Dorfman
||||Are you using 2003 server and applied SP1? If so, I did the following and
solved my same problem:
"create a DWORD entry called DisableLoopbackCheck to
HKLM\System\CurrentControlSet\Control\Lsa. Set this key to a value of 1"
This is an issue which occures after appling SP1 to 2003 server.
I hope, this helps.
Barbaros Saglamtimur
MCDBA, MCAD
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:wrpXrMFVFHA.2476@.TK2MSFTNGXA01.phx.gbl...
> Hello Michael,
> To understand the issue better, I'd like to know the following
> information:
> 1. Does the issue only occur with a specific RS report or any RS report
> such as sample reports including in RS installation?
> 2. Do you have anonymous access enabled on Report Manager or Report Server
> virtual directories?
> Also, this issue might be related to a known issue in .Net framework 1.1
> sp1, I suggest that you contact CSS to get 887563 installed hotfix 887563
> to see if it helps:
> 884537 FIX: You may receive a "System.Net.WebException" error message when
> you
> http://support.microsoft.com/?id=884537
> 887563 Availability of the .NET Framework 1.1 Post-Service Pack 1 rollup
> http://support.microsoft.com/?id=887563
> Also, please search if there are multiple copies of security.dll on your
> SQL Reporting Services machine. If there are security.dll other than
> %windir%\system32 folder, please tempoarily rename them to test the
> situation.
>
> 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: Intermittent 401: Not Authorized
> | thread-index: AcVTuOW2QlsDZxZ1SwW4LqLFvzorxw==> | X-WBNR-Posting-Host: 62.97.217.178
> | From: =?Utf-8?B?TWljaGFlbCBEb3JmbWFu?= <mercatus2004@.online.nospam>
> | Subject: Intermittent 401: Not Authorized
> | Date: Sun, 8 May 2005 03:30:04 -0700
> | Lines: 11
> | Message-ID: <E81A662F-4F37-45EB-8174-9C17787D5295@.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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.sqlserver.reportingsvcs:43126
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | The first time I try to access a RS report after an IISreset, I get a
> | "System.Net.WebException: The request failed with HTTP status 401:
> | Unauthorized." error. If I try to access it again, I get in without a
> | problem.
> |
> | In addition to the "first attempt after the iisreset", which happens
> | consistently, we also intermittently experience the same error,
> infrequently.
> |
> | Any idea what is going on here? Caching of Credentials?
> |
> | Michael Dorfman
> |
>|||I have 4 different security.dll files...
C:\WINDOWS\system32 - version 5.2.3790.0
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
Files\reportserver\28ed0657\f12b7b77\assembly\dl2\d011044e\8fb1f7af_6dc3c401
C:\WINDOWS\system32\dllcache
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\bin - version 1.0.1770.24267
should I keep the Reporting Services version or the Windows version?
"Peter Yang [MSFT]" wrote:
> Hello Michael,
> To understand the issue better, I'd like to know the following information:
> 1. Does the issue only occur with a specific RS report or any RS report
> such as sample reports including in RS installation?
> 2. Do you have anonymous access enabled on Report Manager or Report Server
> virtual directories?
> Also, this issue might be related to a known issue in .Net framework 1.1
> sp1, I suggest that you contact CSS to get 887563 installed hotfix 887563
> to see if it helps:
> 884537 FIX: You may receive a "System.Net.WebException" error message when
> you
> http://support.microsoft.com/?id=884537
> 887563 Availability of the .NET Framework 1.1 Post-Service Pack 1 rollup
> http://support.microsoft.com/?id=887563
> Also, please search if there are multiple copies of security.dll on your
> SQL Reporting Services machine. If there are security.dll other than
> %windir%\system32 folder, please tempoarily rename them to test the
> situation.
>
> 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: Intermittent 401: Not Authorized
> | thread-index: AcVTuOW2QlsDZxZ1SwW4LqLFvzorxw==> | X-WBNR-Posting-Host: 62.97.217.178
> | From: =?Utf-8?B?TWljaGFlbCBEb3JmbWFu?= <mercatus2004@.online.nospam>
> | Subject: Intermittent 401: Not Authorized
> | Date: Sun, 8 May 2005 03:30:04 -0700
> | Lines: 11
> | Message-ID: <E81A662F-4F37-45EB-8174-9C17787D5295@.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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:43126
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | The first time I try to access a RS report after an IISreset, I get a
> | "System.Net.WebException: The request failed with HTTP status 401:
> | Unauthorized." error. If I try to access it again, I get in without a
> | problem.
> |
> | In addition to the "first attempt after the iisreset", which happens
> | consistently, we also intermittently experience the same error,
> infrequently.
> |
> | Any idea what is going on here? Caching of Credentials?
> |
> | Michael Dorfman
> |
>

Wednesday, March 21, 2012

interesting error message

Hi,
I keep geeting this error message in one of my servers.
Replication: agent failed.: Unable to expand message 17055 [-1073724769]
18265 Log backed up: Database: mine, creation date(time):
2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
dump devices: 1, device informa... ..
There is no replication configured on the server. The backup job is also
successful. What is this message about?
I don't know, but if it's really from August 11 of last year, are you sure
it's still relevant?
On 3/2/05 8:45 PM, in article
545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
<Bharath@.discussions.microsoft.com> wrote:

> Hi,
> I keep geeting this error message in one of my servers.
> Replication: agent failed.: Unable to expand message 17055 [-1073724769]
> 18265 Log backed up: Database: mine, creation date(time):
> 2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
> dump devices: 1, device informa... ..
>
> There is no replication configured on the server. The backup job is also
> successful. What is this message about?
|||Aaron,
It is relevant - I think the message is of Aug 11 - because the db was
created on Aug 11th 2004 - but it is a current message only.
"Aaron [SQL Server MVP]" wrote:

> I don't know, but if it's really from August 11 of last year, are you sure
> it's still relevant?
>
> On 3/2/05 8:45 PM, in article
> 545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
> <Bharath@.discussions.microsoft.com> wrote:
>
>

interesting error message

Hi,
I keep geeting this error message in one of my servers.
Replication: agent failed.: Unable to expand message 17055 [-1073724769]
18265 Log backed up: Database: mine, creation date(time):
2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
dump devices: 1, device informa... ..
There is no replication configured on the server. The backup job is also
successful. What is this message about?I don't know, but if it's really from August 11 of last year, are you sure
it's still relevant?
On 3/2/05 8:45 PM, in article
545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
<Bharath@.discussions.microsoft.com> wrote:
> Hi,
> I keep geeting this error message in one of my servers.
> Replication: agent failed.: Unable to expand message 17055 [-1073724769]
> 18265 Log backed up: Database: mine, creation date(time):
> 2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
> dump devices: 1, device informa... ..
>
> There is no replication configured on the server. The backup job is also
> successful. What is this message about?|||Aaron,
It is relevant - I think the message is of Aug 11 - because the db was
created on Aug 11th 2004 - but it is a current message only.
"Aaron [SQL Server MVP]" wrote:
> I don't know, but if it's really from August 11 of last year, are you sure
> it's still relevant?
>
> On 3/2/05 8:45 PM, in article
> 545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
> <Bharath@.discussions.microsoft.com> wrote:
> > Hi,
> >
> > I keep geeting this error message in one of my servers.
> >
> > Replication: agent failed.: Unable to expand message 17055 [-1073724769]
> > 18265 Log backed up: Database: mine, creation date(time):
> > 2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
> > dump devices: 1, device informa... ..
> >
> >
> > There is no replication configured on the server. The backup job is also
> > successful. What is this message about?
>

interesting error message

Hi,
I keep geeting this error message in one of my servers.
Replication: agent failed.: Unable to expand message 17055 [-1073724769]
18265 Log backed up: Database: mine, creation date(time):
2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number of
dump devices: 1, device informa... ..
There is no replication configured on the server. The backup job is also
successful. What is this message about?I don't know, but if it's really from August 11 of last year, are you sure
it's still relevant?
On 3/2/05 8:45 PM, in article
545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
<Bharath@.discussions.microsoft.com> wrote:

> Hi,
> I keep geeting this error message in one of my servers.
> Replication: agent failed.: Unable to expand message 17055 [-107372476
9]
> 18265 Log backed up: Database: mine, creation date(time):
> 2004/08/11(14:41:52), first LSN: 10:14151:1, last LSN: 10:14151:1, number
of
> dump devices: 1, device informa... ..
>
> There is no replication configured on the server. The backup job is also
> successful. What is this message about?|||Aaron,
It is relevant - I think the message is of Aug 11 - because the db was
created on Aug 11th 2004 - but it is a current message only.
"Aaron [SQL Server MVP]" wrote:

> I don't know, but if it's really from August 11 of last year, are you sure
> it's still relevant?
>
> On 3/2/05 8:45 PM, in article
> 545CADDF-C5EF-48A2-967F-A4246D13D306@.microsoft.com, "Bharath"
> <Bharath@.discussions.microsoft.com> wrote:
>
>

Monday, March 12, 2012

Interactive Resolver

Error message: "The process failed to get information about the Interactive Resolver from the registry".
I am using MSDE to subscribe to a central 2000 database using a pull subscription and the active X controls. However, the default resolver fails to operate. I have a call in with Product Support and sent them this:
Publication articles are all marked “Use the default resolver” and “Allow Subscribers to resolve conflicts interactively during on-demand synchronizations”. Note we are treating changes to the same column as being a conflict.
On the subscriber, “on demand synchronisations” are marked “Resolve Conflicts interactively…”
In my code to control the ActiveX objects, if I set the “UseInteractiveResolver” property to True, then the error message appears. If I leave this out, the default priority subscription happens.
We ARE NOT using any third party resolver, nor are we using any resolver aside from the interactive one.
However, I still cannot get the interactive resolver to display.
Is there something else. I have tried re-registering all DLLs back on the client after copying them from the 2000 CD ROM (SP3)
Hi Top,
From your descriptoin, I learnt that you the default resolver failed to operate when you subscribed to a
central 2000 database using a pull subscription and the active X controls.
Based on my experience (not 100% sure), the issue would occur if we manually or programmatically
change the Progid of conflict viewer from Wzconflict to CnfViewer. If so, the sync manager is unable to
launch the conflict viewer.
As you have call into Microsoft with Product Support, could you provide us with the Case ID so that we can
handle your post more gracefully and also for community benefits. In this way, we can address your
problem quickly and efficiently making headway to a solution.
We look forward to hearing from you.
Best regards,
Billy Yao
Microsoft Online Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
|||SRS040408600030
|||Hi Mark,
Thank you for your information! We have looked into the issue and found the causes of this issue as I
mentioned in my previous post.
When you tried to merge the data from your client which had MSDE installed you got following error 'The
process failed to get information about the interactive resolver component from the registry". This error was
due to missing DLL files or registry entries of the conflict viewer on your client system.
To solve the problem, we should check the following Registry Keys
------
HKCR\CLSID\{A2CA91F1-7328-4949-8611-8BEDB4AD503C}\InprocServer32 --> 'C:\Program Files
\Common Files\Microsoft Shared\Database Replication\Conflict Viewer\wzcnf.dll'
Check if the dll exists in the same location.
[INFO]Other Keys Accessed by conflict viewer:
HKCR\CLSID\{00000514-0000-0010-8000-00AA006D2EA4}\InprocServer32 -->'C:\Program Files\Common
Files\system\ado\msado15.dll'
HKCU\CLSID\{0BE35204-8F91-11CE-9DE3-00AA004BB851}\InprocServer32 -->'oleaut32.dll'
HKCR\CLSID\{0BE35204-8F91-11CE-9DE3-00AA004BB851}\InprocServer32 -->'oleaut32.dll'
------
and verify this steps
Steps:
======
1) The Following Files must be in the Directories mentioned for Interactive Conflict resolver to work.
\Program Files\Common Files\Microsoft Shared\Database Replication\Conflict Viewer: wzcnf.dll ,
wzcnfclt.exe
2) The following resource file should be installed in a language specific directory \Program Files\Common
Files\Microsoft Shared\Database Replication\Conflict Viewer\Resources\<LCID>: wzcnfrc.rll
The <LCID> is usually 1033.
IF these files are missing from these directories copy them from the same location on other systems where
the conflict viewer is working fine , or copy them from the Setup CD.Now go to the directory where "Wzcnf.dll
" is located and register it by typing "Regsvr32 wzcnf.dll".
NOTE: If we dont have the Resource file Wzcnfrc.rll, The Conflict viewer will still come up, but the Labels will
be missing from the Buttons on the User Interface.Once we have the Files in place and the Dll file registered,
we'll get the Interactive conflict viwer to come up normally on the MSDE Subscribers.
NOTE: The Conflict Viewer and Interactive Conflict Viewer uses the same exe and Dll.
We appreciated your time and efforts throughout the troubleshooting process. Thank you for posting in
newsgroup.
Best regards,
Billy Yao
Microsoft Online Support
Please reply to newsgroups only. Thanks.

Friday, March 9, 2012

Integrity checks keeps failing

Hi All,
I am driving myself crazy trying to debug this one. My Integrity check
keeps failing due to:
Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
And
Test (emptySlotCnt == 0) failed. Values are 1 and 0.
I have been researching this all morning. I ran a simple select on the
offending table and it turned out there where 2 columns that had a date that
went beyond the year 9999. I have nulled out the offending columns since
these dates are meaningless in the table. I can now run a select on this
table and return all rows, but the integrity check still fails for the same
reasons.
Can anyone please tell me how to fix this error? restoring the DB is out of
the question since i dont have a clean one without this issue. I am new to
this company and this job has been failing for long before I got here.
TIA,
Joejaylou
It is unclear, please provide DDL+ sample data+ keys to test the problem
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
> Hi All,
> I am driving myself crazy trying to debug this one. My Integrity check
> keeps failing due to:
> Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
> And
> Test (emptySlotCnt == 0) failed. Values are 1 and 0.
> I have been researching this all morning. I ran a simple select on the
> offending table and it turned out there where 2 columns that had a date
> that
> went beyond the year 9999. I have nulled out the offending columns since
> these dates are meaningless in the table. I can now run a select on this
> table and return all rows, but the integrity check still fails for the
> same
> reasons.
> Can anyone please tell me how to fix this error? restoring the DB is out
> of
> the question since i dont have a clean one without this issue. I am new
> to
> this company and this job has been failing for long before I got here.
> TIA,
> Joe
>|||Can you tell me how to send you that info?
"Uri Dimant" wrote:
> jaylou
> It is unclear, please provide DDL+ sample data+ keys to test the problem
>
>
>
>
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
> > Hi All,
> > I am driving myself crazy trying to debug this one. My Integrity check
> > keeps failing due to:
> > Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
> > And
> > Test (emptySlotCnt == 0) failed. Values are 1 and 0.
> >
> > I have been researching this all morning. I ran a simple select on the
> > offending table and it turned out there where 2 columns that had a date
> > that
> > went beyond the year 9999. I have nulled out the offending columns since
> > these dates are meaningless in the table. I can now run a select on this
> > table and return all rows, but the integrity check still fails for the
> > same
> > reasons.
> >
> > Can anyone please tell me how to fix this error? restoring the DB is out
> > of
> > the question since i dont have a clean one without this issue. I am new
> > to
> > this company and this job has been failing for long before I got here.
> >
> > TIA,
> > Joe
> >
>
>|||Post it here
CREATE TABEL tbl....
INSERT INTO tbl VALUES (.....
Desired result :
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:547DA248-751B-48FB-A5FC-B14D399554BC@.microsoft.com...
> Can you tell me how to send you that info?
> "Uri Dimant" wrote:
>> jaylou
>> It is unclear, please provide DDL+ sample data+ keys to test the problem
>>
>>
>>
>>
>> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
>> news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
>> > Hi All,
>> > I am driving myself crazy trying to debug this one. My Integrity check
>> > keeps failing due to:
>> > Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
>> > And
>> > Test (emptySlotCnt == 0) failed. Values are 1 and 0.
>> >
>> > I have been researching this all morning. I ran a simple select on the
>> > offending table and it turned out there where 2 columns that had a date
>> > that
>> > went beyond the year 9999. I have nulled out the offending columns
>> > since
>> > these dates are meaningless in the table. I can now run a select on
>> > this
>> > table and return all rows, but the integrity check still fails for the
>> > same
>> > reasons.
>> >
>> > Can anyone please tell me how to fix this error? restoring the DB is
>> > out
>> > of
>> > the question since i dont have a clean one without this issue. I am
>> > new
>> > to
>> > this company and this job has been failing for long before I got here.
>> >
>> > TIA,
>> > Joe
>> >
>>

Integrity checks job failed

Hello, I had a DB Maintenance plan, the schedule is every day, but today I found teh 'Integrity checks job is failed". What is that mean? How to check this. Thanks.You need to run DBCC CHECKDB and see if one of your databases fail the check. Maintenance plans are useful, unless you want to troubleshoot of course.|||I found one database failed, I found one user didn't exit the database last night, is that will affect the database backup and integrity check? Another thing, what is integrity check means? How to trouble shoot? Thank you very much! I am a new in sql server.|||Oh my...you have a lot to learn. :) What was the error on the database that failed?|||I know i need to learn, can you tell me which book is good for me to learn? I need to learn quickly, I found the error for the job history, that :

Executed as user: DOM\ServerAdmin. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Is that help you to figure out?|||http://www.dbforums.com/t812439.html

Gotta love microsoft. Looks like you have a classic generic error message. Could mean "disk is full", or "login failed" or almost anything. Kind of like the engine light in your car. I would start with running

DBCC Checkdb with no_infomsgs

on all of your databases to see if any of them have suddenly become corrupt. It is unlikely, but it is something you want to know about immediately. The user in the database could be the cause, but I can not say that for certain. Good luck.|||http://www.dbforums.com/t812439.html

Gotta love microsoft. Looks like you have a classic generic error message. Could mean "disk is full", or "login failed" or almost anything. Kind of like the engine light in your car. I would start with running

DBCC Checkdb with no_infomsgs

on all of your databases to see if any of them have suddenly become corrupt. It is unlikely, but it is something you want to know about immediately. The user in the database could be the cause, but I can not say that for certain. Good luck.

Hey, Listen...I'm alway one to give M$ a shot...

They all do it...

You can NEVER believe an Error Message

You always have to look outside the box...

DAMN, did I just say that?|||I didn't mean the error that the stupid maintenance plan gave you:

Executed as user: DOM\ServerAdmin. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.

This is AS USUAL for MS Maintenance Plans absolutely useless. Run the DBCC CHECKDB for the database that failed. Don't do it with a maintenance plan. Run it in good old Query Analyzer. Let us know what the error is you get from that, which will hopefully, and usually is, be more informative then gee, you seem to have a problem.

:) That's like one of our developers who came up to me today and said "Derrick, there's a problem with one of my programs." and then just stood there. "Yeah...SO....GO AWAY!!!!!"|||Listen...you CRACK ME UP...

ok, Now you want storeis?

Had an Ireland near shore ask me if it was a good idea to do a join or a 12 level nested cursor...

PLEASE!

I'll trade with you in a heart beat....|||12 level? WOW. You should have told him it was a great idea. It probably would have been a good contract after he got fired. :) Hey....FREEEEEE Trip.|||Can you nest 12 cursors? And more importantly, can you run anything else on the box when it kicks off?|||Hi, guys, i was away yesterday, i check today, everything is fine, No any problem, i think the database should be in single user mode. Thank you all.
But i have another question, why one user use sql server database, they have two process ID with same user and database?|||Open up two Query Analyzer connections. You'll see the same thing for you. :)|||But they are database user (Client), Why they also have two Process ID, also, i found the two host are different, one is their own host, another is not, why that happen? Thanks.

58 0 DOM\ssapienza Notary sleeping 0 AWAITING COMMAND Microsoft Office XP 0 not waiting 953 0 0 7/27/2004 11:02 7/27/2004 11:53 S27567 Named Pipes 00105A6D68CD 0 0
59 0 DOM\ssapienza Notary sleeping 0 AWAITING COMMAND Microsoft Office XP 0 not waiting 1048 6 91 7/27/2004 11:02 7/27/2004 11:53 D27450 Named Pipes 00105A6D68CD 0 0|||Use Profiler and trace SP:Completed and RPC:Completed with a filter on this user. Find out what they're doing. Does this user use Access to do things in the SQL Server database by any chance?|||Thanks, I will try. First i need to learn how to use profile, Is that use the memory? My server memory space is limit.

Integrity Checks job causing SQL 7 database to enter single-user mode

Hi,
I've encountered with very strange problem on this issue on one of my my SQL 7 Servers.
The integrity checks job on the database failed, and caused the database to enter the single user mode, thus preventing applications to access the database. I had to manually switch the database to normal mode to repair the problem.
Right now, every time i try to run the integrity checks job, it fails and causes the database to enter the single user mode again.
Any ideas how to solve the problem?
Thanks in advance,
BarakThis looks like a known issue. Have you seen this?
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B259551
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"Barak Turovsky" <barak.turovsky@.comverse.com> wrote in message
news:7DA294DF-065F-431A-91D6-AA23B4AA50CE@.microsoft.com...
Hi,
I've encountered with very strange problem on this issue on one of my my SQL
7 Servers.
The integrity checks job on the database failed, and caused the database to
enter the single user mode, thus preventing applications to access the
database. I had to manually switch the database to normal mode to repair the
problem.
Right now, every time i try to run the integrity checks job, it fails and
causes the database to enter the single user mode again.
Any ideas how to solve the problem?
Thanks in advance,
Barak

Integrity Checks Failed?

We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status: Faile
d
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?Have you looked at the report that is generated from your maintenance plan?
Possibly this report will help you determine what is wrong. If you are not
generating the report, then review your options under the "Reporting" tab
while editing your maintenance plan.
----
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
> We have 3 maintenance plans, each running against a different subset of
> databases on the same server. Each maintenance plan runs integrity checks
> once a week. According to "Job History", one of the three jobs fails
every
> week. Looking at the sql logs every DBCC check shows "found 0 errors and
> repaired 0 errors." In the server's Application Event Log we see this
vague
> error message:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 1/2/2005
> Time: 12:00:27 AM
> User: N/A
> Computer: FBENSQLP1
> Description:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
> 'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
> - Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
> invoked by Schedule 19 (Schedule 1). The last step to run was step 1
(Step
> 1).
> Is it possible that this is some sort of a false alert? The other two
> weekly integrity checks always show successful completions.
> What might cause this job to "Fail" every week?
>|||No, something indeed happened; the problem is finding out more details as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If there
were database connectivity issues, then this information will be missing and
the text log files your created above will be the only source of information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?|||You need to uncheck the checkbox in the MP wizard that states to "Fix Minor
Repairs". Then it won't attempt to put the db into single user mode and it
will operate properly. If there is a problem the job will fail and then you
can handle the issue the correct way as is best suited for your environment
.
--
Andrew J. Kelly SQL MVP
"Anna Emegard" <Anna.Emegard@.harryda.se> wrote in message news:ufX7Xb$HFHA.1
172@.TK2MSFTNGP12.phx.gbl...
Hi!
We have the exact same error. We run the integrity check once a week on this
one database and it has run smoothly until three weeks ago. In the log file
it says "Database state cannot be changed while other users are using the d
atabase". There are other jobs running before and after this job and there a
re no problems with them. I can't figure out why this particular job won't r
un.
Sincerely,
Anna
[vbcol=seagreen]
No, something indeed happened; the problem is finding out more details as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If there
were database connectivity issues, then this information will be missing and
the text log files your created above will be the only source of information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas
--
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?

Integrity Checks Failed?

We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status: Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?Have you looked at the report that is generated from your maintenance plan?
Possibly this report will help you determine what is wrong. If you are not
generating the report, then review your options under the "Reporting" tab
while editing your maintenance plan.
--
----
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
> We have 3 maintenance plans, each running against a different subset of
> databases on the same server. Each maintenance plan runs integrity checks
> once a week. According to "Job History", one of the three jobs fails
every
> week. Looking at the sql logs every DBCC check shows "found 0 errors and
> repaired 0 errors." In the server's Application Event Log we see this
vague
> error message:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 1/2/2005
> Time: 12:00:27 AM
> User: N/A
> Computer: FBENSQLP1
> Description:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
> 'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
> - Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
> invoked by Schedule 19 (Schedule 1). The last step to run was step 1
(Step
> 1).
> Is it possible that this is some sort of a false alert? The other two
> weekly integrity checks always show successful completions.
> What might cause this job to "Fail" every week?
>|||No, something indeed happened; the problem is finding out more details as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If there
were database connectivity issues, then this information will be missing and
the text log files your created above will be the only source of information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?|||--____XAVHMWYRSQSWQDYPECYE____
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Hi!
We have the exact same error. We run the integrity check once a week on =this one database and it has run smoothly until three weeks ago. In the =log file it says "Database state cannot be changed while other users are =using the database". There are other jobs running before and after this =job and there are no problems with them. I can't figure out why this =particular job won't run.
Sincerely,
Anna
>> AnthonyThomas<Anthony.Thomas@.CommerceBank.com> 2005-01-03 17:11:38 >>
No, something indeed happened; the problem is finding out more details as =to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info =on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If =there
were database connectivity issues, then this information will be missing =and
the text log files your created above will be the only source of informatio=n
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas
--
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails =every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this =vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 =(Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?
--____XAVHMWYRSQSWQDYPECYE____
Content-Type: multipart/related; boundary="____JVBAVOGAYIGGGPIKBBLQ____"
--____JVBAVOGAYIGGGPIKBBLQ____
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
&

Hi!
We have the exact same error. We run the integrity check once a =week on this one database and it has run smoothly until three weeks ago. =In the log file it says "Database state cannot be changed while other =users are using the database". There are other jobs running before and =after this job and there are no problems with them. I can't figure =out why this particular job won't run.
Sincerely,
Anna> AnthonyThomas 2005-01-03 17:11:38 >>
No, something indeed happened; the problem =is finding out more details as towhy. There are several logging =options available to you.1. In the maintenance plan, Reporting =Tab, choose to retain informationwithin the MSDB database but also =create Job Run report to a text file.Oftentimes, this information= will provide you with the necessary detail.2. On the job, make =sure it is configured to output additional step info onthe advanced =tab of the step settings.3. You've already discovered the SQL =Server error logs and the WindowsApplication event logs, also take a =look at the SQL Agent error logs.To view the maintenance history, =in SQL EM, right-click one of themaintenance plans and choose to view =the history. This log will tell youeach activity, and each =database, whether successfull or failure. If therewere database =connectivity issues, then this information will be missing andthe text =log files your created above will be the only source of informationouts=ide of the error logs you have already discovered.Hope this =helps.Sincerely,Anthony Thomas-- "A=nthonyMunoz" wrote in =messagenews:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...We= have 3 maintenance plans, each running against a different subset =ofdatabases on the same server. Each maintenance plan runs =integrity checksonce a week. According to "Job History", one of =the three jobs fails everyweek. Looking at the sql logs every =DBCC check shows "found 0 errors andrepaired 0 errors." In the =server's Application Event Log we see this vagueerror message:E=vent Type: WarningEvent Source: SQLSERVERAGENTEvent Category: Job =EngineEvent ID: 208Date: 1/2/2005Time: 12:00:27 AMUser: =N/AComputer: FBENSQLP1Description:SQL Server Scheduled Job ='Integrity Checks Job for DB Maintenance Plan'Internal Maintenance'' =(0x860A641AB3C0FD4CA22C0369E63523E4) - Status:Failed- Invoked on: =2005-01-02 00:00:00 - Message: The job failed. The Job wasinvoked= by Schedule 19 (Schedule 1). The last step to run was step 1 =(Step1).Is it possible that this is some sort of a false =alert? The other twoweekly integrity checks always show =successful completions.What might cause this job to "Fail" every =week?

--____JVBAVOGAYIGGGPIKBBLQ____--
--____XAVHMWYRSQSWQDYPECYE____--|||This is a multi-part message in MIME format.
--=_NextPart_000_0070_01C51FCF.9D6B6680
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
You need to uncheck the checkbox in the MP wizard that states to "Fix =Minor Repairs". Then it won't attempt to put the db into single user =mode and it will operate properly. If there is a problem the job will =fail and then you can handle the issue the correct way as is best suited =for your environment.
-- Andrew J. Kelly SQL MVP

"Anna Emegard" <Anna.Emegard@.harryda.se> wrote in message =news:ufX7Xb$HFHA.1172@.TK2MSFTNGP12.phx.gbl...
Hi!
We have the exact same error. We run the integrity check once a week =on this one database and it has run smoothly until three weeks ago. In =the log file it says "Database state cannot be changed while other users =are using the database". There are other jobs running before and after =this job and there are no problems with them. I can't figure out why =this particular job won't run.
Sincerely,
Anna
>> AnthonyThomas<Anthony.Thomas@.CommerceBank.com> 2005-01-03 17:11:38 =
No, something indeed happened; the problem is finding out more details =as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain =information
within the MSDB database but also create Job Run report to a text =file.
Oftentimes, this information will provide you with the necessary =detail.
2. On the job, make sure it is configured to output additional step =info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell =you
each activity, and each database, whether successfull or failure. If =there
were database connectivity issues, then this information will be =missing and
the text log files your created above will be the only source of =information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas
--
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in =message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset =of
databases on the same server. Each maintenance plan runs integrity =checks
once a week. According to "Job History", one of the three jobs fails =every
week. Looking at the sql logs every DBCC check shows "found 0 errors =and
repaired 0 errors." In the server's Application Event Log we see this =vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job =was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 =(Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?
--=_NextPart_000_0070_01C51FCF.9D6B6680
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

You need to uncheck the checkbox in the MP =wizard that states to "Fix Minor Repairs". Then it won't attempt to put the db =into single user mode and it will operate properly. If there is a =problem the job will fail and then you can handle the issue the correct way as is =best suited for your environment.
-- Andrew J. Kelly SQL MVP
"Anna Emegard" =wrote in message news:ufX7Xb$HFHA.1172=@.TK2MSFTNGP12.phx.gbl...
Hi!

We have the exact same error. We run the integrity check =once a week on this one database and it has run smoothly until three weeks ago. In =the log file it says "Database state cannot be changed while other users are =using the database". There are other jobs running before and after this job =and there are no problems with them. I can't figure out why this =particular job won't run.

Sincerely,
Anna> AnthonyThomas 2005-01-03 =17:11:38 >>
No, something indeed happened; the =problem is finding out more details as towhy. There are several logging =options available to you.1. In the maintenance plan, Reporting Tab, =choose to retain informationwithin the MSDB database but also create =Job Run report to a text file.Oftentimes, this information will provide =you with the necessary detail.2. On the job, make sure it is configured =to output additional step info onthe advanced tab of the step settings.3. You've already discovered the SQL Server error =logs and the WindowsApplication event logs, also take a look at the SQL =Agent error logs.To view the maintenance history, in SQL EM, right-click =one of themaintenance plans and choose to view the history. This =log will tell youeach activity, and each database, whether successfull or failure. If therewere database connectivity issues, then =this information will be missing andthe text log files your created =above will be the only source of informationoutside of the error logs you =have already discovered.Hope this helps.Sincerely,Anthony Thomas-- "AnthonyMunoz" =wrote in =messagenews:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...=We have 3 maintenance plans, each running against a different subset ofdatabases on the same server. Each maintenance plan runs =integrity checksonce a week. According to "Job History", one of the =three jobs fails everyweek. Looking at the sql logs every DBCC check =shows "found 0 errors andrepaired 0 errors." In the server's =Application Event Log we see this vagueerror message:Event Type: WarningEvent Source: SQLSERVERAGENTEvent Category: Job =EngineEvent ID: 208Date: 1/2/2005Time: 12:00:27 AMUser: =N/AComputer: FBENSQLP1Description:SQL Server Scheduled Job 'Integrity =Checks Job for DB Maintenance Plan'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:Failed- Invoked =on: 2005-01-02 00:00:00 - Message: The job failed. The Job =wasinvoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step1).Is it possible that this is some sort of a false alert? The other twoweekly integrity checks always show =successful completions.What might cause this job to "Fail" every week?

--=_NextPart_000_0070_01C51FCF.9D6B6680--

Integrity Checks Failed?

We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type:Warning
Event Source:SQLSERVERAGENT
Event Category:Job Engine
Event ID:208
Date:1/2/2005
Time:12:00:27 AM
User:N/A
Computer:FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status: Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?
Have you looked at the report that is generated from your maintenance plan?
Possibly this report will help you determine what is wrong. If you are not
generating the report, then review your options under the "Reporting" tab
while editing your maintenance plan.
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
> We have 3 maintenance plans, each running against a different subset of
> databases on the same server. Each maintenance plan runs integrity checks
> once a week. According to "Job History", one of the three jobs fails
every
> week. Looking at the sql logs every DBCC check shows "found 0 errors and
> repaired 0 errors." In the server's Application Event Log we see this
vague
> error message:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 1/2/2005
> Time: 12:00:27 AM
> User: N/A
> Computer: FBENSQLP1
> Description:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
> 'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
> - Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
> invoked by Schedule 19 (Schedule 1). The last step to run was step 1
(Step
> 1).
> Is it possible that this is some sort of a false alert? The other two
> weekly integrity checks always show successful completions.
> What might cause this job to "Fail" every week?
>
|||No, something indeed happened; the problem is finding out more details as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If there
were database connectivity issues, then this information will be missing and
the text log files your created above will be the only source of information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas

"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?
|||You need to uncheck the checkbox in the MP wizard that states to "Fix Minor Repairs". Then it won't attempt to put the db into single user mode and it will operate properly. If there is a problem the job will fail and then you can handle the issue the correct way as is best suited for your environment.
Andrew J. Kelly SQL MVP
"Anna Emegard" <Anna.Emegard@.harryda.se> wrote in message news:ufX7Xb$HFHA.1172@.TK2MSFTNGP12.phx.gbl...
Hi!
We have the exact same error. We run the integrity check once a week on this one database and it has run smoothly until three weeks ago. In the log file it says "Database state cannot be changed while other users are using the database". There are other jobs running before and after this job and there are no problems with them. I can't figure out why this particular job won't run.
Sincerely,
Anna
[vbcol=seagreen]
No, something indeed happened; the problem is finding out more details as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If there
were database connectivity issues, then this information will be missing and
the text log files your created above will be the only source of information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas

"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?

Wednesday, March 7, 2012

Integrity Check set in Maintenance Plan failed....

I'm trying to troubleshoot why this job failed. Welcome any suggestion
DURATION: 0 hours, 0 minutes, 49 second
STATUS: Faile
MESSAGES: The job failed. The Job was invoked by Schedule 35 (Schedule 1). The last step to run was step 1 (Step 1)Make sure that you have defined a report file for the maint job and check for error messages in the
report file.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Janice" <anonymous@.discussions.microsoft.com> wrote in message
news:EDF91295-5A27-43C3-AA1C-402F35FB629F@.microsoft.com...
> I'm trying to troubleshoot why this job failed. Welcome any suggestions
>
> DURATION: 0 hours, 0 minutes, 49 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 35 (Schedule 1). The last step to run
was step 1 (Step 1).
>|||Thanks TIBOR - I viewed the report and discovered that db needs to be in single user mode.
-- Tibor Karaszi wrote: --
Make sure that you have defined a report file for the maint job and check for error messages in the
report file.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Janice" <anonymous@.discussions.microsoft.com> wrote in message
news:EDF91295-5A27-43C3-AA1C-402F35FB629F@.microsoft.com...
> I'm trying to troubleshoot why this job failed. Welcome any suggestions
>> DURATION: 0 hours, 0 minutes, 49 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 35 (Schedule 1). The last step to run
was step 1 (Step 1).
>|||The maint plan will try to set the db in single user, but that will fail if there are users in the
database. Also, some of the system databases cannot be set in single user mode.
I suggest you remove the option "attempt to repair minor problems" from the integrity checks. If you
do run into problems, you want to be there and contemplate over what you want to do to fix it.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Janice" <anonymous@.discussions.microsoft.com> wrote in message
news:8FF8A86A-F50A-4EB8-BF6D-058B99EF2455@.microsoft.com...
> Thanks TIBOR - I viewed the report and discovered that db needs to be in single user mode.
> -- Tibor Karaszi wrote: --
> Make sure that you have defined a report file for the maint job and check for error messages
in the
> report file.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Janice" <anonymous@.discussions.microsoft.com> wrote in message
> news:EDF91295-5A27-43C3-AA1C-402F35FB629F@.microsoft.com...
> > I'm trying to troubleshoot why this job failed. Welcome any suggestions
> >> DURATION: 0 hours, 0 minutes, 49 seconds
> > STATUS: Failed
> > MESSAGES: The job failed. The Job was invoked by Schedule 35 (Schedule 1). The last step
to run
> was step 1 (Step 1).
> >

integrity check failed

on sql server 2000, try to do integrity check on several database once a week
but failed, what would be main area to look up? thank youDrop and recreate your indexes then update statistics
I have a script somewhere that can automate the process
Do this during low usage times, as it willl greatly affect performance
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:2EFA3260-8995-4985-BB70-9D770878A9EB@.microsoft.com...
> on sql server 2000, try to do integrity check on several database once a
> week
> but failed, what would be main area to look up? thank you|||no error found on the appliation event viewer and no error found on the sql
server error log. How would i get the script? thank you
"Randy Pitkin" wrote:
> Drop and recreate your indexes then update statistics
> I have a script somewhere that can automate the process
> Do this during low usage times, as it willl greatly affect performance
> "tulip" <tulip@.discussions.microsoft.com> wrote in message
> news:2EFA3260-8995-4985-BB70-9D770878A9EB@.microsoft.com...
> > on sql server 2000, try to do integrity check on several database once a
> > week
> > but failed, what would be main area to look up? thank you
>
>|||Read the error messages that the DBCC CHECKDB command produced.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:2EFA3260-8995-4985-BB70-9D770878A9EB@.microsoft.com...
> on sql server 2000, try to do integrity check on several database once a week
> but failed, what would be main area to look up? thank you

Integrity check and optimization job failed

I found the following error in my maintenance plan please help me on this

Under maintenace plan history i found this error:-

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL Server Driver][SQL Server]UPDATE STATISTICS failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER'.

and jobs failed with following error

i found this error in job history of optimization & integrity check jobs:-

Executed as user: XXXX\admin. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.

Please help me find out the solution

Thanks in advance

Regards,

Sumitdo not use maintenance plans. setup your own jobs for this stuff. easier to troubleshoot and you have more granular control.|||This error isn't caused by the maintenance plan, but rather occurs within the job the maintenance plan creates. The error is generated by UPDATE STATISTICS, and in my experience is related to attempts to update the stats on a table that is used to record or maintain table statistics (such as a table within the msdb database). Unfortunately, I have not been able to reliably reproduce the problem in order to debug it. When I run UPDATE STATS on the offending table a second time, it always completes succesfully. So far, it has not bothered my enough to make me want to delve into it any deeper.

Monday, March 26, 2012

intermittent connection problems

intermittent connection problems

Intermittent 401: Not Authorized

Wednesday, March 21, 2012

interesting error message

interesting error message

interesting error message

Monday, March 12, 2012

Interactive Resolver

Friday, March 9, 2012

Integrity checks keeps failing

Integrity checks keeps failing

Integrity checks keeps failing

Integrity checks job failed

Integrity Checks job causing SQL 7 database to enter single-user mode

Integrity Checks Failed?

Integrity Checks Failed?

Integrity Checks Failed?

Wednesday, March 7, 2012

Integrity Check set in Maintenance Plan failed....

integrity check failed

integrity check failed

Integrity check and optimization job failed

Integrated Security

Blog Archive

About Me