Its ok.
If you ONLY have 1 IIS server, then you are NOT doing DNS load
balancing. If your IIS server is at IP 10.0.1.1, then your domain
points to it, (www.mysite.com 10.0.1.1) then the is no dns load
balancing. When the request comes into your IIS server, the witango
plugin looks at the
Robert,
I don't mean to question, but I would like to understand.
I don't have IIS running on the second server. I don't understand DNS load
balancing, but are you running all of your Witango websites on both of the
servers that you are running IIS and the Witango Client and then using DNS
Load B
In IIS, you set the home directory as a share on another computer.
You set the path using UNC notation, like \\server1\webfiles\mysite
or whatever. This path must point to same files for the IIS server,
and all witango services. I have a setup with 7 servers for instance.
2 IIS servers with
Robert,
Where in Windows, IIS or Witango do you indicate or use this? My setup is
working correctly without this.
Unless:
Maybe because I have shares setup on each server with Administrative Rights
as follows:
\\ics9\wwwroot
\\ics14\wwwroot
Thanks,
Steve
-Original Message-
From: Robert
Both servers need to have access to the files, and the web directory,
and the path to the files must be the same for both servers. LIke:
\\Server1\webfiles\mysite\
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph
Hi,
I ran a test with the following setup.
Server A will run one Witango service and the databases will reside here.
Server B will run IIS, Witango Client and one Witango service
Server B contains all the Witango and web files in the wwwroot folder. IIS
is setup to run this website.
Server A do
Before you move to nine you need to make sure that you are not using
the "show" DB technique for ODBC.
If you have DB A with data in it and DB B with no data but references
to the A tables and you connect through B then you are better off
sticking with 8 until the update to the ODBC plug in
This bodes the question then, why did they cut off the only marketing
arm they had, the distributors and resellers?
As was stated by David the product is priced not to sell. With many
solutions out there at 1/5 the cost growing and thriving, humm
Ben
On Oct 5, 2007, at 10:38 AM, Roland
this is the crux of the matter. A small user base cannot support
much service or even development. Aggressive and smart marketing is
needed. Marketing in the large sense of strategic product and brand
marketing. Genius-in-a-box is not marketing.
On Oct 5, 2007, at 7:07 AM, Jesse Parker wr
Dan
I am using remote FMSA8 as data source via ODBC for 6 months. Have had
problems, not with Witango hanging, but that the FMSA does not
re-establish ODBC upon a reboot of the FMSA server hardware. FMSA says
ODBC is enabled but no connections can be made from any ODBC enabled PC
or app. U
You can reduce the probability of this occuring by reducing the
datasourcelife variable, what is it set to now?
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTE
Random thought based on complete ignorance:
* Have an error handler trap error -113 and then run a stored
procedure to have Oracle kill the connection from its side.
* Have an error handler trap error -113 and then run set the
DataSourceLife to immediately expire, and then reset it to norma
Sure, we have seen those too with FM7; 8 has resolved some of those
issues for us.
These are cases where something happens like a network hiccup that
kills the connection. This is definitely a case where the db
connection is not properly closed. It's also a situation that is
bound to hap
Witango is what it is.
I am in the same boat as David - the product does all I need it to do and has
for many years. If there wasn't another release of any kind it wouldn't cause
trouble for me.
As some of you know, I had the responsibility of supporting Tango for a few
years and take it from
Shannon,
There are know issues with xODBC and Filemaker 7-9 I am not sure if
they extend to JDBC but there are related to the FMP plug in in not
Witango as I can reproduce them with any ODBC connection to FMP.
I have been working for 1 year with FMI to resolve these.
We are close.
They are
OK, I'm going to take some of the suggestions I have seen here and
try this a different way. Is there any company, here on the list, that
can send in a consultant to look at our setup over a period of say, 3
days, make suggestions as to what we can improve, tell us what we may
have done wrong (p
An astute observation David, I like it.
Of course none of us can (or are trying to) speak for Phil, who by the way
graciously lets us rant and rave about him on "his" email list server. But if
you couple David's assessment with a previous post of mine, I think some things
come into perspective.
17 matches
Mail list logo
