I'm attempting to setup reporting services 2005 on a system that has never
had reporting services installed and has a previous SQL 2000 (sp4) instance.
This server is running Windows 2000 SP4.
In the Reporting Services Configuration Manager I have successfully have
completed (check marks) the following steps "Server Status, Report Server
Virtual Directory, Report Manager Virtual Directory, Windows Service
Identity, Email Settings".
My problem is when I attempt to perform the database connection step. I
click connect and type in my computer name and leave in windows
authenticaiton. I am then able to browse the drop down list of my SQL 2000
databases. I then click new, leave the defaults and say OK. It successfully
creates a ReportServer and ReportServerTempDB. I click Apply, however, and
get the following error:
There was a failure applying your change. A virtual directory must first be
created before performing this operation.
I already created both of the virtual directory steps with no issue. I even
went into IIS and see the directories have been created by the Configuration
Manager. Any suggestions?
--
-DanielMaybe its a clue... But it appears on this server that the application log
is being filled up with .NET Runtime Optimization Service entries. I even
cleared the log yesterday and its full again. Here is what an entry looks
like:
Event Type: Information
Event Source: .NET Runtime Optimization Service
Event Category: None
Event ID: 1100
Date: 11/15/2005
Time: 7:12:20 PM
User: N/A
Computer: PUMBAA
Description:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Began
compiling: Microsoft.ReportingServices.Interfaces, Version=9.0.242.0,
Culture=neutral, PublicKeyToken=89845dcd8080cc91
--
-Daniel
Showing posts with label erroneous. Show all posts
Showing posts with label erroneous. Show all posts
Wednesday, February 15, 2012
Erroneous EOF's from Simple Queries
I am testing a VB.NET application using SQL Server Express (2005) and
ADODB.
Multiple instances of the application all access the database. In some
cases, they access and try to update the same row of a table. I am
opening this table with a single row query and
ADODB.LockTypeEnum.adLockPessimistic which I understand to be
equivalent to ROWLOCK.
Sample query:
SELECT Semaphores.* FROM Semaphores WHERE
(((Semaphores.SemaphoreName)='MySem'));
PROBLEM:
This query should always return the one record where this condition is
true. Most of the time it does this. However, sometimes it opens
without error, but the EOF condition is true (even though the query
should return the existing record).
My assumption was that the adLockPessimistic would fail the Open with
an exception if the the row could not be accessed with the lock. Is it
possible I am instead getting an EOF in this case? If not, any ideas
what may cause an EOF on a query that works almost every other time?
Other settings:
m_Connection.CommandTimeout = 5
m_Connection.ConnectionTimeout = 15
SET LOCK_TIMEOUT 0
Note:
Since I know the record is there, I could technically loop on the
erroneous EOF to get around the problem. But I believe I am seeing it
occur in other places where I cannot guarantee the EOF is not valid.
Gary Geniesse"GaryGen" <gary@.garygen.com> wrote in message
news:1146582362.350598.240750@.j73g2000cwa.googlegroups.com...
>I am testing a VB.NET application using SQL Server Express (2005) and
> ADODB.
Why are you using ADODB instead of System.Data.SqlClient?
> Multiple instances of the application all access the database. In some
> cases, they access and try to update the same row of a table. I am
> opening this table with a single row query and
> ADODB.LockTypeEnum.adLockPessimistic which I understand to be
> equivalent to ROWLOCK.
>
Ditch ADODB, use SqlClient, and read the BOL for lock hints and OUTPUT
clause.
No one remembers details of exactly ADO works, and no one wants to figure it
out. But plenty of people here can help with pure SQL solutions.
So what are you trying to acomplish? What are the table structures (DDL
please), and desired results?
David
ADODB.
Multiple instances of the application all access the database. In some
cases, they access and try to update the same row of a table. I am
opening this table with a single row query and
ADODB.LockTypeEnum.adLockPessimistic which I understand to be
equivalent to ROWLOCK.
Sample query:
SELECT Semaphores.* FROM Semaphores WHERE
(((Semaphores.SemaphoreName)='MySem'));
PROBLEM:
This query should always return the one record where this condition is
true. Most of the time it does this. However, sometimes it opens
without error, but the EOF condition is true (even though the query
should return the existing record).
My assumption was that the adLockPessimistic would fail the Open with
an exception if the the row could not be accessed with the lock. Is it
possible I am instead getting an EOF in this case? If not, any ideas
what may cause an EOF on a query that works almost every other time?
Other settings:
m_Connection.CommandTimeout = 5
m_Connection.ConnectionTimeout = 15
SET LOCK_TIMEOUT 0
Note:
Since I know the record is there, I could technically loop on the
erroneous EOF to get around the problem. But I believe I am seeing it
occur in other places where I cannot guarantee the EOF is not valid.
Gary Geniesse"GaryGen" <gary@.garygen.com> wrote in message
news:1146582362.350598.240750@.j73g2000cwa.googlegroups.com...
>I am testing a VB.NET application using SQL Server Express (2005) and
> ADODB.
Why are you using ADODB instead of System.Data.SqlClient?
> Multiple instances of the application all access the database. In some
> cases, they access and try to update the same row of a table. I am
> opening this table with a single row query and
> ADODB.LockTypeEnum.adLockPessimistic which I understand to be
> equivalent to ROWLOCK.
>
Ditch ADODB, use SqlClient, and read the BOL for lock hints and OUTPUT
clause.
No one remembers details of exactly ADO works, and no one wants to figure it
out. But plenty of people here can help with pure SQL solutions.
So what are you trying to acomplish? What are the table structures (DDL
please), and desired results?
David
Erroneous behaviour of COALESCE versus ISNULL??
I am getting very 
of why COALESCE doesnt report NULL as NULL.
Can somebody please explain the behavoiour described below?
Create these tables:
create table dbo.Warrants (
WarrantId bigint not null
constraint WarrantsPKCO primary key nonclustered (WarrantId)
)
go
create table dbo.TextLimitations (
WarrantId bigint not null,
LimitationText text not null,
constraint TextLimitationsPKCO primary key clustered (WarrantId)
)
go
EXECUTE SP_TABLEOPTION 'dbo.TextLimitations',
'TEXT IN ROW', 'ON'
go
Insert this data:
insert into dbo.Warrants values (1)
insert into dbo.Warrants values (2)
go
insert into dbo.TextLimitations values (1, 'a very long text')
go
Run this query:
SELECT W.WarrantId
,Text1 = COALESCE(LimitationText, '')
,Text2 = CASE
WHEN (LimitationText IS NOT NULL) THEN LimitationText
WHEN (LimitationText IS NULL) THEN 'it is null'
ELSE 'else null'
END
,Text3 = ISNULL(LimitationText, '')
FROM dbo.Warrants W
LEFT JOIN dbo.TextLimitations T
ON W.WarrantId = T.WarrantId
WHERE W.WarrantId = 2
go
Why is text1 and text2 NULL?
/kHi
I get
WarrantId Text1 Text2 Text3
-- -- -- --
2 it is null
Which is what I would expect. Text1 and Text3 are both empty strings (which
is different to NULL)
You may want to check version and compatibility settings.
John
"kurt sune" wrote:
> I am getting very of why COALESCE doesnt report NULL as NULL.
> Can somebody please explain the behavoiour described below?
> Create these tables:
> create table dbo.Warrants (
> WarrantId bigint not null
> constraint WarrantsPKCO primary key nonclustered (WarrantId)
> )
> go
> create table dbo.TextLimitations (
> WarrantId bigint not null,
> LimitationText text not null,
> constraint TextLimitationsPKCO primary key clustered (WarrantId)
> )
> go
> EXECUTE SP_TABLEOPTION 'dbo.TextLimitations',
> 'TEXT IN ROW', 'ON'
> go
> Insert this data:
> insert into dbo.Warrants values (1)
> insert into dbo.Warrants values (2)
> go
> insert into dbo.TextLimitations values (1, 'a very long text')
> go
> Run this query:
> SELECT W.WarrantId
> ,Text1 = COALESCE(LimitationText, '')
> ,Text2 = CASE
> WHEN (LimitationText IS NOT NULL) THEN LimitationText
> WHEN (LimitationText IS NULL) THEN 'it is null'
> ELSE 'else null'
> END
> ,Text3 = ISNULL(LimitationText, '')
> FROM dbo.Warrants W
> LEFT JOIN dbo.TextLimitations T
> ON W.WarrantId = T.WarrantId
> WHERE W.WarrantId = 2
> go
>
> Why is text1 and text2 NULL?
>
> /k
>
>|||Addendum:
on two machines I get
2 NULL NULL emptystring
on all others I get
2 emptystring it is null emptystring
What makes the first two machines answer incorrectly?
/k
"kurt sune" <apa@.apa.com> wrote in message
news:uzi99p%23xFHA.3408@.TK2MSFTNGP09.phx.gbl...
> I am getting very of why COALESCE doesnt report NULL as NULL.
> Can somebody please explain the behavoiour described below?
> Create these tables:
> create table dbo.Warrants (
> WarrantId bigint not null
> constraint WarrantsPKCO primary key nonclustered (WarrantId)
> )
> go
> create table dbo.TextLimitations (
> WarrantId bigint not null,
> LimitationText text not null,
> constraint TextLimitationsPKCO primary key clustered (WarrantId)
> )
> go
> EXECUTE SP_TABLEOPTION 'dbo.TextLimitations',
> 'TEXT IN ROW', 'ON'
> go
> Insert this data:
> insert into dbo.Warrants values (1)
> insert into dbo.Warrants values (2)
> go
> insert into dbo.TextLimitations values (1, 'a very long text')
> go
> Run this query:
> SELECT W.WarrantId
> ,Text1 = COALESCE(LimitationText, '')
> ,Text2 = CASE
> WHEN (LimitationText IS NOT NULL) THEN LimitationText
> WHEN (LimitationText IS NULL) THEN 'it is null'
> ELSE 'else null'
> END
> ,Text3 = ISNULL(LimitationText, '')
> FROM dbo.Warrants W
> LEFT JOIN dbo.TextLimitations T
> ON W.WarrantId = T.WarrantId
> WHERE W.WarrantId = 2
> go
>
> Why is text1 and text2 NULL?
>
> /k
>|||On Mon, 3 Oct 2005 09:40:53 +0200, kurt sune wrote:
>Addendum:
>on two machines I get
>2 NULL NULL emptystring
>on all others I get
>2 emptystring it is null emptystring
>
>What makes the first two machines answer incorrectly?
Hi Kurt,
Maybe an older service pack? What's the output of SELECT @.@.VERSION on
each of the machines?
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||One machine that answers correctly:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
One machine that answers wrong:
Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
Nov 19 2001 13:23:50
/k
"Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
news:lp63k1pjr8uh3us6o63abhiirh6lhkfcra@.
4ax.com...
> On Mon, 3 Oct 2005 09:40:53 +0200, kurt sune wrote:
>
> Hi Kurt,
> Maybe an older service pack? What's the output of SELECT @.@.VERSION on
> each of the machines?
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi
After you have upgraded to SP3a or possibly standardised on SP4, check out
differences in the output sp_dboption and sp_dbcmptlevel for each of the
databases.
John
"kurt sune" wrote:
> One machine that answers correctly:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> One machine that answers wrong:
> Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
> /k
>
> "Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
> news:lp63k1pjr8uh3us6o63abhiirh6lhkfcra@.
4ax.com...
>
>|||On Tue, 4 Oct 2005 08:14:09 +0200, kurt sune wrote:
>One machine that answers correctly:
>Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
>One machine that answers wrong:
>Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
Hi Kurt,
Upgrade all your machines to at least SP 3a (version 8.00.760) ASAP.
This will probably remove your bug. But even better is that it will cure
your current vulnerability to the SQL Slammer worm.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Unfortunately I work for a very bureaucratic company and upgrading is a
veeery slow affair.
Thanks for the tip of slammer, now I have three arguments in my
argumentation box.
(the coalesce bug, length of mail message body bug, slammer worm)
/k
"Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
news:jgv5k1dh91hno6m50l1a8gtk85ufumrr66@.
4ax.com...
> On Tue, 4 Oct 2005 08:14:09 +0200, kurt sune wrote:
>
> Hi Kurt,
> Upgrade all your machines to at least SP 3a (version 8.00.760) ASAP.
> This will probably remove your bug. But even better is that it will cure
> your current vulnerability to the SQL Slammer worm.
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi Hugo
Is there a KB for this COALESCE bug?
John
"Hugo Kornelis" wrote:
> On Tue, 4 Oct 2005 08:14:09 +0200, kurt sune wrote:
>
> Hi Kurt,
> Upgrade all your machines to at least SP 3a (version 8.00.760) ASAP.
> This will probably remove your bug. But even better is that it will cure
> your current vulnerability to the SQL Slammer worm.
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)
>|||Also have a look at
http://toponewithties.blogspot.com/...es.blogspot.com
"kurt sune" <apa@.apa.com> wrote in message
news:eovaSQXyFHA.3312@.TK2MSFTNGP09.phx.gbl...
> Unfortunately I work for a very bureaucratic company and upgrading is a
> veeery slow affair.
> Thanks for the tip of slammer, now I have three arguments in my
> argumentation box.
> (the coalesce bug, length of mail message body bug, slammer worm)
> /k
>
> "Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
> news:jgv5k1dh91hno6m50l1a8gtk85ufumrr66@.
4ax.com...
>
of why COALESCE doesnt report NULL as NULL.Can somebody please explain the behavoiour described below?
Create these tables:
create table dbo.Warrants (
WarrantId bigint not null
constraint WarrantsPKCO primary key nonclustered (WarrantId)
)
go
create table dbo.TextLimitations (
WarrantId bigint not null,
LimitationText text not null,
constraint TextLimitationsPKCO primary key clustered (WarrantId)
)
go
EXECUTE SP_TABLEOPTION 'dbo.TextLimitations',
'TEXT IN ROW', 'ON'
go
Insert this data:
insert into dbo.Warrants values (1)
insert into dbo.Warrants values (2)
go
insert into dbo.TextLimitations values (1, 'a very long text')
go
Run this query:
SELECT W.WarrantId
,Text1 = COALESCE(LimitationText, '')
,Text2 = CASE
WHEN (LimitationText IS NOT NULL) THEN LimitationText
WHEN (LimitationText IS NULL) THEN 'it is null'
ELSE 'else null'
END
,Text3 = ISNULL(LimitationText, '')
FROM dbo.Warrants W
LEFT JOIN dbo.TextLimitations T
ON W.WarrantId = T.WarrantId
WHERE W.WarrantId = 2
go
Why is text1 and text2 NULL?
/kHi
I get
WarrantId Text1 Text2 Text3
-- -- -- --
2 it is null
Which is what I would expect. Text1 and Text3 are both empty strings (which
is different to NULL)
You may want to check version and compatibility settings.
John
"kurt sune" wrote:
> I am getting very
of why COALESCE doesnt report NULL as NULL.> Can somebody please explain the behavoiour described below?
> Create these tables:
> create table dbo.Warrants (
> WarrantId bigint not null
> constraint WarrantsPKCO primary key nonclustered (WarrantId)
> )
> go
> create table dbo.TextLimitations (
> WarrantId bigint not null,
> LimitationText text not null,
> constraint TextLimitationsPKCO primary key clustered (WarrantId)
> )
> go
> EXECUTE SP_TABLEOPTION 'dbo.TextLimitations',
> 'TEXT IN ROW', 'ON'
> go
> Insert this data:
> insert into dbo.Warrants values (1)
> insert into dbo.Warrants values (2)
> go
> insert into dbo.TextLimitations values (1, 'a very long text')
> go
> Run this query:
> SELECT W.WarrantId
> ,Text1 = COALESCE(LimitationText, '')
> ,Text2 = CASE
> WHEN (LimitationText IS NOT NULL) THEN LimitationText
> WHEN (LimitationText IS NULL) THEN 'it is null'
> ELSE 'else null'
> END
> ,Text3 = ISNULL(LimitationText, '')
> FROM dbo.Warrants W
> LEFT JOIN dbo.TextLimitations T
> ON W.WarrantId = T.WarrantId
> WHERE W.WarrantId = 2
> go
>
> Why is text1 and text2 NULL?
>
> /k
>
>|||Addendum:
on two machines I get
2 NULL NULL emptystring
on all others I get
2 emptystring it is null emptystring
What makes the first two machines answer incorrectly?
/k
"kurt sune" <apa@.apa.com> wrote in message
news:uzi99p%23xFHA.3408@.TK2MSFTNGP09.phx.gbl...
> I am getting very
of why COALESCE doesnt report NULL as NULL.> Can somebody please explain the behavoiour described below?
> Create these tables:
> create table dbo.Warrants (
> WarrantId bigint not null
> constraint WarrantsPKCO primary key nonclustered (WarrantId)
> )
> go
> create table dbo.TextLimitations (
> WarrantId bigint not null,
> LimitationText text not null,
> constraint TextLimitationsPKCO primary key clustered (WarrantId)
> )
> go
> EXECUTE SP_TABLEOPTION 'dbo.TextLimitations',
> 'TEXT IN ROW', 'ON'
> go
> Insert this data:
> insert into dbo.Warrants values (1)
> insert into dbo.Warrants values (2)
> go
> insert into dbo.TextLimitations values (1, 'a very long text')
> go
> Run this query:
> SELECT W.WarrantId
> ,Text1 = COALESCE(LimitationText, '')
> ,Text2 = CASE
> WHEN (LimitationText IS NOT NULL) THEN LimitationText
> WHEN (LimitationText IS NULL) THEN 'it is null'
> ELSE 'else null'
> END
> ,Text3 = ISNULL(LimitationText, '')
> FROM dbo.Warrants W
> LEFT JOIN dbo.TextLimitations T
> ON W.WarrantId = T.WarrantId
> WHERE W.WarrantId = 2
> go
>
> Why is text1 and text2 NULL?
>
> /k
>|||On Mon, 3 Oct 2005 09:40:53 +0200, kurt sune wrote:
>Addendum:
>on two machines I get
>2 NULL NULL emptystring
>on all others I get
>2 emptystring it is null emptystring
>
>What makes the first two machines answer incorrectly?
Hi Kurt,
Maybe an older service pack? What's the output of SELECT @.@.VERSION on
each of the machines?
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||One machine that answers correctly:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
One machine that answers wrong:
Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
Nov 19 2001 13:23:50
/k
"Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
news:lp63k1pjr8uh3us6o63abhiirh6lhkfcra@.
4ax.com...
> On Mon, 3 Oct 2005 09:40:53 +0200, kurt sune wrote:
>
> Hi Kurt,
> Maybe an older service pack? What's the output of SELECT @.@.VERSION on
> each of the machines?
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi
After you have upgraded to SP3a or possibly standardised on SP4, check out
differences in the output sp_dboption and sp_dbcmptlevel for each of the
databases.
John
"kurt sune" wrote:
> One machine that answers correctly:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> One machine that answers wrong:
> Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
> /k
>
> "Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
> news:lp63k1pjr8uh3us6o63abhiirh6lhkfcra@.
4ax.com...
>
>|||On Tue, 4 Oct 2005 08:14:09 +0200, kurt sune wrote:
>One machine that answers correctly:
>Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
>One machine that answers wrong:
>Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
Hi Kurt,
Upgrade all your machines to at least SP 3a (version 8.00.760) ASAP.
This will probably remove your bug. But even better is that it will cure
your current vulnerability to the SQL Slammer worm.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Unfortunately I work for a very bureaucratic company and upgrading is a
veeery slow affair.
Thanks for the tip of slammer, now I have three arguments in my
argumentation box.
(the coalesce bug, length of mail message body bug, slammer worm)
/k
"Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
news:jgv5k1dh91hno6m50l1a8gtk85ufumrr66@.
4ax.com...
> On Tue, 4 Oct 2005 08:14:09 +0200, kurt sune wrote:
>
> Hi Kurt,
> Upgrade all your machines to at least SP 3a (version 8.00.760) ASAP.
> This will probably remove your bug. But even better is that it will cure
> your current vulnerability to the SQL Slammer worm.
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi Hugo
Is there a KB for this COALESCE bug?
John
"Hugo Kornelis" wrote:
> On Tue, 4 Oct 2005 08:14:09 +0200, kurt sune wrote:
>
> Hi Kurt,
> Upgrade all your machines to at least SP 3a (version 8.00.760) ASAP.
> This will probably remove your bug. But even better is that it will cure
> your current vulnerability to the SQL Slammer worm.
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)
>|||Also have a look at
http://toponewithties.blogspot.com/...es.blogspot.com
"kurt sune" <apa@.apa.com> wrote in message
news:eovaSQXyFHA.3312@.TK2MSFTNGP09.phx.gbl...
> Unfortunately I work for a very bureaucratic company and upgrading is a
> veeery slow affair.
> Thanks for the tip of slammer, now I have three arguments in my
> argumentation box.
> (the coalesce bug, length of mail message body bug, slammer worm)
> /k
>
> "Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
> news:jgv5k1dh91hno6m50l1a8gtk85ufumrr66@.
4ax.com...
>
Erroneous "Pending System Reboot" SCC result...
I am installing a SQL 2005 active/active cluster. The system consistency
checker is reporting that a "pending system restart" is needed, but I have
restarted multiple times on both nodes.
because of this, I am unable to failover the SQL instance to the node that
had the SCC error detected. Is there something I can do to correct this
erroneous reporting of a pending restart?
Thanks very much
Chris
Check the Registry for the following:
1- run regedit
2- go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session Manager
3- Do you see a "PendingFileRenameOperations" key? if so, delete it.
4- You need to check this on both nodes
Usually, rebooting the server should clear the PendingFileRenameOperations
key but just double check if it still exist.
Ayad Shammout
"GaTech_Geek" <GaTechGeek@.discussions.microsoft.com> wrote in message
news:D64EB964-9E77-4030-B13D-F93E021A07C8@.microsoft.com...
>I am installing a SQL 2005 active/active cluster. The system consistency
> checker is reporting that a "pending system restart" is needed, but I have
> restarted multiple times on both nodes.
> because of this, I am unable to failover the SQL instance to the node that
> had the SCC error detected. Is there something I can do to correct this
> erroneous reporting of a pending restart?
> Thanks very much
> Chris
checker is reporting that a "pending system restart" is needed, but I have
restarted multiple times on both nodes.
because of this, I am unable to failover the SQL instance to the node that
had the SCC error detected. Is there something I can do to correct this
erroneous reporting of a pending restart?
Thanks very much
Chris
Check the Registry for the following:
1- run regedit
2- go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session Manager
3- Do you see a "PendingFileRenameOperations" key? if so, delete it.
4- You need to check this on both nodes
Usually, rebooting the server should clear the PendingFileRenameOperations
key but just double check if it still exist.
Ayad Shammout
"GaTech_Geek" <GaTechGeek@.discussions.microsoft.com> wrote in message
news:D64EB964-9E77-4030-B13D-F93E021A07C8@.microsoft.com...
>I am installing a SQL 2005 active/active cluster. The system consistency
> checker is reporting that a "pending system restart" is needed, but I have
> restarted multiple times on both nodes.
> because of this, I am unable to failover the SQL instance to the node that
> had the SCC error detected. Is there something I can do to correct this
> erroneous reporting of a pending restart?
> Thanks very much
> Chris
Subscribe to:
Posts (Atom)