Announcements

Between mid-October and November, the content on AREA will be relocated to the Autodesk Community M&E Hub and the Autodesk Community Gallery. Learn more HERE.

Problems installing Revit 2024 update 1

Problems installing Revit 2024 update 1

Simon_Weel
Advisor Advisor
9,132 Views
25 Replies
Message 1 of 26

Problems installing Revit 2024 update 1

Simon_Weel
Advisor
Advisor

Here we go again. Just as with Revit 2023. Installing update 1.0 fails. This time I have a brand new pc, so everything is still fresh. First I tried a silent install like Revit_2024_1_0.exe -q which finished remarkably quick. Because it didn't install. So I left out the -q, ran the installer again and after a while, the installer popped up a small window Insert the 'Formit Converter For Revit 2024' disk and click OK.  So I browsed to the Revit deployment, found the required file at image\RVT_2024_en-US\x64\FormIt after which the installer informs me the file Formit360Converter.msi at that location is not a valid installation package for the product Formit Converter for Revit 2024. Try again.

Ok, at the start of the installation, I noticed the installer unpacks the update file. So maybe there's an update for the converter as well - lets try and find those unpacked files. They turn up under  C:\Users\administrator\AppData\Local\Temp\Revit_2024_1_0\x64\FormIt\FormIt360Converter.msi

Same message, not a valid installation package. So I cancel installation of the Formit converter and the installation continues. The progress bar creeps up.... and creeps down. Error 1603 - which could mean anything. There's this link How do I fix this? which leads me to 404 error We can't seem to find that page. The 1603 error most likely means it could not install the Formit converter.

The installer doesn't clean up the unpacked files, so I try to run FormIt360Converter.msi on it's own. Same result - it pops up the 'browse for file' window and no matter which file I choose, it insists not a valid installation package. So I copied the folder with the unpacked files to another drive and tried again. Doesn't make a difference.

Sigh.

 

Edit: as a work-around, I unpacked the update file, modified setup.xml by removing the line about Formit360converter, ran Setup and the update installs fine.

9,133 Views
25 Replies
Replies (25)
Message 2 of 26

Simon_Weel
Advisor
Advisor

Unfortunately, the work-around doesn't execute silently. Switches like -q don't work. I checked setup.exe with a resource hacker, looking for any switches, but can't find them. Seems to me the update exe itself must call the embedded setup.exe in a way to convey any switches specified on the command line.

So how to tackle this one?

0 Likes
Message 3 of 26

Thanos603
Autodesk
Autodesk

A prompt for the original MSI file indicates that at least one of the install files associated with this component has been modified.  In this scenario, the installer needs to check the original content of the modified file to ensure the upgrade does not remove the modifications.

 

Typically, you would want to point to the MSI included in the original install media but this may change depending on which updates/hotfixes have been installed.  In this case, I'm curious if you had installed the Revit 2024.0.2 Update, which included an update to the FormIt component.  If so, this prompt would be looking for the Formit360Converter.msi file that was included in the 2024.0.2 patch wrapper.  If this is the case, you can download the 2024.0.2 Update here, extract the contents using 7-zip, and point to the MSI in the x64\FormIt folder.

Tony Michniewicz
Autodesk Delivery Team  


Anthony Michniewicz
Principal QA Analyst
0 Likes
Message 4 of 26

Simon_Weel
Advisor
Advisor

n.a.

0 Likes
Message 5 of 26

Simon_Weel
Advisor
Advisor

Gave it another try. I created a deployment with Revit build is 24.0.5.432. No previous updates installed. At 37% it pops up a 'browse for file' window and the source path is empty. If I specify the Formit converter found in the original deployment, it warns that is not a valid installation package. Doesn't matter what file I choose, it just won't accept it. So in the end I have to click Cancel and the update is rolled back.

 

In doing more testing, I discovered another problem. Contrary to previous installers, this one unpacks the file, starts setup.exe and exits. This is a problem for unattended deployments - you don't want another process to start before the current one finished. For example, we use the Domain Shutdown script to install updates, among other things. The exe file for updates is called from within the script using Start /B /Wait "Update" update.exe. With this update, the installer doesn't wait - it unpacks the file and then returns to the script, leaving the update running in the background.

Now when Windows is shut down by the user, it will wait for the Shutdown script to finish and then shuts down Windows. Since this update doesn't wait to finish (i.e. keep the Shutdown script running), Windows shuts down, regardless the update running in the background. Leaving a botched installation.

 

