Not able to add Web reference in Asp.Net Web application

I need a solution

I am trying to add Symantec VIP soap services (https://services-auth.vip.symantec.com/mgmt/soap) as “Web Reference” in my Asp.net Web application to consume the same.

i have downloaded trail symantec certificate and installed in my system. while adding “Web referenece”, i am getting below error. and i have downloaded the wsdl files from symantec VIP manager and dont know where to add those files.

The document at the url https://services-auth.vip.symantec.com/ was not recognized as a known document type.
The error message from each known type may help you fix the problem:
– Report from ‘XML Schema’ is ‘Data at the root level is invalid. Line 1, position 1.’.
– Report from ‘DISCO Document’ is ‘Data at the root level is invalid. Line 1, position 1.’.
– Report from ‘WSDL Document’ is ‘There is an error in XML document (1, 1).’.
  – Data at the root level is invalid. Line 1, position 1.

please help me to add web reference and move further.

0

Related:

Modification of Application Schema in Infoarchive

Article Number: 501357 Article Version: 3 Article Type: How To



InfoArchive 4.3,InfoArchive 4.2,InfoArchive 4.1,InfoArchive 4.0

In order to add support for new version of xsd schema for an existing holding, so that the field is searched, follow steps:

1. Add new “120-pdi-schema.xml” object.

2. Add new “pdiConfig” for a “170-holding.xml”

3. Add new “190-aic.xml” and “220-query.xml”.

4. Modify “pdi.xml” with indexes definition, so that new ingested sips are processed in accordance to the new pdi.xml and indexes are created for this new SIP for new schema.

For example please see modified Invoices sample application, that shows how to support two schema within the single holding.

For assistance on custom Application Schema modification please engage Professional Services.

Related:

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:

Handle schema soap fault exception and customize it

Hi All,

I am working on ibm odm 8.9 and using XSD( decision engine). I have already implemented custom exception handler for it. I have below 2 queries and it would be great if someone can help me on it.

1. Is there any way where we can set exception handler for ruleflow like the way we use to do in classic engine.
2. Can we capture schema validation exceptions or soap fault exception due to schema validation failures and return some customize response. In case yes please let me know the process.

Thanks in advance.

Related:

How can I retrieve XSDs in WSRR from DataPower?

Hi,
We are working on a project involving WSRR and DataPower integration. We would like information on how to retrieve XSD artifacts stored in WSRR from Datapower for our validate node.
We are fetching WSDL and XSD from WSRR Server object while creating WSP in DataPower . We don’t want to use user policy to validate the XSD because we need a switching mechanism to turn it off at runtime. Thus the reason for wanting to fetch XSD in validate node from WSRR , so we can skip that action at runtime by using some parameter. We are using DataPower IDG 7.5

Related: