Shoutbox

Chat LOg viewer Broken - Printable Version

-Shoutbox (https://shoutbox.menthix.net)
+-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58)
+--- Forum: Messenger Plus! for Live Messenger (/forumdisplay.php?fid=4)
+---- Forum: WLM Plus! Bug Reports (/forumdisplay.php?fid=7)
+----- Thread: Chat LOg viewer Broken (/showthread.php?tid=98730)

Chat LOg viewer Broken by pablindo on 12-16-2011 at 12:58 PM

What happened? My Chat Log viewer is showing the follow message: The HTTP service located at https://service.msgplus.net/MsgPlusService/MsgPlusOnLineLogs.svc is too busy.

I dont know what to do.


RE: Chat LOg viewer Broken by si3rra on 12-17-2011 at 12:43 AM

MsgPlusOnLineLogs Service


You have created a service.

To test this service, you will need to create a client and use it to call the service. You can do this using the svcutil.exe tool from the command line with the following syntax:



svcutil.exe https://service.msgplus.net/MsgPlusService/MsgPlusOnLineLogs.svc/mex

This will generate a configuration file and a code file that contains the client class. Add the two files to your client application and use the generated client class to call the Service. For example:


C#

class Test
{
    static void Main()
    {
        MsgPlusOnLineLogsClient client = new MsgPlusOnLineLogsClient();

        // Use the 'client' variable to call operations on the service.

        // Always close the client.
        client.Close();
    }
}



Visual Basic

Class Test
    Shared Sub Main()
        Dim client As MsgPlusOnLineLogsClient = New MsgPlusOnLineLogsClient()
        ' Use the 'client' variable to call operations on the service.

        ' Always close the client.
        client.Close()
    End Sub
End Class


RE: Chat LOg viewer Broken by CookieRevised on 12-17-2011 at 03:43 AM

si3rra,

That is just the output of that link. It doesn't provide anything usefull*.
The OP is not making his own client. The message he shows is a genuine error. Which needs to be explained and fixed by Yuna because their online service is obviously faulty.

(*it would be the same as showing the source of the "Forum is too busy" page when there is a forum overload here)


;)