Why don't you post a small shell working version of the service program source and maybe we can help.

Beyond that hard to tell what you're running up against.

I know I've been successful calling the IWS stuff from VB.Net.

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
----------------------------------------------------------------------

message: 1
date: Thu, 21 Oct 2010 10:03:00 -0700
from: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
subject: Re: IWS problems

James H. H. Lampert wrote:
Back to our customer who wants to communicate with our product via web
services.

It seems that they are attempting to call one of the web services I
hastily deployed a month ago, and they're calling it from Visual BASIC.NET.

1. It seems that the web service is throwing a number format
exception, but we can't tell which parameter it's throwing it on.
(Other than obviously one of the ones coded as numeric.)

2. For all of the parameters specified as "decimal," they're also
finding a "specified" field associated with the parameter. Anybody
have the slightest idea what that's about?

More:

Several of the parameters had decimal points. They worked just fine from the web service tester, as I recall, but they appear to have been the problem with the customer's call from VB.NET, because when we scaled the parameters to eliminate the decimal points, and redeployed, everything worked just fine.

Any idea what's up with that?

--
JHHL




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.