2xc file related issues

0 users found this article helpful

Symptoms

Cause

The .2xc file may be incomplete, malformed, damaged, or contain settings that are not supported by the Parallels Client version into which it is being imported.

Import problems can also occur when the file was generated by a different Client version or platform, or when the file contains credentials that are handled differently by the target Client installation.

Resolution

  1. Confirm that the file is a Parallels Client settings file with the .2xc extension. Do not rename an unrelated file to use the .2xc extension.

  2. Use a compatible Parallels Client version to export and import the settings. If possible, install the same Client version and build on both computers, reproduce the problem, and then test the import with a newly exported file.

  3. Export the settings again from the source Client instead of reusing the affected file:

    1. Open the main menu and select Export Settings. In the classic interface, select File > Export Settings.
    2. Select the destination and save the file with the .2xc extension.
    3. Copy the file to the target computer without modifying its contents.
  4. Import the file into Parallels Client:

    1. Open the main menu and select Import Settings. In the classic interface, select File > Import Settings.
    2. Select the .2xc file and select Open.

Important: Importing a .2xc file overrides the existing Parallels Client settings. Export or otherwise back up the current settings before importing the file.

Warning: If the exported settings include access credentials, the file contains sensitive information. Protect the file during transfer and delete it securely after use when it is no longer required.

Validate the file contents

  1. Open a copy of the file in a text editor that does not automatically rewrite or reformat the contents.
  2. Confirm that the file is complete and that its structure matches the documented Parallels Client .2xc format.
  3. Check for truncated content, invalid XML or other malformed data, unsupported properties, and accidental changes introduced while copying or editing the file.
  4. Do not manually edit the file unless the required format and property values have been verified for the target Client version.

When the file is used during Windows Client installation

If the file is supplied through the Windows Client installer, verify the installer properties and the handling of credentials. For example, DEFSETTINGS specifies the settings file, while IGNORESETTCREDS controls whether credentials stored in the file are used.

For troubleshooting, test the installation with credentials excluded from the file unless the deployment specifically requires them.

Collect information for Support

If the issue continues, collect the following information:

 

Was this article helpful?

Tell us how we can improve it.