Crystal Reports Problem

The following error loaded today when trying to output a crystal report from asp.Net:

Logon failed. Details: crdb_adoplus : Object reference not set to an instance of an object. Error in Filename.rpt: Unable to connect: incorrect log on parameters.

The problem was that I didn’t set the report’s DataSource. Next is the code that worked:

ReportDocument report = new ReportDocument();

report.Load(Server.MapPath(“Reports\Label.rpt”));

report.SetDataSource(dset);

report.ExportToDisk(ExportFormatType.PortableDocFormat, full_path);

report.Clone();

report.Dispose();

Hope this helps someone!!

ContextSwitchDeadlock was detected

Last week i was debugging an application and after while the following exception was being loaded:

ContextSwitchDeadlock was detected
Message: The CLR has been unable to transition from COM context 0x1b2938 to
COM context 0x1b2aa8 for 60 seconds. The thread that owns the destination
context/apartment is most likely either doing a non pumping wait or
processing a very long running operation without pumping Windows messages.
This situation generally has a negative performance impact and may even lead
to the application becoming non responsive or memory usage accumulating
continually over time. To avoid this problem, all single threaded apartment
(STA) threads should use pumping wait primitives (such as
CoWaitForMultipleHandles) and routinely pump messages during long running
operations.

After googling, i found that this error happens when an operation is performing lenghty operations not allowing the message queue to pump. Continue reading »

Visual Studio 2005 – Crashes Randomly

 

Last week i was using Visual Studio 2005 and all of a sudden it started to crash. Everytime i tried to open VS after 1 or 2 minutes it would crash. I checked the event log and the following error appeared:

Faulting application devenv.exe, version 8.0.50727.762, time stamp 0×45716759, faulting module craxddrt.dll_unloaded, version 0.0.0.0,
time stamp 0×43068582, exception code 0xc0000005, fault offset 0x0d26e30f, process id 0×1180, application start time 0x01c75cae13960a41.

After googling the problem, i found the following solution. The problem was that when opening my solution, by default it opened the last crystal report that i was working on. This seemed to start some crystal report ActiveX thing that didn’t work on Vista.

Sometimes it would take 2 minutes and sometimes 5 minutes, but it would always crash, even if i closed the report straight away.  The only way to stop this problem was to load up VS, close the report immediately and safely close VS before it got a chance to crash! The next time it opens, there is no crystal report and the ActiveX control never loads.

So the next time you save the solution and close visual studio be sure to close all Crystal Reports window

Happy Programming.

Reference: http://tim.mackey.ie/FIXVS2005CrashesRandomlyWhenUsingCrystalReports.aspx

Total Number of Lines of Code (VS Add-Ins)

Ever wonder how many lines of code did you write in your application/solution in visual studio 2005. Well now you can, or at least now i found how. Here’s a Visual Studio 2005 Add-In that not only shows you the total lines of code within your solution/project but also shows the breakout of each individual file. It also has an assortment of useful utilities to help programmers monitor, explore, and inspect the contents of their code.

Click here to get your free collection of free utilities for the Microsoft® Visual Studio® 2005 development environment.

Update: While searching for visual studio add-ins, i also found the Ten Essential Visual Studio Add-ins that every developer should download Now. Click here to see what it’s all about or here for other (not so essential) visual studio add-ins.