Bumping this ... anyone can help please?

Jenny

-----Original Message-----
From: Jenny Gavin-Wear [mailto:[email protected]]
Sent: 21 July 2009 13:17
To: cf-talk
Subject: RE: Coldfusion 7 and Helm 3

Hi Mike,

Many thanks for your reply, great info.

I think I'm 99% of the way to getting it all setup.

I got the admin API:
http://russ.michaels.me.uk/index.cfm/2007/9/29/ColdFusion-Administrator-API-
Web-Service
and have it configured in Helm.

i also set my IPs in the config.cfm and test that the AdminAPIWrapper.cfm
can be accessed (ran it from a browser to check the path).

However, when I try to add a CF DSN I get
Unable to save DSN. Your IP (127.0.0.1) is not allowed!

The Helm 3 errors logs show:
2009-07-21 13:03:08 ColdFusionDSN.AddCFDSN 000000000002: Unable to save DSN.
Your IP (127.0.0.1) is not allowed!{0}
2009-07-21 13:03:08 Website.IWeb_Execute 000000000002: Unable to save DSN.
Your IP (127.0.0.1) is not allowed!{0}
2009-07-21 13:03:08 cCFDSN.AddEx 000000000002: Unable to save DSN. Your IP
(127.0.0.1) is not allowed!{0}
2009-07-21 13:03:08 HELM:CCFDSN::Add 000000000002: Unable to save DSN. Your
IP (127.0.0.1) is not allowed!{0}

I found a posting about adding the IPs to an ip.cfm file, but I can't see
this file anywhere in the CFIDE path. (I even tried creating one and that
didn't help.)
http://forums.webhostautomation.com/pda/index.php/t-22591.html

I can't see anywhere in the CFadmin to add IPs other than the debug and
sandbox configs.

Any ideas where I'm going wrong please?

Also, if you have any further info on how you config'd the sandbox, it would
be much appreciated.

Thanks,

Jenny Gavin-Wear
Fast Track Online
Tel: 01262 602013
http://www.fasttrackonline.co.uk/


-----Original Message-----
From: Mike Kear [mailto:[email protected]]
Sent: 17 July 2009 14:59
To: cf-talk
Subject: Re: Coldfusion 7 and Helm 3



You can set it up in a variety of ways.  We use HELM and CF8 nowdays
but we were using HELM and CF7 not so long ago.

We have some tags disabled by default, but they can be enabled on
request.  When we are requested, we set up a sandbox for the user
requesting it   There are only a couple of functions we will never
enable for anyone, and a few mappings that arent available for anyone
(e.g. "coldspring" and "Modelglue") but once the clients have their
own sandbox, they have a set up very close to their own server (at
least in terms of functionality anyway).

First read the HELM documentation for how to set it all up.

Make sure you have the latest patches for the HELM control panel.  The
first few months of our using HELM to create coldfusion datasources
were error prone - we had to run a function on the database created to
fix a cursor error.   There was a bug in the HELM-Coldfusion
interaction but its fixed now.

Broadly, though, the HELM control panel is splendid.  There are very
few things users want to set up for their sites that arent handled by
HELM.     I think back 5 or 6 years to the control panel we were using
then, and the switch to HELM eliminated nearly all of our support
calls, because clients could set up almost anything they wanted
themselves, any time they liked.

Cheers
Mike Kear
Windsor, NSW, Australia
Adobe Certified Advanced ColdFusion Developer
AFP Webworks
http://afpwebworks.com
ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Want to reach the ColdFusion community with something they want? Let them know 
on the House of Fusion mailing lists
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325004
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to