Setup And Deployment Problem

[#1]

I recently upgraded to Crystal 2008 SP3. I am trying to deploy a .Net application. I have created the setup project and built it successfully. I downloaded the Merge modules for Crystal 2008, and I have them setup in the Setup project with the proper key code. I made sure that the dependencies for the project were refreshed so that I got the proper referenced items. I also set the prerequisites in the Setup project to include the C++ redistributable package.

When I try to install the application, I get the following error:

Module C:\Program Files\Business Objects\Business Objects Enterprise 12.0\win32_x86\CEReportSource.dll failed to register

I looked this error up and found several references in the forums. The references indicated that I needed to have the Visual Studio 2005 C++ Redistributable installed. I downloaded this from Microsoft and installed it on the target machine. None of this helps. I am still getting the error during the setup on the target machine.

Any help would be appreciated.

[Former Member · Accepted solution]

Sounds like you've done the correct things.

What OS are you doing the install on?

Can you run the set up on your development computer with no errors (just as a test...)?

Can you ignore out of the "failed to register" error that you get during the install? If you can, we could do couple of things:

1) Use the [Depends20|http://www.dependencywalker.com] utility to find out what dependency is missing

2) Try to see if we can manually register the dll

Ludek

Follow us on Twitter http://twitter.com/SAPCRNetSup

[Former Member · Accepted solution]

I'm running Windows XP.

I ran the Setup and installed through the errors. It looks like every reference to a Crystal module produced the same result, and I had to continue through maybe a dozen or more errors.

I ran the Dependency checker that you indicated. The only reference it could not find was DWMAPI.DLL, which I don't believe is related to this. I didn't see anything in here that resembled Crystal Reports modules.

The application will open, but when I try to produce a report, it throws an exception, and immediately dumps and closes.

[Former Member · Accepted solution]

You're right re. dwmapi.dll.

The issue you are describing sounds like that documented in the blog [Building a deployment project with Crystal Reports 2008 (12.1.0.892) SP1|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13427] [original link is broken] [original link is broken] [original link is broken];.

Can you also check out the following KBase please:

[1352616 - How to build a setup package with Crystal Reports 2008 SP1 merge modules and Visual Studio .NET 2008?|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_dev/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do] and see if that helps?

Ludek

[Former Member · Accepted solution]

I'm running Crystal 2008 SP3 (12.3.0.601). I'm using the merge modules for SP3: CRRuntime_12_3.msm.

I assume that is the correct set of versions to use.

[Former Member · Accepted solution]

Yup. I'd still like you to check out the links in my previous post...

Ludek

[Former Member · Accepted solution]

I'm working through those now. I just wanted to verify the versions.

[Former Member · Accepted solution]

I followed those instructions exactly. I created a new setup project to be sure that I was starting clean and didn't have any residual problems carried forward. When I build the Setup project it fails with the following error:

No 'PublicKey' or 'Hash' attribute specified for file 'vcredist_x86_8.0\vcredist_x86.exe' in item 'Visual Studio 2005 SP1 C++ Runtime Libraries (x86)'. C:\Documents and Settings\mmcclendon\My Documents\Visual Studio 2008\Projects\Lab_Solution\LabV2008_SetupV3\LabV2008_SetupV3.vdproj

This problem is caused because the ZIP file for the VS2005 redistributable does not actually include the executable. It only includes the XML files. You hve to download that separately, and then copy it to the folder where the ZIP file was stored.

C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\vcredist_x86_8.0

Unfortunately after all this, I have the same problem. I downloaded the proper version of the C++ Merge Modules. I specifically included them in the setup along with the prerequisite. I made sure that the version num bers matched the ones in the link you posted. It's all correct.

The setup fails at the same point.

[Former Member · Accepted solution]

Does the setup work on your own development box? E.g.; presumably that has all of the pre-requisites so it should work there. It would be nice to know if that is the case.

Ludek

[Former Member · Accepted solution]

Yes it does. I did get this to work, although not with the Merge Modules.

I went into the prerequisites and clicked the Crystal 2008 as a prerequisite. This caused the target machine to install the Crystal Runtime that I normally use on servers. The runtime installed properly with no problems, and the application works when I do that.

I'm not sure that is the best way to accomplish this. The merge module approach should work.

[Former Member · Accepted solution]

I discussed the issue with others around here. Apparently there are at least two other reports of a similar of perhaps identical issue. We'll test this and get back with results. We'll try for Friday, but early next week is more likely...

Ludek

[Former Member · Accepted solution]

That's fine. I'll keep watching the thread.

I appreciate the help.

[former_member208657 · Accepted solution]

