Inserachof
asked on
Server Performance Issues
Windows 2003 Standard R2 DC SP2 server
SQL 2005 Standard SP3
Today at 11:00 AM I got these errors
Type : Error
Date : 4/2/2010
Time : 11:03:03 AM
Event : 7011
Source : Service Control Manager
Category : None
User : N/A
Computer : TGCS001
Description:
Timeout (60000 milliseconds) waiting for a transaction response from the NtFrs service.
Type : Information
Date : 4/2/2010
Time : 11:00:36 AM
Event : 17890
Source : MSSQLSERVER
Category : Server
User : N/A
Computer : TGCS001
Description:
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 1784, committed (KB): 666732, memory utilization: 0%.
Type : Error
Date : 4/2/2010
Time : 11:01:31 AM
Event : 107
Source : Report Server Windows Service (MSSQLSERVER)
Category : Management
User : N/A
Computer : TGCS001
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
Type : Information
Date : 4/2/2010
Time : 11:03:02 AM
Event : 833
Source : MSSQLSERVER
Category : Server
User : N/A
Computer : TGCS001
Description:
SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ tempdb.mdf ] in database [tempdb] (2). The OS file handle is 0x0000070C. The offset of the latest long I/O is: 0x0000000008a000
Type : Error
Date : 4/2/2010
Time : 11:03:06 AM
Event : 5000
Source : SQLDUMPER
Category : None
User : N/A
Computer : TGCS001
Description:
EventType sql90exception, P1 sqlservr.exe, P2 2005.90.4266.0, P3 4acd5494, P4 sqlservr.exe, P5 2005.90.4266.0, P6 4acd5494, P7 0, P8 011b7c15, P9 000001ff, P10 NIL.
Type : Information
Date : 4/2/2010
Time : 11:03:06 AM
Event : 17883
Source : MSSQLSERVER
Category : Server
User : N/A
Computer : TGCS001
Description:
Process 2:0:0 (0x7c4) Worker 0x03B200E8 appears to be non-yielding on Scheduler 0. Thread creation time: 12914553878609. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 97%. Interval: 70014 ms.
Type : Information
Date : 4/2/2010
Time : 11:03:07 AM
Event : 5001
Source : SQLDUMPER
Category : None
User : N/A
Computer : TGCS001
Description:
Bucket 1072696965, bucket table 5, EventType sql90exception, P1 sqlservr.exe, P2 2005.90.4266.0, P3 4acd5494, P4 sqlservr.exe, P5 2005.90.4266.0, P6 4acd5494, P7 0, P8 011b7c15, P9 000001ff, P10 NIL.
Type : Information
Date : 4/2/2010
Time : 11:03:14 AM
Event : 1010
Source : SQLDUMPER
Category : None
User : N/A
Computer : TGCS001
Description:
Bucket 1072696965, bucket table 5.
Type : Information
Date : 4/2/2010
Time : 11:06:15 AM
Event : 17890
Source : MSSQLSERVER
Category : Server
User : N/A
Computer : TGCS001
Description:
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 339 seconds. Working set (KB): 78532, committed (KB): 181348, memory utilization: 43%.
I am getting event 17890 on a regular basis
Any ideas
thanks
SQL 2005 Standard SP3
Today at 11:00 AM I got these errors
Type : Error
Date : 4/2/2010
Time : 11:03:03 AM
Event : 7011
Source : Service Control Manager
Category : None
User : N/A
Computer : TGCS001
Description:
Timeout (60000 milliseconds) waiting for a transaction response from the NtFrs service.
Type : Information
Date : 4/2/2010
Time : 11:00:36 AM
Event : 17890
Source : MSSQLSERVER
Category : Server
User : N/A
Computer : TGCS001
Description:
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 1784, committed (KB): 666732, memory utilization: 0%.
Type : Error
Date : 4/2/2010
Time : 11:01:31 AM
Event : 107
Source : Report Server Windows Service (MSSQLSERVER)
Category : Management
User : N/A
Computer : TGCS001
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
Type : Information
Date : 4/2/2010
Time : 11:03:02 AM
Event : 833
Source : MSSQLSERVER
Category : Server
User : N/A
Computer : TGCS001
Description:
SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\
Type : Error
Date : 4/2/2010
Time : 11:03:06 AM
Event : 5000
Source : SQLDUMPER
Category : None
User : N/A
Computer : TGCS001
Description:
EventType sql90exception, P1 sqlservr.exe, P2 2005.90.4266.0, P3 4acd5494, P4 sqlservr.exe, P5 2005.90.4266.0, P6 4acd5494, P7 0, P8 011b7c15, P9 000001ff, P10 NIL.
Type : Information
Date : 4/2/2010
Time : 11:03:06 AM
Event : 17883
Source : MSSQLSERVER
Category : Server
User : N/A
Computer : TGCS001
Description:
Process 2:0:0 (0x7c4) Worker 0x03B200E8 appears to be non-yielding on Scheduler 0. Thread creation time: 12914553878609. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 97%. Interval: 70014 ms.
Type : Information
Date : 4/2/2010
Time : 11:03:07 AM
Event : 5001
Source : SQLDUMPER
Category : None
User : N/A
Computer : TGCS001
Description:
Bucket 1072696965, bucket table 5, EventType sql90exception, P1 sqlservr.exe, P2 2005.90.4266.0, P3 4acd5494, P4 sqlservr.exe, P5 2005.90.4266.0, P6 4acd5494, P7 0, P8 011b7c15, P9 000001ff, P10 NIL.
Type : Information
Date : 4/2/2010
Time : 11:03:14 AM
Event : 1010
Source : SQLDUMPER
Category : None
User : N/A
Computer : TGCS001
Description:
Bucket 1072696965, bucket table 5.
Type : Information
Date : 4/2/2010
Time : 11:06:15 AM
Event : 17890
Source : MSSQLSERVER
Category : Server
User : N/A
Computer : TGCS001
Description:
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 339 seconds. Working set (KB): 78532, committed (KB): 181348, memory utilization: 43%.
I am getting event 17890 on a regular basis
Any ideas
thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Refer:
https://www.experts-exchange.com/questions/22503216/A-significant-part-of-sql-server-process-memory-has-been-paged-out-This-may-result-in-a-performance-degradation.html
http://blogs.technet.com/askperf/archive/2007/05/18/sql-and-the-working-set.aspx
http://msmvps.com/blogs/omar/archive/2007/09/19/a-significant-part-of-sql-server-process-memory-has-been-paged-out-this-may-result-in-performance-degradation.aspx
http://www.sqlnewsgroups.net/group/microsoft.public.sqlserver.server/topic22050.aspx
Drivers are source of problem:
http://msdn.microsoft.com/en-us/library/bb630354.aspx
http://weblogs.asp.net/omarzabir/arc...gradation.aspx
http://blogs.msdn.com/psssql/archive...t-message.aspx
https://www.experts-exchange.com/questions/22503216/A-significant-part-of-sql-server-process-memory-has-been-paged-out-This-may-result-in-a-performance-degradation.html
http://blogs.technet.com/askperf/archive/2007/05/18/sql-and-the-working-set.aspx
http://msmvps.com/blogs/omar/archive/2007/09/19/a-significant-part-of-sql-server-process-memory-has-been-paged-out-this-may-result-in-performance-degradation.aspx
http://www.sqlnewsgroups.net/group/microsoft.public.sqlserver.server/topic22050.aspx
Drivers are source of problem:
http://msdn.microsoft.com/en-us/library/bb630354.aspx
http://weblogs.asp.net/omarzabir/arc...gradation.aspx
http://blogs.msdn.com/psssql/archive...t-message.aspx
ASKER
to rrjegan17:
My server had 4GB of mem
32 bit verison of Windows 2003 R2 Standard
The sql 2005 has only one instance
My boot.ini does not have any of those items you mention
Not sure about them neer worked with them before
One thing I noticed is that when WSUS updates which occurs around 11:00 am every day
thats when it gives the errors
The event 107 for REport server contines to pop up also
Also to sfossupport:
I agree I beive it is also being over taxed
The items you listed to check thanks
I am not sure how to get that info
As I mentioned above WSUS 3.0 SP2 is also running and it downloads updates from ms once a day
and reports status once a day and the same time frame as this happens maybe should thnk about moving the wsus over to my member server but I would have to install sql 2005 on there also
That might help
Oh Sharepoint 3.0 SP1 also runs on this server so thats my thinking about moving wsus over
Your opions please
Thanks Tom
My server had 4GB of mem
32 bit verison of Windows 2003 R2 Standard
The sql 2005 has only one instance
My boot.ini does not have any of those items you mention
Not sure about them neer worked with them before
One thing I noticed is that when WSUS updates which occurs around 11:00 am every day
thats when it gives the errors
The event 107 for REport server contines to pop up also
Also to sfossupport:
I agree I beive it is also being over taxed
The items you listed to check thanks
I am not sure how to get that info
As I mentioned above WSUS 3.0 SP2 is also running and it downloads updates from ms once a day
and reports status once a day and the same time frame as this happens maybe should thnk about moving the wsus over to my member server but I would have to install sql 2005 on there also
That might help
Oh Sharepoint 3.0 SP1 also runs on this server so thats my thinking about moving wsus over
Your opions please
Thanks Tom
>> My server had 4GB of mem 32 bit verison of Windows 2003 R2 Standard
In order for your 32 bit System to use the 4 GB completely, you need to have both /3GB and /PAE switches in boot.ini file.. Otherwise your system wont be able to completely utilize 4 GB memory..
More info below:
http://blogs.technet.com/perfguru/archive/2007/12/05/scenarios-using-3gb-and-pae-switch-and-appropriate-uses-of-these-switches.aspx
>> One thing I noticed is that when WSUS updates which occurs around 11:00 am every day thats when it gives the errors The event 107 for REport server contines to pop up also
Is there any other major application running in your machine..
Configure WSUS updates to run at some point of time and turn it off for few days and check whether that is the one which actually creates problem or is it some other else..
In order for your 32 bit System to use the 4 GB completely, you need to have both /3GB and /PAE switches in boot.ini file.. Otherwise your system wont be able to completely utilize 4 GB memory..
More info below:
http://blogs.technet.com/perfguru/archive/2007/12/05/scenarios-using-3gb-and-pae-switch-and-appropriate-uses-of-these-switches.aspx
>> One thing I noticed is that when WSUS updates which occurs around 11:00 am every day thats when it gives the errors The event 107 for REport server contines to pop up also
Is there any other major application running in your machine..
Configure WSUS updates to run at some point of time and turn it off for few days and check whether that is the one which actually creates problem or is it some other else..
ASKER
rrjegan17
How do I add those switches to the boot.ini I never played with the boot.ini on a server before
I used msconfig to display the boot.ini
Again my server has 4gb of memory
Only applications on the server are
WSUS 3.0 SP1
Sharepoint 3.1
SQL 2005 SP3
I stopped the WSUS Service now
How do I add those switches to the boot.ini I never played with the boot.ini on a server before
I used msconfig to display the boot.ini
Again my server has 4gb of memory
Only applications on the server are
WSUS 3.0 SP1
Sharepoint 3.1
SQL 2005 SP3
I stopped the WSUS Service now
ASKER
rrjegan17
I found out how to update boot.ini
I read the technet notes on these two parameters
I looks like they are for if you have more than 4gb of memory on the server
I only have 4gb memory will this matter?
I have another server also that have only 4gb of memory if this works I should do the same on that one dont you think?
Also one other thing we might consider I just remembered this just started after I moved the WSUS content database folder from a USB drive to the local "C" drive of the server. This was done becasue we thought the perfoemance on the usb drive was giving me a problem when in fact it was Kaspersky Anti virus needed an update from Kaspersky which solved that perfomance issue
Maybe I should move the wsus folder back to the usb drive what do you think?
Thanks
I found out how to update boot.ini
I read the technet notes on these two parameters
I looks like they are for if you have more than 4gb of memory on the server
I only have 4gb memory will this matter?
I have another server also that have only 4gb of memory if this works I should do the same on that one dont you think?
Also one other thing we might consider I just remembered this just started after I moved the WSUS content database folder from a USB drive to the local "C" drive of the server. This was done becasue we thought the perfoemance on the usb drive was giving me a problem when in fact it was Kaspersky Anti virus needed an update from Kaspersky which solved that perfomance issue
Maybe I should move the wsus folder back to the usb drive what do you think?
Thanks
>> I have another server also that have only 4gb of memory if this works I should do the same on that one dont you think?
Yes, it is..
>> This was done becasue we thought the perfoemance on the usb drive was giving me a problem when in fact it was Kaspersky Anti virus needed an update from Kaspersky which solved that perfomance issue
Seems like you have Kaspersky antivirus and Sharepoint in your server..
Add one more physical disk to your server machine and move your WSUS content database folder to that physical drive and then try it out which should help..
Yes, it is..
>> This was done becasue we thought the perfoemance on the usb drive was giving me a problem when in fact it was Kaspersky Anti virus needed an update from Kaspersky which solved that perfomance issue
Seems like you have Kaspersky antivirus and Sharepoint in your server..
Add one more physical disk to your server machine and move your WSUS content database folder to that physical drive and then try it out which should help..
ASKER
ok I am tring the USB drive now
moving the wsus content folders now
Server cpu is holding while this copy is going it spikes a little now an then but that is expected
I will make the same changes to the boot.ini to the other server as soon I a restart this server and make sure I have the syntex correct
Thanks for you help
Will post results soon
Tom
moving the wsus content folders now
Server cpu is holding while this copy is going it spikes a little now an then but that is expected
I will make the same changes to the boot.ini to the other server as soon I a restart this server and make sure I have the syntex correct
Thanks for you help
Will post results soon
Tom
ASKER
Update
today I restarted the server
Now boot.ini has /3gb /pae options
SQL 2005 min max memory options set 1500 to 2500
lock pages in memory option is set
Now I wait till 11:00AM to see what happens
will post results
today I restarted the server
Now boot.ini has /3gb /pae options
SQL 2005 min max memory options set 1500 to 2500
lock pages in memory option is set
Now I wait till 11:00AM to see what happens
will post results
ASKER
Well today at 11:00 AM I received no errors looking good so far
Give it thru the weekend to see if it is a go
Give it thru the weekend to see if it is a go
ASKER
Sorry guys the error is back and now on the other server it is happening also
This is after doing /3gb /pae in boot.ini
mem 1500 max 2500 memory in sql
awe setting in sql server
Bot my server have only 4gb on physical memory
Not sure what is going on here now?
Help
This is after doing /3gb /pae in boot.ini
mem 1500 max 2500 memory in sql
awe setting in sql server
Bot my server have only 4gb on physical memory
Not sure what is going on here now?
Help
Are you receiving the same error message or some other error message..
Any error messages in Event viewer while you are receiving this error message so that it can be nailed out.
Any error messages in Event viewer while you are receiving this error message so that it can be nailed out.
ASKER
still reviewing
>> fixed rescheduled sql jobs added /4gb option to boot.ini added memory restrictions to sql
Those set of memory Allocations are explained by me above and kindly let us know why to delete the question..
Those set of memory Allocations are explained by me above and kindly let us know why to delete the question..
Hard disc counters:
Logical Disk
1. Average Disk Queue Length – is drive keeping up with demand of running processes.
2. Disk Bytes/Sec – Is the drive keeping up to expectations
3. Free Megabytes – Useful in predicting future needs
Memory
4. Available Kbytes - If this counter is greater than 10% of the actual RAM in your machine then you probably have more than enough RAM and don't need to worry.
5. Pages/Sec – Tracks number of virtual memory pages read or written per second. Multiply value x 4kb memory pages = data moved from memory to disk each second. Indicator of insufficient ram
Network
6. Bytes Total/sec – Baseline measure for load
7. Output Queue Length – If this value average is 2 or greater it indicates the network card isn’t able to handle the capabilities of the server
Processor
8. %Processor Time
Measures the total utilization of your processor by all running processes. Note that if you have a multiprocessor machine, Processor(_Total)\%Process