file with cmd and bat no longer run

[Arch Willingham]

If I try to run a file with an extension of either .cmd or .bat, it just
pops back with:

C:\batch>eventlogs

C:\batch>?e
'?e' is not recognized as an internal or external command, operable program
or batch file.


This is on a Terminal Server machine (win2000). I have tried changing the
file association but it will not let you.
Any ideas?

Arch

 

[Mark V]

Arch Willingham wrote in

If I try to run a file with an extension of either .cmd or .bat,
it just pops back with:

C:\batch>eventlogs

C:\batch>?e
'?e' is not recognized as an internal or external command,
operable program or batch file.


This is on a Terminal Server machine (win2000). I have tried
changing the file association but it will not let you.
Any ideas?

Those batch files may be locked-out (on a TS machine). Have you asked
the administrors?

 

[Arch Willingham]

I am the administrator. I have full admin permissions.

 

[Mark V]

Arch Willingham wrote in

Arch Willingham wrote in

If I try to run a file with an extension of either .cmd or
.bat, it just pops back with:
C:\batch>eventlogs [ ]
This is on a Terminal Server machine (win2000). I have tried
changing the file association but it will not let you.
Any ideas?

Those batch files may be locked-out (on a TS machine). Have you
asked the administrors?

I am the administrator. I have full admin permissions.

Oops. I'd start with
assoc .bat
assoc .cmd
ftype batfile
ftype cmdfile
to see what may be up in File Associations.

And entering a SET P at a cmd prompt should show
".BAT" and ."CMD" in the
PATHEXT=
variable.

I've no notion about "eventlogs" but something is certainly weird and
it might just be the associations. I assume a full A-V scan and a
check that cmd.exe is correct for the SP level. You might also check
in HKCU\software\classes\ to be sure something account-specific
hasn't been applied there. You have tried an alternate Admion.
account already?

Once you pin it down it may be you need to make a global change
(change user install) perhaps... I've only ever worked with TS on
NT4 though.

 

[Vera Noest [MVP]]

Arch Willingham wrote in

Arch Willingham wrote in

If I try to run a file with an extension of either .cmd or
.bat, it just pops back with:
C:\batch>eventlogs [ ]
This is on a Terminal Server machine (win2000). I have tried
changing the file association but it will not let you.
Any ideas?

Those batch files may be locked-out (on a TS machine). Have
you asked the administrors?

I am the administrator. I have full admin permissions.

Oops. I'd start with
assoc .bat
assoc .cmd
ftype batfile
ftype cmdfile
to see what may be up in File Associations.

And entering a SET P at a cmd prompt should show
".BAT" and ."CMD" in the
PATHEXT=
variable.

I've no notion about "eventlogs" but something is certainly
weird and it might just be the associations. I assume a full
A-V scan and a check that cmd.exe is correct for the SP level.
You might also check in HKCU\software\classes\ to be sure
something account-specific hasn't been applied there. You have
tried an alternate Admion. account already?

Once you pin it down it may be you need to make a global change
(change user install) perhaps... I've only ever worked with TS
on NT4 though.

This migth at least explain why you can't change the file
associations:

257592 - Changes in File Types and File Association Features in
Windows 2000 and Windows Server 2003
http://support.microsoft.com/?kbid=257592

 

[Philip Nunn]

Did you edit the group policy? Under User>Admin templates>system there is a
setting to turn off CMD and BAT files. It will also mess us script
processing if you have enable this setting. you may want to check it out.

Philip Nunn

Arch Willingham wrote in

Arch Willingham wrote in

If I try to run a file with an extension of either .cmd or
.bat, it just pops back with:
C:\batch>eventlogs [ ]
This is on a Terminal Server machine (win2000). I have tried
changing the file association but it will not let you.
Any ideas?

Those batch files may be locked-out (on a TS machine). Have
you asked the administrors?

I am the administrator. I have full admin permissions.

Oops. I'd start with
assoc .bat
assoc .cmd
ftype batfile
ftype cmdfile
to see what may be up in File Associations.

And entering a SET P at a cmd prompt should show
".BAT" and ."CMD" in the
PATHEXT=
variable.

I've no notion about "eventlogs" but something is certainly
weird and it might just be the associations. I assume a full
A-V scan and a check that cmd.exe is correct for the SP level.
You might also check in HKCU\software\classes\ to be sure
something account-specific hasn't been applied there. You have
tried an alternate Admion. account already?

Once you pin it down it may be you need to make a global change
(change user install) perhaps... I've only ever worked with TS
on NT4 though.

This migth at least explain why you can't change the file
associations:

257592 - Changes in File Types and File Association Features in
Windows 2000 and Windows Server 2003
http://support.microsoft.com/?kbid=257592

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---