Fatal error when starting cacti

[sirprotos]

i've setup a new server using IIS instead of apache. but when i browse to http://localhost i got an error message of :

Fatal error: Call to undefined function mysql_connect() in C:\cacti\lib\adodb\drivers\adodb-mysql.inc.php on line 338


can anybody tell me how to overcome this problem !

THanks

[BelgianViking]

Check your IIS configuration, and certainly all ISAPI filter stuff.

[sirprotos]

i've change to apache... but still got the same problem
about the IIS config, i've double check it and all is done.

PLs somebody help me with this !

[BSOD2600]

Read my updated install guide here: http://bsod2600.home.comcast.net/install_windows.html

Sounds like you need to apply the old password setting for mysql.

[sirprotos]

i've read ur updated guided but i found that u state that only user with PHP4 and sql 4.1 where need to do that !

Is there any other things that needs to be done

TQ

[BSOD2600]

Yes, did you try the mysql password update I linked to?
Did you make sure to update the cacti/include/config.php ?

[sirprotos]

Now i know !? why ! it is because of my apache is using different php.ini file. diffrent from c:\php. my windows use c:\windows\php.ini insteed.

To all cacti user using windows. if u encounter this problem. please have a look in ur windows directory c:\windows and seach for php.ini in it. If it's there just add all the line (the extension value).

TQ all for guiding me !

and now i'm having a problem with graph. no graph showing :

ERROR: opening 'C:/Apache2/htdocs/cacti/rra/ag_kk_traffic_in_11.rrd': No such file or directory

[BSOD2600]

1) did you wait 2 polling cycles?
2) are the rrd files being created?
3) did you read my updated windows guide and follow it?

[sirprotos]

yeah.. thanks SIFUs..... right now i'm strugling to make my cactid run ..... i got this msg.....

10/25/2005 03:18:57 PM - POLLER: Poller[0] Maximum runtime of 296 seconds exceeded. Exiting.

what is this means !?

[BSOD2600]

Means cacti wasnt able to poll all your devices in under 5 minutes. Turn the logging level to debug for one cycle and look in your log for the cause.