Re: establishing cause of access violation?
From: Dan Guzman (guzmanda_at_nospam-online.sbcglobal.net)
Date: 10/18/04
- Next message: Aaron [SQL Server MVP]: "Re: Issue with Last()"
- Previous message: mklapp: "RE: Linked Servers"
- In reply to: Bonj: "Re: establishing cause of access violation?"
- Next in thread: Bonj: "Re: establishing cause of access violation?"
- Reply: Bonj: "Re: establishing cause of access violation?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 18 Oct 2004 08:54:36 -0500
You might try a Knowledge base search for article 322884. I am not
suggesting that you use SQL 2005 since it is currently in beta and has not
yet been released. I am suggest you use an alternate method (e.g. unmanaged
code) if you need to implement this under SQL 2000.
Below is the relevant info from the article.
.
<Excerpt>
Microsoft does not support the use of Microsoft Common Language Runtime
(included with .NET Framework) for any COM Callable Wrapper or Managed
Extensions for C++ in either Microsoft SQL Server 7.0 or Microsoft SQL
Server 2000. This limitation for support pertains directly to the use of
extended stored procedures and the use of OLE Automation for any loading of
the libraries that you must load to run in the SQL Server memory space.
</Excerpt>
-- Hope this helps. Dan Guzman SQL Server MVP "Bonj" <Bonj@discussions.microsoft.com> wrote in message news:63E2865A-EF29-4723-87E4-D5D5DA839A5A@microsoft.com... >I get KB article is not available. > FYI, I haven't got SQL server 2005, so please don't suggest solutions > involving that. > > > "Dan Guzman" wrote: > >> See http://support.microsoft.com/default.aspx?scid=kb;en-us;322884. CLR >> integration will be included in SQL Server 2005. >> >> -- >> Hope this helps. >> >> Dan Guzman >> SQL Server MVP >> >> "Bonj" <Bonj@discussions.microsoft.com> wrote in message >> news:EEC5B90F-49A7-4096-9D28-47DEAC73416A@microsoft.com... >> > Hi >> > I have a mixed managed/unmanaged project which thanks to you guys I've >> > managed to get rid of the linker errors of, so cheers for that. >> > But now I'm experiencing an unknown access violation. >> > Firstly this is an extended stored procedure DLL, I've been able to >> > debug >> > it >> > successfully by starting SQL server with the -c switch and when it is >> > called >> > via osql then it breaks into the debugger. Fine. I'm happy with >> > that.... >> > However the project also has a .cpp file that is compiled with /clr. >> > This >> > contains one managed function, which instantiates a C# class in a >> > separate >> > assembly. The accessor function is called by the main (unmanaged) .cpp >> > file >> > that is the entry point of the extended stored procedure. When I press >> > F11 >> > or >> > F10 on the accessor function, I get 'SQL server generated an access >> > violation, and is terminating process 51'. >> > This function used to be OK. I've got the debugger set to 'mixed', but >> > it >> > won't step into the managed function. >> > Any idea how I can trace what's actually going on? >> > >> > >> > >> >> >>
- Next message: Aaron [SQL Server MVP]: "Re: Issue with Last()"
- Previous message: mklapp: "RE: Linked Servers"
- In reply to: Bonj: "Re: establishing cause of access violation?"
- Next in thread: Bonj: "Re: establishing cause of access violation?"
- Reply: Bonj: "Re: establishing cause of access violation?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
