error creating a new lob relay
-
quinta-feira, 22 de dezembro de 2011 21:13
hi,
I am getting this error creating a new lob relay:
*******************
The operation has timed out
System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.ApplicationServer.Integration.AFConnect.Common.ServiceBusConnectClient.CreateOrUpdateRelay(LobRelay relay)
at Microsoft.ApplicationServer.Integration.MetadataSearchBrowse.FormAddLobRelay.ButtonOK_Click(Object sender, EventArgs e)*******************
checing the internal log, I could see these errors:
"A blocking operation was interrupted by a call to WSACancelBlockingCall"
"The socket transfer timed out after 00:00:00. You have exceeded the timeout set on your binding. The time allotted to this operation may have been a portion of a longer timeout."
"The write operation failed, see inner exception."
any idea how I can resolve this?
Todas as Respostas
-
sexta-feira, 23 de dezembro de 2011 04:08
Carlos,
Do you see this happening each time, or sometimes? Can you share the stack traces as well for the errors that you saw in the log? I assume that these are Service side logs.
Thanks,
Manas
-- Please mark as answered if this answers your question. -
sábado, 24 de dezembro de 2011 06:57
Hi Manas,
I just sent you the logs by email. in addition, I have a question about this functionality because the lobrealy is created in the afconnect db, even tough I got a request timeout in vs... here is the escenario
1. I try to create the lobrelay... and the lobrelay entry is created in the afconnect database
2. The lobrelay can't be created in azure and I got a request timeout exception in Visual Studio
NOTE: Even though I got the request timeout in VS, the SBConnect wcf service is still trying to create the lobrealy and the registry in the afconnect db is not deleted yet
3. At this point if I restart the sql server where the afconnect db exists, the SBConnect wcf service cannot rollback the transaction and the lobrealy will be in the database forever
or
3. At this point, if I try to create a new lobrelay with the same name I will get an error because the "lobrelay already exist"
In my opinion, the SBConnect wcf service must rollback the operation and delete the temporal lobrelay when I got the any exception in VS, e.g. the request timeout exception... instead of trying creating it.... in other way, I must wait around 3 minutes to try to create the same lobrealy with another values.
Regards.!
- Editado carlos medina sábado, 24 de dezembro de 2011 07:13 better description
-
terça-feira, 27 de dezembro de 2011 05:50
So this was sorted out offline - the issue was that the credential that was being used for the AppPool did not have permission to access the network.
Manas
-- Please mark as answered if this answers your question.- Sugerido como Resposta Nitin Mehrotra_MSFTMicrosoft Employee quinta-feira, 12 de abril de 2012 23:47

