Squirrel.windows: Fatal error: Unable to commit changes at Squirrel.Update.Program.<setPEVersionInfoAndIcon>d__20.MoveNext()

[kjpacheco]

Having issues with the --releasify command. Below is the error from Package Manager Console. After looking at similar issues, I tried seeing if the rcedit.exe needed to be replaced, but that didn't change anything. Please HELP!

PM> squirrel --releasify C:codebaseGMAD_Test_Matrix-MainTestMatrixTEST.1.0.0.nupkg
squirrel : System.AggregateException: One or more errors occurred. ---> System.Exception: Failed to modify resources, command invoked was:
'C:codebaseGMAD_Test_Matrix-MainGMAD_TestMatrixpackagessquirrel.windows.1.7.8toolsrcedit.exe "C:codebaseGMAD_Test_Matrix-MainGMAD_TestMatrixReleasesSetup.exe" --set-version-string "CompanyName" "KJPACHECO"
--set-version-string "LegalCopyright" "" --set-version-string "FileDescription" "" --set-version-string "ProductName" "Test Matrix for User Testing ONLY" --set-file-version 1.0.0 --set-product-version 1.0.0'
At line:1 char:1

• squirrel --releasify C:codebaseGMAD_Test_Matrix-MainTestMatrixTEST ...
• ~~~~~~~~~~~~~~~~~
  
  
  
  • CategoryInfo : NotSpecified: (System.Aggregat...-version 1.0.0':String) [], RemoteException
  
  
  • FullyQualifiedErrorId : NativeCommandError
  
  

Output was:
Fatal error: Unable to commit changes
at Squirrel.Update.Program.d__20.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Squirrel.Update.Program.<>c__DisplayClass10_1.b__15()
at Squirrel.Utility.<>c__DisplayClass8_0.b__0()
at Squirrel.Utility.RetryT
at Squirrel.Utility.Retry(Action block, Int32 retries)
at Squirrel.Update.Program.Releasify(String package, String targetDir, String packagesDir, String bootstrapperExe, String backgroundGif, String signingOpts, String baseUrl, String setupIcon, Boolean generateMsi,
String frameworkVersion, Boolean generateDeltas)
at Squirrel.Update.Program.executeCommandLine(String[] args)
at Squirrel.Update.Program.main(String[] args)
at Squirrel.Update.Program.Main(String[] args)
---> (Inner Exception #0) System.Exception: Failed to modify resources, command invoked was: 'C:codebaseGMAD_Test_Matrix-MainGMAD_TestMatrixpackagessquirrel.windows.1.7.8toolsrce
dit.exe "C:codebaseGMAD_Test_Matrix-MainGMAD_TestMatrixReleasesSetup.exe" --set-version-string "CompanyName" "KJPACHECO" --set-version-string "LegalCopyright" "" --set-version-string "FileDescription" ""
--set-version-string "ProductName" "Test Matrix for User Testing ONLY" --set-file-version 1.0.0 --set-product-version 1.0.0'

Output was:
Fatal error: Unable to commit changes
at Squirrel.Update.Program.d__20.MoveNext()<---

[fr4gles]

1. Is that x86, x64 or compiled as "Any"?
2. Did you try to run squirrel as administator (try to run Powershell as administator)?
3. What windows version are you using?
4. It looks like it could be related to: https://github.com/electron/rcedit/issues/3

[kjpacheco]

1.) Any
2.) I was using Package Manager Console in VS 2015. I followed the directions and it worked once, then when I tried releasing the same project code (after being branched and merged to a different folder), it wouldn't work. So, I don't think running as admin or not is the issue.
3.)Windows 10
4.) That was my thought, too. I tried replacing the rcedit.exe file and it didn't have any effect.

[anaisbetts]

Do you have 3rd party antivirus installed? If so, try uninstalling it

[kjpacheco]

@paulcbetts I do have thrid party antivirus, but it wasn't an issue the first time I used squirrel. When I branched the project so I could connect/test with data from a different database, I ran into this problem. So essentially, I have two seperate applications with the same code inside. I don't understand why it would work for one and not the other.

[spaviot]

@paulcbetts I had this error or a very similar error while I was experimenting with various scenarios in order to automate the creation for release packages from Visual Studio.
Somehow it seems that if the stub "Setup.exe" (from wherever the squirrel package is located) is read-only, and when it is copied by the --releasify option to the release directory, this read-only flag is not removed after and thus the next write operation fails.

[quasarea]

run into similar issue when publishin on network share, had to replace rcedit.exe with current (1.1.1) from https://github.com/electron/rcedit

[Thieum]

@quasarea I found publishing over network always tricky (and not only with squirrel, but also with other software that attempt to work with files over network). One way to get around this kind of issue is to robocopy the content of the relesase folder, then robocopy it back after the release has been done locally, if the size of it is reasonable. Or have a way to sync it from network to local, do the release local, then sync back from local to network.

[shiftkey]

Merging this into #888 which is about upgrading rcedit, but I'm hesitant that this will resolve it because of this earlier comment:

4.) That was my thought, too. I tried replacing the rcedit.exe file and it didn't have any effect.

[Thieum]

@shiftkey I feel like we should avoid releasify over network as much as we can. If it's not rcedit failing, it's sharpcompress, or something else.