SendLetterResult : -3150

General error..doesn't really help me get it working! :P

Any ideas on what this is and how I can figure out how to fix it?
Here is a copy of the soap message being sent.

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:tm="" xmlns:SOAP-ENV="" xmlns:soap12="" xmlns:mime="" xmlns:soap="" xmlns:s="" xmlns:wsdl="" xmlns:xsi="" xmlns:http="" xmlns:soapenc="" xmlns:s1="PostalMethods/AbstractTypes" xmlns:tns="PostalMethods" SOAP-ENV:encodingStyle="">
      <Username xsi:type="s:string">ryandetzel</Username>
      <Password xsi:type="s:string">******</Password>
      <MyDescription xsi:type="s:string">description for test 2</MyDescription>
      <FileExtension xsi:type="s:string">html</FileExtension>
      <FileBinaryData xsi:type="s:base64Binary">UENGR...FvPQo=</FileBinaryData>


Ryan, Can you post the code


Can you post the code you were using when this occurred?

Hi Ryan, 1. You are right

Hi Ryan,

1. You are right about the general error code not helping. We've developed our Web Service to provide detailed error descriptions but it seems not handle all cases yet. We've developed a new version of the Web Service which handles all possible cases we know of. It completed testing this morning and we will make an emergency upgrade tomorrow early morning.

2. Using the current Web Service version, it seems that the only reason to get the general error code is when some of the properties of the request are empty or do not exist. In case you are using python, a very skilled programmer had a similar problem and he told me that isn't sophisticated enough to interpret XMLSchema. He uses the Zolera SOAP Infrastructure (ZSI, with no problem. Please let me know if this is your case and I could ask him to provide additional information.

I'm using Perl, the message

I'm using Perl, the message that is being sent appears to be correct..the only thing I can think of is it's not handling the base64 message correctly.

use strict;
use warnings;
use SOAP::Lite +trace => 'debug';;
use MIME::Base64;
use Data::Dumper;
open FILE,"PostalMethodsPopulated.html";
my $file = join("\n",<FILE>);
close FILE;
$file = encode_base64($file);
$SOAP::Constants::PREFIX_ENV = 'SOAP-ENV';  ## Bug in Soap::Lite
my $service = SOAP::Lite->service('');
my $result = $service->SendLetter('ryandetzel','******','description for test 2','html',$file);
print Dumper($result);

Hi! This worked for me (.net


This worked for me (.net webservices are a little picky about their namespaces):

my $soap = SOAP::Lite
    -> uri('PostalMethods')
    -> on_action( sub { join '/', 'PostalMethods', $_[1] } )
    -> proxy('');
print $soap->SendLetter(
                        SOAP::Data->new(name => 'Username', value => 'username', type => 'xsi:string')->uri('PostalMethods'),
                        SOAP::Data->new(name => 'Password', value => 'password', type => 'xsi:string')->uri('PostalMethods'),
                        SOAP::Data->new(name => 'MyDescription', value => 'aaaaaaaaaa', type => 'xsi:string')->uri('PostalMethods'),
                        SOAP::Data->new(name => 'FileExtension', value => 'html', type => 'xsi:string')->uri('PostalMethods'),
                        SOAP::Data->new(name => 'FileBinaryData', value => $file, type => 'xsi:base64Binary')->uri('PostalMethods')

Also, I think you'll need to chomp your $file.


On a separate note, it's

On a separate note, it's best to default to using an SSL-secured connection to the PostalMethods Web Service. There's no real performance penalty while the security of your app is greatly enhanced. Here's the SSL endpoint:

Hi, I using the WSDL of


I using the WSDL of postal methods for testing puropose using SOAPUI.

I am testing the Send Letter method.

Below is the request I am sending and I am getting a blank response.


Can you please let me know what could have casued this issue?

Also, I would like get some guidelines on how to pass binary data in the request message for testing SendLetterAndAddress.

Below is the request message I am trying to send.

<soap:Envelope xmlns:xsi="" xmlns:xsd="" xmlns:soap="">
    <SendLetterAndAddress xmlns="PostalMethods">

There seems to be a problem

There seems to be a problem in SOAPUI version 2.5 when sending SOAP requests containing binary attachments.

The best workaround at the moment is to convert your document to Base64 using a free online converter, such as: and edit the SOAPUI request using the FORM or XML tabs, pasting the encoded string between the appropriate tags - <pos:FileBinaryData>base64 Binary String</pos:FileBinaryData>

Please note, the problem

Please note, the problem seems to be solved in SOAPUI version 2.5.2, which is currently in BETA.