
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-14-2011 12:26 AM
Had been trying to get a very simple custom action using nbtstat.exe to work. Surprisingly I kept receiving an error message that the file could not be found.
I modified the custom action specifying the exact path to the nbtstat executable and verified that it was there, however the custom action still said that the file could not be found.
After some searching I found this article and it not only explained the issue very clearly but provided a fix for the problem. I hope this helps someone else.
http://scottiestech.info/2009/06/20/calling-a-32-bit-system-command-from-a-script-in-x64-windows/
I modified the custom action specifying the exact path to the nbtstat executable and verified that it was there, however the custom action still said that the file could not be found.
After some searching I found this article and it not only explained the issue very clearly but provided a fix for the problem. I hope this helps someone else.
http://scottiestech.info/2009/06/20/calling-a-32-bit-system-command-from-a-script-in-x64-windows/
Labels:
- Labels:
-
Custom Actions
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-20-2012 07:17 PM
Adding nbtstat.exe to the actions folder did not resolve the issue. I created a seperate nbtstat-64 action with the command:
cmd.exe /K "%windir%/sysnative/nbtstat.exe -a {computer}"
A little klunky, but it works.
JW
cmd.exe /K "%windir%/sysnative/nbtstat.exe -a {computer}"
A little klunky, but it works.
JW

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-14-2011 03:07 PM
another workaround: copy nbtstat.exe to the actions folder.
