Problem with Crystal report 13 update 12 merge modules
Posted: Mon Jan 12, 2015 12:34 pm
Installaware 18 have a bug I have discovered trying to using the CR13 update 12 merge modules downloaded from the SAP site.
If you use this merge modules and you start Installawareproject relatively deep on folder names (in my case D:\Develop\ProjectName\Setup), something was wrong.
What appen is that 1 file on the merge modules is not copied to the single setup. This is because the complete name of the unzipped file is too long for the pc that compile the setup. Please note that the problem is generated in the developer PC, the effect in the customer PC is an installaware error "file not found or access denied".
The big problem is that installaware do not show any error during the setup compilation, nor stop compilation or show warning messages. Simply skip the long name file and finish the compilation. The setup exe is generated... but it will stop during the customer installation.
The only way to solve this problem is to copy the setup project near the root of the disc, in my case D:\ProjectName. In this case the setup will be compiled correctly... you cannot see any different respect the wrong compilation, but this setup macigally works.
I hope this problem will be fixed in next release, I have lost a lot of time to understand what appens and it was not my cause.
Hope this article helps somebody other,
Best regards
If you use this merge modules and you start Installawareproject relatively deep on folder names (in my case D:\Develop\ProjectName\Setup), something was wrong.
What appen is that 1 file on the merge modules is not copied to the single setup. This is because the complete name of the unzipped file is too long for the pc that compile the setup. Please note that the problem is generated in the developer PC, the effect in the customer PC is an installaware error "file not found or access denied".
The big problem is that installaware do not show any error during the setup compilation, nor stop compilation or show warning messages. Simply skip the long name file and finish the compilation. The setup exe is generated... but it will stop during the customer installation.
The only way to solve this problem is to copy the setup project near the root of the disc, in my case D:\ProjectName. In this case the setup will be compiled correctly... you cannot see any different respect the wrong compilation, but this setup macigally works.
I hope this problem will be fixed in next release, I have lost a lot of time to understand what appens and it was not my cause.
Hope this article helps somebody other,
Best regards