VS 2010 crashes when trying to set up links for subreport

[Former Member]

I'm trying to add a subreport to a crystal report within my Visual Studio 2010 application (vb.net). I can Insert....Subreport and choose the subreport but when I click on the Link tab and choose what fields I want to link together, VS crashes on me.

Three files are generated. Which one tells me what the problem is?

WER1308.tmp.WERInternalMetadata.xml

WER1ECB.tmp.appcompat.txt

WER1F68.tmp.mdmp

[saurabh_pathak · Accepted solution]

Hi,

I am assuming that you are using Crystal Reports for Visual Studio 2010.

Ensure that you are on SP1:

http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_13_0_1.exe

You can run the [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] to check if there is any dll causing the problem.

Thanks,

Saurabh

Edited by: Saurabh.Pathak on Nov 22, 2011 7:38 PM

[Former Member · Accepted solution]

Yes, I'm using CR for VS 2010.

I downloaded SP1. I'm pretty sure I had it to begin with but am not sure how to check. I get the same problem when selecting a field for linking after downloading.

OK, I ran the modules but am not sure what to look for. The instructions that come with it troubleshoot why an app works on one computer but not another. So I'm not sure what to look for.

Thanks for your help.

[Former Member · Accepted solution]

The main report is based on an SQL view. The subreport will be based on an SQL table.

[former_member183750 · Accepted solution]

I'm not sure about the Modules idea either...

One thing to check though

Make sure you do not have a c:\windows\temp directory. If you do, rename it to mytemp.

- Ludek

[Former Member · Accepted solution]

Deleting the c:\windows\temp folder will have no adverse affect on any other software applications?

[Former Member · Accepted solution]

(That should read "Renaming the...", not "Deleting the...")

But, if I try to rename it, I get a message that it's in use and can't be renamed

[former_member183750 · Accepted solution]

Atually, [SP2|http://www.sdn.sap.com/irj/boc/support?rid=/webcontent/uuid/d01fdad8-44e5-2d10-61ad-9d2d4158f3a8] for CRVS2010 just shipped and this issue is resolved there. I have not tested this, but downloading SP2 will not hurt.

- Ludek

[Former Member · Accepted solution]

No, SP2 does not solve the problem.

[Former Member · Accepted solution]

What else can I try to get this subreport to work?

I've downloaded SP2, which did not solve the problem.

I cannot rename C:\Windows\Temp to MyTemp because I get an error message that the folder is in use. I have two more temp folders: C:\Users\...\Temp and C:\Users\...\AppData\Local\Temp, which I've renamed to MyTemp but that doesn't solve the problem.

I tried recreating the report and subreport.

I tried recreating the report and subreport and tried linking on a different field.

I created a new project and recreated the report and subreport.

Everytime I click on OK or Cancel on the subreport Link tab, VS crashes on me.

[former_member183750 · Accepted solution]

I cannot rename C:\Windows\Temp to MyTemp because I get an error message that the folder is in use.

Determine what app is using the folder(?). [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx] may help you there.

Reboot and try to rename right after reboot(?).

- Ludek

[Former Member · Accepted solution]

Any news on what SP2 is supposed to correct?

My network admin is uncomfortable with me trying to remove or rename these temp folders. So it appears that I'm stuck with a product that I can't use.

I've just started converting Access database applications to Visual Studio. All the reports for this current application that I'm working on are in Access. I can call Access to manipulate those reports. So at least I have a reporting tool that I can use.

[former_member183750 · Accepted solution]

The following is what applies to your issue directly as far as SP2 is concerned:

FR: ADAPT01511363 Using c:/temp can case VS2010 to crash if wrong files are present
PR: ADAPT01511359 Yes 1/10/2011 9:54:22PM
Submitter:
Closed
Fixed

Expected: We should not be using c:/temp
Database Expert can crash VS 2010 if local user has created a folder c:/temp and an unknown xml files
exists.

Observed:
Install VS2010
Install CR for VS 2010
Create a c:\temp and c:\temp\crystal folder
Copy the attached report into the \crystal folder
Copy the logo.bmp into c:\
Copy the other 2 files into the \temp folder
Create a new Windows App, VB or C#, change the project to 4.0 Framework
Drop the viewer into the form
Drag and drop the report from \crystal folder into the app.
From the design mode right click in the gray area at the bottom of the report and select Database, Set
Location. This is where it crashes.

The rest of what is fixed will be published eventually...

- Ludek

[Former Member · Accepted solution]

Is c:\temp the same as c:\windows\temp?

Currently there are about 10 xml files in c:\windows\temp. Most are dated in 2009 with one dated 2010. If my network admin says OK, then I'll delete those and see what happens.

VS2010 crashes for me when I try to link the main report to the subreport.

[former_member183750 · Accepted solution]

Could be - depends.

Couple of way to determine what temp directory is being used by Crystal Reports \ process CR is running under:

1) Type %TMP% in start | Run, this will get you to the directory CR win app will use - and possibly a web app, depending on permissions, etc.

2) Use [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx]. Filter ProcMon for your process, then look where the temp report files are being written to in the logs.

- Ludek

[Former Member · Accepted solution]

%TMP% points to c:\Users\emanning\Appdata\Local\Temp

The only xml file in this temp folder is gwstylen.xml, which is used by Groupwise.

[former_member183750 · Accepted solution]

Let's see what procmon tells you

- Ludek

