I am currently trying to integrate ExpressionEngine and Salesforce using a SOAP API. I have a working WSDL but when I try and parse the WSDL and create APEX classes in Salesforce it ends up throwing some weird errors. I have posted extensively on this at the following salesforce forum link: http://boards.developerforce.com/t5/Apex-Code-Development/URGENT-WSDL-Issues-Error-Failed-to-parse-wsdl-type-not-specified/td-p/548983
It was originally throwing an error saying that the name attribute could not be null so I then added name="salesforce" to the node. After that it began throwing a type error:
Error: Failed to parse wsdl: type not specified for attribute: salesforce
I have tried to debug this, but can't really find much wrong with the following declaration:
<xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="tns:Associative[]" name="salesforce"/>
The full WSDL document can be found at the above link. Any help would be greatly appreciated as this is not my particular area of expertise and I have a fast approaching deadline.
The WSDL is using the rpc/encoded interaction style, this is not supported by the Salesforce WSDL2Apex tool. You'll have to manually create/parse requests to this API.
Related
I am running wsdl.exe tool on http://files.developer.sabre.com/wsdl/sabreXML1.0.00/pnrservices/GetReservation_1.19.0.wsdl, following the Sabre .NET sample, and the Get Itinerary Resources which warn that: "TravelItineraryReadRQ API will be decommissioned; please use GetReservationRQ"
But failed with error:
WSDL: error WSDL1: There was an error processing 'http://files.developer.sabre.com/wsdl/sabreXML1.0.00/pnrservices/GetReservation_1.19.0.wsdl'.
The document was understood, but it could not be processed.
- The WSDL document contains links that could not be resolved.
- There was an error downloading 'http://files.developer.sabre.com/wsdl/sabreXML1.0.00/pnrservices/PNRBuilderTypes_v1.19.0.xsd'.
- The request failed with HTTP status 404: Not Found.
.Net has some issues with choice elements and the way Sabre created some WSDLs. You can find more information at https://developer.sabre.com/resources/api_versioning.
Sabre team fixed the broken address and now there is no error when running the wsdl tool. Thanks
When i run my application it tells me that "Class TraCoreModule not found". I tried to google witch class this is or where it comes from but no results.
Can anyone tell me what module this is or why i get this error please?
The application connects to a sql server database and updates a few fields.
It also uses ActiveX to send emails.
I am using Woll2Woll.
I wish i could provide more information but this is all i have.
I tried to locate the error in my code by printing debug messages in a memmo but this does not help.
So i figured out the issue. The TppReport was corrupted...
I am trying to integrate the power bi report with our asp.net mvc application. So I found this https://azure.microsoft.com/en-us/documentation/articles/power-bi-embedded-get-started-sample/ article and followed the steps. I have successfully created the workspace collection and generated the access keys. And I downloaded this https://github.com/Azure-Samples/power-bi-embedded-integrate-report-into-web-app/ sample application as specified in the article and ran the ProvisionSample contsole application. I selected the 5th step and provided the appropriate values for workspace collection name and access key and it throws the following error "Operation returned an invalid status code 'Forbidden'". I looked at the audit logs and there is no error. Anyone have idea what causes for this issue?
There is an issue going on right now that is effecting some parts of the world. We are actively working on a fix.
We are using IBM Web Experience Factory 7.0.1 for our project. In one of the models we are connecting to a WSDL based service. For that we are using Web Service Multiple Operation Builder. I have enabled testing support for the builder. But when I am testing by launching the model and try to invoke any methods I get the follwing error:
An error has occurred. The error message returned was: "Error in
method sd_WSMultiOpServicesGetOrdersGotoOperation. Error in method
sd_WSMultiOpServicesGetOrders_ShowResults. Error in method
getOrdersExecute. Error in method getOrders.invoke. Error in method
getOrders.invokeInternal. (404)Not Found".
Both of the Web Experience Factory (WEF) Web Service builders have an advanced input (checkbox) to tell them to log the requests and responses they're making/getting back. Check that checkbox then save the model and run it again (redeploy if not auto-synching the project to the deployed WAR). Then when you run the action that hits the web service, it should log additional debugging info into the deployed WAR's WEB-INF/logs folder in debugTracing.txt. That should tell you what URL it's trying to hit with the web service that you're receiving the 404 error back from.
I hope that info helps,
..Mike Burati
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.
Use WCF-SAP binding in WCF-Custom adapter, ReceiveIDOCFormat is set to 'String', in the pipeline component, we wrap and call a flat file disassembler to disassemble the SAP request to XML and process it later. We also have a log compnent which will log the SAP raw message prior to disassembler (the string version) to database (streaming way using CForwardOnlyStream)
Here is the problem, during the UAT testing with SAP, we find occasionally the flat file disassembler is complaining 'Unexpected end of stream while looking for:....', when we inspect the SAP message sent over the wire, we find the SAP request only contains the header (EDI_DC40), with emty content after that. What makes me worry is , when we go into SAP, resubmit the failed message using transaction WE19, disassembler has no problem parsing it.
I am totally lost, can someone please sugguest how to troubleshoot this?
Thanks a million!!
I think probably I found the problem now, SAP guys added a field, what I used to do (which I think is right but it may be the flaw) is, I didn't regenerate the schema, instead, I just manually added the field in Visual Studio and set the field length based on IDOC description.
I regenerated the IDOC using the WCF wizard, it seems it is not as same as added a field in visual studio, I just deployed this schema and hope it will address the problem, I'll post my findings later if it worked