Cannot execute VBE scripts on SBS2003

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?
LouisvilleGeekAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dan_blagutCommented:
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
LouisvilleGeekAuthor Commented:
Disabled the Symantec services and still not having any luck.
0
LouisvilleGeekAuthor Commented:
Went ahead and completely uninstalled Symantec and I'm still receiving the same error.
vbeError.png
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

LouisvilleGeekAuthor Commented:
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
footechCommented:
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
LouisvilleGeekAuthor Commented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LouisvilleGeekAuthor Commented:
This solution worked.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.