Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
XML, Serialization, Custom Class - Help Please
Message
 
To
23/02/2003 03:13:35
Keith Payne
Technical Marketing Solutions
Florida, United States
General information
Forum:
ASP.NET
Category:
Web Services
Miscellaneous
Thread ID:
00756699
Message ID:
00756704
Views:
10
The first thing to do is try and fix IIS mappings for ASP.NET. Please refer to the instructions in the following link:

http://support.microsoft.com/default.aspx?scid=KB;en-us;q306005


>Reply to this message please. Refer to the root post for the full code listing.
>
>>NOTE: Full code listing at the end of this message (there is lots of code).
>>
>>I am getting a HTTP 500 error when I Invoke the following Web Method:
>>
>>    <WebMethod(Description:="Inserts a new lead into the Lead table")> _
>>        Public Function InsertLead( _
>>            ByVal LeadTypeID As Integer, _
>>            ByVal PromotionID As Integer, _
>>            ByVal SourceID As Integer, _
>>            ByVal Name As String, _
>>            ByVal Address As String, _
>>            ByVal City As String, _
>>            ByVal State As String, _
>>            ByVal PostalCode As String, _
>>            ByVal Country As String, _
>>            ByVal Phone As String, _
>>            ByVal Fax As String, _
>>            ByVal Phone2 As String, _
>>            ByVal Email As String, _
>>            ByVal LeadData As String) As DataOperationResult
>>.
>>.
>>.
>>
>>    End Function
>>
>>
>>It doesn't go beyond the Function declaration.
>>
>>DataOperationResult (DOR) is a class I created to pass back general information about the success or failure of the Insert. DOR has some public properties and two collections of custom classes. DOR has a default constructor and so do the class definitions for the collection types. The collections have default accessors too.
>>
>>I went through all of the iterations to get the service to compile - I didn't know anything about serialization when I started. The problem is that I don't know how to proceed troubleshooting this now that I get the lovely HTTP 500 error.
>>
>>I suspect the problem has something to do with .NET choking on the serialization at run-time. Any ideas would be helpful.
>>
-----------------------------------------

Cathi Gero, CPA
Prenia Software & Consulting Services
Microsoft C# / .NET MVP
Mere Mortals for .NET MVP
cgero@prenia.com
www.prenia.com
Weblog: blogs.prenia.com/cathi
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform