Look@Lan has been updated
http://www.over-look.com
Friday, November 26, 2010
Thursday, November 25, 2010
SQl Server Blocking Detection
here is a good script that can be run when a SQL block occurs.
http://blog.sqlauthority.com/2010/10/06/sql-server-quickest-way-to-identify-blocking-query-and-resolution-dirty-solution/
SELECT
db.name DBName,
tl.request_session_id,
wt.blocking_session_id,
OBJECT_NAME(p.OBJECT_ID) BlockedObjectName,
tl.resource_type,
h1.TEXT AS RequestingText,
h2.TEXT AS BlockingTest,
tl.request_mode
FROM sys.dm_tran_locks AS tl
INNER JOIN sys.databases db ON db.database_id = tl.resource_database_id
INNER JOIN sys.dm_os_waiting_tasks AS wt ON tl.lock_owner_address = wt.resource_address
INNER JOIN sys.partitions AS p ON p.hobt_id = tl.resource_associated_entity_id
INNER JOIN sys.dm_exec_connections ec1 ON ec1.session_id = tl.request_session_id
INNER JOIN sys.dm_exec_connections ec2 ON ec2.session_id = wt.blocking_session_id
CROSS APPLY sys.dm_exec_sql_text(ec1.most_recent_sql_handle) AS h1
CROSS APPLY sys.dm_exec_sql_text(ec2.most_recent_sql_handle) AS h2
GO
http://blog.sqlauthority.com/2010/10/06/sql-server-quickest-way-to-identify-blocking-query-and-resolution-dirty-solution/
SELECT
db.name DBName,
tl.request_session_id,
wt.blocking_session_id,
OBJECT_NAME(p.OBJECT_ID) BlockedObjectName,
tl.resource_type,
h1.TEXT AS RequestingText,
h2.TEXT AS BlockingTest,
tl.request_mode
FROM sys.dm_tran_locks AS tl
INNER JOIN sys.databases db ON db.database_id = tl.resource_database_id
INNER JOIN sys.dm_os_waiting_tasks AS wt ON tl.lock_owner_address = wt.resource_address
INNER JOIN sys.partitions AS p ON p.hobt_id = tl.resource_associated_entity_id
INNER JOIN sys.dm_exec_connections ec1 ON ec1.session_id = tl.request_session_id
INNER JOIN sys.dm_exec_connections ec2 ON ec2.session_id = wt.blocking_session_id
CROSS APPLY sys.dm_exec_sql_text(ec1.most_recent_sql_handle) AS h1
CROSS APPLY sys.dm_exec_sql_text(ec2.most_recent_sql_handle) AS h2
GO
Thursday, October 21, 2010
Monday, October 18, 2010
How to transfer filezilla server settings
You can easily trasfer all settings from one filezilla server to another by copying the filezilla server.xml from one server to another
stop filezilla server
copy in filezilla server.xml
start filezilla server
stop filezilla server
copy in filezilla server.xml
start filezilla server
How to check for a postmaster in Exchange 2007
http://www.petri.co.il/creating-a-postmaster-mailbox-in-exchange-server-2007.htm
Servers:2008:IIS7:urlrewrite
http://learn.iis.net/page.aspx/803/using-custom-rewrite-providers-with-url-rewrite-module/
Tuesday, June 15, 2010
Servers:2008:IIS7:mem leak
Every so often 4-6 months
There is a memory leek in the NPP memory pool at a customer server which causes a IIS to stop responding.
The easiest resolution is to reboot the server.
Lots of extra analysis would need to be performed to find the root cause. i.e the driver which is causing the memory leek.
The symptoms are
1, Around every 4-6 months the IIS service on the server stops responding. The only way to resolve is to reboot the server.
2, From investigation IIS uses a NPP Kernal memory. This is used by other drivers on the server. If this runs out IIS will stop responding and will put a message into the http error log ‘connection refused’.
3. Even through all the services connected to IIS are restarted the site still does not respond. This points to a memory leek.
4, IIS uses HTTP.SYS in the NPP memory. Another process is hogging all the memory – used it up. HTTP.SYS needs to use that memory to handle connections.
There are two resolutions to this problem.
1, Automate a reboot of the server every weekend when no one is using it. This will clear out the NPP memory. This assumes the problem driver or process slowly increases it memory usage over time
2, Run through the articles below, find the driver/process, try updating it or remove the program.
KB 177415 - How to Use Memory Pool Monitor (Poolmon.exe) to Troubleshoot Kernel Mode Memory Leaks – http://support.microsoft.com/?id=177415
KB 298102 - How to Find Pool Tags that are used by Third-Party Drivers – http://support.microsoft.com/?id=298102
There is a memory leek in the NPP memory pool at a customer server which causes a IIS to stop responding.
The easiest resolution is to reboot the server.
Lots of extra analysis would need to be performed to find the root cause. i.e the driver which is causing the memory leek.
The symptoms are
1, Around every 4-6 months the IIS service on the server stops responding. The only way to resolve is to reboot the server.
2, From investigation IIS uses a NPP Kernal memory. This is used by other drivers on the server. If this runs out IIS will stop responding and will put a message into the http error log ‘connection refused’.
3. Even through all the services connected to IIS are restarted the site still does not respond. This points to a memory leek.
4, IIS uses HTTP.SYS in the NPP memory. Another process is hogging all the memory – used it up. HTTP.SYS needs to use that memory to handle connections.
There are two resolutions to this problem.
1, Automate a reboot of the server every weekend when no one is using it. This will clear out the NPP memory. This assumes the problem driver or process slowly increases it memory usage over time
2, Run through the articles below, find the driver/process, try updating it or remove the program.
KB 177415 - How to Use Memory Pool Monitor (Poolmon.exe) to Troubleshoot Kernel Mode Memory Leaks – http://support.microsoft.com/?id=177415
KB 298102 - How to Find Pool Tags that are used by Third-Party Drivers – http://support.microsoft.com/?id=298102
Subscribe to:
Posts (Atom)
