Having issues with template edit button after upgrade.

Just upgraded to Orion Core 2012.2.1, SAM 5.2.0 SP1, NPM 10.4.1. Everything seems to come up ok, but when going to check out some new features. I tried to open a new template and the edit button did not work. Even went to a template I had created before and the edit button did not work.

Anyone have this experience and know how to resolve? Is there more information needed to help?

I will create a ticket but thought I would bring it here too.

thanks,

Find more posts tagged with

edit_button

upgrade

application_monitor_template

Accepted answers

All comments

jangliss

Can you define "did not work"? Did you get any errors, or did the browser just not do anything? One of the things I noticed after we did a big upgrade on APM->SAM was some cached javascripts caused some issues, so we had to clear the browser cache to get some pages to behave properly again. Have you tried that?

What browser are you using? Any chance of using diagnostic tools like the developer toolbar in IE, or Firebug in Firefox, for example. You might not be seeing a javascript issue if the page is just not processing your click action.

scotthill

After clicking the Edit button nothing happened. No errors came up. I have

not tried clearing the browser cache I will do that and let you know.

Using IE 9. I will check with some one on the other things you mentioned.

Scott Hill

Information Technology

Office of State Courts Administrator

1-888-541-4894

Scott.Hill@courts.mo.gov

From: Jonathan Angliss

<solarwindscommunityteam@communications.solarwinds.com>

To: Scott Hill <scott.hill@courts.mo.gov>

Date: 02/07/2013 03:28 PM

Subject: Re: - Having issues with

template edit button after upgrade.

aLTeReGo

As suggested I would clear the browser cache and see if that resolves the issue. Also try another browser (FireFox/Chrome) to see if this is reproducible outside of IE. If it is, please try re-running the Web Site portion of the Configuration Wizard to see if that resolves the issue. If none of those steps help please open a case with support and reference this thread. Also be sure to post back your case number here so we can track this issue properly.