Forum Discussion

alex_hokanson's avatar
alex_hokanson
Occasional Contributor
12 years ago
Solved

Can't find Description.tc.log

What causes this sort of error.  Whenever I run a test on one of my machines, I get this after the test finished and then I dont' know if the test passed, failed, etc.  The project suite that I am wor...
  • hlalumiere's avatar
    hlalumiere
    11 years ago
    To be honest, there are versions of every file IO API that supports longer path name. That limitation was essentially lifted after Windows XP. You can call the unicode version of the API by pre-pending "\\?\" to your path. C:\TestPath becomes \\?\C:\TestPath. That raises the limit to 32K length.  This might however be incompatible with some implementations if you supply it externally, the issue should be solved internally, by Smartbear.
alex_hokanson's avatar
alex_hokanson
Occasional Contributor
11 years ago
Ok, I found the real cause. 



Windows has a file path length limit: 



"In the Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path isMAX_PATH, which is defined as 260 characters."



from: http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx



So TestComplete could save the path via relative path in the configuration files, but when executing various read/write operations on specific files Windows would silently error and then TestComplete would throw the error that it can't find the Description.tcLog file.  I figured I would post a real solution after this ocurred to a coworker of mine.