.NET 4.0 runtimes: No files matching wildcard pattern

[roecki]

Hi,

after upgrading to Installaware 12/NX i can't build our setup.

There is the following error:
No files matching wildcard pattern C:\PROGRA~2\INSTAL~2\INSTAL~2\runtimes\netfx_extended_x86
The path is valid and contains files.

If have removed all .NET 4.0 runtimes. The project builds now just fine.

After readding the .NET 4.0 runtimes by checking the checkbox under runtimes, the project doesn't build any more.

What can I do?

Thanks,
Anton

[FrancescoT]

Dear Anton,

Have you regenerated your personal license file and used it to activate your product?

Regards

[roecki]

Hi Francesco,

yes i have regenerated the license file and i have installed it.

Anton

[FrancescoT]

Dear Anton,

I know, it is a very obvious question, have you installed all NX feature?

Regards

[roecki]

Hi,

i have not installed sql server features and some runtimes. I have installed all .NET 4.0 an .NET 4.5 runtimes (32 & 64bit, Client Profile & Full).

The directory mentioned by the error message exists and is containing the .NET files (at least it looks like).

Anton

[FrancescoT]

Dear Anton,

I still suppose that your error is caused by a missing runtime / feature, if as you said, you have already regenerated and installed your personal license file.

Because the Net 4 runtime selection causes in IA NX the automatic inclusion of other NET runtimes version as well ( ... Windows Installer runtimes are also automatically included), have you installed all the NET runtimes version available with the InstallAware setup package?

Regards

[MortSkil]

I have the same problem as Anton.

The message I get when trying to compile my setup is

WARNING!

No files matching wildcard pattern
D:\PROGRA~2\INSTAL~1\INSTAL~3\runtimes\vc91bin\*.*

If you were trying to build application runtimes, run InstallAware
setup again, and add all optional features.

In D:\Program Files (x86)\InstallAware\InstallAware 17\runtimes\vc91bin I find vc_x86runtime.cab and vc_c86runtime.msi as well as 9 dlls with a corresponding eula, as well as install.exe.

Could this be caused by a wrong configuraiton setting?

I am running InstallAware 17 and I have installed our license.

Thank you for any help.

MortSkil

[FrancescoT]

Dear User,

please have a look at the following link.
http://www.installaware.com/forum/viewtopic.php?f=2&t=9469

Regards

[MortSkil]

Hello,
I tried the steps recommended in the link you provided, and using the short folder names, I now get the following message:

No files matching wildcard pattern
D:\PGMF_X86\IA\IA17\runtimes\vc91bin\*.*

If I type "dir D:\PGMF_X86\IA\IA17\runtimes\vc91bin", 24 files are listed.
Why does this not work? Is it not advisable to install IA on other than C:\ ?

I also can not see why the legacy 8.3 mode should still create problems in a presumably modern product as IA.

I really hope this may be solved - I am in a real hurry to create some installers, and do not really want to switch back to InstallShield or other alternatives.

Regards

[FrancescoT]

Dear User,

I am not quite sure if you followed the suggested steps correctly, anyway these are;

1- verify that your target drive has the "8.3" files system setting disabled, if not disable it.
2- completely un-install IA
3- restart the system and install IA once again.

//////////////////////////////////////////////////
An alternative workaround, it could be to manually replace the "IA installation path" stored within your System Path environment variable, with the same as short path format.

- Supposing that your IA installation directory is; "D:\PGMF_X86\IA\IA17"

The short path format can be retrieved using the following command via "Command Prompt ";
- cmd /c for %A in ("D:\PGMF_X86\IA\IA17") do @echo %~sA

Restart your system once done.

/////////////////////////////////////////////////

I also can not see why the legacy 8.3 mode should still create problems in a presumably modern product as IA.

In reality the problem is caused by the OS.
Under some circumstances (... I never found it enabled with my OSes) it enables the "8dot3name" setting for the non system drives, which it is instead disabled by default with a system drive.

Regards

[MortSkil]

I followed your advice - deleted and reinstalled IA 17. I even installed it to the system drive (C:) to be sure to have no 8.3 related problems.

8.3 is disabled:

D:\>fsutil 8dot3name query
The registry state of NtfsDisable8dot3NameCreation is 1 (Disable 8dot3 name crea
tion on all volumes).

When compiling, I still get the same warning:

No files matching wildcard pattern
C:\PROGRA~2\INSTAL~2\INSTAL~1\runtimes\vc91bin\*.*

vc91bin is now in C:\Program Files (x86)\InstallAware\InstallAware 17\runtimes.
Why do I still have this problem?

Thank you for your advice - it is highly appreciated. And I definitely run out of time here...

I also installed IA on my Windows 7 desktop PC. Same problem there, although I have disabled 8.3 on this computer as well.
So, I have tried to install IA 17 both on a virtualized single core server running Windows Server 2008 R2 Standard and on my PC. Same error on both.

BTW: The 8dot3name setting was 2 on both computers before I changed the setting.

- and I realize that I did not reboot the computers after disabling 8.3 file names.

Is this trouble possible to avoid when installing IA? I do not think it should be necessary to touch OS configuration prior to installing IA...

Regards,

[MortSkil]

After uninstalling IA, reboot, then reinstall, I try to compile the project I have created.
First click on Compile gives no error message.
Second click on Compile is also OK.
Try to build CD or DVD, and I get
the same error as before.

8dot3name is set to 1.

Is there somewhere else I can look for the cause of this problem?

[MortSkil]

If I open another project, it seems to go better.
At least there are other files reported missing - and they really are missing.

I suspect there are some hidden settings in my project (created by the IA wizard before reinstall)

[FrancescoT]

Dear User,

for what you are reporting it seems that you still have the "8dot3name" flag enabled ... it should be "0" if disabled.

fsutil 8dot3name query C: // To query the status of the "C" drive flag
fsutil 8dot3name set C: 0 // to disable the status of the "C" drive flag
fsutil 8dot3name set C: 1 // to enable the status of the "C" drive flag
NOTE! To have IA working correctly, the above flag has to be "0" disabled.

If I query my "C" drive, the "fsutil " command returns "0" (zero).

Regards

[MortSkil]

Here is a snapshot from the MSDN documentation on 8dot3name.

Changes the file system behavior for 8dot3 name creation in the following instances:
When DefaultValue is specified, the registry key, HKLM\System\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreationNtfsDisable8dot3NameCreationNtfsDisable8dot3NameCreation, will be set to the DefaultValue.

The DefaultValue can have the following values:

0: Enables 8dot3 name creation for all volumes on the system.

1: Disables 8dot3 name creation for all volumes on the system.

2: Sets 8dot3 name creation on a per volume basis.

3: Disables 8dot3 name creation for all volumes except the system volume.

When a VolumePath is specified, the specified volumes on disk flag 8dot3name properties will be set to enable 8dot3 name creation for a specified volume (0) or set to disable 8dot3 name creation on the specified volume (1).

You must set the default file system behavior for 8dot3 name creation to the value 2 before you can enable or disable 8dot3 name creation for a specified volume.

I interpret this as 1 being the correct value to set in order to disable 8dot3 name creation for all volumes.

BTW: I deleted the project created with 8dot3 enabled, then created a new one after I reinstalled everything. Then, before adding any of my system files, I tried to compile and build with the Application runtimes I want. It worked! Twice!
Hence, I think InstallAware should add a fix to this problem, excluding 8dot3 completely if possible, and correcting whatever internal traces of the legacy file names.