Title: Re: Witango-Talk: SourceForge project updated: CronTabEdit file posted
Jason Pamental at [EMAIL PROTECTED] wrote:
It's been a while since I last posted on the topic, but I just got around to posting the source file for the CronTab Edit app I created on SourceForge.
Just had an
Title: Tango 2000 and Windows Server 2003
Hello All,
We just got a new Win Server 2003 box for our Tango 2000 Apps.
T2K installed ok and I copied across a small App as a test but for some reason I get the 'The page cannot be found' when I try to run any taf file.
Is there anything I
Title: Tango 2000 and Windows Server 2003
Hi Ciaran,
Have you added and set
a Web Server Extension in IIS (t4iis.dll) to allowed for the Tango2000 plugin?
Mike.
From: Ciaran Rudden
[mailto:[EMAIL PROTECTED]
Sent: 09 March 2006 13:19
To: witango-talk@witango.com
Subject:
Ciaran,In the IIS control application you need to create an allowed application for Tango (or Witango) to be allowed to process- the installer for Tango doesn't do this. I know there were posts about this - I'll see if I can find the one with the pictures...Jason -Jason PamentalDirector of Web
I checked to make sure port 3306 is open, changed the server IP from old to new IP address. save. reboot., and still can't connect to database. Very perplexingOn Mar 8, 2006, at 10:44 PM, Customer Support wrote:Roland,It will look something like this in your odbc.ini file. Make sure you specify
Roland,Can you connect with the MySQL admin program from your machine to the colo dev server? If so, then it's probably a config thing on your machine - otherwise it might be blocked on the other end. See if the colo facility blocks traffic on certain ports, or if maybe it's blocked on the dev
Thanks a Million Jason, adding the Web service extension did the trick.
Working away fine now.
Thanks to all who replied
Ciaran Rudden
IT Section
Meath Co.Council
-Original Message-
From: Jason Pamental [mailto:[EMAIL PROTECTED]
Sent: 09 March 2006 14:32
To:
FYI
If you are running other technologies on Windows 2003 server (ASP.NET, PhP,
Cold Fusion) it will conflict with WiTango. The workaround for this to put each
server technology in its own application pool in IIS. This will help IIS
differentiate between the different ISAPI filters.
Rick
Thanks for that Rick - I hadn't run into that problem with Witango -
only with running sites on .NET 1.1 and 2.0. Hadn't thought about the
implications of that with Witango...
Jason
(of course, I try not to run them on the same box anyway, but that's
a whole other discussion, isn't it? :P
Glad you're squared away - good to look at Rick's suggestion too, if
you are going to run anything else besides Tango apps.
Jason
-
Jason Pamental
Director of Web Services
North Sails
Office: 401.643.1415
Fax: 401.643.1420
Mobile: 401.743.4406
Email: [EMAIL PROTECTED]
On Mar 9,
- can connect with jdbc admin tool - port scan shows 3306 is open, so no firewall issues- mysql permissions allow connection from the user coming from host=%- nothing on the server has changed, just moved to new IP address- odbc connection has new IP address in itpuzzled.did a recent OS X
Title: Re: Witango-Talk: what port for odbc?
Usually the colo will require a VPN connection before you a access. They are not going to leave that port open for everyone.
You should contact you colo and they should give you support on this.
on 3/9/06 10:13, Jason Pamental at [EMAIL PROTECTED]
actually, not the colo, not the server, not the routerI booted from my latest backup (Sunday) and witango has no problems connecting to the datasource. I'm thinking the latest security update broke something. On Mar 9, 2006, at 7:55 AM, Dan Stein wrote: Usually the colo will require a VPN
Roland,Maybe it just tweaked a security setting - check the permissions on the ODBC files and compare between what you seen booting from the backup and the current setup. Or just try 'repair permissions' on the new setup first?Jason -Jason PamentalDirector of Web ServicesNorth SailsOffice:
Roland,
This is suddenly very interesting to me: I have a server for which
witango pages are not served when clients are outside the LAN, but for
clients from non-routable IPs, the Witango pages work fine. HTML pages
work fine from both places. I can't think of any changes I made to IIS,
other
good theory, but repairing permissions/comparing them does nada. Looking at my log of updates, the backup copy of the startup volume predates the latest security patch. That's my main suspect now. Has anyone else applied the latest OS X security patch?Is there a list of ODBC-related files that I
Hi Bill,
Your issue sounds like a router/firewall issue
Check them to see if you have a NAT set up to allow ANY External IP to
INTERNAL IP
Ben
-Original Message-
From: Bill Downall [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 09, 2006 8:54 AM
To: witango-talk@witango.com
Subject:
ok, so my problem is that the odbc drivers can't load after updating my desktop to 10.4.5 latest security update. Could be coincidence, but that looks like the culprit. The files still exist, but when I run the iODBC test command, I get:1: SQLDriverConnect = [iODBC][Driver Manager]NSLinkModule()
I would download the latest ODBC manager from openlinksw.Then try, also, there is a better version of iodbc, out, based on 3.52.4, that has some mac bug fixes. The only thing, you have to compile it yourself.I am running 10.4.5, and I have the latest ODBC SDK/manager from openlinksw installed,
I don't necessarily use the openlink drivers, but I use the manager.I don't know how robust they are, but I have used these for a LONG time in development, and have had zero problems.http://www.actualtechnologies.com/product_opensourcedatabases.phpAnd they work with the above openlink manager, and
20 matches
Mail list logo