I've been ranting about ODIS before - it's disruptive. And it keeps getting more disruptive with every incarnation, it seems. Sigh.

0 Likes
Message 6 of 26

Simon_Weel
Advisor
Advisor

Did some more testing with FormIt360Converter.msi. Tried to install it separately. If I launch the file in the original deployment, it says "A newer version is already installed". If I try remove or repair, it says "This action is only valid for products that are currently installed". If I try to install the version that came with the update, it pops up that browse for file dialog. And no matter which version I pick, not a valid installation package.

0 Likes
Message 7 of 26

m_latz
Advisor
Advisor

Simon,

try the following find the cached msi package in the folder C:\windows\installer, use this to do a repair or try a install and uninstall to remove (sometimes this fixes also the problem, that you can not uninstall). Copy from the "installer" folder to a temporary folder ...

 

For internal use I have written a small program that "dumps" all cached msi packages. Then I can find quick the appropriate msi file or I can delete orphans. I have to check if I can extract that function from a bigger "tools program".

 

regards

 

Markus

 

 

0 Likes
Message 8 of 26

Simon_Weel
Advisor
Advisor

Checked C:\Windows\installer but it's not there or one of the sub-folders. Both the old and new FormIt360Converter.msi have exactly the same size. Searched the registry for FormIt360Converter.msi and it lists the one for Revit 2022 and at C:\ProgramData\Autodesk\ODIS\extract\{E47A204A-5F04-4907-A57C-04606EB3ED16}\x64\FormIt\ but that folder doesn't exist.

Used Nirsoft SearchMyFiles to find msi files containing formit and although it does find a bunch of files, none of them is the Formit Converter.

0 Likes
Message 9 of 26

m_latz
Advisor
Advisor

Okay,

 

let me check a few things, I'll get back to you ...

 

regards

 

Markus

0 Likes
Message 10 of 26

m_latz
Advisor
Advisor

Is it possible, that you have installed with different users ?

 

For example base Revit 2024 with user "system", Update Revit_02 with user "admin", etc ?

 

regards

 

Markus

0 Likes
Message 11 of 26

Simon_Weel
Advisor
Advisor

No, same user to install anything. I ran the installer with the logging option msiexec /i FormIt360Converter.msi /l*v C:\msi.log for both the original version as well as the update version. Log attached - edited out share names.

 

Another thing to note. Although the initial installation of the update fails and the action is rolled back, it's actually not rolled back completely. Revit lists the new build number. When I run the update installer again, it informs me the update is already installed.

0 Likes
Message 12 of 26

m_latz
Advisor
Advisor

Can you try to execute in a cmd window with admin rights:

 

msiexec /x {A4D93D5A-1942-4AB3-828E-C58A8DDB4377}

 

msiexec /x {A4D93D5A-1942-4AB2-828E-C58A8DDB4377}

 

msiexec /x {A4D93D5A-1942-4AB1-828E-C58A8DDB4377}

 

this tries to remove the Formit Converter for Revit 2024

 

I'm not sure what happens, ideally, we will get Formit uninstalled.

 

regards

 

Markus

0 Likes
Message 13 of 26

Thanos603
Autodesk
Autodesk

We are investigating reports of unexpected FormIt360Converter.msi prompts during installation of the recent Revit 2023 and 2024 updates.  To date we have not been able to reproduce this issue and are looking to obtain log files from impacted customers to assist in our troubleshooting efforts.  It would be much appreciated if you could use the Install Log Collection tool, available here, and post the resulting zip file.

 

Tony Michniewicz
Autodesk Delivery Team


Anthony Michniewicz
Principal QA Analyst
0 Likes
Message 14 of 26

m_latz
Advisor
Advisor

Hello @Simon_Weel ,

 

just took a closer look to your log files.

 

From your "Original.log" I see, that you try to install "FormIt Converter for Revit 2024" version 24.0.5.432, ProductCode {A4D93D5A-1942-4AB1-828E-C58A8DDB4377}.

 

But during the install the msi action:

Action start 14:24:33: FindRelatedProducts.
FindRelatedProducts: Found application: {A4D93D5A-1942-4AB2-828E-C58A8DDB4377}

 

notices that already product code "{A4D93D5A-1942-4AB2-828E-C58A8DDB4377}" is installed. This is the product code from "FormIt Converter for Revit 2024" version 24.0.20.20 (contained in Revit_2024_0_2.exe)

 

That's the reason why the installation fails, because according the defined rules in the upgrade table, the installation of an older version is not alllowed.

 

Next you try to install the update "Update.log"

