The XML might be messed up in such a way that it looks fine from a text editor, but is invalid. You could try opening the TAF in the Dev Studio (on OS X TAFs with invalid XML don't open in the Studio). You could also try taking a simple TAF from a server that is known to work and trying it on your new server.
- Jeff
Hey all,--
I have a strange problem here. Just finished a brand new install on a Win 2K box with IIS 5 and WiTango. When attempting to hit some taf files on the server I get an "HTTP 500 Internal Server Error" in the browser. After checking the tango log, I see the request for the taf is indeed sent to the app server, but WiTango reports the following in the log
[Error] -3 The application file was either missing or invalid. /test.taf
The strange part is, I can serve up a .tml file that is sitting in the exact same directory as the test.taf file. My question is, why is WiTango processing .tml files and not .taf files? I opened up the .taf in a text editor to see if it was corrupt, but it seemed to be fine. Anyone got any ideas?
Thanks.
Mike
Jeff Bohmer VisionLink, Inc. _________________________________ 303.402.0170 www.visionlink.org _________________________________ People. Tools. Change. Community. ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
