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

Variables in scheduled jobs not working after upgrade to 5.0

Hi Everyone,

After our recent upgrade to 5.0 all of the variables in our scripts stopped being processed. We use simple scripts to back up our Enterasys equipment. An example for the E1 switches is:

copy device-config t10.4.1.66/.../${SysName}-${MediumDate}.cfg

In the past the variables would be converted and the file would be saved with a name like "switch1-04-Nov-08.cfg". After the upgrade it is saved as "${SysName}-${MediumDate}.cfg".

I have recreated all the jobs and the new ones have the same results. If I run the same exact script manually by choosing the device and selecting Execute Command Script... it works fine. It is only when the job is run using the scheduler.

I have a case open with tech support but we haven't had much progress yet. Has anyone seen this behavior before?

Thanks.

Find more posts tagged with

Accepted answers

All comments

chris.lapoint

We are working through this issue now. If there are others experiencing this same issue, please speak up to help us prioritize.

Tomas

Yes, I have the same problem, see my post "tftp issue after upgrading NPM and Cirrus ->Orion".

... It means that the variable ${sysname} was not interpreted.

Regards,

Tomas

chris.lapoint

Can you open a support ticket on this item and include your post details? We've got a potential fix for this one and we'd like to have customers experiencing this issue validate that our fix works in their environment. For internal folks, this is currently being tracked as #2673.

Slider

I have support case 66668 open currently. Should I open another case to try and get/test the fix you mentioned?