1001 Could Not Find File .installstate

Posted on admin
  1. Could Not Find File Name . (error 3024)
  2. Could Not Find File System /dev/root

Installer Custom Actions - Missing InstallState on rollback. Discussion in 'Microsoft Dot NET Framework' started by Guest. InstallState file could not be found. I have tried to create a custom action for a Visual Studio Installer project to modify the permissions for a config file. 1001: Could not find file myApp.InstallState. Error 1001 Could Not Find File Installstate After having double clicked on Setup.exe, the installation seems to run normal (prerequisites, gui setup dialog.

This isn't accurate. You don't have to add anything to both phases. I added an update at that link. I used just the Install override in the Installer class after adding the 'Primary output' to each section in the Custom Actions. I set my CustomActionData value on the Install phase Primary output properties.

Could Not Find File Name . (error 3024)

Error

I ignored the other phases altogether in my Installer class - they don't need to be overridden and will just do what they always did. I got the same error as the OP until I added a closing quote around one of my textbox names that was in my CustomActionData string that was missing. – Dec 1 '16 at 21:04. For me, the issue was as simple as just adding a closing quote around one of the textbox names in my CustomActionData string.

FileFind

Could Not Find File System /dev/root

I was using the 'Textboxes (A)' and 'Textboxes (B)' windows in the User Interface section. A has 1 box, EDITA1, where I get the path to a file, and B has 2 boxes, EDITB1 and EDITB2, for some database parameters. My CustomActionData string looked like this: /filepath='EDITA1' /host='EDITB1 /port='EDITB2' It should have been: /filepath='EDITA1' /host='EDITB1' /port='EDITB2' (closing quote on EDITB1) I used the Install override in my Installer class to get the values (i.e. String filepath = Context.Parameters'filepath';) and used it to write them to an INI file for my app to use once installed. I put the 'Primary output' under all of the phases in the Custom Actions GUI, but did nothing with the InstallerClass property (default: True) and only set the CustomActionData string on the Install one.

I didn't even include override functions in my Installer class, since I was doing nothing that was custom in the other phases.