Stand-alone EXE or a Windows Service version).">
 
  •      Powered by
 
  Home | Log In | Register | Search | Help
   
IIS Logs – Install, Configure, Forget! > General Information > Bug reports > (No Subject)
 
Forum Quick Jump
 
New Topic Post Reply Printable Version
[ | Show Oldest Post First ]

Forum Administrator
Forum Moderator

Email Address Not AvailableClick to visit Forum Administrator's website.Send a Private Message to Forum AdministratorAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Jul 2004
Total Posts : 31
 
   Posted 8/29/2004 12:12 PM (GMT -4)    Quote This PostAlert An Admin About This Post.

Problem

IISLogs Windows Service version won’t install on Windows 2000, receives an error invalid password or invalid account, then the install doesn’t complete.

Solution w/comments

The original IISLogs Windows Service Package was setup to use an local account called LOCAL SERVICE. This local account isn’t on Windows 2000 server. This is a windows 2003 feature ONLY. This would cause the IISLogs Windows Service version not to install because the local account doesn’t exist. One of the goals of IISLogs isn’t required to run as Administrative or SYSTEM credentials. To address this, additional packages have been added to allow for different default install accounts. One installs as SYSTEM, another will prompt you for a USER.

Here is additional comments

Installing on Windows 2003 and running IISLogs on Windows 2003

One feature that we’ve discovered during the beta cycle is there is a *feature* in IIS 6. When IIS log files are rolled everyday, the ONLY permissions granted to the log files are Administrators and SYSTEM accounts. Even if you have a non-admin on the parent folder to inherit the non-admin user, the IIS Log file won’t inherit this permission. If IISLogs files is configured to run as a non-admin (LOCAL SERVICE) and tries to compress/delete the file, it won’t have permission too. The long story short, you CAN configure IISLogs service version to run as local service but the files won’t be compressed and/or deleted because of this *feature*. There are a couple of options if you DON”T want to run IISLogs as an Administrator or SYSTEM is to have a script that resets the NTFS permissions on the log files created everyday so the LOCAL SERVICE account can have access to them. Either way hopefully Microsoft will fix this problem in Windows 2003 SP 1.

Installing on Windows 2000

The default package originally available from IISLogs was to run as LOCAL SERVICE. Windows 2000 doesn’t have an local machine account called LOCAL SERVICE (Only available in Windows 2003). To get IISLogs Windows Service version installed on Windows 2000, the package you’ll need will be the one that installs by default as LOCAL SYSTEM. After IISLogs install is complete, you can change IISLogs to run as a non-administrator.  Another option is 1:create a local user that has logon as service credentials 2: Download the IISLogs package that prompts you for a user. 


* —————————————– *
* Steve Schofield – MCP, CCA
* [email protected]
*
* Microsoft MVP – ASP.NET
* http://www.deviq.com
* —————————————– *

Back to Top
 
New Topic Post Reply Printable Version
   
Forum Information
Currently it is Tuesday, October 17, 2022 10:46 PM (GMT -4)
There are a total of 30 posts in 23 threads.
In the last 3 days there were 0 new threads and 0 reply posts. View Active Threads

 

tio

Terms of Use | Privacy Statement ©2005-2006 IISLogs.com. All rights reserved - Powered by IIS7 - info @ www.IIS.net