search

MattRiddell / unimrcp

Automatically exported from code.google.com/p/unimrcp
Apache License 2.0
0 stars 0 forks source link

WSAStartup Issue During Agent Loading of unimrcpclient.xml #100

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The main error I am seeing is:

[WARN]   Failed to Create Wakeup Pipe: Either the application has not called 
WSAStartup, or WSAStartup failed.

This then seems to prevent the agents from being available later during the 
loading of the profiles.

As a background, I am attempting to develop an MRCP client using your libraries.

I chose to write my utility as a DLL library in VC++/Visual Studio 2005.

All of the UniMRCP functionality is wrapped into a single class.  I then wrote 
a small function to instantiate the object and synthesize a WAV file which is 
exposed via a .def file for easy reference.

I am testing this by calling this function via a simple VB6 form application, 
but am hitting a snag during loading of the agents during unimrcp_client_create.

I have attached the output of the logger instantiated using settings from the 
logger.xml file provided.  I have also attached the general project properties 
of my VS2005 DLL project for reference.

The "umc" project starts and executes as expected with no errors with the same 
configuration file, so I know it's not an environment issue.  However,  I seem 
to be running into trouble within my own application.

The configuration file I am using is actually included with the UniMRCP package 
(unimrcpclient.xml).

I'm happy to provide any other details or source code, but I figured the log 
might be enough as it seems I'm hitting a very simple roadblock...

Thanks,

Patrick McDonald

Original issue reported on code.google.com by p2mcd...@gmail.com on 20 Oct 2010 at 8:11

Attachments:

GoogleCodeExporter commented 9 years ago 
My apologies...  I had searched the Wiki for issues and then tried the search 
provided when entering a new bug, but it seems I didn't try the correct terms...

After searching for WSAStartup in the issue-search, I found an unrelated issue 
in which a contributor was told that WSAStartup was actually called internally 
by apr_initialize.  I had tried to "move" this function call (in other words, 
cut but never pasted) and thus I wasn't calling it at all.  What threw me, I 
suppose was that I could initialize the apr_pool_t without error.

My issue is solved and can be ignored.

Original comment by p2mcd...@gmail.com on 20 Oct 2010 at 8:20

GoogleCodeExporter commented 9 years ago

Original comment by achalo...@gmail.com on 21 Dec 2010 at 9:47