Showing posts with label address. Show all posts
Showing posts with label address. Show all posts

Friday, February 24, 2012

BSOD blamed on nlemsql.sys

We have Server 2003 crashing every day or so, saying:
*** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x0000
0000
*** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
There are only two references to nlemsql on Google, neither of which are
related to a crash.
We're trying to narrow down what happens just before this, but haven't
managed to get any useful information yet.
It's a stab in the dark, but: anyone seen this before?
Rikthat's the good ole KERNEL_MODE_EXCEPTION_NOT_HANDLED, an error which the os
did not know how to handle. These are almost always hardware compatibility
issues, you need a firmware or driver update. The question is which one, it
looks like the driver for nlemsql.sys. That driver is not part of SQL
Server. Search your system looking for it and when you find it right click
on it and look at properties, and then the version tab. There should be a
clue as to what this driver is for, or who made it somewhere here. You can
also open it in text pad looking for clues. Another thing you can do is to
check the directory it is in which occasionally well tell you something.
this file is not part of SQL 2000 or SQl 2005.
I would also contact your vendor of the server.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rik Hemsley" <rik@.rikkus.info> wrote in message
news:uy$h8OSZGHA.3972@.TK2MSFTNGP04.phx.gbl...
> We have Server 2003 crashing every day or so, saying:
> *** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x0000
0000
> *** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
> There are only two references to nlemsql on Google, neither of which are
> related to a crash.
> We're trying to narrow down what happens just before this, but haven't
> managed to get any useful information yet.
> It's a stab in the dark, but: anyone seen this before?
> Rik

BSOD blamed on nlemsql.sys

We have Server 2003 crashing every day or so, saying:
*** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x00000000
*** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
There are only two references to nlemsql on Google, neither of which are
related to a crash.
We're trying to narrow down what happens just before this, but haven't
managed to get any useful information yet.
It's a stab in the dark, but: anyone seen this before?
Rikthat's the good ole KERNEL_MODE_EXCEPTION_NOT_HANDLED, an error which the os
did not know how to handle. These are almost always hardware compatibility
issues, you need a firmware or driver update. The question is which one, it
looks like the driver for nlemsql.sys. That driver is not part of SQL
Server. Search your system looking for it and when you find it right click
on it and look at properties, and then the version tab. There should be a
clue as to what this driver is for, or who made it somewhere here. You can
also open it in text pad looking for clues. Another thing you can do is to
check the directory it is in which occasionally well tell you something.
this file is not part of SQL 2000 or SQl 2005.
I would also contact your vendor of the server.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rik Hemsley" <rik@.rikkus.info> wrote in message
news:uy$h8OSZGHA.3972@.TK2MSFTNGP04.phx.gbl...
> We have Server 2003 crashing every day or so, saying:
> *** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x00000000
> *** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
> There are only two references to nlemsql on Google, neither of which are
> related to a crash.
> We're trying to narrow down what happens just before this, but haven't
> managed to get any useful information yet.
> It's a stab in the dark, but: anyone seen this before?
> Rik

Sunday, February 19, 2012

broker and mirroring

Hi,

I tried to setup a service broker from one database to another that is mirrored. I specified the mirror address in the create route sql. When I tried to failover to the mirror database, the message was never sent to the mirror database. I do not see any error in transmission_status of sys.transmission_queue. I do see the following errors in the sql log

Service Broker login attempt failed with error: 'Connection handshake failed. The certificate used by the peer is invalid due to the following reason: Certificate not found. State 89.'. [CLIENT: 10.76.223.38]

The mirror route is not operational. 'TCP://11.78.223.54:4022' is acting as 'Mirror' []. 'TCP://11.78.223.38:4022' is acting as 'Unknown' [].

what should I be checking here?

thanks

P

Hi P,

Looks like you did set up the endpoint authentication between the sender and the mirror, but you did not set up the endpoint authentication between the sender and the principal. Therefore the sender cannot connect to the principal. Exchange the certificates, create the login, grant CONNECT permission etc.

In order to use the mirrored route, the sender's instance must be able to connect and authenticate with both instances involved in the mirroring session (principal and mirror).

HTH,
~ Remus

Tuesday, February 14, 2012

Breaking out data from a text field type

In my database there is a text field type that is used to enter street
address. This address could be a few lines long, each line with a
carriage return at the end.
Is there a way to search for these carriage returns and break out what
is in each line seperately?

Thanks.
Mike[posted and mailed, please reply in news]

Mike (mrea@.ohiotravelbag.com) writes:
> In my database there is a text field type that is used to enter street
> address. This address could be a few lines long, each line with a
> carriage return at the end.
> Is there a way to search for these carriage returns and break out what
> is in each line seperately?

