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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Consuming ASP.NET web services in a PHP pageConsuming ASP.NET web services in a PHP page
Previous
 
Next
New Post
7/16/2009 12:17 PM
 

I'm using PHP and the NUSOAP client to access a .net webservice.

I'm getting the following error when accessing my service from PHP via NuSoap, but not if I use ASP.NET, via a compiled site on same server or a different machine and visual studio.

Any idea why?

Below are the last 12 lines of the nusoap debug call.

10:48:20.417138 nusoap_client: got response, length=423 type=text/xml; charset=utf-8
10:48:20.417346 nusoap_client: Entering parseResponse() for data of length 423 headers: array(10) { ["connection"]=> string(5) "close" ["date"]=> string(29) "Wed, 15 Jul 2009 09:48:20 GMT" ["server"]=> string(17) "Microsoft-IIS/6.0" ["x-powered-by"]=> string(7) "ASP.NET" ["x-ua-compatible"]=> string(13) "IE=EmulateIE7" ["microsoftofficewebserver"]=> string(7) "5.0_Pub" ["x-aspnet-version"]=> string(9) "2.0.50727" ["cache-control"]=> string(18) "private, max-age=0" ["content-type"]=> string(23) "text/xml; charset=utf-8" ["content-length"]=> string(3) "423" **
10:48:20.417622 nusoap_client: Got response encoding: utf-8
10:48:20.417841 nusoap_client: Use encoding: UTF-8 when creating nusoap_parser
10:48:20.418120 nusoap_parser: Charset from HTTP Content-Type matches encoding from XML declaration
10:48:20.418326 nusoap_parser: Entering nusoap_parser(), length=423, encoding=UTF-8
10:48:20.418828 nusoap_parser: found root struct TicketClosedResponse, pos 2
10:48:20.419174 nusoap_parser: in buildVal() for TicketClosedResponse(pos 2) of type struct
10:48:20.419386 nusoap_parser: in buildVal, there are children
10:48:20.419630 nusoap_parser: in buildVal, adding Java Vector or generic compound type TicketClosedResponse
10:48:20.419853 nusoap_parser: in buildVal, return: array(1) { ["TicketClosedResult"]=> &string(48) "mscorlib:Value cannot be null. Parameter name: s" **
10:48:20.420126 nusoap_parser: parsed successfully, found root struct: 2 of name TicketClosedResponse
10:48:20.420389 nusoap_client: sent message successfully and got a(n) array return=array(1) { ["TicketClosedResult"]=> string(48) "mscorlib:Value cannot be null. Parameter name: s" **
 

 
New Post
7/20/2009 10:52 AM
 

I am not sure what would be causing this, unless values are not being sent correctly to the service.

Also, you might get better assistance if you post either at the http://forums.asp.net or MSDN forums sites, as those are for general .NET items.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Consuming ASP.NET web services in a PHP pageConsuming ASP.NET web services in a PHP page


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