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
Related
I updated our signalr packages from 2.4.0 and added RunAzureSignalR instead of RunSignalR. Added this code in de Startup.cs
app.Map("/signalr", map =>
{
var hubConfiguration = new HubConfiguration
{
EnableDetailedErrors = true
};
map.RunAzureSignalR(typeof(Startup).FullName, hubConfiguration, options =>
{
options.ConnectionString = AppApiSettings.SignalRServiceConnectionString;
});
});
But when I try to send a message to the hub I get an exception The connection is not active, data cannot be sent to the service.. Can't find any reason this would happen or why the service would not run.
When I use RunSignalR (self hosted) everything runs great.
Any help would be greatly appreciated.
It turns out Azure Service only support TLS1.2 for security concerns.
Please add following code to your Startup:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
The hint for this solution was found on a github ticket: https://github.com/Azure/azure-signalr/issues/279
"No server available" indicates that your app server has trouble connecting to Azure service. You can enable tracing from the app server side with the following to see if any error throws.
GlobalHost.TraceManager.Switch.Level = SourceLevels.Information;
A sample here: https://github.com/Azure/azure-signalr/blob/dev/samples/AspNet.ChatSample/AspNet.ChatSample.SelfHostServer/Startup.cs#L19
If you are local debugging the server side, you can also uncheck "Just My Code" and break when any CLR exception throws:
System.Security.Authentication.AuthenticationException: "A call to SSPI failed, see inner exception."
- (inner) "The function requested is not supported"
System.ObjectDisposedException: 'Safe handle has been closed'
System.Net.WebException: 'The request was aborted: Could not create SSL/TLS secure channel.'
System.Net.WebSockets.WebSocketException: 'Unable to connect to the remote server'
- (inner) WebException: The request was aborted: Could not create SSL/TLS secure channel.
I recently had the same issue and again the accepted answer didn't help me. My project was a .NET 4.8 MVC application (so TLS version shouldn't be an issue) and following an update of the projects Nuget packages the issue arose.
I knew it was the Nuget updates that had broken my application but I didn't want to go through each one to figure out where the issue was.
Thanks to #cognophile for pointing me in the right direction. For me though I only needed to downgrade the following three Nuget packages to version 5.0.17 to fix the issue. Anything 6.x with these packages caused the issue again.
Microsoft.AspNetCore.Connections.Abstractions
Microsoft.AspNetCore.Http.Connections.Client
Microsoft.AspNetCore.Http.Connections.Common
I've recently had the same issue whereby the negotiation worked with map.RunSignalR(...) but not map.RunAzureSignalR(...) and tried the accepted answer here without resolution. For anyone still experiencing this issue having tried the accepted answer like myself, I found the below to work for a .NET Framework 4.6.1 project.
Navigating to the negotiation link (e.g. .../signalr/negotiate?clientProtocol=2.1&connectionData=...&callback=jQuery...&_=...) in the browser would give a
HTTP 500: Azure SignalR Service is not connected yet, please try again later
Having enabled the exception debugging suggestions from #Youp Hulsebos and the SignalR GitHub (source), I was able to find the following exceptions being thrown from the SignalR registration call in Startup.Configure(...):
Microsoft.Azure.SignalR.Common.ServiceConnectionNotActiveException: 'The connection is not active, data cannot be sent to the service.'
LoaderException - Method 'get_Features' in type 'Microsoft.AspNetCore.Http.Connections.Client.HttpConnection' from assembly 'Microsoft.AspNetCore.Http.Connections.Client, Version=1.0.0.0, Culture=neutral' does not have an implementation.":"Microsoft.AspNetCore.Http.Connections.Client.HttpConnection"
Having found the second of these exceptions and applying some Google-fu, I found this GitHub issue discussing the LoaderException from Microsoft.Azure.SignalR.WebSocketConnectionContext discussing this as the result of upgrading Microsoft.AspNetCore.Http.Connections.Client from 5.0.12.0 to 6.0.0.0.
Having tried downgrading the package to 5.0.12.0, I still encountered the same issue. Having checked the linked issue ([dotnet/aspnetcore#38699]), I downgraded the following packages to 5.0.11.0 and this resolved the issue:
Microsoft.AspNetCore.Connections.Abstractions
Microsoft.AspNetCore.Http.Connections.Client
Microsoft.AspNetCore.Http.Connections.Common
Microsoft.AspNetCore.Http.Features
I am getting this error while loading a WSDL to SOAP UI.SCREEN SHOT OF ERROR
Your WSDL file is malformed, best way to find out what is wrong with it is to run it through some WSDL validation tool, like:
built in Eclipse WSDL validation tool
https://www.w3.org/wiki/WsdlValidator
https://www.wsdl-analyzer.com/
...
Disclaimer, I have not used any of this except for the Eclipse one, so proceed at your own risk.
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.
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.
I’m trying to add a team project collection to a TFS2010 instance. The instance already has project collections set-up and in use, but when I try to add another I get warnings from the Data Tier Configuration. The warnings are as follows:
TF255153: Service is not set to start automatically: SQL Server Database Services:
TF255437: An error occurred while querying the Windows Management Instrumentation (WMI) interface on the following computer: MYTFSSERVER. The following error message was received: .
TF255437: An error occurred while querying the Windows Management Instrumentation (WMI) interface on the following computer: MYTFSSERVER. The following error message was received: .
(TF255437 is reported twice)
I’ve had a good look around, and found a couple of articles that implied TF255437 is caused by WMI compatibility not being enabled in IIS (TFS2010 is running on IIS7.5). However, this is enabled as far as I can tell.
Has anyone come across either of these errors before? The admin console seems happy for me to create the TPC regardless, but without understanding the errors fully, I’m reluctant to do so.
This was all caused by the "SQL Server Agent" service not being started on the server.