Sharepoint Forum

 
Home » Forum » Sharepoint       Ask a questionRSS Feeds

IIS Log Files for SPS2003 Site are Enormous - Can Anything Done Abo

  Asked By: Alyssa Lewis         Date: Jun 14, 2006      Category: Sharepoint      Views: 469
 

The IIS Logfiles for my SPS2003 site are extremely large, now topping 100MB per day.

Using Microsoft Log Parser 2.2, I ran this query against yesterday’s log (ex060228.log) to get my 20 most popular “pages”:

C:\Program Files\Log Parser 2.2>logparser "select top 20 cs-uri-stem as stem, count(*) as rCount from ex060228.log group by cs-uri-stem order by rCount desc"

And got these results:

stem rCount

--------------------------------- ------

/_vti_bin/sitedata.asmx 80259

/_vti_bin/owssvr.dll 69288

/_layouts/1033/ows_taskhistory.js 41548

/_layouts/1033/ows_livemail.js 34507

/default.aspx 25300

/_vti_bin/spscrawl.asmx 24596

/_layouts/1033/ows_audit.js 24184

/_layouts/1033/webservice.htc 13587

/_layouts/1033/ows_cutandpaste.js 11301

/_layouts/1033/Menu.htc 9886

/_layouts/1033/msstring.js 8809

/_layouts/1033/styles/menu.css 8208

/_layouts/1033/styles/sps.css 8085

/_layouts/1033/owsbrows.js 6808

/_layouts/1033/styles/Menu.css 6717

/_layouts/1033/styles/ows.css 6180

/_layouts/1033/Menu.js 6055

/_layouts/1033/styles/jso.css 5906

/_layouts/images/blank.gif 5412

/_layouts/images/icongo02.gif 5200


Statistics:
-----------

Elements processed: 569863

Do my numbers seem extremely high, like maybe I’ve mis-configured SPS or WSS search or indexing?

Does 570K “hits” per day seem high for a corporate intranet? Note that we have perhaps 2K users, almost none using SPS2003/WSS in what I would consider an active or enthused way.

Have other SPS2003/WSS admins run into similarly large log files? If so, do you just constantly compress and/or archive the files?

Tagged:                        

 

6 Answers Found

 
Answer #1       Answered By: Gopal Jamakhandi          Answered On: Jun 14, 2006       

No, this looks pretty normal to me. You have to take into account that raw IIS logs are exactly that. Raw. They’re hits and inside SharePoint, it uses things like ows.js on every page, owssvr.dll is called for almost any aspx  page, etc. so you’re not going to get popular pages from raw IIS logs like you would a static site. Check out the SQL Reporting Services and SharePoint reporting pack for this as it retrieves the data from a number of sources (including the IIS logs) and then parses it intelligently to find your best bet searches, most popular pages, users, sites, etc. as it understands how to interpret those from the raw sources.

 
Answer #2       Answered By: Keenan Whitehead          Answered On: Jun 14, 2006       

Agreed… they look normal to me. Keep in mind that they are raw text files. This means you could write a batch file that would archive (zip/rar) up the raw files  for previous days/weeks. Since they are raw text files, I’d expect they’d compress to a fraction of their raw size.

 
Answer #3       Answered By: Damon Garner          Answered On: Jun 14, 2006       

When looking at everything that is logged by SharePoint there is a lot
of information that you don't really need and can be filtered out.

I wrote a web log  entry about this. Have a look at
http://weblogs.asp.net/soever/archive/2005/05/29/409614.aspx" target="_blank" rel="nofollow">weblogs.asp.net/.../409614.aspx

Serge van den Oever [Macaw]
weblog: http://weblogs.asp.net/soever

 
Answer #4       Answered By: Dameon Dejesus          Answered On: Jun 14, 2006       

We have an article on the Mindsharp Premium Content site  that not only
explains the log  files but how to query  them.

 
Answer #5       Answered By: Tejaswani Barve          Answered On: Jun 14, 2006       

where on the site? I am on the premium content area

 
Answer #6       Answered By: Harshita Padwal          Answered On: Jun 14, 2006       

It used to be there, I swear.

I will look for it and post a link to this group  when I find it. Sorry
for the misdirection.

 


Your Answer
  • Answer should be atleast 30 Characters.
  • Please put code inside [Code] your code [/Code].