Error opening connection resulting in HTTP 500 - Internal server error

[Saverio Tedeschi]

Hi all gurus,
I'm getting a strange behaviour in Web services design: when I try to open a
connection, or to fill a DataSet, I get the error in subj (totally unrelated
to the actual error). I've tried SQL Server connection, SSPI integrated or
not, OledB (mdb) connection with enclosed password in the connection string,
but I get consistently the same error. I've even tried to
deinstall/reinstall Framework (1.1 SP1), IIS (5.1), S.O.(WXp SP2) HotFixes
and recovering VisualStudio 2003, with no luck. This issue is driving me
nut, pls can some1 give me a clue?

In the following code, error rises on "...Connection. Open", and then I
receive the error page, while the execution never reaches the "Return"
statement, nor the "Try" one.

Code snippet:
<WebMethod()> _

Public Function Test() As DataSet

OleDbConnection 1.Open()

Return DataSet11

Try

Catch ex As Exception

Dim errore As String = ex.ToString

errore = ""

End Try

End Function

[John Scragg]

you should always open sql connections inside a try block.

OleDbConnection conn = new OleDbConnection ()
conn.Connection String = "connection string here"
Try
conn.Open()
Catch ex As Exception
Console.WriteLi ne(ex.Message)
Finally
conn.Close()
End Try

HTH,

John Scragg

"Saverio Tedeschi" wrote:

Hi all gurus,
I'm getting a strange behaviour in Web services design: when I try to open a
connection, or to fill a DataSet, I get the error in subj (totally unrelated
to the actual error). I've tried SQL Server connection, SSPI integrated or
not, OledB (mdb) connection with enclosed password in the connection string,
but I get consistently the same error. I've even tried to
deinstall/reinstall Framework (1.1 SP1), IIS (5.1), S.O.(WXp SP2) HotFixes
and recovering VisualStudio 2003, with no luck. This issue is driving me
nut, pls can some1 give me a clue?

In the following code, error rises on "...Connection. Open", and then I
receive the error page, while the execution never reaches the "Return"
statement, nor the "Try" one.

Code snippet:
<WebMethod()> _

Public Function Test() As DataSet

OleDbConnection 1.Open()

Return DataSet11

Try

Catch ex As Exception

Dim errore As String = ex.ToString

errore = ""

End Try

End Function

[Saverio Tedeschi]

Thank you, John, 4 your reply.
However, even if what you say is surely true, the "Try" block should catch
exception, and it does not. Why?
Furthermore, this is only a simple sample, 'cause I always get this error,
and my real app is quitly more complicated than the snippet I've posted. Now
I'm trying to de-install and reinstall VS2003, and all related components,
even if I've already performe a "refresh" of the previous install. ?????

"John Scragg" <Jo********@dis cussions.micros oft.com> ha scritto nel
messaggio news:12******** *************** ***********@mic rosoft.com...

you should always open sql connections inside a try block.

OleDbConnection conn = new OleDbConnection ()
conn.Connection String = "connection string here"
Try
conn.Open()
Catch ex As Exception
Console.WriteLi ne(ex.Message)
Finally
conn.Close()
End Try

HTH,

John Scragg

"Saverio Tedeschi" wrote:

Hi all gurus,
I'm getting a strange behaviour in Web services design: when I try to
open a
connection, or to fill a DataSet, I get the error in subj (totally
unrelated
to the actual error). I've tried SQL Server connection, SSPI integrated
or
not, OledB (mdb) connection with enclosed password in the connection
string,
but I get consistently the same error. I've even tried to
deinstall/reinstall Framework (1.1 SP1), IIS (5.1), S.O.(WXp SP2)
HotFixes
and recovering VisualStudio 2003, with no luck. This issue is driving me
nut, pls can some1 give me a clue?

In the following code, error rises on "...Connection. Open", and then I
receive the error page, while the execution never reaches the "Return"
statement, nor the "Try" one.

Code snippet:
<WebMethod()> _

Public Function Test() As DataSet

OleDbConnection 1.Open()

Return DataSet11

Try

Catch ex As Exception

Dim errore As String = ex.ToString

errore = ""

End Try

End Function

[John Scragg]

The Try block will only catch exceptions thrown within the bock. you are
calling .Open() on your connection outside of the try block.

I think you are barking up the wrong tree by trying to reinstall all you
apps, OS and database. You are more likely to introduce a new bug then you
are to solve this one.

Put you .Open() inside the try block, put a break point on the code in your
catch block and see what you get. I am sure that if you are getting an error
thrown by .Open() you will catch it there.

John

"Saverio Tedeschi" wrote:

