Finally...

Marginal progress.  I didn't mean to take such a negative tone
earlier.  My patience was wearing thin after a couple days of
struggling to get everything built and configured.

I mean django is sweet but witango allows you to just drop everything
into place (very nice).

Anyway, now I'm fighting with a data source problem.  I have FM Pro 6
open and I'm running apache and witangod.  In the dev studio I add the
FM data source and create a page but now I can't connect to the data
source.  I had OBDC working on a Linux box a few weeks ago but I'm
trying to get FM working on a Mac.

Here is what the logs say:
13/03/2008      01:33:35     [Datasource] No existing connection to
the data source found, creating a new connection. DSN: FMPm.#; User: ;
13/03/2008      01:33:35     [Error] -110 The specified data source
cannot be found. play.fp5
13/03/2008      01:33:35     [Datasource] Unable to open a connection
to FMPm.# due to an unknown error during connection
13/03/2008      01:33:35     [Datasource] Total Connection in
Datasource Pool: 0; Max connections for the host: 0; Current
connections in use for the host:
13/03/2008      01:33:35     [Error] -4 Unable to connect to the
specified data source. Verify that data source is properly configured
and that database server is online.

So... I can't connect to the data source.  I've got my witango server
running and I have FM open.  I think this has to do with 'user name'.
I don't think Apple Events knows that I'm the same user running
witangod (even though I started witangod with a "-u myusername"
option.

Anyone have suggestions on where I start looking to solve this problem?

Thanks!
.cpb

On Thu, Mar 13, 2008 at 12:23 AM, Colin Bell <[EMAIL PROTECTED]> wrote:
> Thanks Bill,
>
>  At least I have an idea where to start looking now.  I don't really
>  know what to make of this but I'll keep poking.
>
>  I'm newish to witango and I'm trying to work in an unconventional
>  environment.  Right now I just don't know where to start looking.  I
>  wish I could just use django and forget this middleware crud (circa
>  2004).  Unfortunately, that's not possible right now.
>
>  At this point it just feels like I have a huge monolithic piece of
>  software that is angry and refuses to behave.
>
>  Thanks for (at least) a little guidance.

-- 
Colin Bell <[EMAIL PROTECTED]> [+15195911384]
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to