VRC Documentation

Appendix D - Error Messages

Following is a list of the various error messages you may encounter while working with VRC. Refer to this list for a description of the error if it is not clear from the context.

Aircraft not found.: You have attempted to perform an action on an aircraft and you specified an unknown callsign.
All squawk codes in the configured range are taken.: You have attempted to assign a squawk code to an aircraft but all codes in the range specified in your POF file are in use by other aircraft.
Already monitoring the maximum number of weather stations.: You have attempted to add a weather station to the weather panel, but you are already monitoring the maximum of 20 stations.
Amendment command not supported. Please use flight strip window.: You attempted to use a flight plan amendment command from ASRC that is not supported in VRC.
ATIS contains too many lines!: Your ATIS text contains too many lines. The recommended number of lines is 4. The absolute maximum allowed by VRC is 10.
ATIS is currently empty.: You have requested your own ATIS, but it is empty.
Callsign in use: You have attempted to connect with a callsign that another controller is already using.
Callsign invalid: The callsign you specified in the Connect window was rejected by the server as invalid.
CID/PID was suspended: Your VATSIM account has been suspended.
Command restricted to supervisors and admins.: You attempted to use a command for which you do not have the appropriate privileges.
Connection failed.: Your connection to VATSIM has failed.
Controller not found.: You attempted to perform a command on a controller using an unknown callsign.
Could not accept land line call.: There was a problem making the requested ground-to-ground voice connection.
Could not find point: _____.: You attempted to locate or use a fix, navaid or airport that was not found in the sector file.
Could not open land line.: There was a problem making the requested ground-to-ground voice connection.
Could not write to server list cache file.: VRC was unable to write the servers.txt file which stores the downloaded server list. This could be a file permissions problem.
Error loading alias file!: Your specified alias file could not be found or opened.
Error loading position file!: Your specified POF file could not be found or opened.
Error saving chat log to specified file.: You attempted to save a chat window log to a file but the file could not be opened. This could be a file permissions problem.
Error saving radio log to specified file.: You attempted to save your radio text log to a file but the file could not be opened. This could be a file permissions problem.
Fix, airport or navaid not found.: You attempted to locate or use a fix, navaid or airport that was not found in the sector file.
Flight strip not found for specified callsign.: You attempted to delete a flight strip from the Flight Strip Bay, but no such strip existed in the bay.
Handoff of _____ refused.: You attempted to transfer control of the specified aircraft to another controller, but that controller refused the handoff.
Invalid CID/password: You attempted to connect to VATSIM with an invalid CID or incorrect pasword.
Invalid control.: You attempted to perform an action (such as initiating track) on an aircraft, yet you are not a valid controller. (Usually because you are an observer.)
Invalid parameter. Enter either the sectorID or single-digit chat group index.: You attempted to use the Controller Select (CSEL) key to open a chat window, but the specified sector ID or chat group index was not found in the Controller List.
Invalid position for rating: You attempted to connect to VATSIM and specified a facility for which you must have a higher rating.
Invalid profile name.: You attempted to save a profile and specified an invalid name. Profile names must consist of only letters, numbers, underscores and spaces.
Invalid speed and/or heading detected on one of the selected targets.: You attempted to activate the separation predictor lines for two aircraft, but one of those aircraft is reporting an invalid speed and/or heading.
Invalid squawk code range.: The range of squawk codes specified in the POF file is invalid. This could be caused by having the low end of the range set higher than the high end.
Must click a different aircraft than the one that is radio selected.: You attempted to send a traffic advisory to a pilot, but didn't select a different aircraft to point out. (You attempted to point out an aircraft to itself.)
Must specify a callsign or use <ASEL>.: You attempted to perform a command that requires a callsign parameter but didn't specify one.
Must specify a single callsign.: You attempted to perform a command that requires a single callsign parameter but didn't specify one or you specified too many.
Must specify at least one separator label.: You attempted to add a separator to the Flight Strip Bay but didn't specify the separator label.
Must specify callsign.: You attempted to perform a command that requires a callsign parameter but didn't specify one.
Must specify filename as a single parameter.: You attempted to save a chat or radio text log to a file but didn't specify the filename to use.
Must specify URL.: You attempted to open a web page via the .openurl command but didn't specify the URL.
No aircraft selected.: You attempted to send a traffic advisory to a pilot, but didn't have an aircraft selected.
No departure airport filed.: You attempted to request the METAR for an aircraft's departure airport, but the aircraft has no departure airport filed.
No destination airport filed.: You attempted to request the METAR for an aircraft's destination airport, but the aircraft has no destination airport filed.
No flight plan selected.: You attempted to amend an aircraft's route with the .am command, but had no flight plan loaded into the Flight Plan Editor window.
No flightplan: You requested the flight plan for an aircraft which has not yet filed one.
No frequency specified.: You attempted to use an entry in the Comms Panel for which no frequency is defined.
No history to save!: You attempted to save the history for a chat window or the radio text history but there has been no chat or text radio messages recieved yet.
No more clients: The server you attempted to connect to is full.
No such callsign: This generic error comes from the server when you attempt to perform an action on a callsign that does not exist on the network.
No such weather profile: You requested the weather for a station for which the server has no weather information.
No voice channel specified.: You attempted to connect to the voice channel associated with a Comms Panel entry, but no voice channel has yet been defined for the selected entry.
Not authorized software: You are not authorized to use VRC on the selected server, or a network timing problem has occurred and you have been disconnected.
Not connected.: You have attempted some function which requires you to be connected, while not connected.
Not enough parameters.: The command you attempted to perform requires additional parameters.
Not valid control: You attempted to perform an action (such as initiating track) on an aircraft, yet you are not a valid controller. (Usually because you are an observer.)
Not your control.: You attempted to perform an action on an aircraft that requires you to be tracking the aircraft, but another controller currently has track.
Observers cannot initiate land line calls.: Self-explanatory.
Observers cannot send text radio messages.: Self-explanatory.
Point not found.: You attempted to locate or use a fix, navaid or airport that was not found in the sector file.
Requested level too high: You attempted to connect to VATSIM and specified a rating for which your CID does not qualify. Choose a lower rating.
Specified display does not exist.: You attempted to send a command to a secondary display which does not exist.
Specify two points or one point and select an aircraft.: You attempted to use the .rsb command and did not specify enough parameters.
Targets not converging.: You attempted to activate the separation predictor lines on two aircraft which are not on converging courses.
Targets will not converge within one hour.: You attempted to activate the separation predictor lines on two aircraft which will not converge within a reasonable amount of time.
Unknown controller list index.: You attempted to open a chat window using a one or two character index from the Controller List, but the specified index does not exist.
Version check failed! HTTP error.: VRC's initial version check failed. This is not a problem unless it happens consistently. In that case, check your firewall to be sure web connections to vrc.rosscarlson.dev are not blocked.
You can only monitor one controller at a time.: Self-explanatory.
You must select two different aircraft.: You attempted to activate the separation predictor lines without selecting two distinct aircraft.
You were forcibly disconnected from the network. Reason: __________: You were disconnected from the network, most likely by a supervisor or administrator. Refer to the specified reason.
Could not open UDP voice port. Perhaps another VATSIM program is running such as ASRC?: VRC could not open the network port needed for voice connections. This is usually because it is already in use by another program such as ASRC, AVC, etc.
Could not read and/or parse VRC.ini: VRC could not find the VRC.ini file, or did not have permissions to read it. The VRC.ini file must be in your "My Documents\VRC" folder.
Error loading POF file!: VRC could not locate or read the POF file specified in the profile you are trying to load. Make sure the file exists in the specified location and that VRC has the appropriate file permissions to read it.
Error loading alias file!: VRC could not locate or read the alias file specified in the profile you are trying to load. Make sure the file exists in the specified location and that VRC has the appropriate file permissions to read it.
The default profile cannot be deleted.: VRC does not let you delete the Default profile so that you can always revert to it in case something in your profile settings gets corrupted.
Are you sure you want to delete the selected profile? This action cannot be undone.: This is just a reminder that if you delete a profile, it is gone for good. There is no way to restore it from the Recycle Bin or undo the deletion.
Invalid ICAO code. Must be 4 characters.: You attempted to enter an airport code into ATISMaker, but did not specify a 4-character code as required.
Invalid runway.: Runways entered into ATISMaker must be one or two digits, followed by an optional C, L, or R for Center, Left, or Right.
Invalid airport code.: You attempted to enter an airport code into the Arrival or Departure Fields lists, but did not specify a 4-character code as required.
Could not retrieve server list from network. Using the cached server list and user-defined servers.: VRC tried to download the VATSIM server list from the network, but the connection failed. This is often due to a firewall or antivirus running on your computer. You can usually still connect to VATSIM using the cached server list.
You cannot overwrite the default profile. Please choose another name.: VRC does not let you overwrite the Default profile so that you can always revert to it in case something in your profile settings gets corrupted.
Must be an active controller to initiate ground-to-ground calls.: You attempted to initiate a ground-to-ground call while logged in as an observer.