[Former Member · Accepted solution]

Here's what I did:

1. Started procmon. Set filter to Path Containing Temp

2. Opened published VS2010 application

3. Opened report created in Crystal (named CrystalReport1.rpt)

4. Found entry in procmon

This is the entry:

Operation=> CreateFile

Path=>C:\Users\Emanning\AppData\Local\Temp\CrystalReport1 {288618B4-B95D-4785-878C-20B0DA99068A}.rpt

Result=> Success

If I'm reading things right, CR is using C:\Users\Emanning\AppData\Local\Temp\

[former_member183750 · Accepted solution]

Open the WER1ECB.tmp.appcompat.txt file in notepad and copy it's contents in here.

Also, see if the following will help;

Check your system for malicious code using an up to date Anti Virus program.

Check your system for spyware and adware using a checker such as Spybot.

Remove unwanted files and applications by running Disk Cleanup.

Check your Hard Disk for errors using Check Disk.

Defrag your Hard Drive

- Ludek

[Former Member · Accepted solution]

I'm not able to dump the contents of the temp file here. I get an error message that I'm posting too many characters. Can I email you the temp file or can you tell me what part of the temp file you need and I'll post just that?

[former_member183750 · Accepted solution]

Not ever having seen the file, I have no idea what to look for either. When I did my last post, I was under the impression from some google searches that this was a relatively simple file to read. As it happens, it's not. An article from here points out:

http://www.lockergnome.com/it/2005/06/17/how-do-i-resolve-my-problem-with-appcompattxt/

Note: itu2019s not meant that you understand this. Itu2019s meant for the engineers back at Microsoft to use to analyze failures and hopefully provide fixes over time.

Additionally, the above article makes a suggestion similar to what I had:

A fix could be as simple as a configuration change, a virus scan a system file check...

So, unless you want to submit the file to MS, do the following:

1) Uninstall CRVS2010

2) Do a repair on VS2010

3) Reinstall CRVS2010

If that does not resolve the issue, go to my previous post re. virus scans, defrags and so on.

- Ludek

[Former Member · Accepted solution]

I uninstalled CRVS2010, repaired VS 2010, reinstalled CRVS2010 - still crashes.

Ran a virus scan on my C drive and found only cookies, which were deleted.

My network admin remoted in and did a disk cleanup. Nothing much to clean up,

Ran Check Disk. There were some issues that I assume got resolved. I went to lunch while it was running and when I came back, my machine had restarted and was waiting for me to continue.

Haven't done a refrag yet. Network admin said to wait until I go home and he will run it this evening.

Tried to add the subreport again but it still crashes.

Is there a possibility that I'm doing something wrong when trying to do the linking? The main report is based on an SQL view. The subreport is based on an SQL table. The linking field is an integer field. I don't know what other info you need, if any.

Thanks for sticking with me on this.

[Former Member · Accepted solution]

Defrag done overnite.....still same error.

[former_member183750 · Accepted solution]

Very strange - I called out for a bit of help \ more suggestions from CR Design guys, etc. A few questions \ suggestions:

Does it crash on any linking field or is this specific to the one field?

Something different with field name (length, special characters)?

Is downloading an eval of CR 2011 a possibility? CR 2011 does not install any SDK, so there will be no issues with assemblies getting mixed up etc. But it would be interesting to see if CR 2011 can do the linking. Sometimes, the designer will even throw a different - perhaps a useful error...

CR 2011 eval can be downloaded from here:

http://www.sap.com/solutions/sapbusinessobjects/sme/freetrials/index.epx

- Ludek

[Former Member · Accepted solution]

OK, got it to work but something is still not right.

I created a crystal report/subreport using a completely different SQL database, but within the same Visual Studio application as the report giving me problems. Subreport didn't crash but I noticed that all records in the subreport table were displaying for each row in the report. So the links were not working. I right-clicked on the subreport, chose "Change Subreport links...", selected the fields again and the subreport then displayed the correct rows. Yay.

I tried recreating the subreport in the report I had problems with, but the subreport crashed.

I then created another report/subreport using different tables from the SQL database for this application. The subreport didn't crash but I had the same linking issue as described above. I was able to resolve it by selecting the fields again.

I then recreated the view that was causing the earlier problems. I selected only 3 fields for the report. Subreport worked but I had to reselect the link fields as described above.

I then recreated the report/subreport and selected all the fields from the view (12 fields in all). Subreport crashed.

I went back into that report (did not recreate) and took out all but 3 fields. The subreport worked but only after I reselected the link fields as described above.

I then went back into this report and added the rest of the fields. Subreport still works fine. I got very brave and deleted the subreport then recreated it. Subreport works fine but I had to reselect the link fields.

So...it appears that initially I cannot too select many fields for the main report. I have to select the link fields, then reselect them again to get the subreport to work right.

I'm thinking I need to try CR 2011.

[former_member183750 · Accepted solution]

If you can try CR 2011, that would be excellent. This is just plain... something. But if you do have any updates, it would be great if you can share.

- Ludek

[former_member208657 · Accepted solution]

It may be worth while to use a tool like DebugDiag from Microsoft and set it up to create a dump file when the visual studio ide crashes. You could then use the DebugDiag tool to run a quick analysis on the .dmp file and see where the offending flle is that is causing the crash to occur.

The resulting log from the analysis doesn't always tell you exactly what is causing the failure, but it may point you in the right direction.