IIRF.ini (Not Found) And logFile Not Found

Topics: Developer Forum, Project Management Forum, User Forum
Dec 29, 2010 at 3:13 PM
Edited Dec 30, 2010 at 4:20 PM

Good day.

The error I have is that I report the Iirf.ini http://localhost/iirfStatus Not Found, as shown in the following


IIRF Status Report

IIRF Global Status

IIRF Version Ionic ISAPI Rewriting Filter (IIRF) x86 RELEASE
Built on May 30 2010 13:26:57
Filter DLL C:\Program Files\IIRF_2.1\IIRF.dll 
PCRE Version 8.02 2010-03-19
IIRF Started 2010/12/29 10:04:50 (local time)
Current time 2010/12/29 10:04:54 (local time)
Server Ini file C:\Program Files\IIRF_2.1\IirfGlobal.ini 
Last Update of Ini 2010/12/29 09:14:22 (local time) 
  #Lines 68
  #Warnings 0
Rewrite Engine (all vdirs) ON

IIRF Vdir Status

Ini file D:\web_site\bolivariano_new\Iirf.ini
Ini file timestamp (file not found)
  Last read 2010/12/29 10:04:50 (local time)
  #Ini Modules 0
  #Lines 0
  #Rules 0
  #Warnings 0
  #Errors 0
Log file (none)
Log level 1
Rewrite Engine ON
Rewrite Base '--'
Remote Status Inquiry disabled
URL Decoding ON
Iteration Limit 8
Proxy Timeouts (sec.) Resolve=30 Connect=30 Send=30 Receive=30
#Requests Processed 104

So I think Iirf.ini file with the following.

# IIRF.ini
RewriteLog  C:\TEMP\iirf\
RewriteLogLevel 3

Restart the IIS and go and charge http://localhost/iirfStatus in the browser and gives me error 404 and I'll see in C: \TEMP \iirf\ and can not find any log file, then do not watch because I like more is failing, I do not record any events in the log windows.


I assign permissions to the DLL IIS_WPG iirf.dll to iirfGlobal.ini and Iirf.ini and each will also verify the permissions for NETWORK SERVICE and are as defined in the documentation, not what I'm missing, and dont know what else to do, I desistalado several times, I called the MSI and I also made by hand, and always arrive at the same point,

Appreciate the help and Thanks

Thanks for the help.


Dec 30, 2010 at 4:22 PM

Any Idea Please?

Jan 3, 2011 at 1:01 PM

Please, help my,

Jan 3, 2011 at 2:44 PM

From the documentation, http://cheeso.members.winisp.net/Iirf21Help/html/06643ce7-6c93-4d2f-ad3b-01e97fade9ef.htm

By default, when a vdir-specific ini file (IIRF.ini) is NOT present, the status inquiry capability for that particular vdir is ON. When a vdir-specific ini file is present, and there is no StatusInquiry directive in that ini file. the status inquiry capability for that particular vdir is OFF. When the status inquiry capability is OFF, submitting a request to http://localhost/iirfStatus will return a 404. If you include a StatusInquiry ON directive in your vdir-specific ini file you will turn ON the status inquiry capability for that vdir. Regardless of the presence or not of ini files or StatusInquiry directives in those ini files, status inquiries work only if not disabled globally in IIrfGlobal.ini. See the documentation on the StatusInquiry directive for more information.

Jan 3, 2011 at 4:21 PM

Thanks for your reply, thank you very much, as to what's ON the IIRF.ini StatusInquiry already assigned, the structure is as follows.

# IIRF.ini

RewriteLog  C:\temp\iirf
RewriteLogLevel 3
StatusInquiry ON

Restart the IIS and keeps coming http://localhost/iirfStatus 404. something you do not see is the error log, or Windows, or in c: / temp / no registration no log appears. and IIRF.ini file I specify the path. and not because it follows saleindo 404 and does not generate the error log to know what I'm missing


Thanks very much

Jan 3, 2011 at 6:43 PM

Well, if /iirfStatus works when you have no IIRF.ini, and /iirfStatus does not work when you DO have an IIRF.ini, then I suspect the problem is related to IIRF.ini.

It is worthwhile checking the permissions on that file, 2 times, 3 times. 

If the file exists but cannot be read, then what will happen?  No message will be written to the IIRF log file, because IIRF does not know where to put the log file, because IIRF cannot read the IIRF.ini file.

I think this is a bug in IIRF.  In the case where there is no logfile, and IIRF cannot read the IIRF.ini file, IIRF should put a message to the Windows Event log. Currently IIRF does not do this.

In any case the fix is to correct your permissions.  I know you said you checked this.  If IIRF cannot create a log file, it is a permissions error, either with reading of IIRF.ini, or writing of IIRf.log. 

good luck.


Jan 3, 2011 at 6:45 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Jan 3, 2011 at 8:04 PM

I agree that the problem should be of permits, but does not know what else to do, the file has permissions iirf.ini they are. for IIS_WPG and the folder c: \ temp \ has FULL permissions I have already read the documentation many times but what else can be done, or if I forgot something ..

thank you very much.