Bagur
asked on
Issue with installing runtime for Crystal Report XI on the remote server
Hi,
I am using InstallShield to create a distribution package for Crystal XI run time. I added all the 3 merge modules in my package. The install ran fine if install in the default location on the target computer which is the C:\. But when I changed the destination directory to D:\ the install still goes to C:\.
I even tried creating the install using Microsoft Visual Studio Installer but it still goes to C:\ even after changing the destination path to D:\
Do I have to change any parameter value in the merge module.msm files? Does anyone came across this issue?
Any help would be appreciated
Thanks
I am using InstallShield to create a distribution package for Crystal XI run time. I added all the 3 merge modules in my package. The install ran fine if install in the default location on the target computer which is the C:\. But when I changed the destination directory to D:\ the install still goes to C:\.
I even tried creating the install using Microsoft Visual Studio Installer but it still goes to C:\ even after changing the destination path to D:\
Do I have to change any parameter value in the merge module.msm files? Does anyone came across this issue?
Any help would be appreciated
Thanks
ASKER
I am doing asp application with VB. I have tried everything and spent so much time figuring it out..The problem with XI is that there is no manual install of runtime dlls,as what crystal says, as it used to be in 8.0,8.5. Everything is in merge modules and I even tried changing the destination in the .msm file but it still insists on installing itself on the C: drive
The client does not have any room on the C: drive and want it under D: drive
The client does not have any room on the C: drive and want it under D: drive
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Don't know exactly what you're doing, but if you're doing a asp.net app, then you'll need to put the Crystal dll's in the Global Assembly on the C drive (which you can do with a distribution package or via command line). The good news is that you can still put your web application on a different drive and utilize the global assy on C - you don't have to put all of your apps that use Crystal on C: