cancel
Showing results for 
Search instead for 
Did you mean: 

Visual Studio Crashing when open an existing crystal report.

Former Member
0 Kudos

I am running windows 7 64 bit with visual studio 2010. I have previously used crystal reports xi r2 to do our reporting, but I wanted to upgrade to the latest release with our upgrade to visual studio 2010. I installed crystal reports 2010 on my machine, and when I open the project it prompts me to upgrade it, which I choose to do. I cam able to open and work with a new file, and set the database location without a problem, and I am able to open an existing report which was created with an older version of crystal, HOWEVER when I try to set the datasource location on an older file or run the database expert with the existing report, it causes visual studio to crash saying that an external component has encountered an error. I am able to create a new report without a problem and set the datasource on that new report, but I am unable to edit the existing reports.

I have tried uninstalling and re-installing to no effect.

I am not sure if this is the same problem as thread number 1829738, but since I am able to edit new reports, I thought it was a little bit different than what they are seeing. Also, as it was suggested in that thread, if I rename the sax dll, I am unable to open any old reports, and visual studio gives me an error that it is unable to open the file, but without crashing.

Any suggestions that you can give me to get this resolved would be greatly appreciated.

Thanks,

Greg

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

See this note for a possible solution and search more:

Thank you

Don

Former Member
0 Kudos

I have searched through all the forms, and I have already done the suggestions that were in the earlier thread (which I mentioned already in my post). AS I mentioned in my earlier post, when I rename saxserialize.dll, the report does NOT load at all.

I don't know what any or all of this means, but when I run the debugging program as mentioned in the other thread, I get the following error displayed:

WARNING - DebugDiag was not able to locate debug symbols for saxserialize.dll, so the information below may be incomplete.

In devenv__PID__6452__Date__12_02_2010__Time_03_30_21PM__773__Second_Chance_Exception_C0000005.dmp the assembly instruction at saxserialize+398a in C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\saxserialize.dll from SAP BusinessObjects has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 0

Function Arg 1 Arg 2 Arg 3 Source

saxserialize+398a 1d69dcd0 271c8614 1d87c8f0

xerces_c_2_1_0!NamedNodeMapImpl::findNamePoint+45ddf 146e0560 00000001 1d6b4800

xerces_c_2_1_0!NamedNodeMapImpl::findNamePoint+366c1 0040d98b 013bda26 1d6b4840

xerces_c_2_1_0!NamedNodeMapImpl::findNamePoint+39d11 00000000 013bda6a 0040db38

xerces_c_2_1_0!NamedNodeMapImpl::findNamePoint+3a00e 0040dae8 013bd9ae 0040db38

xerces_c_2_1_0!NamedNodeMapImpl::findNamePoint+4484a 0040dae8 012a8f2f 0040dbab

saxserialize!DllGetClassObject+5721 013bd976 0040dbab 00000000

xerces_c_2_1_0!NamedNodeMapImpl::findNamePoint+2869a 1d6e3518 1952d8cc 0040db38

craxddrt!DLLGetDocumentation+d99a5 1952d8cc 0040db70 0146fb5c

craxddrt!DLLGetDocumentation+2e3b25 1d8679b8 0040dbbc 0040e59c

craxddrt!DLLGetDocumentation+2e466b 0040dbbc 0146fc8c 0040e59c

craxddrt!DLLGetDocumentation+2e52b1 0146fc70 766fcd35 0040e3b0

craxddrt!DLLGetDocumentation+32c055 0040e6fc 0040e3b0 3830703e

craxddrt!DLLGetDocumentation+84657 780abe57 000b0526 00000110

user32!UserCallDlgProcCheckWow+d7 191f8424 780abe57 000b0526

user32!DefDlgProcWorker+b7 00bbcb90 00000000 00000110

user32!DefDlgProcW+29 000b0526 00000110 000604f8

user32!InternalCallWinProc+23 77a53f44 000b0526 00000110

user32!UserCallWinProcCheckWow+109 191f8424 77a53f44 000b0526

user32!CallWindowProcAorW+ab 77a53f44 000b0526 00000110

user32!CallWindowProcW+1b 77a53f44 000b0526 00000110

Edited by: Don Williams on Dec 2, 2010 5:48 PM

0 Kudos

mfc80u!CWnd::DefWindowProcW+42 00000110 000604f8 00000000

