Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

What would cause these errors?

vefatica

vefatica

May
13,817
211
ZZ in my old machine, networked with my new one. I get this (on the new machine).

Code: 
v:\> start \\zz\c$\Users\vefatica\Documents\Furnace.xlsm
TCC: (Sys) Access is denied.
 "\\zz\c$\Users\vefatica\Documents\Furnace.xlsm"

v:\> excel \\zz\c$\Users\vefatica\Documents\Furnace.xlsm
TCC: (Sys) The file cannot be accessed by the system.
 "C:\Users\vefatica\AppData\Local\Microsoft\WindowsApps\excel.EXE"

Both those commands work in CMD.

And if, in TCC, I do

Code: 
v:\> start \\zz\c$\Users\vefatica\Documents\

I get an explorer window and I can open the file in question by 2-clicking on it.
 
rconn said:
Those are Windows errors, not TCC.

Your CMD setup is apparently not the same as your TCC setup.
Click to expand...
What setup? Where do I go to set them up?

If I copy the file to the local machine I still can't START it with TCC and I can START it with CMD.
 
rconn said:
You would ensure the environments were identical and the user was the same. Did you try running CMD from TCC and vice-versa?

TCC absolutely, positively, cannot affect permission errors in Windows.
Click to expand...
Yes, I tried both with no success.

The same goes for other Office files and for EXCEL.EXE itself.

I have

Code: 
v:\> which /a excel
excel is an external : C:\Users\vefatica\AppData\Local\Microsoft\WindowsApps\excel.EXE
excel is an external : C:\Program Files\WindowsApps\Microsoft.Office.Desktop.Excel_16051.11929.20254.0_x86__8wekyb3d8bbwe\Office16\EXCEL.exe

CMD can run either of those by name. TCC cannot run the first by name, which is apparently what it's trying to do. TCC can run the second by name. TCC can START either one (but as I said can't START an excel document).

For .XLSM the registry has only this.

1575421299681.png
 
I can successfully use either of the strings "excel" or "v:\furnace.xlsm" ...

1. as a command in CMD
2. as a command in Powershell
3. as the target in the Start\Run dialog
4. as the parameter to "Run" in an AutoHotKey script
5. as the command for a PowerPro button
6. as the target of TaskMgr's CreateNewTask dialog

Neither works in TCC.
 
Let's go back to the original problem, starting a .XLSM file.

Although they're not installed on my new (Win10) machine, I can run old TCCs on the new machine by simply executing them from their home directory on the old machine. They often start with INI file errors and/or an "unregistered" warning, but I can still do a little testing. I have found this:

With TCC v18 all of these three command lines work to open the file in EXCEL.

1. v:\furnace.xlsm
2. start v:\furnace.xlsm
3. shellex v:\furnace.xlsm (shellex is a plugin)

With TCC v19 (as with v25), none of the above work. I get this.

Code: 
\\zz\g$\tc19> v:\Furnace.xlsm
TCC: (Sys) V:\Furnace.xlsm is not a valid Win32 application.

\\zz\g$\tc19> start v:\Furnace.xlsm
TCC: (Sys) Access is denied.
"V:\Furnace.xlsm"

\\zz\g$\tc19> shellex v:\Furnace.xlsm
TCC: (Sys) Access is denied.
 
For what it's worth, I just tested this on TCC v21 and was able to open Excel files with or without 'start'.
 
Rod Savard said:
For what it's worth, I just tested this on TCC v21 and was able to open Excel files with or without 'start'.
Click to expand...
Not here. Are you on Windows 10?

Code: 
\\zz\g$\tc21> ver

TCC  21.01.63   Windows 10 [Version 10.0.18362]

\\zz\g$\tc21> v:\Furnace.xlsm
TCC: (Sys) V:\Furnace.xlsm is not a valid Win32 application.

\\zz\g$\tc21> start v:\Furnace.xlsm
TCC: (Sys) Access is denied.
"V:\Furnace.xlsm"

\\zz\g$\tc21> shellex v:\Furnace.xlsm
TCC: (Sys) Access is denied
 
I'm on Windows 10, and I have no trouble opening .XLS and .XLSX files from a UNC share.

Have you tried which excel ?
 
Charles Dye said:
I'm on Windows 10, and I have no trouble opening .XLS and .XLSX files from a UNC share.

Have you tried which excel ?
Click to expand...
Yes. It's discussed in post #5.

The network location seems to have nothing to do with it. In all my recent tests the XLSM file has been on a local drive.
 
Did you start TCC in elevated mode by chance?
Elevated network session is different vs. non-elevated user session.
 
Last edited:
It's not a network session. I get TCC from a remote machine and start it on the local machine like this.

Code: 
start [/elevated] \\zz\g$\tcNN\tcc.exe

I just tested all 4 combinations. The command "v:\furnace.xlsm" works in v18, elevated or not, and it fails in v19 (and later), elevated or not. The file v:\furnace.xlsm is on the local machine.
 
You must log in or register to reply here.
Back
Top