As before, he finds the already installed "FormIt Converter for Revit 2024" version 24.0.20.20, Product Code {A4D93D5A-1942-4AB2-828E-C58A8DDB4377}.

And according the upgrade table he tries to uninstall the lower version to install the higher version. But to do this the CA (custom action) WixRemoveFoldersEx needs the information from the property FORMITCONVERTERDIR, which is not defined. This aborts the installation.

 

The property FORMITCONVERTERDIR is filled by the registry key:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\Revit\2024\Add-Ons\FormIt Converter for Revit 2024\InstallPath

 

FormItCon2024Problem-1.png

So can you check if you have that entry ? And if not create it manually.

 

regards

 

Markus

0 Likes
Message 15 of 26

Simon_Weel
Advisor
Advisor

msiexec /x {A4D93D5A-1942-4AB3-828E-C58A8DDB4377}

This one says "Are you sure you want to remove?" and when clicking Yes, it says "Only valid for installed products"

 

msiexec /x {A4D93D5A-1942-4AB2-828E-C58A8DDB4377}

This one says "Are you sure you want to remove?" and when Yes, it pops up the browse for file window. When specifying the 2024-file (original or update), it says 'Invalid installation file'. Then I had a brain-wave - let's look for all FormIt360Converter.msi files available. Since we use different versions of Revit, I have a deployment for Revit 2017 to 2024. A search lists FormIt360Converter.msi for Revit 2022 and update 1.3 / 1.4; Revit 2023 and update 1.1 / 1.2. So I specified the one for Revit 2023 update 1.1 and then it says 'Preparing to remove...' and then 'Invalid installation file'. Same for all other versions.

 

msiexec /x {A4D93D5A-1942-4AB1-828E-C58A8DDB4377}

This one says "Are you sure you want to remove?" and when clicking Yes, it says "Only valid for installed products"

 

So on to another pc, without update 1 for Revit 2024. When I run the update file, it pops up the browse for FormIt360Converter.msi almost instantly. Maybe the other one did that too, but I didn't notice. Anyway, if I don't do anything (i.e. leave the browse for file window just there), the installer continues. After a couple(!) of hours, it stalls at 97% and I cancel the browse for file window. The installer then stops with error 1603. The button 'how to fix this' presents a 404-error webpage.

The installer doesn't roll back this time and to my surprise, Revit still has the original build number, contrary to the other machine.

 

Ran the log collector; see attachment.

0 Likes
Message 16 of 26

Simon_Weel
Advisor
Advisor

The entry is not there for any version:

Simon_Weel_0-1690202582673.png

 

The install path isn't there either:

Simon_Weel_1-1690202723858.png

 

Created both the registry key and path, but the result is the same.

0 Likes
Message 17 of 26

m_latz
Advisor
Advisor

Yes, that makes sense. What you need now are the right installation sources for "{A4D93D5A-1942-4AB2-828E-C58A8DDB4377}"

 

regards

 

Markus

0 Likes
Message 18 of 26

m_latz
Advisor
Advisor

Have you the msi log file from your last try, that I can check what's now the error is ?

 

regards

 

Markus

0 Likes
Message 19 of 26

m_latz
Advisor
Advisor

Sorry, just saw, that the log files was in your uploaded odis.zip.

 

Okay now the error is, that it could not remove the old version, because the installation is damaged. Can you please try to remove with the correct installation sources (see my private message)

If this does not work try to install again just with:

 

msiexec /i FormIt360Converter.msi

 

if that runs, you can try again to uninstall.

 

If that does not work try to do a repair:

 

msiexec /fvoums FormIt360Converter.msi

 

if that runs, you can try again to uninstall.

 

regards

 

Markus

0 Likes
Message 20 of 26

Simon_Weel
Advisor
Advisor

Hi Markus,

 

Really appreciate the effort you make! Downloaded the various installers. When I try to install the update, it pops the browse for file window, I specify the 24_0_20_20 version, it starts to install... and then says Error applying transform. Another attempt results in Cannot remove old version. Downloaded MicrosoftProgram_Install_and_Uninstall trouble shooter and this _does_ list the Formit Converter 2024 as installed. And was able remove it. And then.... the update version installed without any problem. It's listed in the Registry and all files are there as well. And after that, update 1 for Revit installs quickly and without problems.....

 

Should have used the Microsoft Windows Trouble Shooter right away, I guess....

 

Edit: hold on - I just saw Formit Converter has vanished from both registry and files after the successful installation of update 1. Not sure if this is a good or bad thing....

0 Likes