We've installed APM 2.0 on our NPM server, when we attempt to run the conversion utility the following error is produced: -
Method not found: 'System Guid SolarWinds.APM.BusinessLayer.ScheduledJobFactory. CreateScheduledJob<SolarWinds.APM.Common.Models.Component>'
Has anyone seen this before?
The migration utility does not work with APM 2.0.
Denny LeCompte Sr. Product Manager, Orion SolarWinds Austin, TX
Thanks for the info Denny
So then why this in the Release Notes for APM2.0? I would expect Solarwinds to support this product as we upgraded to it today based on this information in the release notes. A support case was opened (#58741) and was replied to and closed without anyone actually calling or confirming with me.
"Thank you for contacting SolarWinds Support. The AppMon Converter will not convert applications from Application Monitor to Application Performance Monitor 2.0. This is stated in the description of the AM to APM 1.0 Migration Utility. I am sorry for the inconvenience of this. Thank you again for contacting SolarWinds Support."
Another case has been opened and am currently awaiting a call or at least a email back without immediate close of the case (#58743). I have noted that SW staff seem very overeager to close support cases without regard to the issue being fully resolved.
The instructions say to use the AM to APM Migration Utility.
Brad
I have Taken the new ticket for you on the issue. I may have a workaround if you haven't already Done a lot of work on version 2.0
What we could do is Remove Apm 2.0 and roll your back to version 1.0 and run the conversion utility to get your monitors Over and then have you upgrade to version 2.0
You may want to evaluate this in terms of the amount of monitors you need to migrate from Am and the time it would take to roll back .
I have responded in the case For you
-J
One other thing i should have mentioned is That the only way back from 2.0 is to completely drop the Apm tables and start Fresh with version 1.0
So this would only make Sense if you had small amount or minor amount of work done in Version 2.0 But still a large amount of monitors in Am that need converting
If you have a large amount of work already done in Apm2.0 then we cant roll back to 1.0 as they are not backwards compatible
Hope this makes Sense
Joe
Thanks guys. I have put notes in the ticket and I should be able to do this regression method to resolve the issue this coming Sunday. I hope the Release notes are updated asap to make the upgrade path clear to customers.
As an aside about the Support efforts:
I hope that the Support team would also be more interested in actually resolving the customer's problem and not just dropping a generic response and closing the ticket without any interaction with the customer. I have never successfully called the Support phone number and gotten a person on the line. It's always we are too busy, leave a message or open your case online. Are things that tight there?
