Solved

Cannot execute VBE scripts on SBS2003

Posted on 2011-09-20
7
338 Views
Last Modified: 2012-05-12
Whenever I'm attempting to run a VBE script on SBS 2003, I'm receiving the following error:

"Windows cannot access the specified device, path, or file.  You may not have the appropriate permissions to access the item."

I went ahead and checked permissions and everything is in line.  Perhaps Symantec is disabling this?
0
Comment
Question by:LouisvilleGeek
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
7 Comments
 
LVL 22

Expert Comment

by:dan_blagut
ID: 36572474
Hello

Yes the AV can block some extension with a message like that. Can you try to stop the real time protection of your symantec and retry to execute the script.

Dan
0
 

Author Comment

by:LouisvilleGeek
ID: 36573139
Disabled the Symantec services and still not having any luck.
0
 

Author Comment

by:LouisvilleGeek
ID: 36573342
Went ahead and completely uninstalled Symantec and I'm still receiving the same error.
vbeError.png
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 

Author Comment

by:LouisvilleGeek
ID: 36573568
I've also went ahead and ensured that the Windows Scripting Host is enabled.  Still no luck.

Oddly enough, I found a tool from Symantec's website:

http://service1.symantec.com/sarc/sarc.nsf/html/pf/win.script.hosting.html

However when I go to download the tool, the server will act like it's downloading the file, and then it will instantly disappear.
0
 
LVL 40

Expert Comment

by:footech
ID: 36577952
Have you checked the file association for VBE?  It should list "Microsoft Windows Based Script Host".

If you need to reset it, the path for the open command should be:
C:\WINDOWS\System32\WScript.exe "%1" %*
0
 

Accepted Solution

by:
LouisvilleGeek earned 0 total points
ID: 36577960
It turned out to be an option on the properties dialog. The option allowed me to enable the script for runtime because it was made on another PC.
0
 

Author Closing Comment

by:LouisvilleGeek
ID: 36895807
This solution worked.
0

Featured Post

Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The articles for turning off the Client firewall policy on the internet are for SBS 2008 and don't really help for SBS 2011. They actually moved the Client firewall policy. In 2011, the client firewall policy has moved to the SBS computers conta…
You may have discovered the 'Compatibility View Settings' workaround for making your SBS 2008 Remote Web Workplace 'connect to a computer' section stops 'working around' after a Windows 10 client upgrade.  That can be fixed so it 'works around' agai…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…

737 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question