- This topic has 9 replies, 1 voice, and was last updated 9 years, 1 month ago by
.
-
Posts
-
-
Hello everyone,
I am currently building an orchestration which receives a request through a FILE adapter using the XML pipeline, then makes an invocation to a webservice using the ports and messages created by BizTalk and once it responds, a response is also sent back to the user.
Everything goes well until the webservice invocation, where I get the following warning:
Event Type: Warning
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5743
Date: 25-08-2010
Time: 12:09:38
User: N/A
Computer: BPC0DESMZ08
Description:
The adapter failed to transmit message going to send port “CBMOrchestrations_1.0.0.0_CBMOrchestrations.Credinformacoes_CredPort_f85c9f82e19fd991” with URL “http://localhost/testws/Service1.asmx“. It will be retransmitted after the retry interval specified for this Send Port. Details:”Failed to load “CBMOrchestrations.Cred.Service1, CBMOrchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f85c9f82e19fd991” type.
Please verify the fully-qualified type name is valid.
Details: “System.TypeLoadException: Could not load type ‘CBMOrchestrations.Cred.Service1’ from assembly ‘CBMOrchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f85c9f82e19fd991’.”.
The type must derive from System.Web.Services.Protocols.SoapHttpClientProtocol.
The type must have the attribute System.Web.Services.WebServiceBindingAttribute. “.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Even though the information returned by the warning doesn’t help a bit, I think I’ve tried everything already, checked the GAC, web-service connectivity (if I try to call a webservice I am sure to work, the result is the same), completely rebuilding the solution, but the problem persists. I have also tried many suggestions I found over the internet, namely those which imply that I am not using the ports generated by BizTalk. Other solutions which include reinstalling components are not possible to accomplish, but I really want to believe that there is some way out of this.
-
I just tried again to re-do the whole thing and I was finally able to consume the web service. But, when I altered the source code of the web service and refreshed the web reference, this problem came popping out again. What’s interesting is that now, every time I try to add a web reference and make web service calls, Biztalk won’t let me and throws the exception..
-
Known issue – after you delete web reference – close Visual Studio, go to project folder – delete all artefacts and added WebReferences folder too.
-
Thanks for your reply Yonathan!
I did what you proposed, but I’m afraid
it didn’t work out. I erased the webreferences from the project, closed
VS and deleted the webreferences folder. As for the artifacts, I don’t
know what you are referring to, so I did nothing with them. Then I added
the webreferences again, only to see the webservices not working. The funny
thing was that prior to this, I had one ws working and one not working.
After this, both webservices were not working, always throwing that exception.I am completely clueless here, I think
I’m doing everything well. I stop the application, build and deploy it,
start it and restart the host instance, and the exception always comes
out. I even checked the GAC for the elements that BT is complaining about,
and they are there. I don’t know what else to do.It’s a shame I can’t just use the .net
webreferences in a practical way as it is supposed to be, without having
to resort to any kind of schema or trick to be able to consume webservices.
It shouldn’t take me over a week to be able to consume webservices with
.net webreferences. What’s even weirder is that I seem to be the only person
facing this kind of problem on the internet.
-
Did you restart IIS after code changings in WebService?
Did you try to consume the WS from regular code (Console application)?
Do you try to create some test BizTalk project with adding web reference? – Does this work?
Did you try to give different name to Web Service Reference?
-
1º Yes, I did that, although IIS log does not show any access attempt when I try to call a webservice;
2º Yes, it works from a console application using a regular web reference;
3º Yes, it didn’t work;
4º Yes, I always give different names.
One thing I find odd is when I add the webreference, the Reference.odx.cs file is generated but comes empty.. Couldn’t find why yet.
-
Hi,
I’m looking at the error message you pasted in your original post, and these two lines caught my eye:
The type must derive from System.Web.Services.Protocols.SoapHttpClientProtocol.
The type must have the attribute System.Web.Services.WebServiceBindingAttribute.I wonder if you tried adding the Microsoft assembly System.Web.Services to your References folder in the project where you are adding the web reference and see if that resolves the web service invocation warning issue.
Cheers,
Daniel.
-
-
Say, after defining messafes according to your generated schemas – do you use WebPort type? (right click on port surface area – new port port name – port type – use existing port types – select from “WebPort Types” – your port)?
According to this error/post http://www.eggheadcafe.com/software/aspnet/30267049/setting-webservice-destination-programmatically-at-runtime—.aspx
-
Sorry – for the last post – I didn’t read it carefully.
When you define Send Port – (if I get it right you get request – send to WS – get response – return the response to user – right?)
So, if you do use WebPort types – after you deploy the project – and when you define send port with SOAP protocol, did you define your BizTalk assembly in “WebService” tab?
http://i080.radikal.ru/1009/0c/cba0017aead4.jpg
-
-
-
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.