Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesWeb Reference IssueWeb Reference Issue
Previous
 
Next
New Post
7/27/2015 10:32 AM
 

I've been building a module that uses Web References (not to be confused with a Service Reference) to utilize a 3rd party API. In DNN 7.3.2, this web reference works fine. I upgraded the site successfully to 7.4.1 and this same web reference is now broken. Does anyone know if there are breaking changes that disable use of Web References? When adding a Web Reference, VS notifies you that it generates code based on .NET Framework 2.0 Web Services technology. 

 

Here's the error I get when the Web Reference is called in 7.4.1:

AbsoluteURL:/Default.aspx

 

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

 

ExceptionGUID:412663ba-6428-47d7-9930-f469bb272293

 

AssemblyVersion:7.4.1

 

PortalId:1

 

UserId:-1

 

TabId:652

 

RawUrl:/Default.aspx?tabid=652&error=An%20unexpected%20error%20has%20occurred&content=0

 

Referrer:

 

UserAgent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.134 Safari/537.36

 

ExceptionHash:1wB6JQgJmRFOLBLlxlfnyg==

 

Message:Server was unable to process request. ---> The system was unable to successfully retrieve the DataTable. [Incorrect syntax near 'length'.] ---> Incorrect syntax near 'length'.

 

StackTrace:

 

InnerMessage:Server was unable to process request. ---> The system was unable to successfully retrieve the DataTable. [Incorrect syntax near 'length'.] ---> Incorrect syntax near 'length'.

 

InnerStackTrace:

 

   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

   at SSO. ThirdPartyApiName. ThirdPartyApiName.GetInfo(String APICode, String EnPID) in C:\Code\ClientName\SSO\SSO\Web References\ThirdPartyApiName\Reference.cs:line 83

   at SSO.SkinObject.Page_Load(Object sender, EventArgs e) in C:\Code\ClientName\SSO\SSO\SkinObject.ascx.cs:line 80

   at System.Web.UI.Control.LoadRecursive()

   at System.Web.UI.Control.LoadRecursive()

   at System.Web.UI.Control.LoadRecursive()

   at System.Web.UI.Control.LoadRecursive()

   at System.Web.UI.Control.LoadRecursive()

   at System.Web.UI.Control.LoadRecursive()

   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

 

 

 

Any thoughts? I've looked through issues in the issue tracker and release notes and haven't been able to find anything that would point to a solution or cause.

 
New Post
7/31/2015 10:22 AM
 
Should this be logged as a bug? Seems like this could be a big issue if there are breaking changes between these versions of DNN.
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesWeb Reference IssueWeb Reference Issue


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out