.NET Error CLR20r3

Bear in mind that I'm a developer with a VB.NET development environment (Visual Studio) loaded onto my PC.

I had previously created an "Invoice Import" program using .NET, and because I was having problems with "Click-Once" deployment, I decided (in frustration) to simply put the .EXE file on the server and get my customer to execute it from there. She got the dreaded CLR20r3 error:
 
 

I didn't get this error at first - the program ran just fine - which was confusing to say the least. I guessed that it was because I had VS installed. Wrong. I re-booted my PC and lo-and-behold, I got the error too.

I Googled for this error for ages and there was no definitive answer. A lot of entries pointed to "missing file or DLL". But which one?

The answer was remarkably simple in my case. I simply chose "Debug the program" and selected "my" VS version (2005):


The next box to appear is the "real" error:


"DataAccessLibrary" is the class library used to access the database and is built as a DLL by VS. I simply located the DLL using Windows Explorer in the bowels of the solution and copied it to the same directory as the .EXE.

 

 I did the same for "BusinessObjectLibrary":

 

 Note: This almost certainly is not the way to issue programs... I have yet to find out why Click-Once insists on installing (at least) 5 versions earlier of the program, even though I uninstalled everything on the the PC and deleted everything off the server. But, it got the Finance Director of our backs...

Comments

Post a Comment

Popular posts from this blog

"The delivery extension for this subscription could not be loaded" when using SSRS

Image
OK, so we upgraded our server farm and put on the latest "stuff" (SSRS, SQL Server etc.) and the engineers gave me two servers to play with - SQL01 & SQL02. The idea being that we used high availability to help keep the factory running. We employed a contractor to load up and configure everything. At this point I wasn't involved. My involvement was to move all the reports and subscriptions from the old servers to the new ones once the servers had been configured. All went swimmingly, until I actually started to fire off the subscriptions to test them. Randomly (like 5 out of 10) I got the error in the title. I would edit the failing subscription and/or change the schedule time and it would work. I finally got around to moving 81 subscriptions for the same report (all slightly different parameters going to about 6 different engineers). I press the "go" button and every single one failed. Let's cut out the long story about how I went through about
Read more

Oooh, look, an Eagle...

Image
The Scottish Holiday . After the trauma of the Astra-breakdown episode and the gutless hirecar, we'd recovered sufficiently to begin to enjoy the rest of our holiday with our friends at the Castle... Chapter Seven: One of the things my wife really wanted to see was a seal, or seals if she was really lucky. So we decided to take a day out and around the Mull Of Kintyre. We stopped at "St Columba's Footprints" and carefully studied the jumbled collection of rocks and seaweed. "No seals there dear, let's carry on" "Oh, alright then, never mind. But that's where we were told they are most likely to be." We drove on and took a gated road signposted " To The Lighthouse ". This took us right up into the hills. As we were driving slowly along admiring the view, my wife whispered quietly... " Ooh, look an Eagle! " "Stop that, that's not funny." "No, really. Stop the car."
Read more

SQL Server 2008 / Reporting Services

Image
Since this has taken me four days to solve this one and, with almost no help from Google, I thought I'd log it here in case anyone else has this most bizarre problem. Scenario: You retrospectively install Reporting Services to an existing installation of SQL Server 2008. You try to configure it using "Reporting Services Configuration Manager" and as soon as you click "Find" you get "Invalid Class" 1 and no other information. These two links gave me the clue, they're essentially both the same. What they say is to run WBEMTEST 3 and connect to the Reporting Services WMI thingy. Then run the query, " SELECT * FROM __NAMESPACE ". When I did this I got: Note: TWO entries. The second one was a test database I had installed months ago and had removed at some point when I worked out that using the default instance of MSSQLSERVER was more convenient - but the registry(?) entries were still hanging around. I selected it by clicking o
Read more