mfc80u!CWnd::Default+2e 0040e3b0 780ac602 7809338d

mfc80u!CDialog::HandleInitDialog+51 000604f8 00000000 0146ffcb

mfc80u!CWnd::OnWndMsg+59d 00000110 000604f8 00000000

mfc80u!CWnd::WindowProc+22 00000110 000604f8 00000000

mfc80u!AfxCallWndProc+a3 84cc0044 000b0526 00000110

mfc80u!AfxWndProc+35 000b0526 00000110 000604f8

craxddrt!DLLGetDocumentation+4dc77b 000b0526 00000110 000604f8

user32!InternalCallWinProc+23 3875b4ed 000b0526 00000110

user32!UserCallWinProcCheckWow+109 191f8424 3875b4ed 000b0526

user32!SendMessageWorker+581 00bbcb90 00000000 3875b4ed

user32!InternalCreateDialog+b9f 40200000 00000007 0000031c

user32!CreateDialogIndirectParamAorW+33 40200000 105e7ac8 00020544

user32!CreateDialogIndirectParamW+1b 40200000 105e7ac8 00020544

mfc80u!CWnd::CreateDlgIndirect+148 00000009 1d8793cc 40200000

mfc80u!CDialog::DoModal+102 0146c354 1d7ed178 1d844c70

cslibu_3_0!CSLib300::CSDialog::DoModal+ba 0040e70c 00070348 0067b398

CRDesigner+207b5 00070348 0067b398 00000001

CRDesigner+3d6ef 0067b398 86a84d1e 0040e83c

CRDesigner+13721 1d81bcb4 029f6e48 00001108

CRDesigner+8588 00000000 00000000 00000000

Microsoft_VisualStudio_Platform_WindowManagement_ni+73306 00000000 00000000 00000000

Microsoft_VisualStudio_Platform_WindowManagement_ni+6f8f3 00000000 00000000 00000000

clr!COMToCLRDispatchHelper+28 03535560 637b66c0 0d6e0fdc

clr!BaseWrapper&ltStub *,FunctionBase&ltStub *,&DoNothing&ltStub *>,&StubRelease&ltStub>,2>,0,&CompareDefault&ltStub *>,2>::~BaseWrapper&ltStub *,FunctionBase&ltStub *,&DoNothing&ltStub *>,&StubRelease&ltStub>,2>,0,&CompareDefault&ltStub *>,2>+fa 637b66c0 0d6e0fdc 00000001

clr!COMToCLRWorkerBody+b4 00596e20 0040ecac 20cd8980

clr!COMToCLRWorkerDebuggerWrapper+34 00596e20 0040ecac 20cd8980

clr!COMToCLRWorker+1b7 00596e20 0040ecac 01e3d6cb

0x0046a1e2 80040100 00000000 00000000

msenv!CVSCommandTarget::ExecCmd+aa8 02d95f88 00001108 00000000

