What's hot ? (and I mean really ...) - scroll down for more
1).  Code Templating - advanced usage of delegates & generics: my slides & demos are available for download! CodeProject article is also available.

2).  My series "TDD in the eyes of a simpleminded" is in progress(including code!): preface, part1, part2, Q&A 1, Manual Stub .vs. Mock Stub

3).  TDD Workshop: SeeCompass v0.1 and v0.2 are out.
# Tuesday, May 02, 2006
# Invalid access to memory location. (Exception from HRESULT: 0x800703E6) in Microsoft.SqlServer.Replication

My team use the Sql Server 2005 Replication feature in order to synchronize between databases in different enviornments. One of the strange things though, is that the reference to Microsoft.SqlServer.Replication generated a weird "Invalid access to memory location. (Exception from HRESULT: 0x800703E6)" Error. After a quick google search I found this link which offers a nice workaround (this seems to be VS.NET 2005 bug) which worked for several folks out there but unfortunately it didn't work for me. The search continues...

.NET | SqlServer 2005
Posted by Oren Ellenbogen 
02/05/2006 09:32, Israel time UTC+03:00,     Comments [4]  |  Related posts:
Microsoft CCR: clean way to write parallel code in .Net
Making WCF Proxy useable
Bring lock back until 12, it has a busy day tomorrow
How to set a free TDD-enabled environment
How to mock static class or static member for testing
Writing Thread Safety tests for instance data
Sunday, May 07, 2006 11:34:26 PM (Jerusalem Standard Time, UTC+02:00)
hi oren.
this problem occurs when MSXML registration became corrupted

The following commands should fix this problem:

regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll


hope that it will help.
good luck.
Shimon Krokhmal
Friday, October 20, 2006 11:34:48 PM (Jerusalem Standard Time, UTC+02:00)
I was having the same issue and it was driving me insane. I tried following the above recommendations and any others I found with no results. It turns out I had an instance of both SqlServer and SqlExpress running. On a hunch, I stopped SqlExpress and the problem went away. Possible because SqlExpress does not support replication and therefore cause Visual Studio to throw the error. Anyway, it worked for me. So the next person who gets this error can try this as well as all the other recommendations.

Michael Pastore
Sunday, October 22, 2006 12:36:57 AM (Jerusalem Standard Time, UTC+02:00)
Michael & Shimon - thanks for sharing!
I hope it will help someone else as well.
Oren Ellenbogen
Monday, February 12, 2007 7:09:35 PM (Jerusalem Standard Time, UTC+02:00)
FYI: The re-registering of the DLLs also fixed that problem for my developer who was using Strataframe.Net to build a web application with a SQLEXPRESS back-end.

Thanks for the insight Shimon.

Jason
Jason Stevenson
Comments are closed.