Skip to main content

I would like to create a service instance but the attached error was found. It was fine for other web services except this time.

Web service with wsdl was used here.

The correct service url was typed (covered up due to authorization issue), for the metadata url, I have tried serval:

i.e. http://....svc, http://....svc?wsdl, http://....svc?singleWsdl

 

Does anyone know how do fix this problem? Or perhaps, what are the possible causes that I could look up?

I am curious, metadata is auto-gen, so is it possible that the problem is not in the code itself?

 

ps I do not have the access to the base code. Nor could try the test with WFC Client.

Thank you! I could provide more information when needed please just tell.


15715i584DBEA89DC76D2C.jpg

Hi Needhelp_,


 


The times we have seen this error it involved an NLB configuration in the mix that caused some lookup issue.  I might have a another way for you to get the service instance registered:


 


In my workaround I am using the following public WCF service:


 


SVC URL:      http://dev.virtualearth.net/webservices/v1/geocodeservice/geocodeservice.svc


WSDL URL:  http://dev.virtualearth.net/webservices/v1/metadata/geocodeservice/geocodeservice.wsdl


 


Steps:


1. Save the WSDL to a file by browsing the WSDL URL and saving the text to a .txt file somewhere on disk


2. Configure the service instance as usua but for the 'Service MetaData URL - Required' property, use the path to the file saved on disk e.g. in the attached screenshot, the path is 'C:FilesWSDL.txt'


3. Finish the service instance wizard


 


In addition to the screenshot I also uploaded the WSDL file I used in this example.


 


If this does not work for you, I suggest you log a ticket with K2 Support.


 


HTH!



ConradK2,

Thank you for your detailed reply. Unfortunatelly it didn't work for my case.

Could you kindly elaborate more on the possible causes of this problem? (perhabs ways to solve it)

What do you mean by NLB Configuration?

Thanks!


Reply