Thank you, John, 4 your reply.
However, even if what you say is surely true, the "Try" block should catch
exception, and it does not. Why?
Furthermore, this is only a simple sample, 'cause I always get this error,
and my real app is quitly more complicated than the snippet I've posted. Now
I'm trying to de-install and reinstall VS2003, and all related components,
even if I've already performe a "refresh" of the previous install. ?????

"John Scragg" <Jo********@dis cussions.micros oft.com> ha scritto nel
messaggio news:12******** *************** ***********@mic rosoft.com...

you should always open sql connections inside a try block.

OleDbConnection conn = new OleDbConnection ()
conn.Connection String = "connection string here"
Try
conn.Open()
Catch ex As Exception
Console.WriteLi ne(ex.Message)
Finally
conn.Close()
End Try

HTH,

John Scragg

"Saverio Tedeschi" wrote:

Hi all gurus,
I'm getting a strange behaviour in Web services design: when I try to
open a
connection, or to fill a DataSet, I get the error in subj (totally
unrelated
to the actual error). I've tried SQL Server connection, SSPI integrated
or
not, OledB (mdb) connection with enclosed password in the connection
string,
but I get consistently the same error. I've even tried to
deinstall/reinstall Framework (1.1 SP1), IIS (5.1), S.O.(WXp SP2)
HotFixes
and recovering VisualStudio 2003, with no luck. This issue is driving me
nut, pls can some1 give me a clue?

In the following code, error rises on "...Connection. Open", and then I
receive the error page, while the execution never reaches the "Return"
statement, nor the "Try" one.

Code snippet:
<WebMethod()> _

Public Function Test() As DataSet

OleDbConnection 1.Open()

Return DataSet11

Try

Catch ex As Exception

Dim errore As String = ex.ToString

errore = ""

End Try

End Function

[Saverio Tedeschi]

Lot of thanks, John.
Actually, there's an authorization issue with default user. For some reason,
the authorizations used till 10 days ago are no more valid and now I'm
trying a new schema.

"John Scragg" <Jo********@dis cussions.micros oft.com> ha scritto nel
messaggio news:6F******** *************** ***********@mic rosoft.com...

The Try block will only catch exceptions thrown within the bock. you are
calling .Open() on your connection outside of the try block.

I think you are barking up the wrong tree by trying to reinstall all you
apps, OS and database. You are more likely to introduce a new bug then
you
are to solve this one.

Put you .Open() inside the try block, put a break point on the code in
your
catch block and see what you get. I am sure that if you are getting an
error
thrown by .Open() you will catch it there.

John

"Saverio Tedeschi" wrote:

Thank you, John, 4 your reply.
However, even if what you say is surely true, the "Try" block should
catch
exception, and it does not. Why?
Furthermore, this is only a simple sample, 'cause I always get this
error,
and my real app is quitly more complicated than the snippet I've posted.
Now
I'm trying to de-install and reinstall VS2003, and all related
components,
even if I've already performe a "refresh" of the previous install. ?????

"John Scragg" <Jo********@dis cussions.micros oft.com> ha scritto nel
messaggio news:12******** *************** ***********@mic rosoft.com...

> you should always open sql connections inside a try block.
>
> OleDbConnection conn = new OleDbConnection ()
> conn.Connection String = "connection string here"
> Try
> conn.Open()
> Catch ex As Exception
> Console.WriteLi ne(ex.Message)
> Finally
> conn.Close()
> End Try
>
> HTH,
>
> John Scragg
>
> "Saverio Tedeschi" wrote:
>
>> Hi all gurus,
>> I'm getting a strange behaviour in Web services design: when I try to
>> open a
>> connection, or to fill a DataSet, I get the error in subj (totally
>> unrelated
>> to the actual error). I've tried SQL Server connection, SSPI
>> integrated
>> or
>> not, OledB (mdb) connection with enclosed password in the connection
>> string,
>> but I get consistently the same error. I've even tried to
>> deinstall/reinstall Framework (1.1 SP1), IIS (5.1), S.O.(WXp SP2)
>> HotFixes
>> and recovering VisualStudio 2003, with no luck. This issue is driving
>> me
>> nut, pls can some1 give me a clue?
>>
>> In the following code, error rises on "...Connection. Open", and then I
>> receive the error page, while the execution never reaches the "Return"
>> statement, nor the "Try" one.
>>
>> Code snippet:
>> <WebMethod()> _
>>
>> Public Function Test() As DataSet
>>
>> OleDbConnection 1.Open()
>>
>> Return DataSet11
>>
>> Try
>>
>> Catch ex As Exception
>>
>> Dim errore As String = ex.ToString
>>
>> errore = ""
>>
>> End Try
>>
>> End Function
>>
>>
>>