Hi,
I have created a client that uses WSE 3.0/MTOM to transfer files to and
from our server to our clients. I know that WSE 3.0 is not supported by
Windows 98 SE but I tried it on one of my clients machines and it works
perfectly. My problem is that I have a test macine at work running
Windows 98 SE as well but it throws an error as soon as I try to create
the service. I created a very simple Web Service (Hello World) and
client to test the problem.
For example it throws the an error when I call:
dim proxy as New helloworld.ServiceWse
The Error I get is:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.UriFormatException: Invalid URI: The hostname could not be
parsed.
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind
uriKind)
at System.Uri..ctor(String uriString)
at Microsoft.Web.Services3.SoapContext.get_FallbackActor()
at Microsoft.Web.Services3.SoapContext..ctor(SoapEnvelope envelope)
at Microsoft.Web.Services3.WebServicesClientProtocol..ctor()
at WSTest.helloworld.ServiceWse..ctor() in C:\Documents and
Settings\Ryan Smith\My Documents\Visual Studio
2005\Projects\HelloWorld\WSTest\Web
References\helloworld\Reference.vb:line 40
at WSTest.Form1.Button1_Click(Object sender, EventArgs e) in
C:\Documents and Settings\Ryan Smith\My Documents\Visual Studio
2005\Projects\HelloWorld\WSTest\Form1.vb:line 4
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at
System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message&
m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32
msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/MICROSOFT.NET/FRAMEWORK/V2.0.50727/mscorlib.dll
----------------------------------------
WSTest
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/MY%20DOCUMENTS/RELEASE/WSTEST.EXE
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
Microsoft.Web.Services3
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5305.0
CodeBase:
file:///C:/MY%20DOCUMENTS/RELEASE/Microsoft.Web.Services3.DLL
----------------------------------------
System.Web.Services
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Web
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
WSTest.XmlSerializers
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase:
file:///C:/MY%20DOCUMENTS/RELEASE/WSTest.XmlSerializers.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
It doesn't even connect to the Webservice before it throws the error. I
have tried changing the webservice address to all kinds of things but
it always returns this error. Do I need to install something else that
would help this work. When I call the normal webserice it works fine
(dim proxy as New helloworld.Service).
Any help would be greatly appreciated.
Ryan
Pablo Cibraro - 16 Mar 2006 15:49 GMT
Hi Ryan
The error seems to be clear.
WSE is not being able to parse the URL for the target service (The URL that
you specified in the proxy for the service).
Does it make sense ?
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
> Hi,
>
[quoted text clipped - 150 lines]
>
> Ryan
RyanS - 17 Mar 2006 00:13 GMT
Hi,
Thanks for your response but it doesn't make sense to me because of a
few reasons.
1) The proxy without the WSE on the end works perfectly fine. (dim
proxy as HelloWorld.Service). For example:
This will throw the error
dim proxy as HelloWorld.ServiceWse
outputTextBox.Text = proxy.HelloWorld (Returns "Hello World" as text)
But this won't
dim proxy as HelloWorld.Service
outputTextBox.Text = proxy.HelloWorld (Returns "Hello World" as text)
2) The extact same build works on another Windows 98 SE machine, and
other clients I have tested it on (Windows 2000,XP, etc)
What does it mean by the Hostname? Is that the URL of the service? Is
it the name of the computer running it. I have tried testing this with
a webservice from an external source and a local webservice.
Thanks
Ryan
RyanS - 17 Mar 2006 00:44 GMT
I have found the problem, when the computer was setup it had been
called WIN98 and WSE doesn't like that, so I changed the computer name
and it now works.