7021554: Errors in Microsoft Visual Studio When Using Verastream Host Integrator 7.x Web Service

The following errors or warnings may display when you add the Verastream Host Integrator (VHI) web service to your project, or subsequently attempt to build your project.

Warnings When Adding Service Reference

In your Microsoft Visual Studio 2008 or 2010 project using .NET Framework 3.0 or 3.5, after adding a service reference to the VHI web service WSDL, the Error List may display warnings similar to the following:

Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 2 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: lang' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 3 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: space' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 11 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: base' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 12 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: id' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 13 Column: 3

Validation Error: The attributeGroup 'http://www.w3.org/XML/1998/namespace:specialAttrs' has already been declared.



Custom tool warning: The optional WSDL extension element 'UsingAddressing' from namespace 'http://www.w3.org/2006/05/addressing/wsdl' was not handled.

XPath: //wsdl:definitions[@targetNamespace='urn:xmlns:attachmate:vhi-ws:<model or session>:<model name>']/wsdl:binding[@name='<model name>PortBinding']

Errors When Building Project in Visual Studio 2010

In a BizTalk Server 2010 project, after importing a VHI web service as a Service Reference and attempting to build the solution, the Error List may display multiple errors similar to the following:

Node "<Schema>" - Schema reference "http://<hostname>:9680/vhi-ws/<model or session>/<model name>/<file>.xsd" is not a valid reference or does not exist in the current project.

Figure 1. Sample build errors in Microsoft Visual Studio 2010 Error List

Errors When Building Project in Visual Studio 2008

When attempting to compile your project in Visual Studio, the Error List and build output may display multiple errors similar to the following:

error CS0102: The type '<project name>.<service reference name>.<type name>' already contains a definition for '<name>'

error CS0111: Type '<project name>.<service reference name>.<type name>' already defines a member called '<name>' with the same parameter types

Figure 2. Sample build errors in Microsoft Visual Studio 2008 Error List

Error in BizTalk WCF Service Consuming Wizard

If you are attempting to add a Verastream Host Integrator 7.0 web service WSDL to a Microsoft BizTalk Server 2006 R2 or 2009 project using the WCF Adapter, the BizTalk WCF Service Consuming Wizard may display the following error:

Figure 3. 'Error consuming WCF service metadata. Object reference not set to an instance of an object.'

Figure 3. 'Error consuming WCF service metadata. Object reference not set to an instance of an object.'

Related:

7022007: NetIQ NIDP STS service runs into a JAVA exception on running a SOAP1.1 request

This document (7022007) is provided subject to the disclaimer at the end of this document.

Environment

  • Access Manager 4.3
  • Access Manager Version 4.3 NIDP Server

Situation

  • The “https://nam.kgast.local/nidp/wstrust/sts?wsdl” defines the following SOAP binding:- Access Manager

    <wsdl:binding name=”STS_Binding” type=”tns:SecurityTokenService”>

    <wsp:PolicyReference URI=”#STS_Policy”/>

    <soap:binding

    transport=”http://schemas.xmlsoap.org/soap/http”/>

    <wsdl:operation name=”Issue”>

    http://schemas.xmlsoap.org/soap/http/

    ==============================================================

    http://schemas.xmlsoap.org/soap/http is the WSDL 1.1 binding for the SOAP 1.1 HTTP binding.

    ==============================================================

  • According to the definition requests should use the SOAP 1.1 binding which will fail at the NIDP server causing a JAVA exception:

    ————————————————————–

    Jan 12, 2017 5:17:28 PM com.sun.xml.wss.jaxws.impl.SecurityServerTube processRequest

    SEVERE: WSSTUBE0025: Error in Verifying Security in the Inbound Message.

    com.sun.xml.ws.protocol.soap.VersionMismatchException: Couldn’t create SOAP message. Expecting Envelope in namespace http://www.w3.org/2003/05/soap-envelope, but got http://schemas.xmlsoap.org/soap/envelope/

    ————————————————————–

  • Running the same request by using a SOAP 1.2 Bindings works without any problems

Resolution

IMPORTANT:Starting from Access Manager 4.0 SP1 release, the default binding supported is SOAP 1.2. If you want to use SOAP 1.1 instead, perform the following steps on all instances of the Identity Server:

Traverse to the /opt/novell/nam/idp/webapps/nidp/WEB-INF folder and edit the sun-jaxws.xml file. Remove all instances of bindings from the endpoints in the sun-jaxws.xml file and save the changes. A binding is represented by the following line in this file:

binding=”http://java.sun.com/xml/ns/jaxws/2003/05/soap/bindings/HTTP/”

Restart the Identity Server using the /etc/init.d/novell-idp restart command.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

Deploying Message Flow in local Integration Node for testing returns no records on output. No error, just no records populating output file.

HELP!!! When I test the DFDL it parses as it should but when I test the message flow in a local Integration Node, I get an output file with no records. There are elements noted in the .esql as those to look for and they match what is in the test file. Here is how I have set the properties in the Message Flow:
Current Properties:
*File Input Node*
Basic and Input Message Parsing are both mapped to correct locations, file names and schema (I have triple checked this)
Records and ElementsRecord detection: Whole File

*File Read Node*
Basic and Input Message Parsing are both mapped to correct locations, file names and schema (I have triple checked this, also)
Records and ElementsRecord detection: Whole File (NOTE: I tried Delimited but it caused an error)

*File Output Node*
Basic and Input Message Parsing are both mapped to correct locations, file names and schema (I have triple checked this too)
Records and ElementsRecord detection: Whole File (NOTE: tried this one as Delimited while other 2 were Whole File, still no luck)

Related:

[IIB10] SOAPRequest node returning ‘nil’ response

I have been facing a weird issue with the SOAPRequest node. Whenever, I make a SOAP request, there is a probability that I will receive a ‘nil’ response that fails with the following errors in the iib log:

BIP5902W: An error occurred in parser ‘Root’ while parsing the field named ‘SOAP’ on behalf of the node or component ‘REDACTED’. The data being parsed was ‘3c3f786d6………’
BIP3614E: A SOAP logical tree cannot be built from the message bitstream
BIP5009E: XML Parsing Errors have occurred.
BIP5025E: XML schema validation error ‘cvc-elt.3.1: Attribute ‘xsi:nil’ must not appear on element “REDACTED”, because the ‘{‘nillable’}’ property of “REDACTED” is false.’ on line ‘1’ column ‘272’ when parsing element ‘/XMLNSC/{http://schemas.xmlsoap.org/soap/envelope/}:Envelope/{http://schemas.xmlsoap.org/soap/envelope/}:Body’. Internal error codes: 5016, 2.

It seems like some long data value consisting of hex characters is coming in as part of the response which is causing the message to fail. This exception occurs sporadically because sometimes a response is actually created and the message flow completes without exceptions. I tried sending 4 equal messages in quick succession and I have observed that out of four only one message returned the correct response, rest failed with the above exception.

I have enabled validation and set the parse timing to “Immediate” on the SOAPRequest node to ensure that the message is parsed immediately. I have also enabled “Build tree using XML schema data types”.

Is there any thing else that I can do to make this SOAPRequest node give 100% consistent responses?

Thanks

Related: