intermittent failures using web synchronisation

HI

We are using HTTPS anonymous merge subscriptions....

Sometimes when trying to synchonise, we will get the following error messages returned to the subscriber....

The upload message to be sent to Publisher '**thewebserver**' is being generated
The merge process is using Exchange ID '0F65CFCB-AF17-47DC-8D98-493A44C243E0' for this web synchronization session.
The Merge Agent could not connect to the URL 'https://**thewebserver**/client/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable.
The Merge Agent could not connect to the URL 'https://**thewebserver**/client/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable.
The Merge Agent received the following error status and message from the Internet Information Services (IIS) server during Web synchronization: [401 :'Unauthorized']. When troubleshooting, ensure that the Web synchronization settings for the subscription are correct, and increase the internet timeout setting at the Subscriber and the connection timeout at the Web server.

If I then go to a web brower, put in the HTTPS address, it brings up the logon dialog - I put in the admin username and password to confirm the connection and that's fine.

We try and synchronise again, and this time it works - it's as though I have 'woken' it up again and it's happy to play.

Is increasing the timeouts as suggested by the error message the way to go ? If so, where does one set the 'internet timeout setting at the subscriber', and the 'connection timeout at the webserver' ?

thanks

I dont think it is the timeout that is causing this. But anyways,

To increase the timeout on the Client (Merge Agent) use the Merge agent parameter: -InternetTimeout

To increase the timeout on the webserver, use IIS-->WebSites-->DefaultWebSite-->Properties-->ConnectionTimeout

From what you describe, it appears to me that the -InternetLogin may not have permissions to load the replisapi.dll once the process goes away? Would that be the case? This is just a hunch.

Under what context is the IIS running? (specifically the w3wp.exe process)

Is your InternetLogin and the login running the IIS (w3wp) the same?

You could also try other ways so that you can specify the w3wp.exe to never exit out after 20 minutes (I think that is the default one)

|||I had this happen just yesterday in my test environment. I added a new subscriber laptop to the mix and I kept on getting this error. It turns out that I had to visit the replisapi.dll via Internet Explorer and install the SSL certificate. (I am using Self SSL on the test environment) Once I installed the cert the error went away.sql

intermittent failures using web synchronisation

HI

We are using HTTPS anonymous merge subscriptions....

Sometimes when trying to synchonise, we will get the following error messages returned to the subscriber....

The upload message to be sent to Publisher '**thewebserver**' is being generated
The merge process is using Exchange ID '0F65CFCB-AF17-47DC-8D98-493A44C243E0' for this web synchronization session.
The Merge Agent could not connect to the URL 'https://**thewebserver**/client/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable.
The Merge Agent could not connect to the URL 'https://**thewebserver**/client/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable.
The Merge Agent received the following error status and message from the Internet Information Services (IIS) server during Web synchronization: [401 :'Unauthorized']. When troubleshooting, ensure that the Web synchronization settings for the subscription are correct, and increase the internet timeout setting at the Subscriber and the connection timeout at the Web server.

If I then go to a web brower, put in the HTTPS address, it brings up the logon dialog - I put in the admin username and password to confirm the connection and that's fine.

We try and synchronise again, and this time it works - it's as though I have 'woken' it up again and it's happy to play.

Is increasing the timeouts as suggested by the error message the way to go ? If so, where does one set the 'internet timeout setting at the subscriber', and the 'connection timeout at the webserver' ?

thanks

I dont think it is the timeout that is causing this. But anyways,

To increase the timeout on the Client (Merge Agent) use the Merge agent parameter: -InternetTimeout

To increase the timeout on the webserver, use IIS-->WebSites-->DefaultWebSite-->Properties-->ConnectionTimeout

From what you describe, it appears to me that the -InternetLogin may not have permissions to load the replisapi.dll once the process goes away? Would that be the case? This is just a hunch.

Under what context is the IIS running? (specifically the w3wp.exe process)

Is your InternetLogin and the login running the IIS (w3wp) the same?

You could also try other ways so that you can specify the w3wp.exe to never exit out after 20 minutes (I think that is the default one)

|||I had this happen just yesterday in my test environment. I added a new subscriber laptop to the mix and I kept on getting this error. It turns out that I had to visit the replisapi.dll via Internet Explorer and install the SSL certificate. (I am using Self SSL on the test environment) Once I installed the cert the error went away.

Intermittent connection dramas: "Cannot open user default database..."

