I have an old web service that is located on a Windows 2003 server and we are getting ready to upgrade the box to Windows 2012. When I regenerate the vb file using the latest wsdl.exe, the new file that is generated does not compile and play well with others, I get hundreds of syntax errors on all "Partial" Classes, I compare the file to the old vb file that was being used and I don't even know if the new one has all the same attributes being called from my legacy program. This program was created originally 10 years ago and if they used an .xsd schema file when generating the final file, I have no idea. Has anyone ran into this issue before? How can I do some forensic work when I don't have any idea how the original vb file got generated? FYI the vb.net program that uses the web service uses it to build menu items based on Reports available and is based on the SSRS ReportServer.
Server Error in '/XXX.Edv.Web' Application.
Object reference not set to an instance of an object. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
Line 288: Dim oItemsManagement() As CatalogItem = Application.Item("MANAGEMENTREPORTS")
Line 289:
Line 290: If oItemsManagement.Length > 0 Then
Line 291: Dim oManagementItem As MenuItem = New MenuItem
Line 292: oManagementItem = New MenuItem