|
|
You're in the
dotnet remoting
group:Cannot find member name System.Data.SqlClient.SqlError
dotnet remoting:
All,
I can't seem to figure this one out: I have a Data Access Layer (DAL) service running on a Windows 2003 Server. Through remoting, I can connect to this service from my Windows XP Pro workstation. This all works great. However, when my DAL service causes a SQL exception, I need the exception to be remoted back to the client. I get the exception of "Cannot find member name System.Data.SqlClient.SqlError" rather than the actual sql exception. If I run the same service on my Windows XP Pro workstation along with the client application, it works fine - giving me the sql exception. I can also run the client application from the Windows 2003 server and hit the DAL running on the workstation and it also correctly gives me the sql exception. So the problem appears to be remoting the SQL exception from the Windows 2003 Server to the Windows XP Pro workstation. Both machines have the 1.1 framework, but the Windows 2003 Server's System.Data.dll file is dated 3/24/2005 whereas the same file on the Windows XP workstation is dated 7/15/2004. I'm kind of at a loss as to what to look for. Any suggestions? Thanks in advance! Dave Wurtz
I'm having the exact same problem, and it all started after installing SP1 of
Windows 2003 Server. Version number of all system.*-files under microsoft.net\framework\v1.1.4322: Server (2003 SP1) is 1.1.4322.2300 Client (Windows XP SP2) is 1.1.4322.2032. This must be kinda easy to reproduce for Microsoft.... [quoted text, click to view] "dave_wurtz@asdsoftware.com" wrote:
> All, > > I can't seem to figure this one out: > > I have a Data Access Layer (DAL) service running on a Windows 2003 > Server. Through remoting, I can connect to this service from my > Windows XP Pro workstation. This all works great. > > However, when my DAL service causes a SQL exception, I need the > exception to be remoted back to the client. I get the exception of > "Cannot find member name System.Data.SqlClient.SqlError" rather than > the actual sql exception. > > If I run the same service on my Windows XP Pro workstation along with > the client application, it works fine - giving me the sql exception. I > can also run the client application from the Windows 2003 server and > hit the DAL running on the workstation and it also correctly gives me > the sql exception. > > So the problem appears to be remoting the SQL exception from the > Windows 2003 Server to the Windows XP Pro workstation. > > Both machines have the 1.1 framework, but the Windows 2003 Server's > System.Data.dll file is dated 3/24/2005 whereas the same file on the > Windows XP workstation is dated 7/15/2004. > > I'm kind of at a loss as to what to look for. Any suggestions? > > Thanks in advance! > > Dave Wurtz >
T,
Thanks, I have also confirmed this in our environment. If I try this on a Windows 2003 server WITHOUT SP1, it works fine. Hopefully, Microsoft will fix this. Dave
Microsoft, are you out there? I'm not really sure how to report this
as a bug?
FYI - as a temporary workaround I have written a new sub that strips out the
original message from the exception and throws a new exception with only the Msg. So try calling a function like this where u would normally throw your exceptio (sorry about the bad formatting) : Public Sub ThrowBaseException(ByVal ex As Exception) Dim oBaseException As Exception = ex.GetBaseException Dim sMsg As String If Not IsNothing(oBaseException) Then If TypeOf oBaseException Is System.Data.SqlClient.SqlException Then Dim n As Integer For n = 0 To CType(oBaseException, SqlClient.SqlException).Errors.Count - 1 Select Case CType(oBaseException, SqlClient.SqlException).Errors.Item(n).Number Case 266 Case Else sMsg += CType(oBaseException, SqlClient.SqlException).Errors.Item(n).Message + vbCrLf End Select Next Else sMsg = oBaseException.Message End If Else sMsg = ex.Message End If Throw New Exception(sMsg) End Sub [quoted text, click to view] "dave_wurtz@asdsoftware.com" wrote:
> Microsoft, are you out there? I'm not really sure how to report this > as a bug? >
I use this little code to throw the original message as a workaround until I
find a permanent solution to the problem (sorry about the formatting). The client will get the proper message now, but not the tracestack...: Public Sub ThrowBaseException(ByVal ex As Exception) Dim oBaseException As Exception = ex.GetBaseException Dim sMsg As String If Not IsNothing(oBaseException) Then If TypeOf oBaseException Is System.Data.SqlClient.SqlException Then Dim n As Integer For n = 0 To CType(oBaseException, SqlClient.SqlException).Errors.Count - 1 Select Case CType(oBaseException, SqlClient.SqlException).Errors.Item(n).Number Case 266 Case Else sMsg += CType(oBaseException, SqlClient.SqlException).Errors.Item(n).Message + vbCrLf End Select Next Else sMsg = oBaseException.Message End If Else sMsg = ex.Message End If Throw New Exception(sMsg) End Sub [quoted text, click to view] "dave_wurtz@asdsoftware.com" wrote:
> Microsoft, are you out there? I'm not really sure how to report this > as a bug? >
Thx for the link, but it has absolutely nothing at all to do with our problem.
Our remoting configuration was working splendidly until we installed SP1 of Windows Server 2003 or our remoting server machine. To me it seems like MS has mucked around with the interface for SQLError, and it makes the client unable to receive errors including SQLError.... /Tommy [quoted text, click to view]
See my post on
Thx a lot. Getting the hotfix (article 887549) solved the problem!
[quoted text, click to view] "Ramon de Klein" wrote:
> See my post on
What exactly did you apply and to what. The hotfix 887549 is a hotfix for
Windows 2003 is it not? [quoted text, click to view] "Tommy" wrote:
> Thx a lot. Getting the hotfix (article 887549) solved the problem! > > > > "Ramon de Klein" wrote: > > > See my post on
What exactly did you apply and to what. The hotfix 887549 is a hotfix for
Windows 2003 is it not? [quoted text, click to view] "Ramon de Klein" wrote:
> See my post on
Which system did you apply the fix to? When I apply it to the server I get
the message: Setup has detected that the Service Pack version of this system is newer than the update you are applying. There is no need to install this update. When I try to apply it to my XP machine I get the message:The version of Windows you have installed does not match the update you are trying to install. The dates of my System.data.dll files matched those in the original post. Thanks,
I didn't apply the fix to either system, though the hotfix is, I believe,
for Server 2003. Since the KB article didn't actually mention the problem I'm having, I was reluctant to apply it. [quoted text, click to view] "Kathleen Braun" <kbraun@xxx.com> wrote in message news:93569df81b8f499aa3ac10e0c189b709@ureader.com... > Which system did you apply the fix to? When I apply it to the server I > get > the message: Setup has detected that the Service Pack version of this > system > is newer than the update you are applying. > > There is no need to install this update. > > When I try to apply it to my XP machine I get the message:The version of > Windows you have installed does not match the update you are trying to > install. > > The dates of my System.data.dll files matched those in the original post. > > Thanks, > Kathleen
Hi, I too am experiencing the same problem as Kathleen. It seems I can't install the hotfix that apparently fixes the problem. Does anyone have a solution to this problem? Thanks. Gary.
This post does not exist, Ramon! Please update or reply with some new info, I'm desperate to resolve this problem. [quoted text, click to view] "Ramon de Klein" wrote:
> See my post on
I'm not able to find the hot fix also...
Hi,
Im facing the similar problem in one of our Project. Not able to find that HOTFIX on specified link. I hope there is some other solution except change
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |