Error with Crystal Reports for Visual Studio 2010

[gcucci]

I have a problem with installation of Crystal Reports for Visual Studio 2010.
I'm using InstallAware Studio 2012 and the merge modules CRRuntime_13_0_1.msm and CRRuntime_maps_13_0_1.msm downloaded from SAP site.
But during execution, my setup stops itself and shows the message "Unable to copy installation data to local folders".
Then it rollbacks all.

If I compile the setup without merge modules of CR, it works fine.

[giaviv]

Are you able to convert the merge module to an MSI and then installing it using the (Un)Install MSI Setup plugin?

[gcucci]

Hi,
I tried a setup with CRRuntime_32bit_13_0_1.msi, but it doesn't work, perhaps because I don't know to configure MSI setup plugin.

I also tried to build my setup (that is built as "Web Deploy") as "Single File": during its execution the message is became "Module C:\Program Files\SAP BusinessObjects Crystal Reports for .NET Framework 4.0\Common\SAP Business Objects Enterprise XI 4.0\win32_86\crtslv.dll failed to register".
By searching into SAP site, I have found some posts and a KB article (1531409 - How to deploy the CRVS2010 runtime when using merge modules), that says "the CRVS201 merge modules do not include VC++ dependencies". Therefore, to install CR it's necessary to include "Microsoft Visual C++ Secure Runtime 8.0 (indluced ATL and MFC) Service Pack 1".
I rebuilt the setup as "Single File" and now it works fine.
But if I rebuild the setup as "Web Deploy", it doesn't work and shows the message "Unable to copy installation data to local folders".
Obviously I need a "Web deployed" setup.

Some suggestions? Is there a log to check?

[giaviv]

Does removing the merge modules from the project solve this error?

[gcucci]

Yes, as I wrote in my first porst, if I compile the setup without merge modules of CR it works fine.
Is there any way to know the exact internal exception of the setup? Is there a file locked? Is there a wrong folder?

[giaviv]

Hi,

You can try using logging - set the LOGGED variable to the path of a log file and InstallAware will write it for you.