Is that really the datatype text? That seems a bit over kill for a street
address. They would very rarely be over 8000 bytes. Or even 4000 if you
are using varchar.

The functions to use are substring and charindex. And char(13) for the
CRs. Or char(13) + char(10) if it's actually CR + LF. charindex does not
handle text beyond the varchar limit, but I don't think this would be
an issue.

You could also do:

SELECT @.adr = adr FROM tbl WHERE ..
SELECT str
FROM iter_charlist_to_table(@.adr, char(13))
ORDER BY listpos

You find this function on
http://www.sommarskog.se/arrays-in-...list-of-strings

Note that if you need to use char(13) + char(10) as delimiter, you
will have to change the function. (And not only the length of delimiter.)

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Break up Record

Hi,
I have a table with only one record in it looks someting like this
Field Titles : Name Address PC
Data : Bert A House CL4
Is it possible to reformat this so that it looks like
Name
Bert
Address
A House
PC
CL4
Usually I am doing this the other way around and moving things up onto one
like, it's been a long morning not much fun being in work at 6.40am so any
help would be brilliant.
Thanks Phil, zzzzzzzzzzzzzzzzzzDont worry about this post, I have woken up and managed to sort it.
Thanks Phil
"Phil" wrote:

> Hi,
> I have a table with only one record in it looks someting like this
> Field Titles : Name Address PC
> Data : Bert A House CL4
> Is it possible to reformat this so that it looks like
> Name
> Bert
> Address
> A House
> PC
> CL4
> Usually I am doing this the other way around and moving things up onto one
> like, it's been a long morning not much fun being in work at 6.40am so any
> help would be brilliant.
> Thanks Phil, zzzzzzzzzzzzzzzzzz

Sunday, February 12, 2012

BPool::Map: no remappable address found