Hi,
I've been experiencing some very strange, intermittent failures connecting
to an MS SQL database... basically at seemingly random times the server
decides that it can't open the requested database (reporting error 4062:
"Cannot open user default database. Using master database instead"). I've
so far been unable to track down any useful background to this error
message; has anyone on this group come across similar problems? Any clues
as to what might be triggering this sort of fault? More specific details
follow:
* In the majority of cases, connection is established correctly (albeit
sometimes a little slowly).
* Connections are being made to the local machine, using straightforward,
static code. The problem isn't something trivial like a mis-typed
database name, incorrect password etc. Re-running the SAME CODE will
eventually succeed.
* The server isn't particularly heavily loaded, and I can perceive no
pattern to the fault (it seems no more prevalent when the
server's busy, nor after any particular events).
* Nothing relevant is documented in the Event Viewer, nor the server logs.
Am I looking in the right place?
* We're running SQL Server 2005 Express Edition, latest service pack...
are there any connection rate limitations on this software? All
documentation I've seen indicates that there are not, but this behaviour
almost suggests that there may be...
* Connecting (from local machine) using PHP mssql module (latest stable
version).
* Although possibly symptomatic of a DoS, there's no other evidence to
suggest that this is the case (TCP to the service is firewalled).
Would be grateful for any advice on this issue.
Cheers,
Alex.
Alex Craven wrote:
> Hi,
> I've been experiencing some very strange, intermittent failures connecting
> to an MS SQL database... basically at seemingly random times the server
> decides that it can't open the requested database (reporting error 4062:
> "Cannot open user default database. Using master database instead"). I've
> so far been unable to track down any useful background to this error
> message; has anyone on this group come across similar problems? Any clues
> as to what might be triggering this sort of fault? More specific details
> follow:
> * In the majority of cases, connection is established correctly (albeit
> sometimes a little slowly).
> * Connections are being made to the local machine, using straightforward,
> static code. The problem isn't something trivial like a mis-typed
> database name, incorrect password etc. Re-running the SAME CODE will
> eventually succeed.
> * The server isn't particularly heavily loaded, and I can perceive no
> pattern to the fault (it seems no more prevalent when the
> server's busy, nor after any particular events).
> * Nothing relevant is documented in the Event Viewer, nor the server logs.
> Am I looking in the right place?
> * We're running SQL Server 2005 Express Edition, latest service pack...
> are there any connection rate limitations on this software? All
> documentation I've seen indicates that there are not, but this behaviour
> almost suggests that there may be...
> * Connecting (from local machine) using PHP mssql module (latest stable
> version).
> * Although possibly symptomatic of a DoS, there's no other evidence to
> suggest that this is the case (TCP to the service is firewalled).
>
> Would be grateful for any advice on this issue.
> Cheers,
> Alex.
>
>
Make sure the "problem" database isn't configured for auto-close, also
make sure it's not the target for log-shipping, or some other process
that might take it offline to do a restore, etc.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Do you periodically rename, remove, or detach the database?
Do you have any jobs that put the database into single-user mode or
otherwise alter the availability of the database?
|||On Fri, 29 Sep 2006 08:14:30 -0500, Tracy McKibben uttered:
[...]
> Make sure the "problem" database isn't configured for auto-close, also
> make sure it's not the target for log-shipping, or some other process
> that might take it offline to do a restore, etc.
Hi Tracy et al,
Thanks for all your advice; so far it looks like the auto-close 'feature'
was most likely the root of my problems (or at least a major factor...);
the system seems to be performing rather more reliably with that disabled.
Cheers,
Alex.
|||Alex Craven wrote:
> On Fri, 29 Sep 2006 08:14:30 -0500, Tracy McKibben uttered:
> [...]
>
> Hi Tracy et al,
> Thanks for all your advice; so far it looks like the auto-close 'feature'
> was most likely the root of my problems (or at least a major factor...);
> the system seems to be performing rather more reliably with that disabled.
> Cheers,
> Alex.
>
That auto-close option should NEVER be enabled for a production
database. Another one to watch out for is auto-shrink.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
sql

Intermittent connection dramas: "Cannot open user default database..."

Hi,
I've been experiencing some very strange, intermittent failures connecting
to an MS SQL database... basically at seemingly random times the server
decides that it can't open the requested database (reporting error 4062:
"Cannot open user default database. Using master database instead"). I've
so far been unable to track down any useful background to this error
message; has anyone on this group come across similar problems? Any clues
as to what might be triggering this sort of fault? More specific details
follow:
* In the majority of cases, connection is established correctly (albeit
sometimes a little slowly).
* Connections are being made to the local machine, using straightforward,
static code. The problem isn't something trivial like a mis-typed
database name, incorrect password etc. Re-running the SAME CODE will
eventually succeed.
* The server isn't particularly heavily loaded, and I can perceive no
pattern to the fault (it seems no more prevalent when the
server's busy, nor after any particular events).
* Nothing relevant is documented in the Event Viewer, nor the server logs.
Am I looking in the right place'
* We're running SQL Server 2005 Express Edition, latest service pack...
are there any connection rate limitations on this software? All
documentation I've seen indicates that there are not, but this behaviour
almost suggests that there may be...
* Connecting (from local machine) using PHP mssql module (latest stable
version).
* Although possibly symptomatic of a DoS, there's no other evidence to
suggest that this is the case (TCP to the service is firewalled).
Would be grateful for any advice on this issue.
Cheers,
Alex.HI Alex
Have you checked for Anti-virus or intrusion detection software in the
server, this can cause connections to fail. If you have the autoclose option
set for the database or attaching the database when you connect then if the
AV software is scanning the files you will not be able to do this.
You may also want to eliminate any particular machine or see if this occurs
on the server, to rule out general networking issues. Check firewalls are
correctly configured and if you are using group policies that they are not
interfering.
You may also want to check if you are service packed to a recent version.
John
"Alex Craven" wrote:
> Hi,
> I've been experiencing some very strange, intermittent failures connecting
> to an MS SQL database... basically at seemingly random times the server
> decides that it can't open the requested database (reporting error 4062:
> "Cannot open user default database. Using master database instead"). I've
> so far been unable to track down any useful background to this error
> message; has anyone on this group come across similar problems? Any clues
> as to what might be triggering this sort of fault? More specific details
> follow:
> * In the majority of cases, connection is established correctly (albeit
> sometimes a little slowly).
> * Connections are being made to the local machine, using straightforward,
> static code. The problem isn't something trivial like a mis-typed
> database name, incorrect password etc. Re-running the SAME CODE will
> eventually succeed.
> * The server isn't particularly heavily loaded, and I can perceive no
> pattern to the fault (it seems no more prevalent when the
> server's busy, nor after any particular events).
> * Nothing relevant is documented in the Event Viewer, nor the server logs.
> Am I looking in the right place'
> * We're running SQL Server 2005 Express Edition, latest service pack...
> are there any connection rate limitations on this software? All
> documentation I've seen indicates that there are not, but this behaviour
> almost suggests that there may be...
> * Connecting (from local machine) using PHP mssql module (latest stable
> version).
> * Although possibly symptomatic of a DoS, there's no other evidence to
> suggest that this is the case (TCP to the service is firewalled).
>
> Would be grateful for any advice on this issue.
> Cheers,
> Alex.
>
>|||Alex Craven wrote:
> Hi,
> I've been experiencing some very strange, intermittent failures connecting
> to an MS SQL database... basically at seemingly random times the server
> decides that it can't open the requested database (reporting error 4062:
> "Cannot open user default database. Using master database instead"). I've
> so far been unable to track down any useful background to this error
> message; has anyone on this group come across similar problems? Any clues
> as to what might be triggering this sort of fault? More specific details
> follow:
> * In the majority of cases, connection is established correctly (albeit
> sometimes a little slowly).
> * Connections are being made to the local machine, using straightforward,
> static code. The problem isn't something trivial like a mis-typed
> database name, incorrect password etc. Re-running the SAME CODE will
> eventually succeed.
> * The server isn't particularly heavily loaded, and I can perceive no
> pattern to the fault (it seems no more prevalent when the
> server's busy, nor after any particular events).
> * Nothing relevant is documented in the Event Viewer, nor the server logs.
> Am I looking in the right place'
> * We're running SQL Server 2005 Express Edition, latest service pack...
> are there any connection rate limitations on this software? All
> documentation I've seen indicates that there are not, but this behaviour
> almost suggests that there may be...
> * Connecting (from local machine) using PHP mssql module (latest stable
> version).
> * Although possibly symptomatic of a DoS, there's no other evidence to
> suggest that this is the case (TCP to the service is firewalled).
>
> Would be grateful for any advice on this issue.
> Cheers,
> Alex.
>
>
Make sure the "problem" database isn't configured for auto-close, also
make sure it's not the target for log-shipping, or some other process
that might take it offline to do a restore, etc.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Do you periodically rename, remove, or detach the database?
Do you have any jobs that put the database into single-user mode or
otherwise alter the availability of the database?|||On Fri, 29 Sep 2006 08:14:30 -0500, Tracy McKibben uttered:
[...]
> Make sure the "problem" database isn't configured for auto-close, also
> make sure it's not the target for log-shipping, or some other process
> that might take it offline to do a restore, etc.
Hi Tracy et al,
Thanks for all your advice; so far it looks like the auto-close 'feature'
was most likely the root of my problems (or at least a major factor...);
the system seems to be performing rather more reliably with that disabled.
Cheers,
Alex.|||Alex Craven wrote:
> On Fri, 29 Sep 2006 08:14:30 -0500, Tracy McKibben uttered:
> [...]
>> Make sure the "problem" database isn't configured for auto-close, also
>> make sure it's not the target for log-shipping, or some other process
>> that might take it offline to do a restore, etc.
>
> Hi Tracy et al,
> Thanks for all your advice; so far it looks like the auto-close 'feature'
> was most likely the root of my problems (or at least a major factor...);
> the system seems to be performing rather more reliably with that disabled.
> Cheers,
> Alex.
>
That auto-close option should NEVER be enabled for a production
database. Another one to watch out for is auto-shrink.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Intermittent connection dramas: "Cannot open user default database..."

Hi,
I've been experiencing some very strange, intermittent failures connecting
to an MS SQL database... basically at seemingly random times the server
decides that it can't open the requested database (reporting error 4062:
"Cannot open user default database. Using master database instead"). I've
so far been unable to track down any useful background to this error
message; has anyone on this group come across similar problems? Any clues
as to what might be triggering this sort of fault? More specific details
follow:
* In the majority of cases, connection is established correctly (albeit
sometimes a little slowly).
* Connections are being made to the local machine, using straightforward,
static code. The problem isn't something trivial like a mis-typed
database name, incorrect password etc. Re-running the SAME CODE will
eventually succeed.
* The server isn't particularly heavily loaded, and I can perceive no
pattern to the fault (it seems no more prevalent when the
server's busy, nor after any particular events).
* Nothing relevant is documented in the Event Viewer, nor the server logs.
Am I looking in the right place'
* We're running SQL Server 2005 Express Edition, latest service pack...
are there any connection rate limitations on this software? All
documentation I've seen indicates that there are not, but this behaviour
almost suggests that there may be...
* Connecting (from local machine) using php mssql module (latest stable
version).
* Although possibly symptomatic of a DoS, there's no other evidence to
suggest that this is the case (TCP to the service is firewalled).
Would be grateful for any advice on this issue.
Cheers,
Alex.Alex Craven wrote:
> Hi,
> I've been experiencing some very strange, intermittent failures connecting
> to an MS SQL database... basically at seemingly random times the server
> decides that it can't open the requested database (reporting error 4062:
> "Cannot open user default database. Using master database instead"). I've
> so far been unable to track down any useful background to this error
> message; has anyone on this group come across similar problems? Any clues
> as to what might be triggering this sort of fault? More specific details
> follow:
> * In the majority of cases, connection is established correctly (albeit
> sometimes a little slowly).
> * Connections are being made to the local machine, using straightforward,
> static code. The problem isn't something trivial like a mis-typed
> database name, incorrect password etc. Re-running the SAME CODE will
> eventually succeed.
> * The server isn't particularly heavily loaded, and I can perceive no
> pattern to the fault (it seems no more prevalent when the
> server's busy, nor after any particular events).
> * Nothing relevant is documented in the Event Viewer, nor the server logs.
> Am I looking in the right place'
> * We're running SQL Server 2005 Express Edition, latest service pack...
> are there any connection rate limitations on this software? All
> documentation I've seen indicates that there are not, but this behaviour
> almost suggests that there may be...
> * Connecting (from local machine) using php mssql module (latest stable
> version).
> * Although possibly symptomatic of a DoS, there's no other evidence to
> suggest that this is the case (TCP to the service is firewalled).
>
> Would be grateful for any advice on this issue.
> Cheers,
> Alex.
>
>
Make sure the "problem" database isn't configured for auto-close, also
make sure it's not the target for log-shipping, or some other process
that might take it offline to do a restore, etc.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Do you periodically rename, remove, or detach the database?
Do you have any jobs that put the database into single-user mode or
otherwise alter the availability of the database?|||On Fri, 29 Sep 2006 08:14:30 -0500, Tracy McKibben uttered:
[...]
> Make sure the "problem" database isn't configured for auto-close, also
> make sure it's not the target for log-shipping, or some other process
> that might take it offline to do a restore, etc.
Hi Tracy et al,
Thanks for all your advice; so far it looks like the auto-close 'feature'
was most likely the root of my problems (or at least a major factor...);
the system seems to be performing rather more reliably with that disabled.
Cheers,
Alex.|||Alex Craven wrote:
> On Fri, 29 Sep 2006 08:14:30 -0500, Tracy McKibben uttered:
> [...]
>
> Hi Tracy et al,
> Thanks for all your advice; so far it looks like the auto-close 'feature'
> was most likely the root of my problems (or at least a major factor...);
> the system seems to be performing rather more reliably with that disabled.
> Cheers,
> Alex.
>
That auto-close option should NEVER be enabled for a production
database. Another one to watch out for is auto-shrink.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Integrity check failures during maintenance plans

Hi
I have maintenance plans which run weekly to check the integrity of all my
databases. I have the option 'repair minor errors' turned on and I then
recieve the following error when the maintenenace plan runs. I have placed
the database in question into single user mode and run the same task on the
database and it completes successfully. The problem is though that I can run
the integrity check with the 'repair minor errors' option turned off and it
does not pick up any errors.
Any advise on solving this issue would be great?
Check Data and Index Linkage
Error Number: 7919
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
processed. Database needs to be in single user mode.Don't use the repair option. If you have a problem in the database, you want to know about it,
analyze why it happened, make sure you repair the faulty hardware (for example) etc. In short, that
option isn't a good idea to use in an automated job. If you still want to use that option, you
either have to add something to the job that kicks out all users, or live with that error if there
are users connected.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"DeanM" <DeanM@.discussions.microsoft.com> wrote in message
news:AFC39BF6-9706-489A-83B5-BF7F7AD366CA@.microsoft.com...
> Hi
> I have maintenance plans which run weekly to check the integrity of all my
> databases. I have the option 'repair minor errors' turned on and I then
> recieve the following error when the maintenenace plan runs. I have placed
> the database in question into single user mode and run the same task on the
> database and it completes successfully. The problem is though that I can run
> the integrity check with the 'repair minor errors' option turned off and it
> does not pick up any errors.
> Any advise on solving this issue would be great?
>
> Check Data and Index Linkage
> Error Number: 7919
> [Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
> processed. Database needs to be in single user mode.

Integrity check failures during maintenance plans

Hi
I have maintenance plans which run weekly to check the integrity of all my
databases. I have the option 'repair minor errors' turned on and I then
recieve the following error when the maintenenace plan runs. I have placed
the database in question into single user mode and run the same task on the
database and it completes successfully. The problem is though that I can ru
n
the integrity check with the 'repair minor errors' option turned off and it
does not pick up any errors.
Any advise on solving this issue would be great?
Check Data and Index Linkage
Error Number: 7919
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement
not
processed. Database needs to be in single user mode.Don't use the repair option. If you have a problem in the database, you want
to know about it,
analyze why it happened, make sure you repair the faulty hardware (for examp
le) etc. In short, that
option isn't a good idea to use in an automated job. If you still want to us
e that option, you
either have to add something to the job that kicks out all users, or live wi
th that error if there
are users connected.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"DeanM" <DeanM@.discussions.microsoft.com> wrote in message
news:AFC39BF6-9706-489A-83B5-BF7F7AD366CA@.microsoft.com...
> Hi
> I have maintenance plans which run weekly to check the integrity of all my
> databases. I have the option 'repair minor errors' turned on and I then
> recieve the following error when the maintenenace plan runs. I have place
d
> the database in question into single user mode and run the same task on th
e
> database and it completes successfully. The problem is though that I can
run
> the integrity check with the 'repair minor errors' option turned off and i
t
> does not pick up any errors.
> Any advise on solving this issue would be great?
>
> Check Data and Index Linkage
> Error Number: 7919
> [Microsoft][ODBC SQL Server Driver][SQL Server]Repair statemen
t not
> processed. Database needs to be in single user mode.

Integrity check failures during maintenance plans

Hi
I have maintenance plans which run weekly to check the integrity of all my
databases. I have the option 'repair minor errors' turned on and I then
recieve the following error when the maintenenace plan runs. I have placed
the database in question into single user mode and run the same task on the
database and it completes successfully. The problem is though that I can run
the integrity check with the 'repair minor errors' option turned off and it
does not pick up any errors.
Any advise on solving this issue would be great?
Check Data and Index Linkage
Error Number: 7919
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
processed. Database needs to be in single user mode.
Don't use the repair option. If you have a problem in the database, you want to know about it,
analyze why it happened, make sure you repair the faulty hardware (for example) etc. In short, that
option isn't a good idea to use in an automated job. If you still want to use that option, you
either have to add something to the job that kicks out all users, or live with that error if there
are users connected.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"DeanM" <DeanM@.discussions.microsoft.com> wrote in message
news:AFC39BF6-9706-489A-83B5-BF7F7AD366CA@.microsoft.com...
> Hi
> I have maintenance plans which run weekly to check the integrity of all my
> databases. I have the option 'repair minor errors' turned on and I then
> recieve the following error when the maintenenace plan runs. I have placed
> the database in question into single user mode and run the same task on the
> database and it completes successfully. The problem is though that I can run
> the integrity check with the 'repair minor errors' option turned off and it
> does not pick up any errors.
> Any advise on solving this issue would be great?
>
> Check Data and Index Linkage
> Error Number: 7919
> [Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
> processed. Database needs to be in single user mode.

Integrity and Optimization failures

Hi All-
I have a websense log database that the Optimization and Integrity check
jobs fail on. My problem is I cannot determine WHY exactly these jobs have
failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands nothing
appears to be a problem. I even tried running the optimization and integrit
y
checks while the database is in single user mode to no avail. How can I A.
determine what the problem is and B. correct it?
Thank You for your help in advance!
--GREENTHUMB--I suggest you specify a report file for the Maint plan and check for specifi
c error messages in that
report file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:B77C25CE-B5FA-4CF2-AF33-EC4383B0F947@.microsoft.com...
> Hi All-
> I have a websense log database that the Optimization and Integrity check
> jobs fail on. My problem is I cannot determine WHY exactly these jobs hav
e
> failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands nothing
> appears to be a problem. I even tried running the optimization and integr
ity
> checks while the database is in single user mode to no avail. How can I A
.
> determine what the problem is and B. correct it?
> Thank You for your help in advance!
> --GREENTHUMB--|||Hi Tibor-
I have enabled writing to the Event Log and notification to my e-mail but
the error message is extremely vague:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 4/20/2005
Time: 10:13:13 AM
User: N/A
Computer: XXXXXXXXX
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Integrity check for wslogdb55'' (0xAAA25C1534A233429802DCAD2F19BC91) -
Status: Failed - Invoked on: 2005-04-20 10:13:06 - Message: The job failed.
The Job was invoked by User XXX\ADMINISTRATOR. The last step to run was ste
p
1 (Step 1).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"Tibor Karaszi" wrote:

> I suggest you specify a report file for the Maint plan and check for speci
fic error messages in that
> report file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
> news:B77C25CE-B5FA-4CF2-AF33-EC4383B0F947@.microsoft.com...
>
>|||The vagueness of that message is exactly why I suggested to specify in the m
aint plan to create a
report file. In there you will find the error messages from SQL Server.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:67884CB9-7C98-4242-A4AC-900F49ACD0E7@.microsoft.com...[vbcol=seagreen]
> Hi Tibor-
> I have enabled writing to the Event Log and notification to my e-mail but
> the error message is extremely vague:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 4/20/2005
> Time: 10:13:13 AM
> User: N/A
> Computer: XXXXXXXXX
> Description:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
> 'Integrity check for wslogdb55'' (0xAAA25C1534A233429802DCAD2F19BC91) -
> Status: Failed - Invoked on: 2005-04-20 10:13:06 - Message: The job failed
.
> The Job was invoked by User XXX\ADMINISTRATOR. The last step to run was s
tep
> 1 (Step 1).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> "Tibor Karaszi" wrote:
>|||Hi Tibor-
Okay - I enabled the reports and the error given is "database is already
open and can only have one user at a time". However, I checked Single User
Mode *AND* even detached and re-attached and set to Single User to no avail.
I also checked Process info. but that database was not being accessed. Any
ideas?
Thank You!!!
--GREENTHUMB--
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
'ORCRASV005' as 'GWN\services' (trusted)
Starting maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
6:35:03 PM
[1] Database wslogdb55: Check Data and Index Linkage...
[Microsoft SQL-DMO] Error 22285: [SQL-DMO]Database 'wslogdb55' is al
ready
open and can only have one user at a time.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Database 'wslogdb
55' is
already open and can only have one user at a time.
** Execution Time: 0 hrs, 0 mins, 4 secs **
End of maintenance plan 'Integrity check for wslogdb55' on 4/20/2005 6:35:07
PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
"Tibor Karaszi" wrote:

> The vagueness of that message is exactly why I suggested to specify in the
maint plan to create a
> report file. In there you will find the error messages from SQL Server.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
> news:67884CB9-7C98-4242-A4AC-900F49ACD0E7@.microsoft.com...
>
>|||You need to uncheck the checkbox in the maintenance plan that says to
"Repair minor problems" and it should work fine. When you have that checked
it tries to put the db in single user mode and if it can't it errors. You
really don't want it repairing things on it's own anyway.
Andrew J. Kelly SQL MVP
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:432B45E0-DA60-455B-AA32-84EC8FCC3700@.microsoft.com...[vbcol=seagreen]
> Hi Tibor-
> Okay - I enabled the reports and the error given is "database is already
> open and can only have one user at a time". However, I checked Single
> User
> Mode *AND* even detached and re-attached and set to Single User to no
> avail.
> I also checked Process info. but that database was not being accessed.
> Any
> ideas?
> Thank You!!!
> --GREENTHUMB--
>
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
> 'ORCRASV005' as 'GWN\services' (trusted)
> Starting maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
> 6:35:03 PM
> [1] Database wslogdb55: Check Data and Index Linkage...
> [Microsoft SQL-DMO] Error 22285: [SQL-DMO]Database 'wslogdb55' is
already
> open and can only have one user at a time.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'wslog
db55' is
> already open and can only have one user at a time.
> ** Execution Time: 0 hrs, 0 mins, 4 secs **
> End of maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
> 6:35:07
> PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> "Tibor Karaszi" wrote:
>|||Since this job is checking database integrity, is this always a good
practice?

Integrity and Optimization failures

Hi All-
I have a websense log database that the Optimization and Integrity check
jobs fail on. My problem is I cannot determine WHY exactly these jobs have
failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands nothing
appears to be a problem. I even tried running the optimization and integrity
checks while the database is in single user mode to no avail. How can I A.
determine what the problem is and B. correct it?
Thank You for your help in advance!
--GREENTHUMB--I suggest you specify a report file for the Maint plan and check for specific error messages in that
report file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:B77C25CE-B5FA-4CF2-AF33-EC4383B0F947@.microsoft.com...
> Hi All-
> I have a websense log database that the Optimization and Integrity check
> jobs fail on. My problem is I cannot determine WHY exactly these jobs have
> failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands nothing
> appears to be a problem. I even tried running the optimization and integrity
> checks while the database is in single user mode to no avail. How can I A.
> determine what the problem is and B. correct it?
> Thank You for your help in advance!
> --GREENTHUMB--|||Hi Tibor-
I have enabled writing to the Event Log and notification to my e-mail but
the error message is extremely vague:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 4/20/2005
Time: 10:13:13 AM
User: N/A
Computer: XXXXXXXXX
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Integrity check for wslogdb55'' (0xAAA25C1534A233429802DCAD2F19BC91) -
Status: Failed - Invoked on: 2005-04-20 10:13:06 - Message: The job failed.
The Job was invoked by User XXX\ADMINISTRATOR. The last step to run was step
1 (Step 1).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"Tibor Karaszi" wrote:
> I suggest you specify a report file for the Maint plan and check for specific error messages in that
> report file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
> news:B77C25CE-B5FA-4CF2-AF33-EC4383B0F947@.microsoft.com...
> > Hi All-
> >
> > I have a websense log database that the Optimization and Integrity check
> > jobs fail on. My problem is I cannot determine WHY exactly these jobs have
> > failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands nothing
> > appears to be a problem. I even tried running the optimization and integrity
> > checks while the database is in single user mode to no avail. How can I A.
> > determine what the problem is and B. correct it?
> >
> > Thank You for your help in advance!
> >
> > --GREENTHUMB--
>
>|||The vagueness of that message is exactly why I suggested to specify in the maint plan to create a
report file. In there you will find the error messages from SQL Server.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:67884CB9-7C98-4242-A4AC-900F49ACD0E7@.microsoft.com...
> Hi Tibor-
> I have enabled writing to the Event Log and notification to my e-mail but
> the error message is extremely vague:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 4/20/2005
> Time: 10:13:13 AM
> User: N/A
> Computer: XXXXXXXXX
> Description:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
> 'Integrity check for wslogdb55'' (0xAAA25C1534A233429802DCAD2F19BC91) -
> Status: Failed - Invoked on: 2005-04-20 10:13:06 - Message: The job failed.
> The Job was invoked by User XXX\ADMINISTRATOR. The last step to run was step
> 1 (Step 1).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> "Tibor Karaszi" wrote:
>> I suggest you specify a report file for the Maint plan and check for specific error messages in
>> that
>> report file.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
>> news:B77C25CE-B5FA-4CF2-AF33-EC4383B0F947@.microsoft.com...
>> > Hi All-
>> >
>> > I have a websense log database that the Optimization and Integrity check
>> > jobs fail on. My problem is I cannot determine WHY exactly these jobs have
>> > failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands nothing
>> > appears to be a problem. I even tried running the optimization and integrity
>> > checks while the database is in single user mode to no avail. How can I A.
>> > determine what the problem is and B. correct it?
>> >
>> > Thank You for your help in advance!
>> >
>> > --GREENTHUMB--
>>|||Hi Tibor-
Okay - I enabled the reports and the error given is "database is already
open and can only have one user at a time". However, I checked Single User
Mode *AND* even detached and re-attached and set to Single User to no avail.
I also checked Process info. but that database was not being accessed. Any
ideas?
Thank You!!!
--GREENTHUMB--
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
'ORCRASV005' as 'GWN\services' (trusted)
Starting maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
6:35:03 PM
[1] Database wslogdb55: Check Data and Index Linkage...
[Microsoft SQL-DMO] Error 22285: [SQL-DMO]Database 'wslogdb55' is already
open and can only have one user at a time.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Database 'wslogdb55' is
already open and can only have one user at a time.
** Execution Time: 0 hrs, 0 mins, 4 secs **
End of maintenance plan 'Integrity check for wslogdb55' on 4/20/2005 6:35:07
PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
"Tibor Karaszi" wrote:
> The vagueness of that message is exactly why I suggested to specify in the maint plan to create a
> report file. In there you will find the error messages from SQL Server.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
> news:67884CB9-7C98-4242-A4AC-900F49ACD0E7@.microsoft.com...
> > Hi Tibor-
> >
> > I have enabled writing to the Event Log and notification to my e-mail but
> > the error message is extremely vague:
> >
> > Event Type: Warning
> > Event Source: SQLSERVERAGENT
> > Event Category: Job Engine
> > Event ID: 208
> > Date: 4/20/2005
> > Time: 10:13:13 AM
> > User: N/A
> > Computer: XXXXXXXXX
> > Description:
> > SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
> > 'Integrity check for wslogdb55'' (0xAAA25C1534A233429802DCAD2F19BC91) -
> > Status: Failed - Invoked on: 2005-04-20 10:13:06 - Message: The job failed.
> > The Job was invoked by User XXX\ADMINISTRATOR. The last step to run was step
> > 1 (Step 1).
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> I suggest you specify a report file for the Maint plan and check for specific error messages in
> >> that
> >> report file.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
> >> news:B77C25CE-B5FA-4CF2-AF33-EC4383B0F947@.microsoft.com...
> >> > Hi All-
> >> >
> >> > I have a websense log database that the Optimization and Integrity check
> >> > jobs fail on. My problem is I cannot determine WHY exactly these jobs have
> >> > failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands nothing
> >> > appears to be a problem. I even tried running the optimization and integrity
> >> > checks while the database is in single user mode to no avail. How can I A.
> >> > determine what the problem is and B. correct it?
> >> >
> >> > Thank You for your help in advance!
> >> >
> >> > --GREENTHUMB--
> >>
> >>
> >>
>
>|||You need to uncheck the checkbox in the maintenance plan that says to
"Repair minor problems" and it should work fine. When you have that checked
it tries to put the db in single user mode and if it can't it errors. You
really don't want it repairing things on it's own anyway.
--
Andrew J. Kelly SQL MVP
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:432B45E0-DA60-455B-AA32-84EC8FCC3700@.microsoft.com...
> Hi Tibor-
> Okay - I enabled the reports and the error given is "database is already
> open and can only have one user at a time". However, I checked Single
> User
> Mode *AND* even detached and re-attached and set to Single User to no
> avail.
> I also checked Process info. but that database was not being accessed.
> Any
> ideas?
> Thank You!!!
> --GREENTHUMB--
>
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
> 'ORCRASV005' as 'GWN\services' (trusted)
> Starting maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
> 6:35:03 PM
> [1] Database wslogdb55: Check Data and Index Linkage...
> [Microsoft SQL-DMO] Error 22285: [SQL-DMO]Database 'wslogdb55' is already
> open and can only have one user at a time.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'wslogdb55' is
> already open and can only have one user at a time.
> ** Execution Time: 0 hrs, 0 mins, 4 secs **
> End of maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
> 6:35:07
> PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> "Tibor Karaszi" wrote:
>> The vagueness of that message is exactly why I suggested to specify in
>> the maint plan to create a
>> report file. In there you will find the error messages from SQL Server.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
>> news:67884CB9-7C98-4242-A4AC-900F49ACD0E7@.microsoft.com...
>> > Hi Tibor-
>> >
>> > I have enabled writing to the Event Log and notification to my e-mail
>> > but
>> > the error message is extremely vague:
>> >
>> > Event Type: Warning
>> > Event Source: SQLSERVERAGENT
>> > Event Category: Job Engine
>> > Event ID: 208
>> > Date: 4/20/2005
>> > Time: 10:13:13 AM
>> > User: N/A
>> > Computer: XXXXXXXXX
>> > Description:
>> > SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
>> > 'Integrity check for wslogdb55'' (0xAAA25C1534A233429802DCAD2F19BC91) -
>> > Status: Failed - Invoked on: 2005-04-20 10:13:06 - Message: The job
>> > failed.
>> > The Job was invoked by User XXX\ADMINISTRATOR. The last step to run
>> > was step
>> > 1 (Step 1).
>> >
>> > For more information, see Help and Support Center at
>> > http://go.microsoft.com/fwlink/events.asp.
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> I suggest you specify a report file for the Maint plan and check for
>> >> specific error messages in
>> >> that
>> >> report file.
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://www.solidqualitylearning.com/
>> >>
>> >>
>> >> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
>> >> news:B77C25CE-B5FA-4CF2-AF33-EC4383B0F947@.microsoft.com...
>> >> > Hi All-
>> >> >
>> >> > I have a websense log database that the Optimization and Integrity
>> >> > check
>> >> > jobs fail on. My problem is I cannot determine WHY exactly these
>> >> > jobs have
>> >> > failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands
>> >> > nothing
>> >> > appears to be a problem. I even tried running the optimization and
>> >> > integrity
>> >> > checks while the database is in single user mode to no avail. How
>> >> > can I A.
>> >> > determine what the problem is and B. correct it?
>> >> >
>> >> > Thank You for your help in advance!
>> >> >
>> >> > --GREENTHUMB--
>> >>
>> >>
>> >>
>>

Integrity and Optimization failures

Hi All-
I have a websense log database that the Optimization and Integrity check
jobs fail on. My problem is I cannot determine WHY exactly these jobs have
failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands nothing
appears to be a problem. I even tried running the optimization and integrity
checks while the database is in single user mode to no avail. How can I A.
determine what the problem is and B. correct it?
Thank You for your help in advance!
--GREENTHUMB--
I suggest you specify a report file for the Maint plan and check for specific error messages in that
report file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:B77C25CE-B5FA-4CF2-AF33-EC4383B0F947@.microsoft.com...
> Hi All-
> I have a websense log database that the Optimization and Integrity check
> jobs fail on. My problem is I cannot determine WHY exactly these jobs have
> failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands nothing
> appears to be a problem. I even tried running the optimization and integrity
> checks while the database is in single user mode to no avail. How can I A.
> determine what the problem is and B. correct it?
> Thank You for your help in advance!
> --GREENTHUMB--
|||Hi Tibor-
I have enabled writing to the Event Log and notification to my e-mail but
the error message is extremely vague:
Event Type:Warning
Event Source:SQLSERVERAGENT
Event Category:Job Engine
Event ID:208
Date:4/20/2005
Time:10:13:13 AM
User:N/A
Computer:XXXXXXXXX
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Integrity check for wslogdb55'' (0xAAA25C1534A233429802DCAD2F19BC91) -
Status: Failed - Invoked on: 2005-04-20 10:13:06 - Message: The job failed.
The Job was invoked by User XXX\ADMINISTRATOR. The last step to run was step
1 (Step 1).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"Tibor Karaszi" wrote:

> I suggest you specify a report file for the Maint plan and check for specific error messages in that
> report file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
> news:B77C25CE-B5FA-4CF2-AF33-EC4383B0F947@.microsoft.com...
>
>
|||The vagueness of that message is exactly why I suggested to specify in the maint plan to create a
report file. In there you will find the error messages from SQL Server.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:67884CB9-7C98-4242-A4AC-900F49ACD0E7@.microsoft.com...[vbcol=seagreen]
> Hi Tibor-
> I have enabled writing to the Event Log and notification to my e-mail but
> the error message is extremely vague:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 4/20/2005
> Time: 10:13:13 AM
> User: N/A
> Computer: XXXXXXXXX
> Description:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
> 'Integrity check for wslogdb55'' (0xAAA25C1534A233429802DCAD2F19BC91) -
> Status: Failed - Invoked on: 2005-04-20 10:13:06 - Message: The job failed.
> The Job was invoked by User XXX\ADMINISTRATOR. The last step to run was step
> 1 (Step 1).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> "Tibor Karaszi" wrote:
|||Hi Tibor-
Okay - I enabled the reports and the error given is "database is already
open and can only have one user at a time". However, I checked Single User
Mode *AND* even detached and re-attached and set to Single User to no avail.
I also checked Process info. but that database was not being accessed. Any
ideas?
Thank You!!!
--GREENTHUMB--
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
'ORCRASV005' as 'GWN\services' (trusted)
Starting maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
6:35:03 PM
[1] Database wslogdb55: Check Data and Index Linkage...
[Microsoft SQL-DMO] Error 22285: [SQL-DMO]Database 'wslogdb55' is already
open and can only have one user at a time.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Database 'wslogdb55' is
already open and can only have one user at a time.
** Execution Time: 0 hrs, 0 mins, 4 secs **
End of maintenance plan 'Integrity check for wslogdb55' on 4/20/2005 6:35:07
PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
"Tibor Karaszi" wrote:

> The vagueness of that message is exactly why I suggested to specify in the maint plan to create a
> report file. In there you will find the error messages from SQL Server.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
> news:67884CB9-7C98-4242-A4AC-900F49ACD0E7@.microsoft.com...
>
>
|||You need to uncheck the checkbox in the maintenance plan that says to
"Repair minor problems" and it should work fine. When you have that checked
it tries to put the db in single user mode and if it can't it errors. You
really don't want it repairing things on it's own anyway.
Andrew J. Kelly SQL MVP
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:432B45E0-DA60-455B-AA32-84EC8FCC3700@.microsoft.com...[vbcol=seagreen]
> Hi Tibor-
> Okay - I enabled the reports and the error given is "database is already
> open and can only have one user at a time". However, I checked Single
> User
> Mode *AND* even detached and re-attached and set to Single User to no
> avail.
> I also checked Process info. but that database was not being accessed.
> Any
> ideas?
> Thank You!!!
> --GREENTHUMB--
>
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
> 'ORCRASV005' as 'GWN\services' (trusted)
> Starting maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
> 6:35:03 PM
> [1] Database wslogdb55: Check Data and Index Linkage...
> [Microsoft SQL-DMO] Error 22285: [SQL-DMO]Database 'wslogdb55' is already
> open and can only have one user at a time.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'wslogdb55' is
> already open and can only have one user at a time.
> ** Execution Time: 0 hrs, 0 mins, 4 secs **
> End of maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
> 6:35:07
> PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> "Tibor Karaszi" wrote:
|||Since this job is checking database integrity, is this always a good
practice?