BobTaylor
03-25-2016, 03:23 PM
I have done hundreds of installation packages for customers but I am having an issue with one.
The customer is running Win7x64 and has administrative permissions. Regardless how many times I rebuild the package he does not update the program he is running. The package is 32-bit.
I have tested it here with Win7x64, Win8, Win10 and they all successfully update the destination.
I created a small package with only the EXE, changed the background to ensure he is grabbing the correct installation package which goes to completion. But when he runs the EXE, it displays a missing DLL message forcing an abort. This indicates to me that it installed into an empty folder.
The packages do not allow him to change the install folder which is under program files (x86). Any data is under a CSIDL public documents sub-folder.
I tried to use this forum as a last resort, but I am very confused and we are both frustrated. Any hints on where to debug this?
Thanks for any suggestions.
Bob
Taysys Software
The customer is running Win7x64 and has administrative permissions. Regardless how many times I rebuild the package he does not update the program he is running. The package is 32-bit.
I have tested it here with Win7x64, Win8, Win10 and they all successfully update the destination.
I created a small package with only the EXE, changed the background to ensure he is grabbing the correct installation package which goes to completion. But when he runs the EXE, it displays a missing DLL message forcing an abort. This indicates to me that it installed into an empty folder.
The packages do not allow him to change the install folder which is under program files (x86). Any data is under a CSIDL public documents sub-folder.
I tried to use this forum as a last resort, but I am very confused and we are both frustrated. Any hints on where to debug this?
Thanks for any suggestions.
Bob
Taysys Software