We are running SQL two node active-active cluster. Since yester day It failed over because of â'BPool::map: No remappable address foundâ' error.
Did some one face the problem? As this is a critical server, we need to fix the same at the earliest. Your valuable input is required.
Is this because of low memory or is it a bug'
( Sql Instance is running with 8GB memory and total OS memory is 15GB)
Following is the part of Logs before fail over:
Todays log:
2004-03-04 11:43:14.30 spid77 BPool::Map: no remappable address found.
2004-03-04 11:43:14.30 spid6 BPool::Map: no remappable address found.
2004-03-04 11:43:14.30 spid85 BPool::Map: no remappable address found.
2004-03-04 11:43:14.30 spid79 BPool::Map: no remappable address found.
2004-03-04 11:43:14.31 spid55 BPool::Map: no remappable address found.
2004-03-04 11:43:14.44 spid6 Buffer Distribution: Stolen=191234 Free=1498 Procedures=204
Inram=0 Dirty=19842 Kept=0
I/O=67, Latched=949, Other=814174
2004-03-04 11:43:14.44 spid6 Buffer Counts: Commited=1027968 Target=1027968 Hashed=835036
InternalReservation=213 ExternalReservation=22524 Min Free=1024
2004-03-04 11:43:14.44 spid6 Procedure Cache: TotalProcs=20 TotalPages=204 InUsePages=202
2004-03-04 11:43:14.44 spid6 Dynamic Memory Manager: Stolen=124482 OS Reserved=1616
OS Committed=1592
OS In Use=1567
Query Plan=560 Optimizer=0
General=12887
Utilities=1334 Connection=249
2004-03-04 11:43:14.44 spid6 Global Memory Objects: Resource=2068 Locks=112941
SQLCache=82 Replication=2
LockBytes=2 ServerGlobal=44
Xact=42
2004-03-04 11:43:14.44 spid6 Query Memory Manager: Grants=5 Waiting=7 Maximum=89476 Available=0
2004-03-04 11:43:14.44 spid79 Buffer Distribution: Stolen=191226 Free=1506 Procedures=204
Inram=0 Dirty=19842 Kept=0
I/O=67, Latched=948, Other=814175
2004-03-04 11:43:14.44 spid79 Buffer Counts: Commited=1027968 Target=1027968 Hashed=835028
InternalReservation=213 ExternalReservation=22524 Min Free=1024
2004-03-04 11:43:14.44 spid79 Procedure Cache: TotalProcs=20 TotalPages=204 InUsePages=202
2004-03-04 11:43:14.44 spid79 Dynamic Memory Manager: Stolen=124482 OS Reserved=1616
OS Committed=1592
OS In Use=1567
Query Plan=560 Optimizer=0
General=12887
Utilities=1334 Connection=249
Yesterday log:
2004-03-03 14:50:27.72 spid90 BPool::Map: no remappable address found.
2004-03-03 14:50:27.74 spid109 BPool::Map: no remappable address found.
2004-03-03 14:50:27.74 spid56 BPool::Map: no remappable address found.
2004-03-03 14:50:27.74 spid52 BPool::Map: no remappable address found.
2004-03-03 14:50:27.75 spid105 BPool::Map: no remappable address found.
2004-03-03 14:50:27.75 spid104 BPool::Map: no remappable address found.
2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
2004-03-03 14:50:27.80 spid111 BPool::Map: no remappable address found.
2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
2004-03-03 14:50:27.89 spid109 Buffer Distribution: Stolen=191002 Free=1171 Procedures=174
2004-03-03 14:50:27.89 spid56 Buffer Distribution: Stolen=191002 Free=1171 Procedures=174
Inram=0 Dirty=10927 Kept=0
I/O=0, Latched=1214, Other=823480
Inram=0 Dirty=10927 Kept=0
I/O=0, Latched=1214, Other=823480
2004-03-03 14:50:27.91 spid56 Buffer Counts: Commited=1027968 Target=1027968 Hashed=835622
InternalReservation=250 ExternalReservation=2278 Min Free=1024
2004-03-03 14:50:27.91 spid109 Buffer Counts: Commited=1027968 Target=1027968 Hashed=835622
InternalReservation=250 ExternalReservation=2278 Min Free=1024
2004-03-03 14:50:27.91 spid56 Procedure Cache: TotalProcs=21 TotalPages=174 InUsePages=170
2004-03-03 14:50:27.91 spid109 Procedure Cache: TotalProcs=21 TotalPages=174 InUsePages=170
2004-03-03 14:50:27.91 spid56 Dynamic Memory Manager: Stolen=117319 OS Reserved=1632
OS Committed=1608
OS In Use=1599
Query Plan=865 Optimizer=14
General=5999
Utilities=838 Connection=403
2004-03-03 14:50:27.91 spid109 Dynamic Memory Manager: Stolen=117319 OS Reserved=1632
OS Committed=1608
OS In Use=1599
Query Plan=865 Optimizer=14
General=5999
Utilities=838 Connection=403
2004-03-03 14:50:27.91 spid56 Global Memory Objects: Resource=3621 Locks=112718
SQLCache=94 Replication=2
LockBytes=2 ServerGlobal=62
Xact=74
2004-03-03 14:50:27.91 spid109 Global Memory Objects: Resource=3621 Locks=112718
SQLCache=94 Replication=2
LockBytes=2 ServerGlobal=62
Xact=74
2004-03-03 14:50:27.91 spid56 Query Memory Manager: Grants=5 Waiting=10 Maximum=76134 Available=0
2004-03-03 14:50:27.91 spid109 Query Memory Manager: Grants=5 Waiting=10 Maximum=76134 Available=0
2004-03-03 14:50:27.91 spid104 Buffer Distribution: Stolen=191003 Free=1170 Procedures=174
Inram=0 Dirty=10927 Kept=0
I/O=0, Latched=1214, Other=823480
2004-03-03 14:50:27.91 spid104 Buffer Counts: Commited=1027968 Target=1027968 Hashed=835621
InternalReservation=250 ExternalReservation=2278 Min Free=1024
2004-03-03 14:50:27.91 spid104 Procedure Cache: TotalProcs=21 TotalPages=174 InUsePages=170
2004-03-03 14:50:27.91 spid104 Dynamic Memory Manager: Stolen=117319 OS Reserved=1632
OS Committed=1608
OS In Use=1599
Query Plan=865 Optimizer=14
General=5999
Utilities=838 Connection=403
2004-03-03 14:50:27.91 spid104 Global Memory Objects: Resource=3621 Locks=112718
SQLCache=94 Replication=2
LockBytes=2 ServerGlobal=62
Xact=74I would contact PSS about this one
http://support.microsoft.com/default.aspx?scid=fh;en-us;Prodoffer41a
I can't recall seeing this before but it sounds like there may be an issue
with AWE. Do you have both /3GB and /PAE enabled or just /PAE in boot.ini ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Hemant" <anonymous@.discussions.microsoft.com> wrote in message
news:2F94E672-07F4-4554-9D0D-BC2F7CC3E164@.microsoft.com...
> We are running SQL two node active-active cluster. Since yester day It
failed over because of "BPool::map: No remappable address found" error.
> Did some one face the problem? As this is a critical server, we need to
fix the same at the earliest. Your valuable input is required.
> Is this because of low memory or is it a bug'
> ( Sql Instance is running with 8GB memory and total OS memory is 15GB)
> Following is the part of Logs before fail over:
> Todays log:
>
> 2004-03-04 11:43:14.30 spid77 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.30 spid6 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.30 spid85 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.30 spid79 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.31 spid55 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.44 spid6 Buffer Distribution: Stolen=191234
Free=1498 Procedures=204
> Inram=0 Dirty=19842 Kept=0
> I/O=67, Latched=949, Other=814174
> 2004-03-04 11:43:14.44 spid6 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835036
> InternalReservation=213 ExternalReservation=22524
Min Free=1024
> 2004-03-04 11:43:14.44 spid6 Procedure Cache: TotalProcs TotalPages=204 InUsePages=202
> 2004-03-04 11:43:14.44 spid6 Dynamic Memory Manager: Stolen=124482 OS
Reserved=1616
> OS Committed=1592
> OS In Use=1567
> Query Plan=560 Optimizer=0
> General=12887
> Utilities=1334 Connection=249
> 2004-03-04 11:43:14.44 spid6 Global Memory Objects: Resource=2068
Locks=112941
> SQLCache=82 Replication=2
> LockBytes=2 ServerGlobal=44
> Xact=42
> 2004-03-04 11:43:14.44 spid6 Query Memory Manager: Grants=5 Waiting=7
Maximum=89476 Available=0
> 2004-03-04 11:43:14.44 spid79 Buffer Distribution: Stolen=191226
Free=1506 Procedures=204
> Inram=0 Dirty=19842 Kept=0
> I/O=67, Latched=948, Other=814175
> 2004-03-04 11:43:14.44 spid79 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835028
> InternalReservation=213 ExternalReservation=22524
Min Free=1024
> 2004-03-04 11:43:14.44 spid79 Procedure Cache: TotalProcs TotalPages=204 InUsePages=202
> 2004-03-04 11:43:14.44 spid79 Dynamic Memory Manager: Stolen=124482 OS
Reserved=1616
> OS Committed=1592
> OS In Use=1567
> Query Plan=560 Optimizer=0
> General=12887
> Utilities=1334 Connection=249
> Yesterday log:
> 2004-03-03 14:50:27.72 spid90 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.74 spid109 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.74 spid56 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.74 spid52 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.75 spid105 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.75 spid104 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.80 spid111 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.89 spid109 Buffer Distribution: Stolen=191002
Free=1171 Procedures=174
> 2004-03-03 14:50:27.89 spid56 Buffer Distribution: Stolen=191002
Free=1171 Procedures=174
> Inram=0 Dirty=10927 Kept=0
> I/O=0, Latched=1214, Other=823480
> Inram=0 Dirty=10927 Kept=0
> I/O=0, Latched=1214, Other=823480
> 2004-03-03 14:50:27.91 spid56 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835622
> InternalReservation=250 ExternalReservation=2278
Min Free=1024
> 2004-03-03 14:50:27.91 spid109 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835622
> InternalReservation=250 ExternalReservation=2278
Min Free=1024
> 2004-03-03 14:50:27.91 spid56 Procedure Cache: TotalProcs=21
TotalPages=174 InUsePages=170
> 2004-03-03 14:50:27.91 spid109 Procedure Cache: TotalProcs=21
TotalPages=174 InUsePages=170
> 2004-03-03 14:50:27.91 spid56 Dynamic Memory Manager: Stolen=117319 OS
Reserved=1632
> OS Committed=1608
> OS In Use=1599
> Query Plan=865 Optimizer=14
> General=5999
> Utilities=838 Connection=403
> 2004-03-03 14:50:27.91 spid109 Dynamic Memory Manager: Stolen=117319 OS
Reserved=1632
> OS Committed=1608
> OS In Use=1599
> Query Plan=865 Optimizer=14
> General=5999
> Utilities=838 Connection=403
> 2004-03-03 14:50:27.91 spid56 Global Memory Objects: Resource=3621
Locks=112718
> SQLCache=94 Replication=2
> LockBytes=2 ServerGlobal=62
> Xact=74
> 2004-03-03 14:50:27.91 spid109 Global Memory Objects: Resource=3621
Locks=112718
> SQLCache=94 Replication=2
> LockBytes=2 ServerGlobal=62
> Xact=74
> 2004-03-03 14:50:27.91 spid56 Query Memory Manager: Grants=5
Waiting=10 Maximum=76134 Available=0
> 2004-03-03 14:50:27.91 spid109 Query Memory Manager: Grants=5
Waiting=10 Maximum=76134 Available=0
> 2004-03-03 14:50:27.91 spid104 Buffer Distribution: Stolen=191003
Free=1170 Procedures=174
> Inram=0 Dirty=10927 Kept=0
> I/O=0, Latched=1214, Other=823480
> 2004-03-03 14:50:27.91 spid104 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835621
> InternalReservation=250 ExternalReservation=2278
Min Free=1024
> 2004-03-03 14:50:27.91 spid104 Procedure Cache: TotalProcs=21
TotalPages=174 InUsePages=170
> 2004-03-03 14:50:27.91 spid104 Dynamic Memory Manager: Stolen=117319 OS
Reserved=1632
> OS Committed=1608
> OS In Use=1599
> Query Plan=865 Optimizer=14
> General=5999
> Utilities=838 Connection=403
> 2004-03-03 14:50:27.91 spid104 Global Memory Objects: Resource=3621
Locks=112718
> SQLCache=94 Replication=2
> LockBytes=2 ServerGlobal=62
> Xact=74
>
Showing posts with label node. Show all posts
Showing posts with label node. Show all posts
Tuesday, March 27, 2012
ERROR: BPool::map: No remappable address
We are running SQL two node active-active cluster. Since yester day It faile
d over because of “BPool::map: No remappable address found” error.
Did some one face the problem? As this is a critical server, we need to fi
x the same at the earliest. Your valuable input is required.
Is this because of low memory or is it a bug'
( Sql Instance is running with 8GB memory and total OS memory is 15GB)
Following is the part of Logs before fail over:
Todays log:
2004-03-04 11:43:14.30 spid77 BPool::Map: no remappable address found.
2004-03-04 11:43:14.30 spid6 BPool::Map: no remappable address found.
2004-03-04 11:43:14.30 spid85 BPool::Map: no remappable address found.
2004-03-04 11:43:14.30 spid79 BPool::Map: no remappable address found.
2004-03-04 11:43:14.31 spid55 BPool::Map: no remappable address found.
2004-03-04 11:43:14.44 spid6 Buffer Distribution: Stolen=191234 Free=14
98 Procedures=204
Inram=0 Dirty=19842 Kept=0
I/O=67, Latched=949, Other=814174
2004-03-04 11:43:14.44 spid6 Buffer Counts: Commited=1027968 Target=102
7968 Hashed=835036
InternalReservation=213 ExternalReservation=22524 Min Free=1024
2004-03-04 11:43:14.44 spid6 Procedure Cache: TotalProcs=20 TotalPages=
204 InUsePages=202
2004-03-04 11:43:14.44 spid6 Dynamic Memory Manager: Stolen=124482 OS R
eserved=1616
OS Committed=1592
OS In Use=1567
Query Plan=560 Optimizer=0
General=12887
Utilities=1334 Connection=249
2004-03-04 11:43:14.44 spid6 Global Memory Objects: Resource=2068 Locks
=112941
SQLCache=82 Replication=2
LockBytes=2 ServerGlobal=44
Xact=42
2004-03-04 11:43:14.44 spid6 Query Memory Manager: Grants=5 Waiting=7 M
aximum=89476 Available=0
2004-03-04 11:43:14.44 spid79 Buffer Distribution: Stolen=191226 Free=15
06 Procedures=204
Inram=0 Dirty=19842 Kept=0
I/O=67, Latched=948, Other=814175
2004-03-04 11:43:14.44 spid79 Buffer Counts: Commited=1027968 Target=102
7968 Hashed=835028
InternalReservation=213 ExternalReservation=22524 Min Free=1024
2004-03-04 11:43:14.44 spid79 Procedure Cache: TotalProcs=20 TotalPages=
204 InUsePages=202
2004-03-04 11:43:14.44 spid79 Dynamic Memory Manager: Stolen=124482 OS R
eserved=1616
OS Committed=1592
OS In Use=1567
Query Plan=560 Optimizer=0
General=12887
Utilities=1334 Connection=249
Yesterday log:
2004-03-03 14:50:27.72 spid90 BPool::Map: no remappable address found.
2004-03-03 14:50:27.74 spid109 BPool::Map: no remappable address found.
2004-03-03 14:50:27.74 spid56 BPool::Map: no remappable address found.
2004-03-03 14:50:27.74 spid52 BPool::Map: no remappable address found.
2004-03-03 14:50:27.75 spid105 BPool::Map: no remappable address found.
2004-03-03 14:50:27.75 spid104 BPool::Map: no remappable address found.
2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
2004-03-03 14:50:27.80 spid111 BPool::Map: no remappable address found.
2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
2004-03-03 14:50:27.89 spid109 Buffer Distribution: Stolen=191002 Free=11
71 Procedures=174
2004-03-03 14:50:27.89 spid56 Buffer Distribution: Stolen=191002 Free=11
71 Procedures=174
Inram=0 Dirty=10927 Kept=0
I/O=0, Latched=1214, Other=823480
Inram=0 Dirty=10927 Kept=0
I/O=0, Latched=1214, Other=823480
2004-03-03 14:50:27.91 spid56 Buffer Counts: Commited=1027968 Target=102
7968 Hashed=835622
InternalReservation=250 ExternalReservation=2278 Min Free=1024
2004-03-03 14:50:27.91 spid109 Buffer Counts: Commited=1027968 Target=102
7968 Hashed=835622
InternalReservation=250 ExternalReservation=2278 Min Free=1024
2004-03-03 14:50:27.91 spid56 Procedure Cache: TotalProcs=21 TotalPages=
174 InUsePages=170
2004-03-03 14:50:27.91 spid109 Procedure Cache: TotalProcs=21 TotalPages=
174 InUsePages=170
2004-03-03 14:50:27.91 spid56 Dynamic Memory Manager: Stolen=117319 OS R
eserved=1632
OS Committed=1608
OS In Use=1599
Query Plan=865 Optimizer=14
General=5999
Utilities=838 Connection=403
2004-03-03 14:50:27.91 spid109 Dynamic Memory Manager: Stolen=117319 OS R
eserved=1632
OS Committed=1608
OS In Use=1599
Query Plan=865 Optimizer=14
General=5999
Utilities=838 Connection=403
2004-03-03 14:50:27.91 spid56 Global Memory Objects: Resource=3621 Locks
=112718
SQLCache=94 Replication=2
LockBytes=2 ServerGlobal=62
Xact=74
2004-03-03 14:50:27.91 spid109 Global Memory Objects: Resource=3621 Locks
=112718
SQLCache=94 Replication=2
LockBytes=2 ServerGlobal=62
Xact=74
2004-03-03 14:50:27.91 spid56 Query Memory Manager: Grants=5 Waiting=10
Maximum=76134 Available=0
2004-03-03 14:50:27.91 spid109 Query Memory Manager: Grants=5 Waiting=10
Maximum=76134 Available=0
2004-03-03 14:50:27.91 spid104 Buffer Distribution: Stolen=191003 Free=11
70 Procedures=174
Inram=0 Dirty=10927 Kept=0
I/O=0, Latched=1214, Other=823480
2004-03-03 14:50:27.91 spid104 Buffer Counts: Commited=1027968 Target=102
7968 Hashed=835621
InternalReservation=250 ExternalReservation=2278 Min Free=1024
2004-03-03 14:50:27.91 spid104 Procedure Cache: TotalProcs=21 TotalPages=
174 InUsePages=170
2004-03-03 14:50:27.91 spid104 Dynamic Memory Manager: Stolen=117319 OS R
eserved=1632
OS Committed=1608
OS In Use=1599
Query Plan=865 Optimizer=14
General=5999
Utilities=838 Connection=403
2004-03-03 14:50:27.91 spid104 Global Memory Objects: Resource=3621 Locks
=112718
SQLCache=94 Replication=2
LockBytes=2 ServerGlobal=62
Xact=74I would contact PSS about this one
http://support.microsoft.com/defaul...us;Prodoffer41a
I can't recall seeing this before but it sounds like there may be an issue
with AWE. Do you have both /3GB and /PAE enabled or just /PAE in boot.ini ?
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Hemant" <anonymous@.discussions.microsoft.com> wrote in message
news:2F94E672-07F4-4554-9D0D-BC2F7CC3E164@.microsoft.com...
> We are running SQL two node active-active cluster. Since yester day It
failed over because of "BPool::map: No remappable address found" error.
> Did some one face the problem? As this is a critical server, we need to
fix the same at the earliest. Your valuable input is required.
> Is this because of low memory or is it a bug'
> ( Sql Instance is running with 8GB memory and total OS memory is 15GB)
> Following is the part of Logs before fail over:
> Todays log:
>
> 2004-03-04 11:43:14.30 spid77 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.30 spid6 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.30 spid85 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.30 spid79 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.31 spid55 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.44 spid6 Buffer Distribution: Stolen=191234
Free=1498 Procedures=204
> Inram=0 Dirty=19842 Kept=0
> I/O=67, Latched=949, Other=814174
> 2004-03-04 11:43:14.44 spid6 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835036
> InternalReservation=213 ExternalReservation=22524
Min Free=1024
> 2004-03-04 11:43:14.44 spid6 Procedure Cache: TotalProcs=20
TotalPages=204 InUsePages=202
> 2004-03-04 11:43:14.44 spid6 Dynamic Memory Manager: Stolen=124482 OS
Reserved=1616
> OS Committed=1592
> OS In Use=1567
> Query Plan=560 Optimizer=0
> General=12887
> Utilities=1334 Connection=249
> 2004-03-04 11:43:14.44 spid6 Global Memory Objects: Resource=2068
Locks=112941
> SQLCache=82 Replication=2
> LockBytes=2 ServerGlobal=44
> Xact=42
> 2004-03-04 11:43:14.44 spid6 Query Memory Manager: Grants=5 Waiting=7
Maximum=89476 Available=0
> 2004-03-04 11:43:14.44 spid79 Buffer Distribution: Stolen=191226
Free=1506 Procedures=204
> Inram=0 Dirty=19842 Kept=0
> I/O=67, Latched=948, Other=814175
> 2004-03-04 11:43:14.44 spid79 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835028
> InternalReservation=213 ExternalReservation=22524
Min Free=1024
> 2004-03-04 11:43:14.44 spid79 Procedure Cache: TotalProcs=20
TotalPages=204 InUsePages=202
> 2004-03-04 11:43:14.44 spid79 Dynamic Memory Manager: Stolen=124482 OS
Reserved=1616
> OS Committed=1592
> OS In Use=1567
> Query Plan=560 Optimizer=0
> General=12887
> Utilities=1334 Connection=249
> Yesterday log:
> 2004-03-03 14:50:27.72 spid90 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.74 spid109 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.74 spid56 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.74 spid52 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.75 spid105 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.75 spid104 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.80 spid111 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.89 spid109 Buffer Distribution: Stolen=191002
Free=1171 Procedures=174
> 2004-03-03 14:50:27.89 spid56 Buffer Distribution: Stolen=191002
Free=1171 Procedures=174
> Inram=0 Dirty=10927 Kept=0
> I/O=0, Latched=1214, Other=823480
> Inram=0 Dirty=10927 Kept=0
> I/O=0, Latched=1214, Other=823480
> 2004-03-03 14:50:27.91 spid56 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835622
> InternalReservation=250 ExternalReservation=2278
Min Free=1024
> 2004-03-03 14:50:27.91 spid109 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835622
> InternalReservation=250 ExternalReservation=2278
Min Free=1024
> 2004-03-03 14:50:27.91 spid56 Procedure Cache: TotalProcs=21
TotalPages=174 InUsePages=170
> 2004-03-03 14:50:27.91 spid109 Procedure Cache: TotalProcs=21
TotalPages=174 InUsePages=170
> 2004-03-03 14:50:27.91 spid56 Dynamic Memory Manager: Stolen=117319 OS
Reserved=1632
> OS Committed=1608
> OS In Use=1599
> Query Plan=865 Optimizer=14
> General=5999
> Utilities=838 Connection=403
> 2004-03-03 14:50:27.91 spid109 Dynamic Memory Manager: Stolen=117319 OS
Reserved=1632
> OS Committed=1608
> OS In Use=1599
> Query Plan=865 Optimizer=14
> General=5999
> Utilities=838 Connection=403
> 2004-03-03 14:50:27.91 spid56 Global Memory Objects: Resource=3621
Locks=112718
> SQLCache=94 Replication=2
> LockBytes=2 ServerGlobal=62
> Xact=74
> 2004-03-03 14:50:27.91 spid109 Global Memory Objects: Resource=3621
Locks=112718
> SQLCache=94 Replication=2
> LockBytes=2 ServerGlobal=62
> Xact=74
> 2004-03-03 14:50:27.91 spid56 Query Memory Manager: Grants=5
Waiting=10 Maximum=76134 Available=0
> 2004-03-03 14:50:27.91 spid109 Query Memory Manager: Grants=5
Waiting=10 Maximum=76134 Available=0
> 2004-03-03 14:50:27.91 spid104 Buffer Distribution: Stolen=191003
Free=1170 Procedures=174
> Inram=0 Dirty=10927 Kept=0
> I/O=0, Latched=1214, Other=823480
> 2004-03-03 14:50:27.91 spid104 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835621
> InternalReservation=250 ExternalReservation=2278
Min Free=1024
> 2004-03-03 14:50:27.91 spid104 Procedure Cache: TotalProcs=21
TotalPages=174 InUsePages=170
> 2004-03-03 14:50:27.91 spid104 Dynamic Memory Manager: Stolen=117319 OS
Reserved=1632
> OS Committed=1608
> OS In Use=1599
> Query Plan=865 Optimizer=14
> General=5999
> Utilities=838 Connection=403
> 2004-03-03 14:50:27.91 spid104 Global Memory Objects: Resource=3621
Locks=112718
> SQLCache=94 Replication=2
> LockBytes=2 ServerGlobal=62
> Xact=74
>
d over because of “BPool::map: No remappable address found” error.
Did some one face the problem? As this is a critical server, we need to fi
x the same at the earliest. Your valuable input is required.
Is this because of low memory or is it a bug'
( Sql Instance is running with 8GB memory and total OS memory is 15GB)
Following is the part of Logs before fail over:
Todays log:
2004-03-04 11:43:14.30 spid77 BPool::Map: no remappable address found.
2004-03-04 11:43:14.30 spid6 BPool::Map: no remappable address found.
2004-03-04 11:43:14.30 spid85 BPool::Map: no remappable address found.
2004-03-04 11:43:14.30 spid79 BPool::Map: no remappable address found.
2004-03-04 11:43:14.31 spid55 BPool::Map: no remappable address found.
2004-03-04 11:43:14.44 spid6 Buffer Distribution: Stolen=191234 Free=14
98 Procedures=204
Inram=0 Dirty=19842 Kept=0
I/O=67, Latched=949, Other=814174
2004-03-04 11:43:14.44 spid6 Buffer Counts: Commited=1027968 Target=102
7968 Hashed=835036
InternalReservation=213 ExternalReservation=22524 Min Free=1024
2004-03-04 11:43:14.44 spid6 Procedure Cache: TotalProcs=20 TotalPages=
204 InUsePages=202
2004-03-04 11:43:14.44 spid6 Dynamic Memory Manager: Stolen=124482 OS R
eserved=1616
OS Committed=1592
OS In Use=1567
Query Plan=560 Optimizer=0
General=12887
Utilities=1334 Connection=249
2004-03-04 11:43:14.44 spid6 Global Memory Objects: Resource=2068 Locks
=112941
SQLCache=82 Replication=2
LockBytes=2 ServerGlobal=44
Xact=42
2004-03-04 11:43:14.44 spid6 Query Memory Manager: Grants=5 Waiting=7 M
aximum=89476 Available=0
2004-03-04 11:43:14.44 spid79 Buffer Distribution: Stolen=191226 Free=15
06 Procedures=204
Inram=0 Dirty=19842 Kept=0
I/O=67, Latched=948, Other=814175
2004-03-04 11:43:14.44 spid79 Buffer Counts: Commited=1027968 Target=102
7968 Hashed=835028
InternalReservation=213 ExternalReservation=22524 Min Free=1024
2004-03-04 11:43:14.44 spid79 Procedure Cache: TotalProcs=20 TotalPages=
204 InUsePages=202
2004-03-04 11:43:14.44 spid79 Dynamic Memory Manager: Stolen=124482 OS R
eserved=1616
OS Committed=1592
OS In Use=1567
Query Plan=560 Optimizer=0
General=12887
Utilities=1334 Connection=249
Yesterday log:
2004-03-03 14:50:27.72 spid90 BPool::Map: no remappable address found.
2004-03-03 14:50:27.74 spid109 BPool::Map: no remappable address found.
2004-03-03 14:50:27.74 spid56 BPool::Map: no remappable address found.
2004-03-03 14:50:27.74 spid52 BPool::Map: no remappable address found.
2004-03-03 14:50:27.75 spid105 BPool::Map: no remappable address found.
2004-03-03 14:50:27.75 spid104 BPool::Map: no remappable address found.
2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
2004-03-03 14:50:27.80 spid111 BPool::Map: no remappable address found.
2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
2004-03-03 14:50:27.89 spid109 Buffer Distribution: Stolen=191002 Free=11
71 Procedures=174
2004-03-03 14:50:27.89 spid56 Buffer Distribution: Stolen=191002 Free=11
71 Procedures=174
Inram=0 Dirty=10927 Kept=0
I/O=0, Latched=1214, Other=823480
Inram=0 Dirty=10927 Kept=0
I/O=0, Latched=1214, Other=823480
2004-03-03 14:50:27.91 spid56 Buffer Counts: Commited=1027968 Target=102
7968 Hashed=835622
InternalReservation=250 ExternalReservation=2278 Min Free=1024
2004-03-03 14:50:27.91 spid109 Buffer Counts: Commited=1027968 Target=102
7968 Hashed=835622
InternalReservation=250 ExternalReservation=2278 Min Free=1024
2004-03-03 14:50:27.91 spid56 Procedure Cache: TotalProcs=21 TotalPages=
174 InUsePages=170
2004-03-03 14:50:27.91 spid109 Procedure Cache: TotalProcs=21 TotalPages=
174 InUsePages=170
2004-03-03 14:50:27.91 spid56 Dynamic Memory Manager: Stolen=117319 OS R
eserved=1632
OS Committed=1608
OS In Use=1599
Query Plan=865 Optimizer=14
General=5999
Utilities=838 Connection=403
2004-03-03 14:50:27.91 spid109 Dynamic Memory Manager: Stolen=117319 OS R
eserved=1632
OS Committed=1608
OS In Use=1599
Query Plan=865 Optimizer=14
General=5999
Utilities=838 Connection=403
2004-03-03 14:50:27.91 spid56 Global Memory Objects: Resource=3621 Locks
=112718
SQLCache=94 Replication=2
LockBytes=2 ServerGlobal=62
Xact=74
2004-03-03 14:50:27.91 spid109 Global Memory Objects: Resource=3621 Locks
=112718
SQLCache=94 Replication=2
LockBytes=2 ServerGlobal=62
Xact=74
2004-03-03 14:50:27.91 spid56 Query Memory Manager: Grants=5 Waiting=10
Maximum=76134 Available=0
2004-03-03 14:50:27.91 spid109 Query Memory Manager: Grants=5 Waiting=10
Maximum=76134 Available=0
2004-03-03 14:50:27.91 spid104 Buffer Distribution: Stolen=191003 Free=11
70 Procedures=174
Inram=0 Dirty=10927 Kept=0
I/O=0, Latched=1214, Other=823480
2004-03-03 14:50:27.91 spid104 Buffer Counts: Commited=1027968 Target=102
7968 Hashed=835621
InternalReservation=250 ExternalReservation=2278 Min Free=1024
2004-03-03 14:50:27.91 spid104 Procedure Cache: TotalProcs=21 TotalPages=
174 InUsePages=170
2004-03-03 14:50:27.91 spid104 Dynamic Memory Manager: Stolen=117319 OS R
eserved=1632
OS Committed=1608
OS In Use=1599
Query Plan=865 Optimizer=14
General=5999
Utilities=838 Connection=403
2004-03-03 14:50:27.91 spid104 Global Memory Objects: Resource=3621 Locks
=112718
SQLCache=94 Replication=2
LockBytes=2 ServerGlobal=62
Xact=74I would contact PSS about this one
http://support.microsoft.com/defaul...us;Prodoffer41a
I can't recall seeing this before but it sounds like there may be an issue
with AWE. Do you have both /3GB and /PAE enabled or just /PAE in boot.ini ?
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Hemant" <anonymous@.discussions.microsoft.com> wrote in message
news:2F94E672-07F4-4554-9D0D-BC2F7CC3E164@.microsoft.com...
> We are running SQL two node active-active cluster. Since yester day It
failed over because of "BPool::map: No remappable address found" error.
> Did some one face the problem? As this is a critical server, we need to
fix the same at the earliest. Your valuable input is required.
> Is this because of low memory or is it a bug'
> ( Sql Instance is running with 8GB memory and total OS memory is 15GB)
> Following is the part of Logs before fail over:
> Todays log:
>
> 2004-03-04 11:43:14.30 spid77 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.30 spid6 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.30 spid85 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.30 spid79 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.31 spid55 BPool::Map: no remappable address found.
> 2004-03-04 11:43:14.44 spid6 Buffer Distribution: Stolen=191234
Free=1498 Procedures=204
> Inram=0 Dirty=19842 Kept=0
> I/O=67, Latched=949, Other=814174
> 2004-03-04 11:43:14.44 spid6 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835036
> InternalReservation=213 ExternalReservation=22524
Min Free=1024
> 2004-03-04 11:43:14.44 spid6 Procedure Cache: TotalProcs=20
TotalPages=204 InUsePages=202
> 2004-03-04 11:43:14.44 spid6 Dynamic Memory Manager: Stolen=124482 OS
Reserved=1616
> OS Committed=1592
> OS In Use=1567
> Query Plan=560 Optimizer=0
> General=12887
> Utilities=1334 Connection=249
> 2004-03-04 11:43:14.44 spid6 Global Memory Objects: Resource=2068
Locks=112941
> SQLCache=82 Replication=2
> LockBytes=2 ServerGlobal=44
> Xact=42
> 2004-03-04 11:43:14.44 spid6 Query Memory Manager: Grants=5 Waiting=7
Maximum=89476 Available=0
> 2004-03-04 11:43:14.44 spid79 Buffer Distribution: Stolen=191226
Free=1506 Procedures=204
> Inram=0 Dirty=19842 Kept=0
> I/O=67, Latched=948, Other=814175
> 2004-03-04 11:43:14.44 spid79 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835028
> InternalReservation=213 ExternalReservation=22524
Min Free=1024
> 2004-03-04 11:43:14.44 spid79 Procedure Cache: TotalProcs=20
TotalPages=204 InUsePages=202
> 2004-03-04 11:43:14.44 spid79 Dynamic Memory Manager: Stolen=124482 OS
Reserved=1616
> OS Committed=1592
> OS In Use=1567
> Query Plan=560 Optimizer=0
> General=12887
> Utilities=1334 Connection=249
> Yesterday log:
> 2004-03-03 14:50:27.72 spid90 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.74 spid109 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.74 spid56 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.74 spid52 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.75 spid105 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.75 spid104 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.80 spid111 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.80 spid100 BPool::Map: no remappable address found.
> 2004-03-03 14:50:27.89 spid109 Buffer Distribution: Stolen=191002
Free=1171 Procedures=174
> 2004-03-03 14:50:27.89 spid56 Buffer Distribution: Stolen=191002
Free=1171 Procedures=174
> Inram=0 Dirty=10927 Kept=0
> I/O=0, Latched=1214, Other=823480
> Inram=0 Dirty=10927 Kept=0
> I/O=0, Latched=1214, Other=823480
> 2004-03-03 14:50:27.91 spid56 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835622
> InternalReservation=250 ExternalReservation=2278
Min Free=1024
> 2004-03-03 14:50:27.91 spid109 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835622
> InternalReservation=250 ExternalReservation=2278
Min Free=1024
> 2004-03-03 14:50:27.91 spid56 Procedure Cache: TotalProcs=21
TotalPages=174 InUsePages=170
> 2004-03-03 14:50:27.91 spid109 Procedure Cache: TotalProcs=21
TotalPages=174 InUsePages=170
> 2004-03-03 14:50:27.91 spid56 Dynamic Memory Manager: Stolen=117319 OS
Reserved=1632
> OS Committed=1608
> OS In Use=1599
> Query Plan=865 Optimizer=14
> General=5999
> Utilities=838 Connection=403
> 2004-03-03 14:50:27.91 spid109 Dynamic Memory Manager: Stolen=117319 OS
Reserved=1632
> OS Committed=1608
> OS In Use=1599
> Query Plan=865 Optimizer=14
> General=5999
> Utilities=838 Connection=403
> 2004-03-03 14:50:27.91 spid56 Global Memory Objects: Resource=3621
Locks=112718
> SQLCache=94 Replication=2
> LockBytes=2 ServerGlobal=62
> Xact=74
> 2004-03-03 14:50:27.91 spid109 Global Memory Objects: Resource=3621
Locks=112718
> SQLCache=94 Replication=2
> LockBytes=2 ServerGlobal=62
> Xact=74
> 2004-03-03 14:50:27.91 spid56 Query Memory Manager: Grants=5
Waiting=10 Maximum=76134 Available=0
> 2004-03-03 14:50:27.91 spid109 Query Memory Manager: Grants=5
Waiting=10 Maximum=76134 Available=0
> 2004-03-03 14:50:27.91 spid104 Buffer Distribution: Stolen=191003
Free=1170 Procedures=174
> Inram=0 Dirty=10927 Kept=0
> I/O=0, Latched=1214, Other=823480
> 2004-03-03 14:50:27.91 spid104 Buffer Counts: Commited=1027968
Target=1027968 Hashed=835621
> InternalReservation=250 ExternalReservation=2278
Min Free=1024
> 2004-03-03 14:50:27.91 spid104 Procedure Cache: TotalProcs=21
TotalPages=174 InUsePages=170
> 2004-03-03 14:50:27.91 spid104 Dynamic Memory Manager: Stolen=117319 OS
Reserved=1632
> OS Committed=1608
> OS In Use=1599
> Query Plan=865 Optimizer=14
> General=5999
> Utilities=838 Connection=403
> 2004-03-03 14:50:27.91 spid104 Global Memory Objects: Resource=3621
Locks=112718
> SQLCache=94 Replication=2
> LockBytes=2 ServerGlobal=62
> Xact=74
>
Monday, March 26, 2012
Error: 7105, Severity: 22, State: 6
My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.
Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.
Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>
Error: 7105, Severity: 22, State: 6
My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.Oops.
Wrong group.
"ME" <ME@.mail.com> wrote in message
news:e7fZBsT$GHA.4800@.TK2MSFTNGP05.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this? Thanks.
>
>sql
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.Oops.
Wrong group.
"ME" <ME@.mail.com> wrote in message
news:e7fZBsT$GHA.4800@.TK2MSFTNGP05.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this? Thanks.
>
>sql
Error: 7105, Severity: 22, State: 6
My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.Make the call, they will tell you up front if it will be a covered (free)
call.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>> My SQL server logs this in Application log:
>> Error: 7105, Severity: 22, State: 6
>> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
>> for
>> a hot fix for this problem.
>> I believe this call is free because this is a bug. Can anyone confirm
>> this?
>> Thanks.
>>
>
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.Make the call, they will tell you up front if it will be a covered (free)
call.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>> My SQL server logs this in Application log:
>> Error: 7105, Severity: 22, State: 6
>> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
>> for
>> a hot fix for this problem.
>> I believe this call is free because this is a bug. Can anyone confirm
>> this?
>> Thanks.
>>
>
Error: 7105, Severity: 22, State: 6
My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.it is a SQL 2000 with SP4 on Windows server 2003 SP1.
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>|||Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.it is a SQL 2000 with SP4 on Windows server 2003 SP1.
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>|||Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>
Wednesday, March 7, 2012
Error with Linked Servers
From time to time the linked servers we have set up cannot be accessed. When
I click on the tables node under the linked server within enterprise manager
the session hangs and no error message is displayed. When querying the data
via an openquery no error is thrown, the query simply runs until manually
aborted.
I've created a linked server OK but immediately cannot open it. The only way
around this problem we have is a reboot of the server. Does anyone know how
to resolve this problem and also what would cause this.
Thanks
MikeMikeD
Do you have ping to linked server?
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:ACBEC816-1EE1-46E8-9535-8E52BB7C502A@.microsoft.com...
> From time to time the linked servers we have set up cannot be accessed.
> When
> I click on the tables node under the linked server within enterprise
> manager
> the session hangs and no error message is displayed. When querying the
> data
> via an openquery no error is thrown, the query simply runs until manually
> aborted.
> I've created a linked server OK but immediately cannot open it. The only
> way
> around this problem we have is a reboot of the server. Does anyone know
> how
> to resolve this problem and also what would cause this.
> Thanks
> Mike|||I can ping the server that sql is on if that's what you mean. I can see and
create linked servers but cannot query them - see below.
"Uri Dimant" wrote:
> MikeD
> Do you have ping to linked server?
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:ACBEC816-1EE1-46E8-9535-8E52BB7C502A@.microsoft.com...
>
>|||MikeD
Do you run the query in this way?
SELECT <> FROM Server.dbname.dbo.table
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:2C11B49F-D1BF-48C2-9ECC-2470666F9691@.microsoft.com...[vbcol=seagreen]
>I can ping the server that sql is on if that's what you mean. I can see and
> create linked servers but cannot query them - see below.
> "Uri Dimant" wrote:
>|||No - it's an openquery so it's :
SELECT * FROM OPENQUERY[linked_server_name], 'Select * from table_name'
But the problem isn't so much in the query it's the fact that when you
select the linked server the system hangs with no error message and the only
way we have of resolving the issue is a server reboot
"Uri Dimant" wrote:
> MikeD
> Do you run the query in this way?
> SELECT <> FROM Server.dbname.dbo.table
>
>
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:2C11B49F-D1BF-48C2-9ECC-2470666F9691@.microsoft.com...
>
>|||Well, is it large set data you want to return?
exec sp_serveroption 'servername','data access','true'
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:6EA13818-E61B-49E7-B6E0-35F581ADAF0F@.microsoft.com...[vbcol=seagreen]
> No - it's an openquery so it's :
> SELECT * FROM OPENQUERY[linked_server_name], 'Select * from table_name
'
> But the problem isn't so much in the query it's the fact that when you
> select the linked server the system hangs with no error message and the
> only
> way we have of resolving the issue is a server reboot
> "Uri Dimant" wrote:
>|||It's nothing to do with the query or the size of data. the problem is that
the linked server cannot be accessed until a reboot is done.
"Uri Dimant" wrote:
> Well, is it large set data you want to return?
> exec sp_serveroption 'servername','data access','true'
>
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:6EA13818-E61B-49E7-B6E0-35F581ADAF0F@.microsoft.com...
>
>
I click on the tables node under the linked server within enterprise manager
the session hangs and no error message is displayed. When querying the data
via an openquery no error is thrown, the query simply runs until manually
aborted.
I've created a linked server OK but immediately cannot open it. The only way
around this problem we have is a reboot of the server. Does anyone know how
to resolve this problem and also what would cause this.
Thanks
MikeMikeD
Do you have ping to linked server?
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:ACBEC816-1EE1-46E8-9535-8E52BB7C502A@.microsoft.com...
> From time to time the linked servers we have set up cannot be accessed.
> When
> I click on the tables node under the linked server within enterprise
> manager
> the session hangs and no error message is displayed. When querying the
> data
> via an openquery no error is thrown, the query simply runs until manually
> aborted.
> I've created a linked server OK but immediately cannot open it. The only
> way
> around this problem we have is a reboot of the server. Does anyone know
> how
> to resolve this problem and also what would cause this.
> Thanks
> Mike|||I can ping the server that sql is on if that's what you mean. I can see and
create linked servers but cannot query them - see below.
"Uri Dimant" wrote:
> MikeD
> Do you have ping to linked server?
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:ACBEC816-1EE1-46E8-9535-8E52BB7C502A@.microsoft.com...
>
>|||MikeD
Do you run the query in this way?
SELECT <> FROM Server.dbname.dbo.table
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:2C11B49F-D1BF-48C2-9ECC-2470666F9691@.microsoft.com...[vbcol=seagreen]
>I can ping the server that sql is on if that's what you mean. I can see and
> create linked servers but cannot query them - see below.
> "Uri Dimant" wrote:
>|||No - it's an openquery so it's :
SELECT * FROM OPENQUERY[linked_server_name], 'Select * from table_name'
But the problem isn't so much in the query it's the fact that when you
select the linked server the system hangs with no error message and the only
way we have of resolving the issue is a server reboot
"Uri Dimant" wrote:
> MikeD
> Do you run the query in this way?
> SELECT <> FROM Server.dbname.dbo.table
>
>
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:2C11B49F-D1BF-48C2-9ECC-2470666F9691@.microsoft.com...
>
>|||Well, is it large set data you want to return?
exec sp_serveroption 'servername','data access','true'
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:6EA13818-E61B-49E7-B6E0-35F581ADAF0F@.microsoft.com...[vbcol=seagreen]
> No - it's an openquery so it's :
> SELECT * FROM OPENQUERY[linked_server_name], 'Select * from table_name
'
> But the problem isn't so much in the query it's the fact that when you
> select the linked server the system hangs with no error message and the
> only
> way we have of resolving the issue is a server reboot
> "Uri Dimant" wrote:
>|||It's nothing to do with the query or the size of data. the problem is that
the linked server cannot be accessed until a reboot is done.
"Uri Dimant" wrote:
> Well, is it large set data you want to return?
> exec sp_serveroption 'servername','data access','true'
>
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:6EA13818-E61B-49E7-B6E0-35F581ADAF0F@.microsoft.com...
>
>
Friday, February 24, 2012
Error while upgrading SQL2005 Standard To SQL 2005 Enterprise
Hello,
I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
Enterprise. I received the following error message during the upgrade of
the database components.
Product: Microsoft SQL Server 2005 -- Error 29550. The
setup has encountered an error while Upgrading Components.
The error: -2147019873
Error message: The group or resource is not in the correct
state to perform the requested operation.
My customers ASPState Database is in simple recovery mode. I was not
sure if this is what could have caused this error. Also will i have to
start with a fresh install of SQL 2005 to resolve this issue?
Thanks for the help.I doubt that is it. Are any of the files, filegroups or dbs read only or in
other than OnLine mode? Do any of the dbs have a computability level of
less than 80?
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> Hello,
> I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
> Enterprise. I received the following error message during the upgrade of
> the database components.
>
> Product: Microsoft SQL Server 2005 -- Error 29550. The
> setup has encountered an error while Upgrading Components.
> The error: -2147019873
> Error message: The group or resource is not in the correct
> state to perform the requested operation.
> My customers ASPState Database is in simple recovery mode. I was not sure
> if this is what could have caused this error. Also will i have to start
> with a fresh install of SQL 2005 to resolve this issue?
> Thanks for the help.|||As far as i am aware all the files, filegroups are not in a read only
mode and all DB files are Online. As far as DB computability level i
will have to look into that.
Andrew J. Kelly wrote:
> I doubt that is it. Are any of the files, filegroups or dbs read only or i
n
> other than OnLine mode? Do any of the dbs have a computability level of
> less than 80?
>
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...[vbcol=seagreen]
SQL2005[vbcol=seagreen]
upgrade of[vbcol=seagreen]
not sure[vbcol=seagreen]
start[vbcol=seagreen]|||Also all DB files are currently set at compatibility level of 90.
Noah wrote:
> As far as i am aware all the files, filegroups are not in a read only
> mode and all DB files are Online. As far as DB computability level i
> will have to look into that.
> Andrew J. Kelly wrote:
> "Noah" <noah@.carpathiahost.com> wrote in message
> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> SQL2005
> upgrade of
> not sure
> start
>|||I just reread your original post. You said "2 node". Is this a cluster? If
so the error is probably talking about the cluster resource group not SQL
Server. Try posting this in the Cluster newsgroup for a better answer.
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:et98dKD2HHA.3760@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Also all DB files are currently set at compatibility level of 90.
>
> Noah wrote:|||Andrew J. Kelly wrote:
> I just reread your original post. You said "2 node". Is this a cluster? I
f
> so the error is probably talking about the cluster resource group not SQL
> Server. Try posting this in the Cluster newsgroup for a better answer.
>
Will Do thanks.
I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
Enterprise. I received the following error message during the upgrade of
the database components.
Product: Microsoft SQL Server 2005 -- Error 29550. The
setup has encountered an error while Upgrading Components.
The error: -2147019873
Error message: The group or resource is not in the correct
state to perform the requested operation.
My customers ASPState Database is in simple recovery mode. I was not
sure if this is what could have caused this error. Also will i have to
start with a fresh install of SQL 2005 to resolve this issue?
Thanks for the help.I doubt that is it. Are any of the files, filegroups or dbs read only or in
other than OnLine mode? Do any of the dbs have a computability level of
less than 80?
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> Hello,
> I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
> Enterprise. I received the following error message during the upgrade of
> the database components.
>
> Product: Microsoft SQL Server 2005 -- Error 29550. The
> setup has encountered an error while Upgrading Components.
> The error: -2147019873
> Error message: The group or resource is not in the correct
> state to perform the requested operation.
> My customers ASPState Database is in simple recovery mode. I was not sure
> if this is what could have caused this error. Also will i have to start
> with a fresh install of SQL 2005 to resolve this issue?
> Thanks for the help.|||As far as i am aware all the files, filegroups are not in a read only
mode and all DB files are Online. As far as DB computability level i
will have to look into that.
Andrew J. Kelly wrote:
> I doubt that is it. Are any of the files, filegroups or dbs read only or i
n
> other than OnLine mode? Do any of the dbs have a computability level of
> less than 80?
>
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...[vbcol=seagreen]
SQL2005[vbcol=seagreen]
upgrade of[vbcol=seagreen]
not sure[vbcol=seagreen]
start[vbcol=seagreen]|||Also all DB files are currently set at compatibility level of 90.
Noah wrote:
> As far as i am aware all the files, filegroups are not in a read only
> mode and all DB files are Online. As far as DB computability level i
> will have to look into that.
> Andrew J. Kelly wrote:
> "Noah" <noah@.carpathiahost.com> wrote in message
> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> SQL2005
> upgrade of
> not sure
> start
>|||I just reread your original post. You said "2 node". Is this a cluster? If
so the error is probably talking about the cluster resource group not SQL
Server. Try posting this in the Cluster newsgroup for a better answer.
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:et98dKD2HHA.3760@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Also all DB files are currently set at compatibility level of 90.
>
> Noah wrote:|||Andrew J. Kelly wrote:
> I just reread your original post. You said "2 node". Is this a cluster? I
f
> so the error is probably talking about the cluster resource group not SQL
> Server. Try posting this in the Cluster newsgroup for a better answer.
>
Will Do thanks.
Error while upgrading SQL2005 Standard To SQL 2005 Enterprise
Hello,
I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
Enterprise. I received the following error message during the upgrade of
the database components.
Product: Microsoft SQL Server 2005 -- Error 29550. The
setup has encountered an error while Upgrading Components.
The error: -2147019873
Error message: The group or resource is not in the correct
state to perform the requested operation.
My customers ASPState Database is in simple recovery mode. I was not
sure if this is what could have caused this error. Also will i have to
start with a fresh install of SQL 2005 to resolve this issue?
Thanks for the help.I doubt that is it. Are any of the files, filegroups or dbs read only or in
other than OnLine mode? Do any of the dbs have a computability level of
less than 80?
--
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> Hello,
> I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
> Enterprise. I received the following error message during the upgrade of
> the database components.
>
> Product: Microsoft SQL Server 2005 -- Error 29550. The
> setup has encountered an error while Upgrading Components.
> The error: -2147019873
> Error message: The group or resource is not in the correct
> state to perform the requested operation.
> My customers ASPState Database is in simple recovery mode. I was not sure
> if this is what could have caused this error. Also will i have to start
> with a fresh install of SQL 2005 to resolve this issue?
> Thanks for the help.|||As far as i am aware all the files, filegroups are not in a read only
mode and all DB files are Online. As far as DB computability level i
will have to look into that.
Andrew J. Kelly wrote:
> I doubt that is it. Are any of the files, filegroups or dbs read only or in
> other than OnLine mode? Do any of the dbs have a computability level of
> less than 80?
>
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> > Hello,
> >
> > I just recently tried to upgrade a two node SQL2005 Standard to
SQL2005
> > Enterprise. I received the following error message during the
upgrade of
> > the database components.
> >
> >
> >
> > Product: Microsoft SQL Server 2005 -- Error 29550. The
> > setup has encountered an error while Upgrading Components.
> > The error: -2147019873
> > Error message: The group or resource is not in the correct
> > state to perform the requested operation.
> >
> > My customers ASPState Database is in simple recovery mode. I was
not sure
> > if this is what could have caused this error. Also will i have to
start
> > with a fresh install of SQL 2005 to resolve this issue?
> >
> > Thanks for the help.|||Also all DB files are currently set at compatibility level of 90.
Noah wrote:
> As far as i am aware all the files, filegroups are not in a read only
> mode and all DB files are Online. As far as DB computability level i
> will have to look into that.
> Andrew J. Kelly wrote:
>> I doubt that is it. Are any of the files, filegroups or dbs read only
>> or in other than OnLine mode? Do any of the dbs have a computability
>> level of less than 80?
> "Noah" <noah@.carpathiahost.com> wrote in message
> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> > > Hello,
> > >
> > > I just recently tried to upgrade a two node SQL2005 Standard to
> SQL2005
> > > Enterprise. I received the following error message during the
> upgrade of
> > > the database components.
> > >
> > >
> > >
> > > Product: Microsoft SQL Server 2005 -- Error 29550. The
> > > setup has encountered an error while Upgrading Components.
> > > The error: -2147019873
> > > Error message: The group or resource is not in the correct
> > > state to perform the requested operation.
> > >
> > > My customers ASPState Database is in simple recovery mode. I was
> not sure
> > > if this is what could have caused this error. Also will i have to
> start
> > > with a fresh install of SQL 2005 to resolve this issue?
> > >
> > > Thanks for the help.
>|||I just reread your original post. You said "2 node". Is this a cluster? If
so the error is probably talking about the cluster resource group not SQL
Server. Try posting this in the Cluster newsgroup for a better answer.
--
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:et98dKD2HHA.3760@.TK2MSFTNGP03.phx.gbl...
> Also all DB files are currently set at compatibility level of 90.
>
> Noah wrote:
>> As far as i am aware all the files, filegroups are not in a read only
>> mode and all DB files are Online. As far as DB computability level i will
>> have to look into that.
>> Andrew J. Kelly wrote:
>> I doubt that is it. Are any of the files, filegroups or dbs read only or
>> in other than OnLine mode? Do any of the dbs have a computability level
>> of less than 80?
>> "Noah" <noah@.carpathiahost.com> wrote in message
>> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
>> > > Hello,
>> > >
>> > > I just recently tried to upgrade a two node SQL2005 Standard to
>> SQL2005
>> > > Enterprise. I received the following error message during the
>> upgrade of
>> > > the database components.
>> > >
>> > >
>> > >
>> > > Product: Microsoft SQL Server 2005 -- Error 29550. The
>> > > setup has encountered an error while Upgrading Components.
>> > > The error: -2147019873
>> > > Error message: The group or resource is not in the correct
>> > > state to perform the requested operation.
>> > >
>> > > My customers ASPState Database is in simple recovery mode. I was not
>> sure
>> > > if this is what could have caused this error. Also will i have to
>> start
>> > > with a fresh install of SQL 2005 to resolve this issue?
>> > >
>> > > Thanks for the help.|||Andrew J. Kelly wrote:
> I just reread your original post. You said "2 node". Is this a cluster? If
> so the error is probably talking about the cluster resource group not SQL
> Server. Try posting this in the Cluster newsgroup for a better answer.
>
Will Do thanks.
I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
Enterprise. I received the following error message during the upgrade of
the database components.
Product: Microsoft SQL Server 2005 -- Error 29550. The
setup has encountered an error while Upgrading Components.
The error: -2147019873
Error message: The group or resource is not in the correct
state to perform the requested operation.
My customers ASPState Database is in simple recovery mode. I was not
sure if this is what could have caused this error. Also will i have to
start with a fresh install of SQL 2005 to resolve this issue?
Thanks for the help.I doubt that is it. Are any of the files, filegroups or dbs read only or in
other than OnLine mode? Do any of the dbs have a computability level of
less than 80?
--
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> Hello,
> I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
> Enterprise. I received the following error message during the upgrade of
> the database components.
>
> Product: Microsoft SQL Server 2005 -- Error 29550. The
> setup has encountered an error while Upgrading Components.
> The error: -2147019873
> Error message: The group or resource is not in the correct
> state to perform the requested operation.
> My customers ASPState Database is in simple recovery mode. I was not sure
> if this is what could have caused this error. Also will i have to start
> with a fresh install of SQL 2005 to resolve this issue?
> Thanks for the help.|||As far as i am aware all the files, filegroups are not in a read only
mode and all DB files are Online. As far as DB computability level i
will have to look into that.
Andrew J. Kelly wrote:
> I doubt that is it. Are any of the files, filegroups or dbs read only or in
> other than OnLine mode? Do any of the dbs have a computability level of
> less than 80?
>
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> > Hello,
> >
> > I just recently tried to upgrade a two node SQL2005 Standard to
SQL2005
> > Enterprise. I received the following error message during the
upgrade of
> > the database components.
> >
> >
> >
> > Product: Microsoft SQL Server 2005 -- Error 29550. The
> > setup has encountered an error while Upgrading Components.
> > The error: -2147019873
> > Error message: The group or resource is not in the correct
> > state to perform the requested operation.
> >
> > My customers ASPState Database is in simple recovery mode. I was
not sure
> > if this is what could have caused this error. Also will i have to
start
> > with a fresh install of SQL 2005 to resolve this issue?
> >
> > Thanks for the help.|||Also all DB files are currently set at compatibility level of 90.
Noah wrote:
> As far as i am aware all the files, filegroups are not in a read only
> mode and all DB files are Online. As far as DB computability level i
> will have to look into that.
> Andrew J. Kelly wrote:
>> I doubt that is it. Are any of the files, filegroups or dbs read only
>> or in other than OnLine mode? Do any of the dbs have a computability
>> level of less than 80?
> "Noah" <noah@.carpathiahost.com> wrote in message
> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> > > Hello,
> > >
> > > I just recently tried to upgrade a two node SQL2005 Standard to
> SQL2005
> > > Enterprise. I received the following error message during the
> upgrade of
> > > the database components.
> > >
> > >
> > >
> > > Product: Microsoft SQL Server 2005 -- Error 29550. The
> > > setup has encountered an error while Upgrading Components.
> > > The error: -2147019873
> > > Error message: The group or resource is not in the correct
> > > state to perform the requested operation.
> > >
> > > My customers ASPState Database is in simple recovery mode. I was
> not sure
> > > if this is what could have caused this error. Also will i have to
> start
> > > with a fresh install of SQL 2005 to resolve this issue?
> > >
> > > Thanks for the help.
>|||I just reread your original post. You said "2 node". Is this a cluster? If
so the error is probably talking about the cluster resource group not SQL
Server. Try posting this in the Cluster newsgroup for a better answer.
--
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:et98dKD2HHA.3760@.TK2MSFTNGP03.phx.gbl...
> Also all DB files are currently set at compatibility level of 90.
>
> Noah wrote:
>> As far as i am aware all the files, filegroups are not in a read only
>> mode and all DB files are Online. As far as DB computability level i will
>> have to look into that.
>> Andrew J. Kelly wrote:
>> I doubt that is it. Are any of the files, filegroups or dbs read only or
>> in other than OnLine mode? Do any of the dbs have a computability level
>> of less than 80?
>> "Noah" <noah@.carpathiahost.com> wrote in message
>> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
>> > > Hello,
>> > >
>> > > I just recently tried to upgrade a two node SQL2005 Standard to
>> SQL2005
>> > > Enterprise. I received the following error message during the
>> upgrade of
>> > > the database components.
>> > >
>> > >
>> > >
>> > > Product: Microsoft SQL Server 2005 -- Error 29550. The
>> > > setup has encountered an error while Upgrading Components.
>> > > The error: -2147019873
>> > > Error message: The group or resource is not in the correct
>> > > state to perform the requested operation.
>> > >
>> > > My customers ASPState Database is in simple recovery mode. I was not
>> sure
>> > > if this is what could have caused this error. Also will i have to
>> start
>> > > with a fresh install of SQL 2005 to resolve this issue?
>> > >
>> > > Thanks for the help.|||Andrew J. Kelly wrote:
> I just reread your original post. You said "2 node". Is this a cluster? If
> so the error is probably talking about the cluster resource group not SQL
> Server. Try posting this in the Cluster newsgroup for a better answer.
>
Will Do thanks.
Error while upgrading SQL2005 Standard To SQL 2005 Enterprise
Hello,
I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
Enterprise. I received the following error message during the upgrade of
the database components.
Product: Microsoft SQL Server 2005 -- Error 29550. The
setup has encountered an error while Upgrading Components.
The error: -2147019873
Error message: The group or resource is not in the correct
state to perform the requested operation.
My customers ASPState Database is in simple recovery mode. I was not
sure if this is what could have caused this error. Also will i have to
start with a fresh install of SQL 2005 to resolve this issue?
Thanks for the help.
I doubt that is it. Are any of the files, filegroups or dbs read only or in
other than OnLine mode? Do any of the dbs have a computability level of
less than 80?
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> Hello,
> I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
> Enterprise. I received the following error message during the upgrade of
> the database components.
>
> Product: Microsoft SQL Server 2005 -- Error 29550. The
> setup has encountered an error while Upgrading Components.
> The error: -2147019873
> Error message: The group or resource is not in the correct
> state to perform the requested operation.
> My customers ASPState Database is in simple recovery mode. I was not sure
> if this is what could have caused this error. Also will i have to start
> with a fresh install of SQL 2005 to resolve this issue?
> Thanks for the help.
|||As far as i am aware all the files, filegroups are not in a read only
mode and all DB files are Online. As far as DB computability level i
will have to look into that.
Andrew J. Kelly wrote:
> I doubt that is it. Are any of the files, filegroups or dbs read only or in
> other than OnLine mode? Do any of the dbs have a computability level of
> less than 80?
>
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...[vbcol=seagreen]
SQL2005[vbcol=seagreen]
upgrade of[vbcol=seagreen]
not sure[vbcol=seagreen]
start[vbcol=seagreen]
|||Also all DB files are currently set at compatibility level of 90.
Noah wrote:
> As far as i am aware all the files, filegroups are not in a read only
> mode and all DB files are Online. As far as DB computability level i
> will have to look into that.
> Andrew J. Kelly wrote:
> "Noah" <noah@.carpathiahost.com> wrote in message
> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> SQL2005
> upgrade of
> not sure
> start
>
|||I just reread your original post. You said "2 node". Is this a cluster? If
so the error is probably talking about the cluster resource group not SQL
Server. Try posting this in the Cluster newsgroup for a better answer.
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:et98dKD2HHA.3760@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Also all DB files are currently set at compatibility level of 90.
>
> Noah wrote:
|||Andrew J. Kelly wrote:
> I just reread your original post. You said "2 node". Is this a cluster? If
> so the error is probably talking about the cluster resource group not SQL
> Server. Try posting this in the Cluster newsgroup for a better answer.
>
Will Do thanks.
I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
Enterprise. I received the following error message during the upgrade of
the database components.
Product: Microsoft SQL Server 2005 -- Error 29550. The
setup has encountered an error while Upgrading Components.
The error: -2147019873
Error message: The group or resource is not in the correct
state to perform the requested operation.
My customers ASPState Database is in simple recovery mode. I was not
sure if this is what could have caused this error. Also will i have to
start with a fresh install of SQL 2005 to resolve this issue?
Thanks for the help.
I doubt that is it. Are any of the files, filegroups or dbs read only or in
other than OnLine mode? Do any of the dbs have a computability level of
less than 80?
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> Hello,
> I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
> Enterprise. I received the following error message during the upgrade of
> the database components.
>
> Product: Microsoft SQL Server 2005 -- Error 29550. The
> setup has encountered an error while Upgrading Components.
> The error: -2147019873
> Error message: The group or resource is not in the correct
> state to perform the requested operation.
> My customers ASPState Database is in simple recovery mode. I was not sure
> if this is what could have caused this error. Also will i have to start
> with a fresh install of SQL 2005 to resolve this issue?
> Thanks for the help.
|||As far as i am aware all the files, filegroups are not in a read only
mode and all DB files are Online. As far as DB computability level i
will have to look into that.
Andrew J. Kelly wrote:
> I doubt that is it. Are any of the files, filegroups or dbs read only or in
> other than OnLine mode? Do any of the dbs have a computability level of
> less than 80?
>
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...[vbcol=seagreen]
SQL2005[vbcol=seagreen]
upgrade of[vbcol=seagreen]
not sure[vbcol=seagreen]
start[vbcol=seagreen]
|||Also all DB files are currently set at compatibility level of 90.
Noah wrote:
> As far as i am aware all the files, filegroups are not in a read only
> mode and all DB files are Online. As far as DB computability level i
> will have to look into that.
> Andrew J. Kelly wrote:
> "Noah" <noah@.carpathiahost.com> wrote in message
> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> SQL2005
> upgrade of
> not sure
> start
>
|||I just reread your original post. You said "2 node". Is this a cluster? If
so the error is probably talking about the cluster resource group not SQL
Server. Try posting this in the Cluster newsgroup for a better answer.
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:et98dKD2HHA.3760@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Also all DB files are currently set at compatibility level of 90.
>
> Noah wrote:
|||Andrew J. Kelly wrote:
> I just reread your original post. You said "2 node". Is this a cluster? If
> so the error is probably talking about the cluster resource group not SQL
> Server. Try posting this in the Cluster newsgroup for a better answer.
>
Will Do thanks.
Subscribe to:
Posts (Atom)