It looks like the dependencies for Microsoft Visual C++ 2005 SP1 have been updated again. I found that there was a security vulnerability in ATL identified by Microsoft and they released an update for the Visual C++ 2005 SP1 Redist Package. See security bulletin [MS09-035 |http://www.microsoft.com/downloads/info.aspx?na=48&p=1&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=766a6af7-ec73-40ff-b072-9112bab119c2&u=http%3a%2f%2fwww.microsoft.com%2ftechnet%2fsecurity%2fbulletin%2fMS09-035.mspx] and kb article [KB973544|http://www.microsoft.com/downloads/info.aspx?na=49&p=1&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=766a6af7-ec73-40ff-b072-9112bab119c2&u=http%3a%2f%2fsupport.microsoft.com%2f%3fkbid%3d973544].

You'll need to install the updated Microsoft Visual C++ 2005 SP1 library before you attempt to install your setup package which includes the merge modules. The new vc_redist_x86.exe is available using the link below.

[Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update|http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en]

In summary, steps to try:

1. Install the Microsoft Visual C++ 2005 SP1 Redist Package from here, http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displa...

2. Run your setup package built using the Crystal Reports 2008 SP3 merge modules.

Edited by: David Hilton on Aug 3, 2010 4:18 PM

Updated to include new info re: Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update

[markabela · Accepted solution]

I seem to have the exact same issue.

I am trying to deploy a web application using a Web Setup Project in Visual Studio 2008 that contains crystal reports. I am using crystal reports 2008 SP3 and I added the merge module to the web setup project with the keycode. I set the prerequisites in the Setup project to include the C++ redistributable package also. I installed the Microsoft Visual C++ 2005 SP1 Redist Package on the deployment machine too.

I followed the steps here: /people/ludek.uher/blog/2009/03/09/building-a-deployment-project-with-crystal-reports-2008-net-2005-net-2008 but no luck.

The OS on the deployment machine is Windows Server 2008 64 bit.

Is there anything else I can try to stop the "failed to register CEReportSource.dll" error during setup of the application?

[Former Member · Accepted solution]

What is the version and size of the vc_redist_x86.exe you are using?

Ludek

[markabela · Accepted solution]

Hi Ludek,

I am using the vcredist_x86.exe downloaded from: http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displa...

The version is 6.0.2900.2180 and size is 2.61MB

Mark

[Former Member · Accepted solution]

I finally got back to this problem, and I installed the update to the C++ Redistributable that you listed. I went through the entire process again as before and got the same result.

I have this working by making Crystal 2008 a Prerequisite in the setup. This installs the Crystal Server runtime when I do the initial install. So, I've used that for my application because I had to move on.

It has always been a problem getting the Merge Modules to work. I've had problems with them in every version of Crystal that I have used over the years. So, I think I'm going to give up on this since I have it working using the other approach. We're going to be moving to VS 2010 before long, which I guess means an upgrade to Crystal 2010 as well. Am I going to have these same problems in that version?

[Former Member · Accepted solution]

Talk about a loaded question

I believe with CRVS2010 there will not be any MSM files, just an MSI. Reason we get into all these problems (in part...) is the changing MS dependencies. And as we can not include the dependencies in the msm due to some licensing issues, it leads to all kinds of problems (I suppose one of which is that in TS we are never told about these new dependencies and have to divine those on out own - ok, that was a rant...). Anyhow, the licensing issues do not apply to msi files and so the dependencies are included, hopefully resolving these issues.

Ludek

[former_member208657 · Accepted solution]

Using these merge modules has been getting more and more problematic over the years. This all started back after Service Pack 1 when we had to pull the Visual C++ library files out of our merge module package. This was due to licensing issues that Ludek mentioned above.

If you can bear it, I recommend to ALWAYS use the redist MSI or EXE package that we provide because it has everything you need in one package. I actually recommend to use this for .NET Windows Form based solutions along with the web based ones. We are permitted to include our merge modules in that setup, plus the Microsoft Visual C++ libraries we need to allow our software to work.

The reason why I recommend to use the MSI or EXE redist package is that it segregates the Crystal Reports .NET runtime from your application. When there is an update to the CR .NET runtime, and let's be honest there will be an update, you can simply go into Add/Remove Programs or Programs and Features and remove the Crystal Reports .NET runtime. Then install the new one. This is done without completely removing your application.

When you use the merge modules you have effectively bound the Crystal Runtime to your application. You'll need to re-package your entire application in order to update the CR .NET runtime in the event there is a patch you need for Crystal. This will mean uninstalling YOUR application as well. Your application could have many config files, databases, or other components that require some detailed configurations to work well for your client.

So if you can, use the redist MSI or EXE that we provide and don't use the merge modules. They are getting tougher and tougher to use.

[Former Member · Accepted solution]

Thanks, That explains a lot. I don't have an issue with the redistributable file. It has always worked well for me, and it isn't a big deal handling the versioning.

As far as I'm concerned, we can close this issue since I opened it initially.

Thanks again.