We received the error listed below last month on our SQL Server 2000 cluster
server with Windows 2003 server.
Please help me resolve this error.
Thanks,
2005-12-23 09:26:06.49 spid119 BPool::Map: no remappable address found.
2005-12-23 09:26:06.50 spid93 BPool::Map: no remappable address found.
2005-12-23 09:26:06.52 spid365 BPool::Map: no remappable address found.
2005-12-23 09:26:06.56 spid126 BPool::Map: no remappable address found.
2005-12-23 09:26:06.61 spid314 BPool::Map: no remappable address found.
2005-12-23 09:26:06.63 spid119 BPool::Map: no remappable address found.
2005-12-23 09:26:06.64 spid132 BPool::Map: no remappable address found.
2005-12-23 09:26:06.77 spid76 BPool::Map: no remappable address found.
2005-12-23 09:26:06.77 spid365 Buffer Distribution: Stolen=321943
Free=1954 Procedures=1218
Inram=0 Dirty=36513 Kept=0
I/O=1, Latched=204, Other=948887
2005-12-23 09:26:06.77 spid365 Buffer Counts: Commited=1310720
Target=1310720 Hashed=985605
InternalReservation=520 ExternalReservation=3156 Min Free=2048
2005-12-23 09:26:06.77 spid365 Procedure Cache: TotalProcs=161
TotalPages=1218 InUsePages=1079
2005-12-23 09:26:06.77 spid365 Dynamic Memory Manager: Stolen=323127 OS
Reserved=2528
OS Committed=2493
OS In Use=2457
Query Plan=300284 Optimizer=14761
General=4611
Utilities=134 Connection=2256
2005-12-23 09:26:06.77 spid365 Global Memory Objects: Resource=3639
Locks=1519
SQLCache=251 Replication=2
LockBytes=2 ServerGlobal=289
Xact=138
2005-12-23 09:26:06.77 spid365 Query Memory Manager: Grants=2 Waiting=7
Maximum=3156 Available=0
2005-12-23 09:26:06.77 spid93 Buffer Distribution: Stolen=321944
Free=1953 Procedures=1218
Inram=0 Dirty=36513 Kept=0
I/O=1, Latched=204, Other=948887
2005-12-23 09:26:06.77 spid93 Buffer Counts: Commited=1310720
Target=1310720 Hashed=985605
InternalReservation=520 ExternalReservation=3156 Min Free=2048
2005-12-23 09:26:06.77 spid93 Procedure Cache: TotalProcs=161
TotalPages=1218 InUsePages=1079
2005-12-23 09:26:06.77 spid93 Dynamic Memory Manager: Stolen=323127 OS
Reserved=2528
OS Committed=2493
OS In Use=2457
Query Plan=300284 Optimizer=14761
General=4611
Utilities=134 Connection=2256
2005-12-23 09:26:06.77 spid93 Global Memory Objects: Resource=3639
Locks=1519
SQLCache=251 Replication=2
LockBytes=2 ServerGlobal=289
Xact=138
2005-12-23 09:26:06.77 spid93 Query Memory Manager: Grants=2 Waiting=7
Maximum=3156 Available=0
2005-12-23 09:26:06.78 spid328 BPool::Map: no remappable address found.
2005-12-23 09:26:06.81 spid83 BPool::Map: no remappable address found.
2005-12-23 09:26:06.83 spid365 BPool::Map: no remappable address found.
2005-12-23 09:26:06.83 spid93 BPool::Map: no remappable address found.
2005-12-23 09:26:06.84 spid126 Buffer Distribution: Stolen=321850
Free=2053 Procedures=1212
Hi
Look at this KB article:
http://support.microsoft.com/kb/838459
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:A5D5C3AA-F593-4087-B17B-F7B67C31FD90@.microsoft.com...
> We received the error listed below last month on our SQL Server 2000
cluster
> server with Windows 2003 server.
> Please help me resolve this error.
> Thanks,
>
> 2005-12-23 09:26:06.49 spid119 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.50 spid93 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.52 spid365 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.56 spid126 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.61 spid314 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.63 spid119 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.64 spid132 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.77 spid76 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.77 spid365 Buffer Distribution: Stolen=321943
> Free=1954 Procedures=1218
> Inram=0 Dirty=36513 Kept=0
> I/O=1, Latched=204, Other=948887
> 2005-12-23 09:26:06.77 spid365 Buffer Counts: Commited=1310720
> Target=1310720 Hashed=985605
> InternalReservation=520 ExternalReservation=3156 Min Free=2048
> 2005-12-23 09:26:06.77 spid365 Procedure Cache: TotalProcs=161
> TotalPages=1218 InUsePages=1079
> 2005-12-23 09:26:06.77 spid365 Dynamic Memory Manager: Stolen=323127 OS
> Reserved=2528
> OS Committed=2493
> OS In Use=2457
> Query Plan=300284 Optimizer=14761
> General=4611
> Utilities=134 Connection=2256
> 2005-12-23 09:26:06.77 spid365 Global Memory Objects: Resource=3639
> Locks=1519
> SQLCache=251 Replication=2
> LockBytes=2 ServerGlobal=289
> Xact=138
> 2005-12-23 09:26:06.77 spid365 Query Memory Manager: Grants=2 Waiting=7
> Maximum=3156 Available=0
> 2005-12-23 09:26:06.77 spid93 Buffer Distribution: Stolen=321944
> Free=1953 Procedures=1218
> Inram=0 Dirty=36513 Kept=0
> I/O=1, Latched=204, Other=948887
> 2005-12-23 09:26:06.77 spid93 Buffer Counts: Commited=1310720
> Target=1310720 Hashed=985605
> InternalReservation=520 ExternalReservation=3156 Min Free=2048
> 2005-12-23 09:26:06.77 spid93 Procedure Cache: TotalProcs=161
> TotalPages=1218 InUsePages=1079
> 2005-12-23 09:26:06.77 spid93 Dynamic Memory Manager: Stolen=323127 OS
> Reserved=2528
> OS Committed=2493
> OS In Use=2457
> Query Plan=300284 Optimizer=14761
> General=4611
> Utilities=134 Connection=2256
> 2005-12-23 09:26:06.77 spid93 Global Memory Objects: Resource=3639
> Locks=1519
> SQLCache=251 Replication=2
> LockBytes=2 ServerGlobal=289
> Xact=138
> 2005-12-23 09:26:06.77 spid93 Query Memory Manager: Grants=2 Waiting=7
> Maximum=3156 Available=0
> 2005-12-23 09:26:06.78 spid328 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.81 spid83 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.83 spid365 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.83 spid93 BPool::Map: no remappable address found.
> 2005-12-23 09:26:06.84 spid126 Buffer Distribution: Stolen=321850
> Free=2053 Procedures=1212
>

BPool error

