Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Cannot execute VBE scripts on SBS2003

Posted on 2011-09-20
7
Medium Priority
?
348 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
  • 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
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 

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 41

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

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

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

Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
The problem of the system drive in SBS 2003 getting full continues to be an issue, even though SBS 2008 and SBS 2011 are both in the market place.  There are several solutions to this, including adding additional drive space or using third party uti…
This lesson discusses how to use a Mainform + Subforms in Microsoft Access to find and enter data for payments on orders. The sample data comes from a custom shop that builds and sells movable storage structures that are delivered to your property. …
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…

783 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