Webchecks which should run on the zabbix-proxy are not synchronised from the master zabbix server. The proxy-log states therse errors:

12587:20120820:162144.527 [Z3005] query failed: [1452] Cannot add or update a child row: a foreign key constraint fails (`zabbix_proxy`.`httpstep`, CONSTRAINT `c_httpstep_1` FOREIGN KEY (`httptestid`) REFERENCES `httptest` (`httptestid`
update httpstep set httptestid=100100000000011,name='Startseite',no=1,url='http://www.SITE1.biz',timeout=15,posts='',required='Copyright',status_codes='200' where httpstepid=100100000000020;
update httpstep set httptestid=100100000000013,name='SITE 2',no=1,url='http://www.SITE2.de/',timeout=15,posts='',required='Kosten',status_codes='200' where httpstepid=100100000000022;
insert into httpstep (httpstepid,httptestid,name,no,url,timeout,posts,required,status_codes) values (100100000000023,100100000000014,'Startseite DE',1,'http://www.SITE3.de/',15,'','Impressum','200');

... and a few more for additional sites.

12587:20120820:162145.673 [Z3005] query failed: [1452] Cannot add or update a child row: a foreign key constraint fails (`zabbix_proxy`.`httpstepitem`, CONSTRAINT `c_httpstepitem_1` FOREIGN KEY (`httpstepid`) REFERENCES `httpstep` (`htt
update httpstepitem set httpstepid=100100000000019,itemid=100100000024856,type=1 where httpstepitemid=100100000000089;
update httpstepitem set httpstepid=100100000000019,itemid=100100000024857,type=0 where httpstepitemid=100100000000090;
update httpstepitem set httpstepid=100100000000020,itemid=100100000024861,type=2 where httpstepitemid=100100000000091;
update httpstepitem set httpstepid=100100000000020,itemid=100100000024862,type=1 where httpstepitemid=100100000000092;
update httpstepitem set httpstepid=100100000000020,itemid=100100000024863,type=0 where httpstepitemid=100100000000093;
update httpstepitem set httpstepid=100100000000022,itemid=100100000024873,type=2 where httpstepitemid=100100000000097;
update httpstepitem set httpstepid=100100000000022,itemid=100100000024874,type=1 where httpstepitemid=100100000000098;
update httpstepitem set httpstepid=100100000000022,itemid=100100000024875,type=0 where httpstepitemid=100100000000099;
insert into httpstepitem (httpstepitemid,httpstepid,itemid,type) values (100100000000100,100100000000023,100100000024879,2);
insert into httpstepitem (httpstepitemid,httpstepid,itemid,type) values (100100000000101,100100000000023,100100000024880,1);
insert into httpstepitem (httpstepitemid,httpstepid,itemid,type) values (100100000000102,100100000000023,100100000024881,0);
insert into httpstepitem (httpstepitemid,httpstepid,itemid,type) values (100100000000103,100100000000024,100100000024885,2);
insert into httpstepitem (httpstepitemid,httpstepid,itemid,type) values (100100000000104,100100000000024,100100000024886,1);
insert into httpstepitem (httpstepitemid,httpstepid,itemid,type) values (100100000000105,100100000000024,100100000024887,0);

... and a few more.

New checks added on the server are not populated to the proxy so the newly added webchecks stay in an unknown state.

I've tried to delete the proxy database, rebuild a new databse with schema.sql (nothing else) from 2.0.2 package, but the error remains.

If you need further information, please contact me.