I'm receiving this in my SQL errorlog:
ERRORLOG:2004-04-20 10:43:56.95 spid85 BPool::Map: no remappable address
found.
ERRORLOG:2004-04-20 10:43:57.09 spid85 Buffer Distribution:
Stolen=126759 Free=1305 Procedures=0
ERRORLOG: Inram=0 Dirty=12894 Kept=0
ERRORLOG: I/O=50738, Latched=108, Other=1643204
ERRORLOG:2004-04-20 10:43:57.09 spid85 Buffer Counts: Commited=1835008
Target=1835008 Hashed=1706944
ERRORLOG: InternalReservation=192 ExternalReservation=17101 Min Free=1024
ERRORLOG:2004-04-20 10:43:57.09 spid85 Procedure Cache: TotalProcs=0
TotalPages=0 InUsePages=0
ERRORLOG:2004-04-20 10:43:57.09 spid85 Dynamic Memory Manager:
Stolen=1178 OS Reserved=1648
ERRORLOG: OS Committed=1626
ERRORLOG: OS In Use=1616
ERRORLOG: Query Plan=20 Optimizer=0
ERRORLOG: General=2079
ERRORLOG: Utilities=151 Connection=252
ERRORLOG:2004-04-20 10:43:57.09 spid85 Global Memory Objects:
Resource=1770 Locks=131
ERRORLOG: SQLCache=92 Replication=2
ERRORLOG: LockBytes=2 ServerGlobal=53
ERRORLOG: Xact=75
ERRORLOG:2004-04-20 10:43:57.09 spid85 Query Memory Manager: Grants=2
Waiting=0 Maximum=138095 Available=66837
It looks very similar to what's mentioned in MS article 319477, except I
never receive an error 17803.
I am running SQL 2000, build 840, on Windows server 2003. Also, I have SQL
configured to use 14GB from a total of 16GB on the server.
Does anyone have any suggestions for how to address this?> I'm receiving this in my SQL errorlog:
> ERRORLOG:2004-04-20 10:43:56.95 spid85 BPool::Map: no remappable
address
> found.
> ERRORLOG:2004-04-20 10:43:57.09 spid85 Buffer Distribution:
> Stolen=126759 Free=1305 Procedures=0
> ERRORLOG: Inram=0 Dirty=12894 Kept=0
> ERRORLOG: I/O=50738, Latched=108, Other=1643204
> ERRORLOG:2004-04-20 10:43:57.09 spid85 Buffer Counts: Commited=1835008
> Target=1835008 Hashed=1706944
> ERRORLOG: InternalReservation=192 ExternalReservation=17101 Min Free=1024
> ERRORLOG:2004-04-20 10:43:57.09 spid85 Procedure Cache: TotalProcs=0
> TotalPages=0 InUsePages=0
> ERRORLOG:2004-04-20 10:43:57.09 spid85 Dynamic Memory Manager:
> Stolen=1178 OS Reserved=1648
> ERRORLOG: OS Committed=1626
> ERRORLOG: OS In Use=1616
> ERRORLOG: Query Plan=20 Optimizer=0
> ERRORLOG: General=2079
> ERRORLOG: Utilities=151 Connection=252
> ERRORLOG:2004-04-20 10:43:57.09 spid85 Global Memory Objects:
> Resource=1770 Locks=131
> ERRORLOG: SQLCache=92 Replication=2
> ERRORLOG: LockBytes=2 ServerGlobal=53
> ERRORLOG: Xact=75
> ERRORLOG:2004-04-20 10:43:57.09 spid85 Query Memory Manager: Grants=2
> Waiting=0 Maximum=138095 Available=66837
>
> It looks very similar to what's mentioned in MS article 319477, except I
> never receive an error 17803.
> I am running SQL 2000, build 840, on Windows server 2003. Also, I have SQL
> configured to use 14GB from a total of 16GB on the server.
> Does anyone have any suggestions for how to address this?
--
Please open an incident with your local Microsoft Product Support so this
can be looked at.
Regards,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Bound SQL to IP address

Hi!
If there are a few NIC installed in server is it possible to make SQL Server
2000 listen only on specific IP address?
Regards
Silmar"Silmar" <silmar@.talex.pl> wrote in message
news:OuC0#kMCHHA.3448@.TK2MSFTNGP03.phx.gbl...
> Hi!
> If there are a few NIC installed in server is it possible to make SQL
> Server 2000 listen only on specific IP address?
>
No. Only SQL 2005 can do this.
David

Bound SQL to IP address

Hi!
If there are a few NIC installed in server is it possible to make SQL Server
2000 listen only on specific IP address?
Regards
Silmar"Silmar" <silmar@.talex.pl> wrote in message
news:OuC0#kMCHHA.3448@.TK2MSFTNGP03.phx.gbl...
> Hi!
> If there are a few NIC installed in server is it possible to make SQL
> Server 2000 listen only on specific IP address?
>
No. Only SQL 2005 can do this.
David