Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
RyanW
Starting Member
1 Post |
 Posted - 2006-07-03 : 14:49:47
|
| Does anyone know if there are any issues with .Net Framework 2.0 and SQL Server 2005?Here is my problem .....I have a web application running on a Windows 2003 Server SE with IIS 6.0. We recently migrated all of our databases to SQL Server 2005 and now we are getting an exception when retrieving data from the DB (Exception Below). We have switched our databases back to Sql Server 2000 and the problem does not occur. What is odd is that we have set up the same application on a diferent machine running Windows 2003 Server Web Edition with IIS 6.0 and it works fine. I have checked the versions of the framework and they are identical. The only difference between the two apps is that we are running SSL and connecting to the database through a VPN tunnel on the app that throws the exception. Any Help would be much appreciated.-RyanEvent Type: ErrorEvent Source: .NET Runtime 2.0 Error ReportingEvent Category: NoneEvent ID: 5000Date: 7/3/2006Time: 10:15:46 AMUser: N/AComputer: WEBSERVER12Description:EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 system.data, P5 2.0.0.0, P6 4333aea2, P7 1946, P8 25, P9 system.invalidoperationexception, P10 NIL.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 63 00 6c 00 72 00 32 00 c.l.r.2.0008: 30 00 72 00 33 00 2c 00 0.r.3.,.0010: 20 00 77 00 33 00 77 00 .w.3.w.0018: 70 00 2e 00 65 00 78 00 p...e.x.0020: 65 00 2c 00 20 00 36 00 e.,. .6.0028: 2e 00 30 00 2e 00 33 00 ..0...3.0030: 37 00 39 00 30 00 2e 00 7.9.0...0038: 31 00 38 00 33 00 30 00 1.8.3.0.0040: 2c 00 20 00 34 00 32 00 ,. .4.2.0048: 34 00 33 00 35 00 62 00 4.3.5.b.0050: 65 00 31 00 2c 00 20 00 e.1.,. .0058: 73 00 79 00 73 00 74 00 s.y.s.t.0060: 65 00 6d 00 2e 00 64 00 e.m...d.0068: 61 00 74 00 61 00 2c 00 a.t.a.,.0070: 20 00 32 00 2e 00 30 00 .2...0.0078: 2e 00 30 00 2e 00 30 00 ..0...0.0080: 2c 00 20 00 34 00 33 00 ,. .4.3.0088: 33 00 33 00 61 00 65 00 3.3.a.e.0090: 61 00 32 00 2c 00 20 00 a.2.,. .0098: 31 00 39 00 34 00 36 00 1.9.4.6.00a0: 2c 00 20 00 32 00 35 00 ,. .2.5.00a8: 2c 00 20 00 73 00 79 00 ,. .s.y.00b0: 73 00 74 00 65 00 6d 00 s.t.e.m.00b8: 2e 00 69 00 6e 00 76 00 ..i.n.v.00c0: 61 00 6c 00 69 00 64 00 a.l.i.d.00c8: 6f 00 70 00 65 00 72 00 o.p.e.r.00d0: 61 00 74 00 69 00 6f 00 a.t.i.o.00d8: 6e 00 65 00 78 00 63 00 n.e.x.c.00e0: 65 00 70 00 74 00 69 00 e.p.t.i.00e8: 6f 00 6e 00 20 00 4e 00 o.n. .N.00f0: 49 00 4c 00 0d 00 0a 00 I.L..... |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-07-03 : 15:03:41
|
| The exception that you have posted does not show any SQL Server errors. You might have better luck if you post on a forum that supports .NET framework 2.0. For a SQL Server site, we would need to see the SQL Server error. If the exception is occurring in SQL Server, then you'd see it in SQL Profiler. Have you run that tool to check for exceptions?Have you been able to figure out what line of code is causing this exception, perhaps by stepping through the code?Tara Kizeraka tduggan |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
|
|
|
|
|
|
|
Sql Server 2005 .NET Framework 2.0