18

I'm trying to create a installer with iexpress for a WAV Audio Player in C that I finished today, but, when I'm on the last step, it cames up with the following error message: "Unable to open the Report file C:\Users\Poleto\Desktop\~SWAV.RPT" Any idea of how can I fix this?

Guilherme Poleto
  • 327
  • 1
  • 2
  • 13
  • I just discovered this error can also be caused, by a filename containing spaces, in the .SED file list. Details below. Even though I put the filename in quotes, when iexpress invokes the Windows makecab utility, makecab chokes on the filename--the intermediate .DDF file does not have the quotes. When I tried manually running makecab on the .DDF file, I found the error reported as "ERROR: Unexpected text: <lastwordofmyfilename.lnk>". – Benjamin Rudolph Apr 12 '19 at 11:33

7 Answers7

20

Sorry, I know this is an old post, but I found a solution, and it doesn't need admin. To create an installer, navigate to the folder you are installing from, click the Explorer path bar, and type in "iexpress". Then, create the installer as normal. You do not need admin privileges. Make sure you save the installer to the same folder. This defines the %cd% environment variable as the path of your installer folder, which makes it work. Maybe it's something with the command-line bundler. I don't know. All I know is that it works. Even with a non-administrator account running as non-elevated.

Proof:

Image of successful installer run

9pfs
  • 560
  • 5
  • 17
  • I am so happy this works. Now I can bundle executables and DLLs for my favorite programs as one file. – 9pfs Mar 21 '21 at 18:28
  • 1
    Wow. It just worked for me. I tried every other thing. But this solution worked well for me. Thanks – Chanks Sep 09 '21 at 06:01
  • It's riddiculous how this works. I can't run iexpress as admin, workplace policy, but now I can use it. Thank you – Nawad-sama Dec 30 '22 at 09:46
  • Confirned working with on-admin user as Aug 11, 2023 on Win10 Pro 21H2. – Fjor Aug 12 '23 at 00:12
13

You probably need to run with elevated permissions, see the SS64 entry on IExpress.

Paul
  • 420
  • 1
  • 5
  • 18
10

You should run iexpress with administrator, then this will be resolved.

Enosh
  • 229
  • 1
  • 4
  • 10
9

I came accross this issue as Admin. Something that worked for me:

On the Package Name and Options screen, tick 'Store files using Long File Name inside Package' and then create.

SmokeyJoe
  • 91
  • 1
  • 2
1

I ran into this issue when I had by mistake, included the same filename twice in this file. I was able to narrow down the culprit section by removing all sections one at a time and running the build until the build passed. And then an analysis of the erring section revealed the filename duplication.

Pankaj Shrivastava
  • 11
  • 2
1

Yes, running IExpress as administrator usually solves this problem, but in my case there was an additional issue. I noticed that IExpress produces the same error when the path to the source files contains folders with spaces AND the path is based on another partition than C: (or maybe the system partition). For example:

Working Path => C:\Some Folder With Space\file.SED
Not Working => D:\Some Folder With Space\file.SED
Working Path => D:\SomeFolderWithSpace\file.SED

I liked that IExpress extracts to temporary folder, generates initial SED file from GUI, which can easily be edited as it has INI format, has command line, can include install script/executable after extraction and is part of Windows. Really nice features, but this bug is a killer. Also, running as administrator and not providing error codes when unable to create archive (from command line) is not nice.

MatrixRonny
  • 437
  • 3
  • 11
0

You have to run it with administrator rights Hope i helped you.

cfp
  • 5
  • 1
  • 3