Tech Forum

Have tried the most of the day to connect to the Meetinghouse Webcast, as we were going to transmit a Stake Conference meeting to a long distance unit.
when I try to connect I get an error message:

System.ServiceModel.ServiceActivationException: Den anmodede tjeneste, https://webcast.ldschurch.org/Services/Webcasting.svc, kunne ikke aktiveres. Du kan finde flere oplysninger i serverens logfiler til diagnosticeringssporing.
Server stack trace:
ved System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory factory, WebException responseException, ChannelBinding channelBinding)
ved System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
ved System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
ved System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
ved System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
ved System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
ved System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
ved System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
ved System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
ved System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
ved Lds.CM.MeetinghouseWebcast.Shared.Services.Contracts.Webcasting.V1.IWebcastingService.Logon(LogonRequest request)
ved Lds.CM.MeetinghouseWebcast.Shared.Services.Contracts.Webcasting.V1.WebcastingServiceDynamicProxyWrapper.Logon(LogonRequest )
ved Lds.CM.MeetinghouseWebcast.UI.Business.Security.Logon(String username, String password, List`1& availableAuthRequestAgents)
ved Lds.CM.MeetinghouseWebcast.UI.Views.Shell.ShellSignIn.SignIn()

But no support anywere or notifications on problems with the server.

Also the download link gives an error:
502 - Web server received an invalid response while acting as a gateway or proxy server.

There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.


Please fix and please provide info on who to contact when there are server problems.

hdarre wrote:Please fix and please provide info on who to contact when there are server problems.

Welcome to the forum. I know it can be frustrating when systems are not working and time is running out -- it's getting well into the evening in Denmark.

You can find a lot of helpful information on the wiki at Answers about Meetinghouse Webcast. If the troubleshooting steps there don't help, the Support section at the end tells you whom to contact for help. Note that the Global Service Desk is not open on Sunday, so if you need to contact them, you should probably do so soon.

hdarre wrote:Have tried the most of the day to connect to the Meetinghouse Webcast, as we were going to transmit a Stake Conference meeting to a long distance unit.
when I try to connect I get an error message:

The GSD, and the Engineers are aware of the issue and actively working on right now.

Primary and secondary webcast communicator streams,

on Sat a.m., 18Jun2011, we had similar issues with Meetinghouse Webcasts
We had done several tests earlier in the week with the new 3.0.1 version of the desktop/laptop Meetinghouse Webcast and ran tests with Webcast Communicators most of Friday and had no issues until Saturday a.m when we went live, but we were blessed that one (1) of our webcast communicator streams ran smoothly for the entire time of the event

Primary and secondary backup webcast communicator streams, (each went to a different ISP), were started at about 08:40 a.m., Eastern Daylight Saving Time UTC/GMT-5 (EDST) the secondary stream ran until about 11:32 a.m. (EDST) with no issues

The primary webcast communicator stream could not be restarted and the third backup laptop Meetinghouse Webcast stream would not start and returned a similar error message as posted by "hdarre" (#1)

The issue that both hdarre and pete.arnett was on Saturday morning were because the Meetinghouse Webcast application server was down due to a problem caused because of an OS update that accurred as part of a regular schedule maintainence. The engineers has it back up and running later that afternoon.

gdgudmundson wrote:The issue that both hdarre and pete.arnett was on Saturday morning were because the Meetinghouse Webcast application server was down due to a problem caused because of an OS update that accurred as part of a regular schedule maintainence. The engineers has it back up and running later that afternoon.

Perhaps scheduling future maintenance midweek rather than on a weekend (when that server is most heavily used for webcasting) or having a page with the current server status/planned maintenance would be useful.

Aaron Z

I am getting this same error right now, when trying to login. I guess server maintenance?


System.ServiceModel.ServiceActivationException: The requested service, 'https://webcast.ldschurch.org/Services/Webcasting.svc' could not be activated. See the server's diagnostic trace logs for more information.

Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory factory, WebException responseException, ChannelBinding channelBinding)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Lds.CM.MeetinghouseWebcast.Shared.Services.Contracts.Webcasting.V1.IWebcastingService.Logon(LogonRequest request)
at Lds.CM.MeetinghouseWebcast.Shared.Services.Contracts.Webcasting.V1.WebcastingServiceDynamicProxyWrapper.Logon(LogonRequest )
at Lds.CM.MeetinghouseWebcast.UI.Business.Security.Logon(String username, String password, List`1& availableAuthRequestAgents)
at Lds.CM.MeetinghouseWebcast.UI.Views.Shell.ShellSignIn.SignIn()

abcampa,

This is actually a current problem with the 2.1 version of the software that we are aware of and we are working to resolve the issue. If you need a resolution right away you can upgrade to the 3.0 version. You can find the download @ http://webcast.ldschurch.org/clientdownload.

Thanks,

Gordon

We were able to resolve the issue mentioned above. You should now be able to login with the 2.1 client. Thanks for reporting the issue!

Gordon