martedì 29 maggio 2012 16:14
I made the terrible mistake of changing my AppFabric Labs ACS password/key (after doing a series of public demos), and now my Service Bus Connect won't work.
Specifically, I can't seem to connect to my on-premises SQL Server anymore. My bridge keeps failing with "internal server error" and when I use the REST service to look at the bridge tracking info, I *think* that I'm seeing a "LOB Relay Endpoint Not Found" error.
I've uninstalled and reinstalled Service Bus Connect, was able to successfully walk through the Visual Studio wizard to create a SQL Server endpoint, and my IIS services are running. However, it doesn't appear that the AppFabric Connect Runtime (management) Service is creating a SB connection.
I can't figure out how to troubleshoot this further. Even a simple demo with a newly created SQL endpoint fails, so it's not just my existing demo. I turned on tracing for the IIS services (in their web.configs) but nothing gets written out.
Tutte le risposte
venerdì 1 giugno 2012 08:00
You seem to be able to crete new Lobrelay and targets without error and yet, sending runtime messges to them seems to are failing ?
What happnes if you try to bowse to the runtime URL of the LOb targer ?
Do u get the base RSS feed or u get the 401 authorization token required error ?
sabato 2 giugno 2012 23:12I get the "401 authorization token required" error. So, it DOES look like the service is somewhat connected. What's strange is that when I run the tracking sample (Samples\Tools\TrackingClient) against the LOB Target URL, I get "LobTargetNotFound" as the exception.
domenica 3 giugno 2012 07:30
LobTarget path is a subpath to the lobrelay path. The LobRelay listens at a root path say-
"https://ns.servicebus.appfabriclabs/com/foo" and can route to different lobTargets based on subpath.
So, if a mesage comes at https://ns.servicebus.appfabriclabs/com/foo/sap1/" , it can be routed to SapServer1
while a mesage comint at "https://ns.servicebus.appfabriclabs/com/foo/sql2/" can be routed at to a SQL sever based on how you organise your lobTagets.
The above fault means that no LobTarget was configured at the subpth (say "sap1/" ).
Can you post the entire fault mesage.
Also, it would be nice if you caould verify that the Route destinatino in the pipleine points to correst LobTaget address (and say ...not to LobRelay addrsss).
lunedì 4 giugno 2012 20:16
Thanks for the help.
My full fault message is as such ...
<Fault xmlns="http://schemas.microsoft.com/ws/2005/05/envelope/none"><Code><Value>Sender</Value></Code><Reason><Text xml:lang="en-US">No LOBTarget found matching the specified address 'eaiemplookup/tracking/default'.</Text></Reason><Detail><AFConnectRuntimeFault xmlns="http://Microsoft.ApplicationServer.Integration.AFConnect/2011" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><ExceptionCode>LobTargetNotFound</ExceptionCode></AFConnectRuntimeFault></Detail></Fault>
I'm not sure where the "tracking/default" part came from. I got this file from running the Tracking Client, so maybe that's what some of this is.
I'll need ot look at the "route destination in the pipeline" as I don't recall there being on. I link the two bridge to the LOB shape on the bridge configuration. The route action has the "action" added for the "select" operation, but there's nothing in the pipeline that points to the LobTarget address.
lunedì 18 giugno 2012 12:25
Were you able to resolve this.
Clearly, the issue is that the address of lobtarget specified on the mesage flow doesn't match the address in server explorer.
- Proposto come risposta Leonid GanelineMVP giovedì 30 agosto 2012 22:16
martedì 31 luglio 2012 18:37
Hey Rohit,Webexception received while sending the data
I am getting kind of similar error but with a little difference.
Tracking ID for the message sent is 176de2be-2f11-435d-b011-91ee8e5b0662
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://ww
nder</Value></Code><Reason><Text xml:lang="en-US">Win32Exception:There are curre
ntly no logon servers available to service the logon request</Text></Reason><Det
I am actually trying to do a scenario similar to the samples provided where in the SQL Server is on premise and has been configured with Windows Credentials.
I also get the Missing Token error while browsing the runtime URL of LOB Target.
The other thing i wanted to know was that is there any way that a sample file can be created out of a schema like provided by BizTalk Schema editor. It kind of helps if there is a way to achieve the same.
- Modificato Ashutosh Maheshwari mercoledì 1 agosto 2012 04:17
mercoledì 1 agosto 2012 06:47
1. There are currently no logon servers available to service the logon request.
>> Looks like the SBconnect servcie sitting on-prem is getting error while tryig to impersoante the given windows credentails. Please check your active directory configuration. Following Kb might help -http://support.microsoft.com/kb/949048
2. I also get the Missing Token error while browsing the runtime URL of LOB Target
>>> This is the expected behaviour. A security token is required to send any msg to the endpoint.
The the HTTP GET from webbrowser doesn't ahve the token, so you get the error.
3. Is there any way that a sample file can be created out of a schema like provided by BizTalk Schema editor
>>> We have receive this feedback from other source as well.
We will most probably be adding this in the next update to the client SDK.
giovedì 2 agosto 2012 02:31
Thanks Rohit... it worked.
I have been trying to simulate the FTP sample. I created a default FTP Site and gave access to all the anonymous users and got it authorized by all the users. For username and password i use 'anonymous' and 'email@example.com' i am able to connect to ftp using command prompt. When i deploy the solution i get the error that 'Error 4 FTPOrderSource deployment failed.Failed to connect to the FTP server using specified configuration. Error message - Unable to connect to the remote server'
I have tried creating a new FTP site and running it under different application pool which was configured to be used by a dummy admin account. It still doesn't work.