Excessive Page Faults?

I am noticing that an many of my servers (Server 2003 EE SP2 R2), that the
MsMpEng.exe and MOMHost.exe processes are creating a significant number of
page faults.
For example, on my SQL 2000 SP4 server with 4GB RAM which has been up for 19
days has nearly 19M page faults on MsMpEng and over 16M faults on MOMHost.
Another example is my Exchange 2003 SP2 with 4GB RAM which has also been up
for 19 days has nearly 182M faults on MsMpEng and nearly 16M faults on
MOMHost.
Keep in mind that the "M" with the number is million.
We only recently started using Forefront on our servers, and this appears to
be a relatively new issue, and I would like to know if others have been
experiencing this as well.
RichardThis is not an exchange issue...
But take a look at
http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
"Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
>I am noticing that an many of my servers (Server 2003 EE SP2 R2), that the
>MsMpEng.exe and MOMHost.exe processes are creating a significant number of
>page faults.
> For example, on my SQL 2000 SP4 server with 4GB RAM which has been up for
> 19 days has nearly 19M page faults on MsMpEng and over 16M faults on
> MOMHost.
> Another example is my Exchange 2003 SP2 with 4GB RAM which has also been
> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M faults on
> MOMHost.
> Keep in mind that the "M" with the number is million.
> We only recently started using Forefront on our servers, and this appears
> to be a relatively new issue, and I would like to know if others have been
> experiencing this as well.
> Richard|||Thanks for the link to the article. This does give some additional
information, however the problem in the article points more to high CPU
utilization rather than high number of page faults. Perhaps since this also
includes the MOM components, I should try posting in that forum as the
Forefront group is fairly new?
Richard
"Betelgeuse" <betelgeuse@.news.postalias> wrote in message
news:OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl...
> This is not an exchange issue...
> But take a look at
> http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
>
> "Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
> news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
>>I am noticing that an many of my servers (Server 2003 EE SP2 R2), that the
>>MsMpEng.exe and MOMHost.exe processes are creating a significant number of
>>page faults.
>> For example, on my SQL 2000 SP4 server with 4GB RAM which has been up for
>> 19 days has nearly 19M page faults on MsMpEng and over 16M faults on
>> MOMHost.
>> Another example is my Exchange 2003 SP2 with 4GB RAM which has also been
>> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M faults on
>> MOMHost.
>> Keep in mind that the "M" with the number is million.
>> We only recently started using Forefront on our servers, and this appears
>> to be a relatively new issue, and I would like to know if others have
>> been experiencing this as well.
>> Richard
>|||Dear Richard,
Thank you for posting here.
I understand that the process MsMpEng.exe and MOMHost.exe processes are
creating a significant number of page faults on several servers.
According to your description, it appears that the issue should not on the
SQL Server side. Based on my experience, this behavior can occur due to a
Memory Leak but sometimes it is normal for some processes. In order to
ensure the current status, I would like to confirm the following
information before going further:
1. Has the performance on these severs been affected due to this issue?
2. Please also use the Performance Monitor utility to monitor the stability
of memory pages used by these two processes.
To do so, please refer to the following steps:
--
a. Enter the Control Panel -> Administrative Tools -> Performance.
b. Select "Process" in the "Performance object" selection
c. Add the following counter for the two processes (MsMpEng.exe and
MOMHost.exe) in question:
- Working Set (The Working Set is the set of memory pages touched recently
by the threads in the process)
- Virtual Bytes (Virtual Bytes is the current size, in bytes, of the
virtual address space the process is using)
NOTE: You can also add some main process for this server. E.X: sqlservr.exe
process
d. If the indication goes very smoothly, it indicates that the memory usage
of these processes is stable. In opposition, the memory leak issue may
exist.
At the same time, on the SQL Server side, we can attempt to adjust the
memory to see if it helps. Below are the detail steps:
--
a. Open the SQL Server Management Studio
b. Right click on the SQL Server instance->choose Properties.
c. Click on the Memory tab on the left panel, adjust the memory for your
SQL Server.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
--
| From: "Richard Perry" <RichardPerry@.newsgroup.nospam>
| References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
<OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
| Subject: Re: Excessive Page Faults?
| Date: Thu, 11 Oct 2007 12:56:40 -0700
| Lines: 1
| Message-ID: <84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=response
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| Importance: Normal
| X-Newsreader: Microsoft Windows Live Mail 12.0.1365
| X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1365
| X-MS-CommunityGroup-PostID: {84D91F2A-E4A6-4933-B34B-72879DD28277}
| X-MS-CommunityGroup-ThreadID: 3BFD2358-2798-4A29-B54A-EA90AD883293
| X-MS-CommunityGroup-ParentID: 47993B93-4F51-47EE-BE41-7DBD1C4B8AF7
| Newsgroups:
microsoft.public.exchange.admin,microsoft.public.security.forefront,microsof
t.public.sqlserver.server
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.security.forefront:71
microsoft.public.sqlserver.server:27713
microsoft.public.exchange.admin:47476
| NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Thanks for the link to the article. This does give some additional
| information, however the problem in the article points more to high CPU
| utilization rather than high number of page faults. Perhaps since this
also
| includes the MOM components, I should try posting in that forum as the
| Forefront group is fairly new?
|
| Richard
|
| "Betelgeuse" <betelgeuse@.news.postalias> wrote in message
| news:OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl...
| > This is not an exchange issue...
| >
| > But take a look at
| > http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
| >
| >
| > "Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
| > news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
| >>I am noticing that an many of my servers (Server 2003 EE SP2 R2), that
the
| >>MsMpEng.exe and MOMHost.exe processes are creating a significant number
of
| >>page faults.
| >>
| >> For example, on my SQL 2000 SP4 server with 4GB RAM which has been up
for
| >> 19 days has nearly 19M page faults on MsMpEng and over 16M faults on
| >> MOMHost.
| >>
| >> Another example is my Exchange 2003 SP2 with 4GB RAM which has also
been
| >> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M faults
on
| >> MOMHost.
| >>
| >> Keep in mind that the "M" with the number is million.
| >>
| >> We only recently started using Forefront on our servers, and this
appears
| >> to be a relatively new issue, and I would like to know if others have
| >> been experiencing this as well.
| >>
| >> Richard
| >
| >
||||Dear Richard,
We just want to say hi and check if there is anything further we can do for
you. If there is, please don't hesitate to let us know.
Regards,
Sophie Tan, MCSE 2000
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| X-Tomcat-ID: 94083421
| References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
<OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
<84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@.online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Fri, 12 Oct 2007 07:35:19 GMT
| Subject: Re: Excessive Page Faults?
| X-Tomcat-NG: microsoft.public.sqlserver.server
| Message-ID: <8LjAyJKDIHA.4664@.TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| Lines: 132
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:27758
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Richard,
|
| Thank you for posting here.
|
| I understand that the process MsMpEng.exe and MOMHost.exe processes are
| creating a significant number of page faults on several servers.
|
| According to your description, it appears that the issue should not on
the
| SQL Server side. Based on my experience, this behavior can occur due to a
| Memory Leak but sometimes it is normal for some processes. In order to
| ensure the current status, I would like to confirm the following
| information before going further:
|
| 1. Has the performance on these severs been affected due to this issue?
|
| 2. Please also use the Performance Monitor utility to monitor the
stability
| of memory pages used by these two processes.
|
| To do so, please refer to the following steps:
| --
| a. Enter the Control Panel -> Administrative Tools -> Performance.
| b. Select "Process" in the "Performance object" selection
| c. Add the following counter for the two processes (MsMpEng.exe and
| MOMHost.exe) in question:
|
| - Working Set (The Working Set is the set of memory pages touched
recently
| by the threads in the process)
| - Virtual Bytes (Virtual Bytes is the current size, in bytes, of the
| virtual address space the process is using)
|
| NOTE: You can also add some main process for this server. E.X:
sqlservr.exe
| process
|
| d. If the indication goes very smoothly, it indicates that the memory
usage
| of these processes is stable. In opposition, the memory leak issue may
| exist.
|
| At the same time, on the SQL Server side, we can attempt to adjust the
| memory to see if it helps. Below are the detail steps:
| --
| a. Open the SQL Server Management Studio
| b. Right click on the SQL Server instance->choose Properties.
| c. Click on the Memory tab on the left panel, adjust the memory for your
| SQL Server.
|
| Have a nice day!
|
| Best regards,
|
| Adams Qu
| MCSE, MCDBA, MCTS
| Microsoft Online Support
|
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
| =====================================================| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| =====================================================| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
| --
| | From: "Richard Perry" <RichardPerry@.newsgroup.nospam>
| | References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
| <OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
| | Subject: Re: Excessive Page Faults?
| | Date: Thu, 11 Oct 2007 12:56:40 -0700
| | Lines: 1
| | Message-ID: <84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
| | MIME-Version: 1.0
| | Content-Type: text/plain;
| | format=flowed;
| | charset="iso-8859-1";
| | reply-type=response
| | Content-Transfer-Encoding: 7bit
| | X-Priority: 3
| | X-MSMail-Priority: Normal
| | Importance: Normal
| | X-Newsreader: Microsoft Windows Live Mail 12.0.1365
| | X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1365
| | X-MS-CommunityGroup-PostID: {84D91F2A-E4A6-4933-B34B-72879DD28277}
| | X-MS-CommunityGroup-ThreadID: 3BFD2358-2798-4A29-B54A-EA90AD883293
| | X-MS-CommunityGroup-ParentID: 47993B93-4F51-47EE-BE41-7DBD1C4B8AF7
| | Newsgroups:
|
microsoft.public.exchange.admin,microsoft.public.security.forefront,microsof
| t.public.sqlserver.server
| | Path: TK2MSFTNGHUB02.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.security.forefront:71
| microsoft.public.sqlserver.server:27713
| microsoft.public.exchange.admin:47476
| | NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| | X-Tomcat-NG: microsoft.public.sqlserver.server
| |
| | Thanks for the link to the article. This does give some additional
| | information, however the problem in the article points more to high CPU
| | utilization rather than high number of page faults. Perhaps since this
| also
| | includes the MOM components, I should try posting in that forum as the
| | Forefront group is fairly new?
| |
| | Richard
| |
| | "Betelgeuse" <betelgeuse@.news.postalias> wrote in message
| | news:OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl...
| | > This is not an exchange issue...
| | >
| | > But take a look at
| | > http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
| | >
| | >
| | > "Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
| | > news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
| | >>I am noticing that an many of my servers (Server 2003 EE SP2 R2),
that
| the
| | >>MsMpEng.exe and MOMHost.exe processes are creating a significant
number
| of
| | >>page faults.
| | >>
| | >> For example, on my SQL 2000 SP4 server with 4GB RAM which has been
up
| for
| | >> 19 days has nearly 19M page faults on MsMpEng and over 16M faults on
| | >> MOMHost.
| | >>
| | >> Another example is my Exchange 2003 SP2 with 4GB RAM which has also
| been
| | >> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M
faults
| on
| | >> MOMHost.
| | >>
| | >> Keep in mind that the "M" with the number is million.
| | >>
| | >> We only recently started using Forefront on our servers, and this
| appears
| | >> to be a relatively new issue, and I would like to know if others
have
| | >> been experiencing this as well.
| | >>
| | >> Richard
| | >
| | >
| |
|
||||Sorry for the long delay in replying to this post. With the fires here is
SoCal, things have been fairly hectic.
Following your suggestions, I am verified that there is not a memory leak
with regards to these processes. Therefore, I am left with the simple
concern of the performance of Forefront on the Server platform. I will raise
this issue in the Forefront forums.
I do have a recurring issue with timeouts to the database that I am
troubleshooting, and it was this issue that prompted my looking at the
paging performance. I have consistently believed that the cause if these
timeouts is due to our network configuration, but for the sake of
completeness, I have been verifying our SQL setup. I will post regarding
those timeouts in another thread.
Sophie Tan, if you see this, I wanted to thank you for your follow up post
as well. At this time, I would consider this thread closed.
Richard Perry
"Adams Qu [MSFT]" <v-adamqu@.online.microsoft.com> wrote in message
news:8LjAyJKDIHA.4664@.TK2MSFTNGHUB02.phx.gbl...
> Dear Richard,
> Thank you for posting here.
> I understand that the process MsMpEng.exe and MOMHost.exe processes are
> creating a significant number of page faults on several servers.
> According to your description, it appears that the issue should not on the
> SQL Server side. Based on my experience, this behavior can occur due to a
> Memory Leak but sometimes it is normal for some processes. In order to
> ensure the current status, I would like to confirm the following
> information before going further:
> 1. Has the performance on these severs been affected due to this issue?
> 2. Please also use the Performance Monitor utility to monitor the
> stability
> of memory pages used by these two processes.
> To do so, please refer to the following steps:
> --
> a. Enter the Control Panel -> Administrative Tools -> Performance.
> b. Select "Process" in the "Performance object" selection
> c. Add the following counter for the two processes (MsMpEng.exe and
> MOMHost.exe) in question:
> - Working Set (The Working Set is the set of memory pages touched recently
> by the threads in the process)
> - Virtual Bytes (Virtual Bytes is the current size, in bytes, of the
> virtual address space the process is using)
> NOTE: You can also add some main process for this server. E.X:
> sqlservr.exe
> process
> d. If the indication goes very smoothly, it indicates that the memory
> usage
> of these processes is stable. In opposition, the memory leak issue may
> exist.
> At the same time, on the SQL Server side, we can attempt to adjust the
> memory to see if it helps. Below are the detail steps:
> --
> a. Open the SQL Server Management Studio
> b. Right click on the SQL Server instance->choose Properties.
> c. Click on the Memory tab on the left panel, adjust the memory for your
> SQL Server.
> Have a nice day!
> Best regards,
> Adams Qu
> MCSE, MCDBA, MCTS
> Microsoft Online Support
> Microsoft Global Technical Support Center
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> --
> | From: "Richard Perry" <RichardPerry@.newsgroup.nospam>
> | References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
> <OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
> | Subject: Re: Excessive Page Faults?
> | Date: Thu, 11 Oct 2007 12:56:40 -0700
> | Lines: 1
> | Message-ID: <84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | format=flowed;
> | charset="iso-8859-1";
> | reply-type=response
> | Content-Transfer-Encoding: 7bit
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | Importance: Normal
> | X-Newsreader: Microsoft Windows Live Mail 12.0.1365
> | X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1365
> | X-MS-CommunityGroup-PostID: {84D91F2A-E4A6-4933-B34B-72879DD28277}
> | X-MS-CommunityGroup-ThreadID: 3BFD2358-2798-4A29-B54A-EA90AD883293
> | X-MS-CommunityGroup-ParentID: 47993B93-4F51-47EE-BE41-7DBD1C4B8AF7
> | Newsgroups:
> microsoft.public.exchange.admin,microsoft.public.security.forefront,microsof
> t.public.sqlserver.server
> | Path: TK2MSFTNGHUB02.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.security.forefront:71
> microsoft.public.sqlserver.server:27713
> microsoft.public.exchange.admin:47476
> | NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | Thanks for the link to the article. This does give some additional
> | information, however the problem in the article points more to high CPU
> | utilization rather than high number of page faults. Perhaps since this
> also
> | includes the MOM components, I should try posting in that forum as the
> | Forefront group is fairly new?
> |
> | Richard
> |
> | "Betelgeuse" <betelgeuse@.news.postalias> wrote in message
> | news:OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl...
> | > This is not an exchange issue...
> | >
> | > But take a look at
> | > http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
> | >
> | >
> | > "Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
> | > news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
> | >>I am noticing that an many of my servers (Server 2003 EE SP2 R2), that
> the
> | >>MsMpEng.exe and MOMHost.exe processes are creating a significant
> number
> of
> | >>page faults.
> | >>
> | >> For example, on my SQL 2000 SP4 server with 4GB RAM which has been up
> for
> | >> 19 days has nearly 19M page faults on MsMpEng and over 16M faults on
> | >> MOMHost.
> | >>
> | >> Another example is my Exchange 2003 SP2 with 4GB RAM which has also
> been
> | >> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M
> faults
> on
> | >> MOMHost.
> | >>
> | >> Keep in mind that the "M" with the number is million.
> | >>
> | >> We only recently started using Forefront on our servers, and this
> appears
> | >> to be a relatively new issue, and I would like to know if others have
> | >> been experiencing this as well.
> | >>
> | >> Richard
> | >
> | >
> |
>|||Dear Richard,
Thank you for posting back.
From your last post, we are glad to hear that the memory leak issue does
not exist after we verified manually on the server.
I also understand that another issue with timeouts to the database is
experienced. To help you resolve the issue more efficiently, I also would
like to share with you the following troubleshooting information. You can
try the following points before submitting the new thread.
Reference Information on the second issue
--
Based on my experience, the time-out connection issue can be concluded to
be caused by one of the following two factors commonly:
a. Caused by the network configuration (as you mentioned)
b. The second cause is that the SQL Server is running on a heavy load at
that time.
c. Application or hard driver factors.
Please use SQL Profiler and Perfmon to monitor your SQL Server to see what
happens if the connection timeout occurs.
I also would like to provide the following links for your reference:
HOW TO: Troubleshoot Application Performance with SQL Server
http://support.microsoft.com/kb/224587/en-us
Troubleshooting Performance Problems in SQL Server 2005
http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx
INF: Understanding and Resolving SQL Server 7.0 or 2000 Blocking Problems
http://support.microsoft.com/kb/224453/en-us
Hope above information is helpful. Once we see your new thread, we will be
glad to follow up and help you. If you have any other questions or
concerns, please do not hesitate to contact us. It is always my pleasure to
be of assistance.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
--
| From: "Richard Perry" <RichardPerry@.newsgroup.nospam>
| References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
<OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
<84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
<8LjAyJKDIHA.4664@.TK2MSFTNGHUB02.phx.gbl>
| Subject: Re: Excessive Page Faults?
| Date: Wed, 31 Oct 2007 16:54:13 -0700
| Lines: 2
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=original
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| Importance: Normal
| X-Newsreader: Microsoft Windows Live Mail 12.0.1365
| X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1365
| Message-ID: <#82$XlBHIHA.4768@.TK2MSFTNGP03.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: 209.242.152.130
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:29221
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Sorry for the long delay in replying to this post. With the fires here is
| SoCal, things have been fairly hectic.
|
| Following your suggestions, I am verified that there is not a memory leak
| with regards to these processes. Therefore, I am left with the simple
| concern of the performance of Forefront on the Server platform. I will
raise
| this issue in the Forefront forums.
|
| I do have a recurring issue with timeouts to the database that I am
| troubleshooting, and it was this issue that prompted my looking at the
| paging performance. I have consistently believed that the cause if these
| timeouts is due to our network configuration, but for the sake of
| completeness, I have been verifying our SQL setup. I will post regarding
| those timeouts in another thread.
|
| Sophie Tan, if you see this, I wanted to thank you for your follow up
post
| as well. At this time, I would consider this thread closed.
|
| Richard Perry
|
|
| "Adams Qu [MSFT]" <v-adamqu@.online.microsoft.com> wrote in message
| news:8LjAyJKDIHA.4664@.TK2MSFTNGHUB02.phx.gbl...
| > Dear Richard,
| >
| > Thank you for posting here.
| >
| > I understand that the process MsMpEng.exe and MOMHost.exe processes are
| > creating a significant number of page faults on several servers.
| >
| > According to your description, it appears that the issue should not on
the
| > SQL Server side. Based on my experience, this behavior can occur due to
a
| > Memory Leak but sometimes it is normal for some processes. In order to
| > ensure the current status, I would like to confirm the following
| > information before going further:
| >
| > 1. Has the performance on these severs been affected due to this issue?
| >
| > 2. Please also use the Performance Monitor utility to monitor the
| > stability
| > of memory pages used by these two processes.
| >
| > To do so, please refer to the following steps:
| > --
| > a. Enter the Control Panel -> Administrative Tools -> Performance.
| > b. Select "Process" in the "Performance object" selection
| > c. Add the following counter for the two processes (MsMpEng.exe and
| > MOMHost.exe) in question:
| >
| > - Working Set (The Working Set is the set of memory pages touched
recently
| > by the threads in the process)
| > - Virtual Bytes (Virtual Bytes is the current size, in bytes, of the
| > virtual address space the process is using)
| >
| > NOTE: You can also add some main process for this server. E.X:
| > sqlservr.exe
| > process
| >
| > d. If the indication goes very smoothly, it indicates that the memory
| > usage
| > of these processes is stable. In opposition, the memory leak issue may
| > exist.
| >
| > At the same time, on the SQL Server side, we can attempt to adjust the
| > memory to see if it helps. Below are the detail steps:
| > --
| > a. Open the SQL Server Management Studio
| > b. Right click on the SQL Server instance->choose Properties.
| > c. Click on the Memory tab on the left panel, adjust the memory for your
| > SQL Server.
| >
| > Have a nice day!
| >
| > Best regards,
| >
| > Adams Qu
| > MCSE, MCDBA, MCTS
| > Microsoft Online Support
| >
| > Microsoft Global Technical Support Center
| >
| > Get Secure! - www.microsoft.com/security
| > =====================================================| > When responding to posts, please "Reply to Group" via your newsreader so
| > that others may learn and benefit from your issue.
| > =====================================================| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| >
| > --
| > | From: "Richard Perry" <RichardPerry@.newsgroup.nospam>
| > | References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
| > <OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
| > | Subject: Re: Excessive Page Faults?
| > | Date: Thu, 11 Oct 2007 12:56:40 -0700
| > | Lines: 1
| > | Message-ID: <84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | format=flowed;
| > | charset="iso-8859-1";
| > | reply-type=response
| > | Content-Transfer-Encoding: 7bit
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | Importance: Normal
| > | X-Newsreader: Microsoft Windows Live Mail 12.0.1365
| > | X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1365
| > | X-MS-CommunityGroup-PostID: {84D91F2A-E4A6-4933-B34B-72879DD28277}
| > | X-MS-CommunityGroup-ThreadID: 3BFD2358-2798-4A29-B54A-EA90AD883293
| > | X-MS-CommunityGroup-ParentID: 47993B93-4F51-47EE-BE41-7DBD1C4B8AF7
| > | Newsgroups:
| >
microsoft.public.exchange.admin,microsoft.public.security.forefront,microsof
| > t.public.sqlserver.server
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.security.forefront:71
| > microsoft.public.sqlserver.server:27713
| > microsoft.public.exchange.admin:47476
| > | NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| > | X-Tomcat-NG: microsoft.public.sqlserver.server
| > |
| > | Thanks for the link to the article. This does give some additional
| > | information, however the problem in the article points more to high
CPU
| > | utilization rather than high number of page faults. Perhaps since this
| > also
| > | includes the MOM components, I should try posting in that forum as the
| > | Forefront group is fairly new?
| > |
| > | Richard
| > |
| > | "Betelgeuse" <betelgeuse@.news.postalias> wrote in message
| > | news:OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl...
| > | > This is not an exchange issue...
| > | >
| > | > But take a look at
| > | > http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
| > | >
| > | >
| > | > "Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
| > | > news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
| > | >>I am noticing that an many of my servers (Server 2003 EE SP2 R2),
that
| > the
| > | >>MsMpEng.exe and MOMHost.exe processes are creating a significant
| > number
| > of
| > | >>page faults.
| > | >>
| > | >> For example, on my SQL 2000 SP4 server with 4GB RAM which has been
up
| > for
| > | >> 19 days has nearly 19M page faults on MsMpEng and over 16M faults
on
| > | >> MOMHost.
| > | >>
| > | >> Another example is my Exchange 2003 SP2 with 4GB RAM which has also
| > been
| > | >> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M
| > faults
| > on
| > | >> MOMHost.
| > | >>
| > | >> Keep in mind that the "M" with the number is million.
| > | >>
| > | >> We only recently started using Forefront on our servers, and this
| > appears
| > | >> to be a relatively new issue, and I would like to know if others
have
| > | >> been experiencing this as well.
| > | >>
| > | >> Richard
| > | >
| > | >
| > |
| >
|