msenv!`anonymous namespace'::ExecForController+6b 029f6e48 00001108 00000000

msenv!CSurfaceCommandingSupport::ExecuteForController+40 0061ed60 12a1331c 00000000

msenv!CExecuteVisitor::VisitButtonController+1ba 00000000 00000000 0040ef90

msenv!CControllerVisitorBase::DispatchVisit+30 12a1331c 00000000 00000000

msenv!CControllerVisitorBase::VisitController+25 23914cf8 12a1331c 00000000

msenv!CSurfaceCommandingSupport::Execute+3c 0061ed64 12a1331c 00000000

msenv!CommandUI::Models::Impl::CExecutableCommandElementDataSource::Execute+62 12a34b3c 0040ef30 0040ef90

msenv!GenericRedispatch&ltCommandUI::Models::Impl::IExecuteVerbDispatch>+66 12a34b3c 0040ef30 0040ef90

msenv!CommandUI::Models::Impl::CExecutableCommandElementDataSource::ExecuteVerbHandler+13 12a34ac8 2877f5e4 0040ef30

msenv!Gel::CDataSource::Invoke+34 12a34ac8 2877f5e4 00000000

Microsoft_VisualStudio_Shell_10_0_ni+1e32f7 0040f00c 00000000 1c0a2ed0

Microsoft_VisualStudio_Shell_10_0_ni+1ca179 0040f00c 00000000 00000000

Microsoft_VisualStudio_Shell_UI_Internal_ni+12119d 00000000 00000000 00000000

PresentationFramework_ni+9bc08f 00000001 287767c8 00000000

PresentationFramework_ni+a8283a 287767e8 00000001 036cc820

WindowsBase_ni+afb93 00000001 287767e8 00000000

WindowsBase_ni+afac2 00000000 00000001 287767e8

WindowsBase_ni+b29b5 2877f578 67b44db5 00000000

WindowsBase_ni+b2918 0040f190 00000000 0040f190

clr!CallDescrWorker+33 0040f1e0 00000000 0040f1b0

clr!CallDescrWorkerWithHandler+8e 0040f1e0 00000000 0040f1b0

clr!MethodDesc::CallDescr+194 67ae8210 0040f418 0040f330

clr!MethodDesc::CallTargetWorker+21 67ae8210 0040f418 0040f330

clr!MethodDescCallSite::Call+1c 0040f330 01a80aeb 00596e20

clr!ExecuteCodeWithGuaranteedCleanupHelper+bb 0040f560 01a80b9f 2877f5c0

clr!ReflectionInvocation::ExecuteCodeWithGuaranteedCleanup+138 00596e20 036cfa84 036cce90

0 Kudos

mscorlib_ni+234cba 00000000 287767f4 00000000

mscorlib_ni+237f34 287767f4 00000000 00000000

WindowsBase_ni+b2848 688673f2 036cc8f8 00000000

WindowsBase_ni+ae57e 00000000 00000000 036cc874

WindowsBase_ni+ae70f 036cce68 00000000 00000000

WindowsBase_ni+afdb6 036cce68 00000000 00000000

WindowsBase_ni+afce5 036cce50 00000001 036cc820

WindowsBase_ni+afb93 00000001 036cce50 00000000

WindowsBase_ni+afac2 00000000 00000001 036cce50

WindowsBase_ni+ae050 00000001 036cce50 036cce30

WindowsBase_ni+af5e0 00020552 0000c1cf 00000000

user32!InternalCallWinProc+23 035734fa 00020552 0000c1cf

user32!UserCallWinProcCheckWow+109 00000000 035734fa 00020552

user32!DispatchMessageWorker+3bc 035734fa 00000000 0040f954

user32!DispatchMessageW+f 0040f96c 00000000 0040f990

msenv!ProcessMessage+69 00000000 02d95f28 ffffffff

msenv!CMsoCMHandler::EnvironmentMsgLoop+d8 02d95f28 012db753 09f8fe28

msenv!CMsoCMHandler::FPushMessageLoop+156 02d95f28 ffffffff 0056d1e0

msenv!SCM::FPushMessageLoop+ab ffffffff 00000000 02d95f48

msenv!SCM_MsoCompMgr::FPushMessageLoop+2a 0056d1e4 005c9428 ffffffff

msenv!CMsoComponent::PushMsgLoop+28 ffffffff 012db4b3 00000000

msenv!VStudioMainLogged+553 012db407 76c23e59 68dbdb1a

msenv!VStudioMain+bc 00000000 01382b45 001c74fc

devenv!util_CallVsMain+fd 0040fbf4 0040fe40 2fb29110

devenv!CDevEnvAppId::Run+938 004e3014 0000000a 2fb5a968

devenv!WinMain+9c 2fb10000 00000000 004e50a4

devenv!operator new[]+1e1 fffde000 0040ff28 77a29d42

kernel32!BaseThreadInitThunk+e fffde000 77e4fa47 00000000

ntdll!__RtlUserThreadStart+70 2fb2e80d fffde000 00000000

ntdll!_RtlUserThreadStart+1b 2fb2e80d fffde000 00000000

SAXSERIALIZE+398AWARNING - DebugDiag was not able to locate debug symbols for saxserialize.dll, so the information below may be incomplete.

In devenv__PID__6452__Date__12_02_2010__Time_03_30_21PM__773__Second_Chance_Exception_C0000005.dmp the assembly instruction at saxserialize+398a in C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\saxserialize.dll from SAP BusinessObjects has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 0Module Information

Image Name: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\saxserialize.dll Symbol Type: Export

Base address: 0x45cb0000 Time Stamp: Sun Oct 24 07:15:52 2010

Checksum: 0x0003bcbf Comments:

COM DLL: True Company Name: SAP BusinessObjects

ISAPIExtension: False File Description: Crystal Reports EROM XML Serializer

ISAPIFilter: False File Version: 13.0.0.99

Managed DLL: False Internal Name:

VB DLL: False Legal Copyright: Copyright 2010 SAP AG. All rights reserved.

Loaded Image Name: saxserialize.dll Legal Trademarks: Report Application Server (tm) is a trademark of Business Objects.

Mapped Image Name: Original filename:

Module name: saxserialize Private Build: 4

Single Threaded: False Product Name: SBOP Report Application Server

Module Size: 228.00 KBytes Product Version: 13.0.0.99

Symbol File Name: saxserialize.dll

Please advise on what else I should try to fix this problem.

Thanks,

Greg

0 Kudos

Hi Greg,

Sorry about that, I was side tracked and sent the post as is....

Thank you for all of the info. I'm seeing this more an more and very interesting that you can't open old reports but new ones are OK. For some renaming saxserializer worked....

The dump file is very helpful. I'm seeing a pattern here from the other posts.

More info on your old reports. What data source are they using? Do you have any Parameters in them and if are the Stored Procedures or Crystal Parameters?

What version is xerces_c_2_1_0.dll and how many do you have? Use the search in Explorer and tell all that are found and the version.

What DEV language is your app written in, VB, C#, etc.? Windows or WEB app?

The reason I ask is it belongs to Tomcat ( Java Web browser ) and CR Parameter UI uses java to render it.

Is it alright to contact you directly? We don't usually do that for forums but I am actively working with the PM and the developers to collect as much info as we can to try to figure this one out. Not everyone has this problem so there is definitely something unique about the Developers who run into this problem....

Thanks again

Don

Former Member
0 Kudos

Hi Don,

The reports are using ado.net data sources (database layout is saved as an xml schema). There are parameters for them, and they are crystal parameters. For the one I have been trying to work on, it is just a text string that is passed in and shown as the report title.

for the versions of xerces_c_2_1_0.dll, I don't seem to have any of these files on my machine.

This program is a web application written in C#.

Yes, I would be happy to help you troubleshoot this problem. Feel free to contact me directly. Do you have my e m a i l or p h o n e number from the profile I filled out, or should I send it to you somehow?

Thanks,

Greg

0 Kudos

Hi Greg,

CR should install it into:

C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86

Go into the install log file located in: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\logging CR4VS_0.log and open it and search for that file name. Do you find it what does it say?

Could be that is the problem.... Try doing a repair install.

The log should look like this, toward the end of the file:

MSI (s) (AC:A8) [13:38:35:048]: Executing op: FileCopy(SourceName=Og7tX711.12q|xerces-c_2_1_0.dll,SourceCabKey=xerces.c_2_1_0.dll.4340B137.8D53.498A.B5D6.4521D52480B7,DestName=xerces-c_2_1_0.dll,Attributes=16384,FileSize=2023424,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,Version=2.1.0.760,Language=1033,InstallMode=58982400,,,,,,,)

MSI (s) (AC:A8) [13:38:35:048]: File: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\xerces-c_2_1_0.dll; To be installed; Won't patch; No existing file

MSI (s) (AC:A8) [13:38:35:048]: Source for file 'xerces.c_2_1_0.dll.4340B137.8D53.498A.B5D6.4521D52480B7' is compressed

InstallFiles: File: xerces-c_2_1_0.dll, Directory: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\, Size: 2023424

MSI (s) (AC:A8) [13:38:35:139]: Executing op: FileCopy(SourceName=EyDhrqjo.OGD|XERCES21_LICENSE.txt,SourceCabKey=XERCES21_LICENSE.txt.4340B137.8D53.498A.B5D6.4521D52480B7,DestName=XERCES21_LICENSE.txt,Attributes=16384,FileSize=2749,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPart1=501637572,HashPart2=-1354263236,HashPart3=1638012431,HashPart4=2002058857,,)

MSI (s) (AC:A8) [13:38:35:139]: File: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\XERCES21_LICENSE.txt; To be installed; Won't patch; No existing file

MSI (s) (AC:A8) [13:38:35:139]: Source for file 'XERCES21_LICENSE.txt.4340B137.8D53.498A.B5D6.4521D52480B7' is compressed

And yes I can get to your card and your e-mail address.

Try the above, if it still doesn't exist then I'll contact you directly.

Thank you

Don

Former Member
0 Kudos

Hi Don,

Thank you for the path to the file. I don't know why the windows search that I did didn't show the xerces file you were asking about, but when I go to the directory manually, the file is there. xerces-c_2_1_0.

file version: 2.1.0.760

product version: 2.1.0

size 1.92MB

date modified: 10/24/10 6:13 am

I know that since the file is there, this probably doesn't matter, but since you asked for it, here is the information from the log file:

in the log file, there are some references to the dll file here: (line 52560)

MSI (s) (4C:B8) [11:33:55:581]: Executing op: ComponentRegister(ComponentId={BEB74ED3-AEB7-4D2E-8F17-A9A1C72C9E08},KeyPath=C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\xerces-c_2_1_0.dll,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)

1: {B2274141-F91E-4133-BF6F-B5AE6B007B1B} 2: {BEB74ED3-AEB7-4D2E-8F17-A9A1C72C9E08} 3: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\xerces-c_2_1_0.dll

MSI (s) (4C:B8) [11:33:55:582]: WIN64DUALFOLDERS: Substitution in 'C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\xerces-c_2_1_0.dll' folder had been blocked by the 1 mask argument (the folder pair's iSwapAttrib member = 0).

MSI (s) (4C:B8) [11:33:55:583]: Executing op: ComponentRegister(ComponentId={CC98681E-6452-4D59-B1A2-93BBBAB42FD3},KeyPath=C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\xerces-c_2_7.dll,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)

1: {B2274141-F91E-4133-BF6F-B5AE6B007B1B} 2: {CC98681E-6452-4D59-B1A2-93BBBAB42FD3} 3: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\xerces-c_2_7.dll

MSI (s) (4C:B8) [11:33:55:584]: WIN64DUALFOLDERS: Substitution in 'C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\xerces-c_2_7.dll' folder had been blocked by the 1 mask argument (the folder pair's iSwapAttrib member = 0).

and starting at line 73253

MSI (s) (4C:B8) [11:34:49:012]: Executing op: SetTargetFolder(Folder=C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\)

MSI (s) (4C:B8) [11:34:49:013]: Executing op: SetSourceFolder(Folder=1\ProgramF\BOBJ\CrystalR\Common\SAPBusin\win32_x8\|Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\)

MSI (s) (4C:B8) [11:34:49:013]: Executing op: FileCopy(SourceName=Og7tX711.12q|xerces-c_2_1_0.dll,SourceCabKey=xerces.c_2_1_0.dll.4340B137.8D53.498A.B5D6.4521D52480B7,DestName=xerces-c_2_1_0.dll,Attributes=16384,FileSize=2023424,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,Version=2.1.0.760,Language=1033,InstallMode=58982400,,,,,,,)

MSI (s) (4C:B8) [11:34:49:013]: File: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\xerces-c_2_1_0.dll; To be installed; Won't patch; No existing file

MSI (s) (4C:B8) [11:34:49:013]: Source for file 'xerces.c_2_1_0.dll.4340B137.8D53.498A.B5D6.4521D52480B7' is compressed

InstallFiles: File: xerces-c_2_1_0.dll, Directory: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\, Size: 2023424

I have already done an uninstall and re-install, and a repair install to no change in functionality.

Thanks,

Greg

0 Kudos

Hi Greg,

I figured it was there and it is the right version....

Can you go to: http://www.belarc.com/free_download.html

And download the tool. What this will do is produce a report on everything that is installed. DON'T post the output here. I'll contact you directly to get it.

Look aver the info also and fill in any info with "xxxxxx" that you think is sensitive.... I'll then pass the info onto the developers to see if they have any idea why this is happening.

Thanks again

Don

Former Member
0 Kudos

Hi Don,

I have some bad news... I decided that I would try to do a repair of crystal reports for vs2010, and it failed - saying that I needed elevated priviledges to perform that operation... although I am a local admin, and it gave me the windows security alert that it was going to be run as an administrator.

So, I uninstalled the product, restarted my computer, and re-installed...

and now, I can't even set the datasource location on a new report... so it has gone from bad to worse.

I have downloaded and run the belarc program, and I will send it to you as soon as I get your email. Thanks for your help with getting this resolved...

Thanks,

Greg

0 Kudos

Belarc only showed the default Administrator account was disabled, which Windows 7 does by default. Did not help to resolve this issue.

Don

Answers (0)