"Unrecoverable build error" building setup project in Visual Studio 2005

[Former Member]

I am having trouble building a setup project in Visual Studio 2005 which only occurs once I add my Crystal project and merge modules to the solution.

Unfortunately, the error message from Visual Studio is not very helpful - "Unrecoverable build error".

From what I have read on MSDN, this error can have many causes (http://support.microsoft.com/kb/329214). One possible cause seems related to Visual Studio not being able to find the right paths for components during the build. Since I have had several other problems with the Crystal 2008 merge modules over the last few months, my gut feeling is that the merge modules are causing the problem, and somehow not exactly telling Visual Studio where to find dependencies.

Any advice on how to narrow the scope of the problem would be much appreciated!

By the way, the solution builds okay on another machine (although the final setup MSI does not seem to include all needed dependencies to run the web application once I deploy it to our development web server).

Thank you in advance for any help!

--

sw

[former_member183750 · Accepted solution]

See my [Topic of the Week - Crystal Reports, Report Application Server, Business Objects Enterprise|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14789] [original link is broken] [original link is broken] [original link is broken]; blog from 17-Jul-09. The information and link in that blog may help you out.

Also, see the [Building a deployment project with Crystal Reports 2008 (12.1.0.892) SP1|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13427] [original link is broken] [original link is broken] [original link is broken]; blog.

Ludek

[Former Member · Accepted solution]

Ludek -

Thank you.. I followed the steps in the following article and this seems to have solved the problem. Visual Studio now builds the solution without the "unrecoverable build error" message.

1353170 - How to build a setup package with Crystal Reports 2008 SP1 merge modules and Visual Studio .NET 2005?

http://tinyurl.com/nf8lb7

I noticed that I had not entered a keycode into the merge module properties before. Is it possible that entering this keycode is what caused the issue to go away? Is the keycode stored in the Visual Studio solution? Or will any developer who opens the solution need to enter the keycode?

Thank you for the help.. I just have three more mysterious Crystal 2008 hurdles to overcome before I can start moving forward with my development again!

[former_member183750 · Accepted solution]

Good to hear the error is gone.

Is it possible that entering this keycode is what caused the issue to go away?

- this would not cause the error, though the print engine would use it's own internal keycode and this would throttle it to one concurrent user as opposed to three concurrent users with the normal keycode.

+ Is the keycode stored in the Visual Studio solution? Or will any developer who opens the solution need to enter the keycode?+

- The keycode is entered into the registry. Thus the app will use the keycode from the registry - using an exe / dll or .NET IDE.will

Ludek

[Former Member]

Unfortunately, this problem has come back.

[former_member183750]

Not sure I understand. This is an error when building a deployment project that contains the Crystal Reports assemblies(?). Once the steps provided in the notes suggested in my blog, the error went away(?). Now it is back. Are you creating a new deployment project?

Ludek

[Former Member]

Yes, this is an error when building a deployment project that contains Crystal assemblies.

Here is the history:

• Initially, this Visual Studio solution built okay

• After a few weeks, I was no longer able to build the solution on this machine

• After following the advice given in some of the links you provided earlier in this thread, the problem went away

• About a week later, the problem has returned

[former_member183750]

I'm not sure which of the notes helped you out. I believe there are three notes refering to this issue, with it's own solution. If you are adding the CR msm files to the deployment project, check that you are also adding the correct VC 80 msm files to the project:

u2022 Microsoft_VC80_ATL_x86.msm; version 8.0.50727.762

u2022 Microsoft_VC80_CRT_x86.msm version 8.0.50727.1433

u2022 Microsoft_VC80_MFCLOC_x86.msm; version 8.0.50727.762

u2022 Microsoft_VC80_MFC_x86.msm; version 8.0.50727.762

u2022 Microsoft_VC80_OpenMP_x86.msm; version 8.0.50727.762

Ludek

[Former Member]

Ludek -

I seem to be able to workaround this problem pretty reliably by following the steps below each time I build the setup project. Does not always work, but usually works.

- First, close all open documents in Visual Studio

- Exit Visual Studio

- Launch Visual Studio

- Build the setup project

I still get these warnings, even on successful builds, but I'm sort of just ignoring these since I can't find a way to make them go away.

Unable to find module dependency with signature 'CRT.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E'

Unable to find module dependency with signature 'MFC.Policy.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E'

Unable to find module dependency with signature 'CRT.Policy.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E'

Unable to find module dependency with signature 'MFC.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E'

Unable to find module dependency with signature 'OpenMP.1E507087_0819_45E0_FF1F_C8B3B9A1E18E'

Unable to find module dependency with signature 'ATL.Policy.66332652_9C28_58B1_FF1F_C8B3B9A1E18E'

Unable to find module dependency with signature 'OpenMP.Policy.04B9F3B6_9645_7658_FF1F_C8B3B9A1E18E'

Unable to find module dependency with signature 'MFCLOC.Policy.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E'

Unable to find module dependency with signature 'MFCLOC.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E'

Unable to find module dependency with signature 'ATL.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E'

Item 'Microsoft Data Access Components 2.8' is required by 'Crystal Reports 2008', but was not included.

Two or more objects have the same target location ('[crystalreportviewers12]\allstrings_en.js')

Two or more objects have the same target location ('[crystalreportviewers12]\web.config')

Two or more objects have the same target location ('[crystalreportviewers12]\processindicator.js')

Two or more objects have the same target location ('[win32_x86]\implode.dll')

[former_member183750]

As long as it works - at least in part. But if you look at this blog:

/people/ludek.uher/blog/2009/03/09/building-a-deployment-project-with-crystal-reports-2008-net-2005-net-2008

those are exactly the files I document as being an issue. Version, name and all that. And there is a resolution mentioned there as well as in that "topic of the week" blog, which points to several notes created by David Hilton that also have possible resolutions.

Now, if your solution works, you may want to simply go with that. I just worry that you will run into issues when you're actually deploying the runtime to a clean computer.

Ludek

[Former Member]

I know those files are problematic from reading your blog post previously. I did spend a few hours trying to get it all sorted out a few weeks ago, and then finally came upon my sort-of workaround.

Just to check, I tried adding all the Microsoft merge modules to the setup package again - unfortunately now I get a lot more errors and the build fails.

When we go to staging and production, I guess you are right - my installation might fail if these dependencies don't exist, right? Is there an easy way for me to resolve that, without continuing to debug the setup project? Not sure why it is working on the development server - I guess maybe I already had some of the dependencies installed and did not realize it.

Also, do you know if SP2 for Crystal 2008 resolves these issues?

Thanks again for your help - this forum has really been very helpful over the last few months!

[former_member183750]

SP 2 does not resolve this. The dependencies for those VC++ files were introduced in SP 1 and they will not be taken away. At this time, you have all the resources I have and these should get you going. If you are not able to get this going, your only other option is to crate a phone case and have a technician walk you through the process. Phone case can be created here:

http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryI...

Ludek