In the event that an error occurs when saving a project, you can still sometimes recover your changes. When a project is saved, then behind the scenes, a snapshot of the current project’s configuration is made. The new project version is saved as a separate file. Then, if the latest version of the project saves properly, the new version is renamed to overwrite the old version. On the other hand, if saving the new version of the project fails, the previous version is not lost. It remains as a backup copy. Opening a project that failed to correctly save the previous time will use the backup version automatically and display a warning. In addition, PolyAnalyst can also be configured to save a separate copy of the project each time.

No progress is displayed when saving a project

Most likely, the folder in which you (the current user) are trying to create this project is not configured in such a way as to allow you to create the project. You will first need to reconfigure the folder to allow your user profile to create projects within this folder. This error message is displayed when there is a problem with the permissions for the user when trying to create a project. You (or some other user) will first need to configure the rights for the folder under which the project was created. To configure the rights for a folder (to even open the Edit rights dialog for the folder), a user must either be the folder’s owner (which by default is the user who created the folder), or must be an administrative user (a member of the administrative group). In order to allow for a user to create projects within that folder, then, the user must be one of the following: the folder owner, or an administrative user (a user who belongs to the Administrators group), or the user, or any of the groups to which the user belongs, must be added to the list of authorized users and have the Create project option explicitly granted.

Therefore, in order to avoid seeing the error message, take the following actions:

Alternatively, you can also just add the desired user to the Administrators group by logging into the Administratrive Tool as an administrator and changing this users group memberships, which inherently grants that user all the necessary privileges, but with the tradeoff that this user also gains other privileges you may not desire.

Alternatively, if you find part of the above somewhat inconvenient, first create a new folder, and set this user as the owner. Create a folder for each user who will be creating projects. Then, set each user’s folder to have each specified user as its owner. This way, each user gets their own folder over which they have complete control (the ability to view projects within the folder, delete projects within the folder, and create or edit projects within the folder).

Unlike many other software programs that wait to save your work until the first time you click the Save button, PolyAnalyst immediately begins saving information from the moment a project is created. Because a project is immediately created, a certain amount of free disk space must be present on the computer running PolyAnalyst Server to store the hidden files that represent the project on the hard drive. PolyAnalyst performs a check for whether there is sufficient space. If there is not, you will be prompted with an error about insufficient space, and you will need to ascertain additional hard drive space before continuing. In rare cases, PolyAnalyst may find that there is insufficient hard disk space available to create a file. If disk space is not available, PolyAnalyst immediately cancels the operation. Note that if this is an export operation, the file may be partially written and contain part of the data. You should delete the file in this case because it may be corrupt.

In some cases, the PolyAnalyst program may not have sufficient permission to write to the location or file on your operating system. If this error occurs, you can attempt to run PolyAnalyst as an administrator or consult your administrator for help. You can also attempt to configure the permissions for the folder that should contain the file so that the PolyAnalyst program can write files to it. To work around this problem, consider writing the file to a location such as your Desktop and moving the file to the desired location after the export. Operating system permissions are not to be confused with user profile permissions in PolyAnalyst, although in some cases PolyAnalyst can be configured so that users inherit the same permissions as their operating system user profile. Please contact Megaputer support for help if operating system security problems occur, or speak with your administrator.

This error is generated by the client when it fails to receive a response from the server in a predetermined allowed period of time. A request was sent to open the project but no response was returned. The primary reason no response was returned is due to the server halting for some reason (e.g. an error occurred). When this error is displayed while trying to open a project, most likely this error is related to something that caused the server to stop responding when trying to open a project. This could be due to a project which was not saved correctly and was corrupted, which caused the server to crash when attempting to open the project. It is recommended in this case to contact Megaputer Support.

To troubleshoot, in the Manage projects window, right-click on the project and check if the Restore from backup option is available. Then open the project.

If this option is not available, perform the following steps.

If you continue to receive the error, please contact Megaputer Support. When contacting Megaputer Support, be prepared to access the Project.xml file or the project folder, as well as the version number of PolyAnalyst (located in the About dialog in the Help menu or the Windows Start Menu). You may also be requested to obtain files that reside in the Logs folder (underneath the same folder identified in step 3).

The Recent projects list (displayed in the File menu of the Analytical Client) is not always updated after making changes to one or more projects. Deleted projects are not immediately removed from this list. In limited cases, upgrading PolyAnalyst may cause older projects to become invalid and incompatible with the current version. Attempting to open these older projects from the Recent projects list may cause PolyAnalyst to display an error message that it cannot open the project. Use the Open project menu option from the File menu instead.

The connection between PolyAnalyst Server and the PolyAnalyst client was not lost, but the server did not respond in time to the request to close a project. Contact Megaputer Support. In the mean time, you will need to forcefully exit the client and restart the server. You should be able to continue using PolyAnalyst, but work in the currently open project may have been lost. This error may also affect other users of the server. This error may be related to compacting projects created in older versions of PolyAnalyst if you have recently upgraded.

This error occurs when PolyAnalyst attempts to create or save a project and a third party program prevents PolyAnalyst from being able to work with some of the operating system tools within your computer’s virtual memory (the computer running PolyAnalyst Server). There is a known incompatibility with certain versions of anti-virus software such as Norton AntiVirus. Norton monitors all programs working within your computer’s virtual memory and attempts to prevent malicious software from executing. In doing so Norton may also stop some non-malicious software programs from functioning, such as PolyAnalyst. To address this error you can change your version of Nortan AntiVirus so that it does not conflict with PolyAnalyst. Certain versions, such as NAVCE10.1, do not cause this problem to appear. Alternatively, prior to creating or saving a project, right-click on the Norton AntiVirus program icon in your Windows taskbar and uncheck the Enable auto-protect option. Then create or save your project, and then re-enable the Norton protection.

Alternatively, change PolyAnalyst’s behavior to not conflict with Norton AntiVirus by forcing PolyAnalyst to use an inefficient, non-binary method of saving information. Open the Administrative Tool, go to Server settings, and locate the Debug options section. Change the objects serialization method option to XML. Ensure it is not set to the binary or text option. Click OK, exit all PolyAnalyst programs, and restart PolyAnalyst Server. Administrators should note that the XML serialization option is the slowest of the three options. Changing this option from binary to XML will seriously decrease the performance of PolyAnalyst, but it is necessary if you wish to avoid this error message and not upgrade or disable your antivirus software each time you wish to save a project.