Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

VBScript works.....usually?

Finished up vbscript I was working on to monitor our NTP servers, but since attaching it, it has been throwing "unknown" status about 10% of the time. When looking at info, it had something like "Microsoft VBScript Runtime Error: Permission Denied", which would probably be easy to diagnose, if it wasn't only giving it 10% of the time.

Any ideas?

(Script is attached, and uses to arguments when running, e.g. from command prompt <wscript ntpscript.vbs "123.456.7.890" "NTP Server Example">)

ntpscript.txt

Find more posts tagged with

Accepted answers

All comments

jiri.tomek

Hello berger,
this message can mean that you don't have access to one of files you are working with. I can see that you call "objFile.Close" twice for "strFile", once before "objTextFile.WriteLine" and once after. Is it possible that you Perl script hangs and so when APM runs monitor again, script file is still opened and so you get "Access denied" error?

It would help if you can get line number of "access denied" error.

berger

Thank's for the reply, I ended up making some last second changes and uploaded to thwack (Fall semester at school is starting back up, so was my last day working with SW for the time being), Also reset the pause after the call to execute the perl script, and didn't receive and non-up emails on it for 10+ hours, so I assume one of the changes did the trick.

You might be right that perl script wasn't finishing, although it's still weird that it was only doing it occasionally. Or maybe the monitors were running over each other, not sure, but anyway the changes seems to have fixed it.