excessive dtexec logging post SP2

Since the other related topic is closed/answered...

The Short version:

SQL is now logging too much info with every package. The volume of the new "User: Diagnostic" event has caused some packages to fail and the command-line exclusion option appears to have no effect on the events logged to the SQL provider. Is this a bug in dtexec or am I using the wrong syntax to exclude log entries? I don't want to modify all of my SSIS packages...

More Info:

SQL SP2 introduced new logging events, most of which appear to get logged by default. So far, none of our packages have used any sort of explicit logging configuration; it's all been set at the command line using a syntax like shown below:

dtexec.exe /FILE "D:\SSIS Packages\MyApp\Vendors.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REP E;Diagnostic /LOGGER "{6AA833A1-E4B2-4431-831B-DE695049DC61}";"MyDBConnName"

This does appear to correctly limit what gets logged to the console (and thereby the SQL Agent's job step log), but has no effect on what's logged to the database. Normally, I'd use /REP EWDCI, but I was attempting to limit the log entries to Errors only.

I first came across this error when a package failed, but it only logged the following to the console with nothing in sysdtslog90 (while not the "latest/greatest" server, this is a relatively low-utilized quad 2.8ghz xeon ProLiant DL580 G2):

Error: 2007-06-21 06:01:30.45
Code: 0xC0202009
Source: MYPACKAGENAME Log provider "{0C3CBE9B-D828-41C2-98D2-99BA498B314A}"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Connection is busy with results for another command".
End Error
Error: 2007-06-21 06:01:30.46
Code: 0xC0014010
Source: MYPACKAGESTEP Load
Description: The SSIS logging provider "{0C3CBE9B-D828-41C2-98D2-99BA498B314A}" failed with error code 0xC0202009 ((null)). This indicates a logging error attributable to the specified log provider.
End Error

I changed this one package to only log OnError events, but I'd rather not have to change every package to do the same, plus I'd like the ability to easily turn on verbose or any other logging level when needed.

At this point, fine-grained control of logging which is initiated external to the package itself, is basically only available programmatically. External logging can be accomplish by by implementing a logger, an event listener, by hooking/redirecting the byte stream produced by dtexec.exe, or by programmatically configuring the LoggingOptions class on the package object. Within the package itself is a differrent story, but it would seem you're looking for externalization of logging control.

dtexec's "/reporting" command line switch relates to console events and the "/consolelog" command line switch relates to fields which are sent to the console for a given event. To observe the applicability of the two switches, run dtexecui.exe, a gui based dtexec command line builder. Notice under the reporting node, the selectable events are listed as "console events".

Exception occurred

Hi,
I installed SQL Server 2000 Dev Edition on a Windows XP SP2, but whenever I
login, and try to open a database's table, or to re-set the SA's password,
(or maybe other command), I will always get this error message,
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Anybody knows what this is and how to overcome?
I have applied the SP3 on the SQL Server.
And my SA's password was set to NULL.
Thanks in advance
Frank
You should contact Microsoft PSS to assist you with this problem.
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Frank" <wangping67@.163.com> wrote in message
news:emysEIIBFHA.3120@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I installed SQL Server 2000 Dev Edition on a Windows XP SP2, but whenever
> I login, and try to open a database's table, or to re-set the SA's
> password, (or maybe other command), I will always get this error message,
> ODBC: Msg 0, Level 19, State 1
> SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> Anybody knows what this is and how to overcome?
> I have applied the SP3 on the SQL Server.
> And my SA's password was set to NULL.
> Thanks in advance
> Frank
>

Exception occurred

Hi,
I installed SQL Server 2000 Dev Edition on a Windows XP SP2, but whenever I
login, and try to open a database's table, or to re-set the SA's password,
(or maybe other command), I will always get this error message,
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Anybody knows what this is and how to overcome?
I have applied the SP3 on the SQL Server.
And my SA's password was set to NULL.
Thanks in advance
FrankYou should contact Microsoft PSS to assist you with this problem.
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Frank" <wangping67@.163.com> wrote in message
news:emysEIIBFHA.3120@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I installed SQL Server 2000 Dev Edition on a Windows XP SP2, but whenever
> I login, and try to open a database's table, or to re-set the SA's
> password, (or maybe other command), I will always get this error message,
> ODBC: Msg 0, Level 19, State 1
> SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> Anybody knows what this is and how to overcome?
> I have applied the SP3 on the SQL Server.
> And my SA's password was set to NULL.
> Thanks in advance
> Frank
>

Exception occurred

Hi,
I installed SQL Server 2000 Dev Edition on a Windows XP SP2, but whenever I
login, and try to open a database's table, or to re-set the SA's password,
(or maybe other command), I will always get this error message,
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Anybody knows what this is and how to overcome?
I have applied the SP3 on the SQL Server.
And my SA's password was set to NULL.
Thanks in advance
FrankYou should contact Microsoft PSS to assist you with this problem.
--
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Frank" <wangping67@.163.com> wrote in message
news:emysEIIBFHA.3120@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I installed SQL Server 2000 Dev Edition on a Windows XP SP2, but whenever
> I login, and try to open a database's table, or to re-set the SA's
> password, (or maybe other command), I will always get this error message,
> ODBC: Msg 0, Level 19, State 1
> SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> Anybody knows what this is and how to overcome?
> I have applied the SP3 on the SQL Server.
> And my SA's password was set to NULL.
> Thanks in advance
> Frank
>

Excel Worksheets Become Corrupt -- Bad Metadata?

One of my main users has had a few Office 2003 SP2 worksheets go corrupt on him and I can't seem to figure out why.

For performance reasons, I recommended that he use page filters whenever possible. As of late, he'll send a workbook along that has a few page filters (between 3 and 4) and one of the page filters gets mixed up somehow.

For example, let's say he has a Product Line page filter and a Product Name page filter. The Product Line page filter has multiple selections enabled and he will go ahead and select a few product lines and save the file so he can simply refresh the data in the future. Eventually, the Product Name filter will actually contain the Product Lines and the Product Line filter becomes unusable, usually resulting in a strange error indicating that Excel cannot complete the task with available resources when the drop-down is selected. The other page filters seem to behave normally and the report will still operate until the corrupted page filter(s) are selected.

I've seen 2 of his worksheet/workbooks exhibit this behavior this week. He says he's encountered this before and has rebuilt these reports from scratch only to end up with the same issue.

The AS2005 cube has not undergone any recent changes.

Any thoughts?

<quote>Product Name filter will actually contain the Product Lines and the Product Line filter becomes unusable...</quote>

This is something strange, and it would be good for you to provide more details here. One idea that crosses my mind: is it possible that some members from Product Line attribute/hierarchy have the same unique name as some members from Product Name attribute/hierarchy? If that is the case, you probably should modify the naming scheme in your SSAS cube to always include hierarchy name in member unique name.

|||

Tigran.Hayrapetyan wrote:

<quote>Product Name filter will actually contain the Product Lines and the Product Line filter becomes unusable...</quote>

This is something strange, and it would be good for you to provide more details here. One idea that crosses my mind: is it possible that some members from Product Line attribute/hierarchy have the same unique name as some members from Product Name attribute/hierarchy? If that is the case, you probably should modify the naming scheme in your SSAS cube to always include hierarchy name in member unique name.

Thanks for the reply Tigran. What are some other details that I can provide?

As for the same names, the values for Product Name and Product Line are vastly different from one another.|||

What I would like to know is what exactly happens in Page filter. When you use the dropdown for Product Name hierarchy, do members from Product Lines hierarchy appear in the Tree control?

But whatever the case, I think the best solution could be to involve Microsoft Support in resolving this issue.

|||

I came accross similar issues and found that the most easiest way to solve this is to use the Excel pivot table wizard to remove all the offending dimensions from the pivot view, refresh the pivot and put back the dimensions in the pivot view.

This will happen mostly when you change dimensions names or when the dimensions member names content change while the client has set a selection on a given member. (no longer in the cube).

Also be carefull with ColumnKeys and ColumNames It lloks like Excel will choke on dimensions where you defined a name and a key column while it was initially only a key column instead of using both a name and a key,

Excel will now use a key (internally, hard to spot). This is mostly impacting Excel views where you use VBA to control the pivot.

Hope it helps a little bit.

So, on the same topic, the issue I am facing now is linked to default member of a time dimension to be the current date.

Initially it works, however, as soon as I update the cube, it will stop to work because the current date set in the Excel view is no longer present in the cube as the current date set as default in the cube. Excel will not pick-up these changes dynamically without removing and putting back-in the dimension. (Excel2003 PTS9)

This lack of dynamic refresh of Excel members is annoying and was already an annoyance in SQL2000.

I would rather have the selector set-back to "ALL" rather than chocking on a missing member.

End users can cope with a selector reset to all, they cannot cope with a cube returning cryptic error messages.

Philippe.

|||

One more comment.

When using VBA to pilot a pivot from code, if you attempt to select a member that is no longer in the cube, you may end-up corrupting your pivot table.

I suspect tha this can also happen in some other cases where you do not use VBA.

Symptoms are as follow:

- Calculated members returns #value error code

- Break-down by individual members are no longer correct while the total remain correct.

Only way out is to rebuild a new pivot table from scratch.

This was happening a lot with Excel XP, it still happen with Excel2003 but very unfrequently.

Just to be on the safe side, when I am done developing a cube and its Excel pivot front-end, I always re-create the pivot from scratch just to make sure it is as clean as it can get.

Philippe

Excel Margins

Hello
Now with SP2 the page margins works fine. Exists a method to set the Footer
and Header margin in the Excel Rendering Extension?
Thanks...Hello Trace,
Can you pls share how the page margin works for excel. I want to define L/R
margin as 0.2 in but excel takes its default settings for .75 inche. What
setting do we need to make change for making it work on Excel with our page
margin.
Thanks in advance
Jasvinder
"Trace" wrote:
> Hello
> Now with SP2 the page margins works fine. Exists a method to set the Footer
> and Header margin in the Excel Rendering Extension?
> Thanks...|||Hello Jasvinder
I set the Margins with the Properties of the Report, but i set to 0.2cm. In
the Page preview of the Excel document the Margins are set to 0.2.
When i set the Margins to 0.2in then the Page preview display 0.5.
"Jasvinder" wrote:
> Hello Trace,
> Can you pls share how the page margin works for excel. I want to define L/R
> margin as 0.2 in but excel takes its default settings for .75 inche. What
> setting do we need to make change for making it work on Excel with our page
> margin.
> Thanks in advance
> Jasvinder
>
> "Trace" wrote:
> > Hello
> >
> > Now with SP2 the page margins works fine. Exists a method to set the Footer
> > and Header margin in the Excel Rendering Extension?
> >
> > Thanks...