below...
Do you have an T3 Editor on the Windows box? If so, try using the SQL Query
window from the editor with the appropriate data source to make a
connection. If it can, you should then be able to eliminate the Mac side as
the source of the problem.
Yep, that's what I was saying - I try a SQL query from the editor on
this datasource (which is definitely a tcp/ip dsn) and I can see it
access via port 8682, loads the user in the Butler Users window, and
then hangs. When we delete the database from the Public Databases
folder, it gives us the appropriate error. So we know that we are
definitely taking to Butler on the Mac. But that's about all we know
at present.
You mentioned that you can see the attempt at a connection in the Users
window of Butler. It is a TCP/IP port that is set up and not program
linking, right?
Yep, seems to be connecting from the Tango editor Ok when I request
the data tables to load.
Also where was the original taf file created? I seem to
recall problems with taf files that were originally set up with Program
Linking rather than TCP/IP after they were moved to a Windows box.
Maybe that's where the problem is - I'll create an entirely new taf
using the Win T3 editor with a tcp/ip dsn and a new database on the
Mac and see how that goes.
The
Butler version that was on that promo CD did not have any limitations on
connections to the best of my knowledge.
I certainly haven't seen any readme about any limitations on the
license apart from the number of concurrent users (which I know to be
10).
One other thing to look at is whether the appropriate port is opened to the
machine running Butler. I think it needs port 8682 and of course this should
be set up in both the datasource, and on the port in Butler. Also make sure
that the port is activated on Butler.
yep -using that and that seems to be working (one way anyway -
sending control data but maybe not receiving data back to the Win box
I don't think the references to the old P.SQL drivers would cause this
problem. Since Pervasive came into the picture in 98 I have always had both
P.SQL and Butler drivers installed on my Win boxes.
well I'll set up an access db and test it with a local datasource as
well and get back to you.
Hope this helps,
Steve Smith
Skadt Information Solutions
Office: (519) 624-4388
GTA: (416) 606-3885
Fax: (519) 624-3353
Cell: (416) 606-3885
Email: [EMAIL PROTECTED]
Web: http://www.skadt.com
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:owner-witango-talk@;witango.com]On Behalf Of Garth Penglase
Sent: October 23, 2002 8:16 AM
To: Multiple recipients of list witango-talk
Subject: RE: Witango-Talk: T3 tcp/ip db connection (licensing issue?)
I don't think so, since it includes demos using PSQL datasources, but
I'll have a look at the info on the Tango CD and see if I can find
any clues as to whether it is licensed only for access. I have been
using the Mac 3.52 promo version only with Butler so I don't know if
it has limitations otherwise.
The installer seems to make references to other ODBC sources I think.
When I use the Windows Tango 3.52 Editor that comes on the CD to open
a taf with the Butler tcp/ip link as the datasource, I can see the
Butler drivers making a connection with Butler on the Mac but then
Butler seems to time out (something times out) because everything
just sits there - whatever user account was used to open the taf in
> the editor and make the load request is shown in the Butler Users
> table and there are connections made, but it hangs from there. We did
> test the connection by deleting the datasource and when we requested
it to load the tables it gave an appropriate error (saying that it
couldn't connect to the datasource) so the connection from the Win 2k
box via Butler tcp/ip on the standard Butler port seems to be working
> - I have a feeling that it may be a port mapping problem between the
two machines since the mac is sitting on the internal network and is
reached externally (form the Internet) by mapping incoming requests
to port 81 for http and that has presented some problems when ftping
to the machine from certains networks - any ideas on how we can test
that?
I'll make a connection to a local dsn (say an access db) and see how
it goes. We did load the PSQL demos but we were having the stanza
problem at that time so we un-installed the whole tango installation
and re-installed a few times, the last couple of times without the
PSQL demos so haven;t tested it with them I don't think.
Another point to note is that the uninstaller did not remove the
references to the PSQL drivers in the ODBC panel in Win2k - is this,
in some way, a possible cause of the problem would you think? It is
annoying - we'll re-install them and see if they work and then try to
un-install them separately - any tips on that?
thanks Steve
Garth
>Any chance you're using a Tango for Access product? Yes there
was a release
>of a product that was similar to Tango for Filemaker but for
Access and the
>windoze platform. I can't remember if it was a 2.x product or
3.x. I used to
>have a list of the serial number prefixes which identified the
exact version
>of the product but I don't know where it is.
>
>Other things to check is that you've set up a system data source, etc. I
>know that the Win Butler driver works under Win2000 because I've used it.
>
>Will that same version connect to any other data source?
>
>Hope this helps,
>
>Steve Smith
>
>Skadt Information Solutions
>Office: (519) 624-4388
>GTA: (416) 606-3885
>Fax: (519) 624-3353
>Cell: (416) 606-3885
>Email: [EMAIL PROTECTED]
>Web: http://www.skadt.com
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:owner-witango-talk@;witango.com]On Behalf Of Garth Penglase
>> Sent: October 22, 2002 9:20 PM
>> To: Multiple recipients of list witango-talk
>> Subject: Witango-Talk: T3 tcp/ip db connection (licensing issue?)
>>
>>
>>
>> --
>> Hi everyone,
>> this is particularly for those who have been around tango for
>> quite a while.
>>
>> I recently installed Tango 3.52 promo version (10 user version) under
>> Win 2k. Originally I was getting stanza probs which we finally were
>> able to resolve (by fluke only though the suggestions from historical
>> and recent entries on this list were useful).
>>
>> Now I am trying to connect from the Win2k box using Butler WIN 32
>> drivers to a Mac running Butler but when running the taf which uses
>> the tcp/ip DSN I get this message:
>>
>> An error occurred while processing your request:
>>
>> Position: Insert
>> Class: Internal
>> Main Error Number: -109
>>
>> This type of data source is not supported by the server license.
> >
>> Position: Insert
>> Class: Internal
>> Main Error Number: -4
>>
>> Unable to connect to the specified data source.
>> Verify that data source is properly configured and that database
>> server is online.
>>
>> I'm sure I remember having connected via tcp/ip from one mac to
>> another using the same license (actually the Mac version of the
>> software off the same CD) so I think the server license message is
>> erroneous. But am I wrong? Is it indeed not possible using this
>> license?
>>
>> thanks
>> Garth
>>
________________________________________________________________________
>> TO UNSUBSCRIBE: send a plain text/US ASCII email to
[EMAIL PROTECTED]
> > with unsubscribe witango-talk in the message body
> >
> >
>
>________________________________________________________________________
>TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
--
________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
--
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
