Error 1712 office install vista

I have seen that office Enterprise is only availble to volume-license customers and it cannot be upgraded from the previous versions. But as per some other debators, it seems to be available as a volume license and retail version. I dont know what is the exact condition of the releases but it would be good to know from a microsoft employee only whether it is available or not. I assure you that it is a legitimate copy of the Office which was bought by an microsoft employee for me.

It has the label of "Home Use Program" with an orange label print on it along with a product key on the back of the case. I wonder why everyone thinks that this version of ms office is still not released although it has been. But in any case, I would like to know a workaround for this problem. Join Date Nov Posts If you are sure that it is a legal copy of the office suite then to install it I assume you will have to uninstall all the remains of the Office from your computer first and then install the new copy.

Upgrading from an old to the new copy of Office might be emitting the error. After uninstalling the Office , you could try to do a clean boot of the system that you are having and then try to install the Office Enterprise version by directly double clicking the setup.

To resolve this error, open your InstallShield project from within Visual Studio, and then import the Visual Studio project into it. If you want to import into an InstallShield project a Visual Studio setup or merge module project that contains a project output, the Visual Studio project must be in the same solution as all of its project dependencies.

Otherwise, this error occurs when you try to import the Visual Studio project. To resolve this error, ensure that your InstallShield project is in the same Visual Studio solution that contains the Visual Studio setup or merge module project that you are importing. In addition, ensure that the solution also includes all of the other Visual Studio projects that are dependencies of the Visual Studio setup or merge module project.

Then you can import the Visual Studio setup or merge module project into your InstallShield project. This error occurs if you convert a Visual Studio setup or merge module project that contains a project output group but InstallShield encounters a problem when incorporating a project output of that group into the InstallShield project. The file was not converted. This warning occurs if you import into an InstallShield project a Visual Studio setup or merge module project that contains a file whose Exclude property is set to True.

If you want the specified file to be excluded from your InstallShield project, you can ignore this warning. If you want the specified file to be included in your InstallShield project, you can use the Files and Folders view in InstallShield to add it. The project output was not converted. This warning occurs if you import into an InstallShield project a Visual Studio setup or merge module project that contains a file in a project output, and True is selected for the Exclude property of that file.

Visual Studio default launch conditions are not supported in InstallShield. This warning occurs if you import into InstallShield project a Visual Studio setup or merge module project that contains a default launch condition. If you want the specified launch condition to be excluded from your InstallShield project, you can ignore this warning.

If you want to add a launch condition to your InstallShield project to check the target system for the default launch condition that Visual Studio added to the original project, you can use the System Search view in InstallShield to add it. For more information, see Adding a System Search.

The MinDate property was not converted. This warning occurs if you attempt to import or convert a Visual Studio setup that has a file search with an invalid value for the MinDate property.

The MaxDate property was not converted. This warning occurs if you attempt to import or convert a Visual Studio setup that has a file search with an invalid value for the MaxDate property. This error occurs if you attempt to import or convert a Visual Studio Web setup project in InstallShield , since InstallShield does not have support for this conversion. If you encounter this type of error, consider creating a new project in InstallShield and using the Internet Information Services view to manage an IIS Web site on a target system.

This error occurs if you attempt to import or convert a Visual Studio CAB setup project in InstallShield , since InstallShield does not have support for this conversion. The Visual Studio project type could not be identified. Therefore, the project was not converted. This error occurs if you attempt to attempt to import or convert a Visual Studio project type that InstallShield could not identify. See Also. Convert a Visual Studio setup project. Convert a Visual Studio merge module project.

Import a Visual Studio setup or merge module project. Error or Warning Number. Troubleshooting Tips. An unknown exception occurred. An unknown COM exception occurred. An error occurred while converting the project. An error occurred while determining the project type. An error occurred while converting the product properties. An error occurred while converting the files. An error occurred while converting the features.

An error occurred while converting the folders. An error occurred while converting the custom actions. An error occurred while converting the file types. In the log file when I search for "error" I can find Error and Error 0x I did an extensive search about the problem with the same error codes and tried a lot of things to make it work but it's always the same One or more of the files required to restore your computer to its previous state could not be found.

Restoration will not be possible. Dear Panda99,. I already researched your logs and found the following error message:. Error writing to file: msddslmp.

System error Verify that you have access to that directory. Did you run the installer as administrator? If not, please try it. After that, please run the installer as administrator again. Product Version: Product Language: Manufacturer: Microsoft Corporation. Update Name: KB Installation success or error status: Please confirm it, in case the package is corrupted. Hope those will helpful for you and looking forward your update.

Best regards,.