Schedule does not exist. Please update this manually.

[mitcheinfo]

Hello everyone.

Well about 7 days ago no driver consegue send PIREPs using FSFK, all pilots out that message.

Schedule does not exist. Please update this manually.

Recently the PHP to version 5.5 update and from there I can not find a solution, any help is welcome.

thank you very much

[flyalaska]

I have the same problem, been looking for this answer for a long time now.

[StartVM]

I can recommend that you upgrade your system to simpilots phpvms at http://github.com/davidjclark

[mitcheinfo]

I'm already using version phpvms_5.5.x but still not working.

The problem is that 80% of my pilots use the keeper.

[simpilot]

I am not real familiar with FSFK but I did get the images all working in phpvms some time ago and I have never come across this message. I am assuming it shows up in the FSFK client as I do not see where it would come from on the script side after a quick look. I guess I would ask if using or not using the code part of the flight number makes a difference? Is there any error log form the site, either the phpvms error log or the server error log? If it is not finding the flight number I would imagine the error starts around this in the controller for FSFK

$flightinfo = SchedulesData::getProperFlightNum($xml->FlightNumber);
$code = $flightinfo['code'];
$flightnum = $flightinfo['flightnum'];

[mitcheinfo]

The error comes with FSFK and Passanger, and with XACARS working properly.

Before switching to PHP 5.5 all systems functioned properly.

I leave here some pictures of the keeper and shedule.

If you need some script just have to say and which way to you.

[simpilot]

Without error logs or any other answers to go on other than it started when you switched to php5.5 I would guess there is a non static function somewhere that is being called as static, but that is a shot in the dark with the limited information and responses.

Also looking at part of the code there is a section that is looking for airport info that is polling the "AIRPORT_LOOKUP_SERVER". If you have this still set to the geonames option in your local config that could be causing the script to return false.

[mitcheinfo]

Look at the way you code app.config

Edited September 27, 2014 by servetas
removed the code

[servetas]

It exists on your app.config.php file (approximately line 219).

[mitcheinfo]

Code local.config

Edited September 27, 2014 by servetas
removed the code

[servetas]

There is no need to share a file with 507 lines inside the forum. Open you app.config.php file and find this:

Config::Set('AIRPORT_LOOKUP_SERVER', 'phpvms');

replace that with this:

Config::Set('AIRPORT_LOOKUP_SERVER', 'geonames');

[mitcheinfo]

Changed and is still the same error: Schedule does not exist. Please update this manually.

Change

#Config::Set('AIRPORT_LOOKUP_SERVER', 'phpvms');

Config::Set('AIRPORT_LOOKUP_SERVER', 'geonames');

[simpilot]

Is using, or not using the code part of the flight number make a difference?

Is there any error log form the site, either the phpvms error log or the server error log?

[mitcheinfo]

Where I can look at that code?

So you step all the necessary information.

[mitcheinfo]

Please do not find the information requested by simpilot.

Someone can tell me where to find the information?

[Edwin]

anyone able to get this one fixed?

[servetas]

Without error logs or any other answers to go on other than it started when you switched to php5.5 I would guess there is a non static function somewhere that is being called as static, but that is a shot in the dark with the limited information and responses.

Also looking at part of the code there is a section that is looking for airport info that is polling the "AIRPORT_LOOKUP_SERVER". If you have this still set to the geonames option in your local config that could be causing the script to return false.

[Edwin]

where can we find these error logs?

And also for me, the change of airport lookup server did not do anything.

[simpilot]

where can we find these error logs?

Error logs are found in /core/logs

If you need to turn debugging error reporting on, that information is here -> http://forum.phpvms....ging-issues-r31

And also for me, the change of airport lookup server did not do anything.

Do you possibly have two instances of the airport lookup server definition in your config file with one overriding the other?