Visio uninstall error 30066

Sign in to vote. I'm trying to create a silent deployment of Office I've edited the config. I've created a new package and program using the following commandline: setup. A failure exit code of was returned.

An exit code of is considered a failure. Solution: For more information on the exit code, refer to the documentation for the program you are distributing. The Application log also shows no evidence of the installation beginning, either. If I run the above command-line from the Run dialogue it executes and installs Office properly with no interaction. Tuesday, December 4, PM. Sometimes when you review a log file, you don't find "Note", "Return Value 3", or an error number.

Instead, you may see text that's similar to the following example:. Therefore, Setup also tries to locate the transform on the root of the Office source location.

When the transform can't be located in either place, the installation stops. All the techniques that are listed in the Windows Installer log files section can be used on verbose log files. However, verbose logging increases Setup times. Only use verbose logging if you're having Setup problems that can't be diagnosed with a default log file.

On the initial install of Office, verbose logging isn't used. If a Setup failure occurs, the second try to install will generate a verbose log file. However, the logging options that are used for these verbose log files aren't all the options that are available to the Windows Installer.

You can create a verbose log file when you perform an administrative installation of Office by using a command line that's similar to the following:. At times, Office Setup stops responding hangs , and you don't receive any error message. The best thing to do in this situation is to restart your computer, and run Office Setup again with complete verbose logging turned on with one additional option.

To do so, follow these steps:. In the Open box, type the following command line, and then click OK :. Typically, 19 lines of logging information are cached in memory before being written to the verbose log file. If you don't use the! If you use the!

After you create the verbose log file, scroll to the end and look at the last one or two lines. These lines tell you what Setup was trying to do when it stopped. For example, you may see text that's similar to the following example:. The resolution for this particular issue is to repair the Windows registry before you run Office Setup again. This indicates a problem with an Office Removal Wizard operation.

This problem may occur when Office Setup is having a problem removing your earlier version of Microsoft Office. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Related Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. Accept all cookies Customize settings. If you are using non-Office product IDs, for Visio product, there still many different versions, such as Visio Standard , Visio Professional The Product IDs are:. Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. I opened the MSI visiomui.

It must be a volume license software for our company use. Can you help me to identify the product ID and I can apply it on my uninstall procedure? If I do the uninstall through Control Panel, and select remove on the small popup window, it will work very well.

Threats include any threat of suicide, violence, or harm to another. Any content of an adult theme or inappropriate to a community web site.