RRDtool and PHP paths not found

[BSOD2600]

RRDtool is located and configured in cacti as
C:/rrdtool/rrdtool.exe
I fixed the permission problems besides the one in the screenshot (I saw it in process monitor).
the one which wasn't fixed even though I corrected the permissions in the regedit is:

Well thats not really a cacti related process, so don't think its a problem. Possibly IIS related... but unsure until you google or do more research for that GUID.

Now I still get the same errors from the first post.
I need to mention that I didn't configure RRDTool Default Font Path.
Could this cause all the problem? and how i do it if i must?

Yes, you need to specify a path to a valid font i.e. C:/WINDOWS/Fonts/VeraMono.ttf. This is all documented in the installation guide. Have you followed it?

Alright, so cmd.exe has read/execute permissions for both the IUSR and IIS_USRS group?

[TheWitness]

I would simply use Apache. It's much easier to deal with these things.

TheWitness

[BSOD2600]

Apache and windows scheduled task still has to launch cmd.exe to do its biddings. Same issues will apply.

[CHOOCH]

Yes, you need to specify a path to a valid font i.e. C:/WINDOWS/Fonts/VeraMono.ttf. This is all documented in the installation guide. Have you followed it?

Alright, so cmd.exe has read/execute permissions for both the IUSR and IIS_USRS group?

I followed the installation guide but I missed the font part.
Anyway, I check and saw that the permissions wasn't correct and also fixed the font issue. now I restarted IIS service and it still doesn't work.

[BSOD2600]

Alright. Fire up sysinternals process monitor and have it ready. Get cacti in the Settings -> General screen. Clear the Process Monitor screen, click on Settings -> Paths, and then tell Process Monitor to stop logging. Save the log to file and attach it here.

[CHOOCH]

I get nothing when I use the filtering.
So I'll attach the whole log file and maybe you'll see something when you'll open it in process monitor.
Here it is
http://www.filedropper.com/logfile
Thanks!

[BSOD2600]

Well nuts, my workstations aren't 64bit so Procmon won't open the log file.

[CHOOCH]

What do you suggest? I really want to solve it.

[BSOD2600]

Well, we can go back to sysinternals FileMon (although not sure if it'll work on a 2008 x64 box).

Otherwise, to validate its a permission issue, one could temporarily test it by adding the scheduled task user and the IUSR / IIS_USRS accounts/groups to the local Administrator group.