Error: The system cannot find the path specified

  • Thread starter Thread starter Girod Marc
  • Start date Start date
G

Girod Marc

Hello!

I am using IBM/Rational ClearCase on a Windows 2000 server.
This application has a scheduler which runs bat files actually feeding
themselves to perl.

One such "task" reports errors like:

"The system cannot find the path specified"

Running it in verbose mode, I get the following transcript excerpt:

C:\apps\atria\config\scheduler\tasks>.\sync_receive.bat -trace
entering DoCmd(cd)
in GetTmpdir() NT EVs:
TMP: C:\DOCUME~1\ccvobadmin_imn\Local Settings\Temp\2
TEMP: C:\DOCUME~1\ccvobadmin_imn\Local Settings\Temp\2
TMPDIR:
TEMPDIR:
The system cannot find the path specified.
[...]

If I set TMP and TEMP to D:\tmp, the error disappears.
So, my guess is that either the batch interpretor or perl is not happy
with the paths containing spaces and long names.
Is there some configuration setting to enable an automatic conversion
of Windows paths to DOS ones (partly in use with the "\DOCUME~1" part
above)?

Thanks for any assistance!
 
Same question as previously, with a new formulation:

I have two Windows 2000 servers.
On the one, in the login directory, if I give "dir /x" in the command
interpretor window, I get to see the short names generated for the
non-8dot3 file names.
Not on the other. Why not? Is this behaviour configurable, and where?
 
MG> Microsoft knowledgebase article 121007

One glitch: this behaviour (hashing the file names) is triggered by
the file creation, i.e. just enabling it is not enough to fix the
problem.
And, as the temp directory I am interested in is under the account
home directory, it is "in use" and I cannot rename it.
 
MG> And, as the temp directory I am interested in is under the account
MG> home directory, it is "in use" and I cannot rename it.

Deleted the profile as admin. Got back, it was recreated. The dir /x
is now fixed.
Not my original problem. Same symptoms. Argh.
 
Back
Top