# Error: Failed to find anything that looks like a service in module XXXXX

**URL:** <https://discourse.nameko.io/t/error-failed-to-find-anything-that-looks-like-a-service-in-module-xxxxx/156>\
**Category:** googlegroup\
**Created:** [October 21, 2016, 2:42am UTC](https://discourse.nameko.io/t/error-failed-to-find-anything-that-looks-like-a-service-in-module-xxxxx/156 "2016-10-21T02:42:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matthew\_Versaggi](https://avatars.discourse-cdn.com/v4/letter/m/8dc957/32.png) [@Matthew\_Versaggi](https://discourse.nameko.io/u/Matthew_Versaggi)\
**Post date:** [October 21, 2016, 2:42am UTC](https://discourse.nameko.io/t/error-failed-to-find-anything-that-looks-like-a-service-in-module-xxxxx/156/1 "2016-10-21T02:42:54Z")

</div>

I'm trying to run nameko on a windows 10 server, using RabbitMQ (and  
Erlang) for the messaging but any getting stuck at "HelloWorld" with the  
following error msgs:

c:\Users\Matthew\workspaces\optum\microservices\nameko\>\*nameko run  
helloworld\*  
\*Error: Failed to find anything that looks like a service in module  
'helloworld'\*

c:\Users\Matthew\workspaces\optum\microservices\nameko\>nameko shell  
\*Nameko Python 2.7.11 |Anaconda 2.3.0 (64-bit)| (default, Jun 15 2016,  
15:21:11) [MSC v.1500 64 bit (AMD64)] shell on win32\*  
\*Broker: amqp://guest:guest@localhost\*  
\*In [1]:\*

In this case I didn't get the expected "\*\>\>\>\*" prompt.

I have the RabbitMQ admin UI up, can log in and peruse the connections,  
channels, exchanges and queues.

I've been interrogating the web for clues for hours now, any idea of what  
is going wrong would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![David\_Szotten](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.nameko.io/david_szotten/32/6_2.png) [@David\_Szotten](https://discourse.nameko.io/u/David_Szotten)\
**Post date:** [October 21, 2016, 8:16am UTC](https://discourse.nameko.io/t/error-failed-to-find-anything-that-looks-like-a-service-in-module-xxxxx/156/2 "2016-10-21T08:16:52Z")

</div>

Hi Matthew,

I'm afraid none of the core devs use windows, and nameko is only tested on  
linux (+developed on os x). windows support isn't an explicit non-goal, but  
it's very possible that we are using apis or libraries that don't support  
windows.

It would be great if we could get to a better windows story, but i'm not  
sure how feasible that is in the sort term, unless someone with more  
windows experience is able to help. Would you consider trying a linux  
virtual machine or docker image?

Best,  
David

> **···**
>
> On Friday, 21 October 2016 03:42:54 UTC+1, Matthew Versaggi wrote:
> 
> > I'm trying to run nameko on a windows 10 server, using RabbitMQ (and  
> > Erlang) for the messaging but any getting stuck at "HelloWorld" with the  
> > following error msgs:
> > 
> > c:\Users\Matthew\workspaces\optum\microservices\nameko\>\*nameko run  
> > helloworld\*  
> > \*Error: Failed to find anything that looks like a service in module  
> > 'helloworld'\*
> > 
> > c:\Users\Matthew\workspaces\optum\microservices\nameko\>nameko shell  
> > \*Nameko Python 2.7.11 |Anaconda 2.3.0 (64-bit)| (default, Jun 15 2016,  
> > 15:21:11) [MSC v.1500 64 bit (AMD64)] shell on win32\*  
> > \*Broker: amqp://guest:guest@localhost\*  
> > \*In [1]:\*
> > 
> > In this case I didn't get the expected "\*\>\>\>\*" prompt.
> > 
> > I have the RabbitMQ admin UI up, can log in and peruse the connections,  
> > channels, exchanges and queues.
> > 
> > I've been interrogating the web for clues for hours now, any idea of what  
> > is going wrong would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![coddericko](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.nameko.io/coddericko/32/16_2.png) [@coddericko](https://discourse.nameko.io/u/coddericko)\
**Post date:** [April 21, 2018, 4:33pm UTC](https://discourse.nameko.io/t/error-failed-to-find-anything-that-looks-like-a-service-in-module-xxxxx/156/3 "2018-04-21T16:33:47Z")

</div>

My suggestion is to use a docker as light VM to Linux. If you need a  
dockerfile for this, let me know...

> **···**
>
> On Thursday, October 20, 2016 at 7:42:54 PM UTC-7, Matthew Versaggi wrote:
> 
> > I'm trying to run nameko on a windows 10 server, using RabbitMQ (and  
> > Erlang) for the messaging but any getting stuck at "HelloWorld" with the  
> > following error msgs:
> > 
> > c:\Users\Matthew\workspaces\optum\microservices\nameko\>\*nameko run  
> > helloworld\*  
> > \*Error: Failed to find anything that looks like a service in module  
> > 'helloworld'\*
> > 
> > c:\Users\Matthew\workspaces\optum\microservices\nameko\>nameko shell  
> > \*Nameko Python 2.7.11 |Anaconda 2.3.0 (64-bit)| (default, Jun 15 2016,  
> > 15:21:11) [MSC v.1500 64 bit (AMD64)] shell on win32\*  
> > \*Broker: amqp://guest:guest@localhost\*  
> > \*In [1]:\*
> > 
> > In this case I didn't get the expected "\*\>\>\>\*" prompt.
> > 
> > I have the RabbitMQ admin UI up, can log in and peruse the connections,  
> > channels, exchanges and queues.
> > 
> > I've been interrogating the web for clues for hours now, any idea of what  
> > is going wrong would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![Chris\_Platts](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@Chris\_Platts](https://discourse.nameko.io/u/Chris_Platts)\
**Post date:** [May 10, 2018, 10:02am UTC](https://discourse.nameko.io/t/error-failed-to-find-anything-that-looks-like-a-service-in-module-xxxxx/156/4 "2018-05-10T10:02:04Z")

</div>

Hi,

I'm using nameko successfully on Windows 7 and Server 2016R2. It didn't  
require any special treatment to get working, either.

There's not much to go on here to help debug, but thought I'd drop in to  
say it should work fine!

Try developing inside a virtualenv. That'll keep everything local to your  
application. Something like:

pip install virtualenv  
mkdir myproject  
cd myproject  
virtualenv env  
env\Scripts\activate.bat

pip install nameko  
\<write your service.py\>

nameko run service

Cheers,

Chris