mark_wiggans

 That is only an estimate- v 8.1 improvements with the DB Maintenance requires the install to restructure the DB and this can take longer than a typical upgrade depending on your DB size.

 Just part of the troubleshooting steps. Process of elimination, etc...

 I would suggest contacting support.

 That could be the issue. The HSE does not have the sufficient rights to access the DB. Try re-running the configuration wizard again to verify.

 vinnman1000 - thanks - we received them.

Due to the size it might appear to be hung yet it is still compacting. How long are you waiting with this message? Others have noted it taking 8 hrs. Unless you are getting specific errors you might try the suggestions from this post in particular the 2nd suggestion. If this does not work I would encourage you to open a…

http://knowledgebase.solarwinds.com/kb/questions/2385/Managing+Duplicate+Subnets+in+IPAM

 ahh ok..I've pulled it up and see it was sent by Benjamin -My guess is the zip was probably snagged somewhere- I'll attach it in a subsequent post..

 For the missing charts try this - In the web console, go to ADMIN > WEB CONSOLE SETTINGS > CHART SETTINGS. Reset "Thumbnail Aspect Ratio" and "Chart Aspect Ratio" to 1, the charts should be available again. more info can be found here .

Check the Logs which can be found in the <STM install directory>\webapps\root\logs\poller.log. The main log to look at is the Poller log. To set in Debug mode - Server Setup -> Server tab -> Poller log level – set to debug.If ssh connection was successful, then you will see message like ‘Connection to the control station…

 SP4 is available now.

The previous collation error appears to be a conflict on the collation of the DB and or the tempdb being utilized during the upgrade. Per the case number referenced, I believe the DEV team is working on a script that will assist in updating your DB schema. I would stick with 8.1.3 until this can get sorted out if possible.…

A few more things to try - Check the SOLARWINDS_WEBSITE and IUSR_<COMPUTER NAME> accounts, where <COMPUTER NAME> is the name of the server where you are logged in. Both of these accounts should be Local Administrators (Domain Administrator is not good enough). 2) Next go to Start-> SolarWinds Orion-> Advanced Features->…

 now you should be able to login as ADMIN and re-enable the DirectLink acct.

 The upload instructions will be in the support ticket.

Sorry my mistake. The issue you describe about Cisco is usually related to the way they handle Interface IDs (IfIDs). When a router boots for the first time, it assigns an IfID to every interface starting with the first available IfID, which is always 0 the first time the device boots. But when the device reboots, the only…

choose Solarwinds- then select from the list (hopefully it will be listed)

 Have not seen this one before. Try clicking Finish and re-applying the SP1.

 In the C:\\Inetpub\Solarwinds folder you will need to add "Everyone" with Full permission to that folder and to the C:\program files\Solarwinds\Orion folder as well.

 Yes it should.

 Yes, Cirrus should be able to pull that info. The network inventory will pull serial numbers, interface and port details, IP addresses, ARP tables, any installed Windows software on all managed devices and include them in the Configuration management database. The only reports out of the box include change management,…

When you hit submit you will receive an auto-reply with your case number and you can then attach the files to your case.

 justinh- Maybe this will help clarify? support.solarwinds.com/.../ProblemDetail.cfm HTH

 sounds great. Just trying to help.

 noob- If you can browse to the MIB in the Custom MIB browser within Orion, then the MIB is already in our database. To monitor a custom MIB with Orion or with Real Time SNMP Graph, it doesn’t have to be in the database. It only needs to be in the database if you want to “Browse” your way to the OID when selecting it.…

 You need to reassign the EngineID in the database so that it sees the old Nodes that are still assigned to the old EngineID. Connect to your SQL Database, and then choose the "Engines" table (hit Query /Refresh) You will see the Engine ID field here as the very first column - move the radial button at the top of the…

 Please open a support ticket and reference this thread so that support can look into the cause of your issue.

It looks like the device does not support that MIB. Try this tool to determine if the Cisco IOS release for your VoIP device supports IP SLA operations - tools.cisco.com/.../index.jsp click Search by Feature, and then select IP SLAs - UDP Based VoIP Operation

 It should be in Program Files\Solarwinds\Orion-

Going through internal testing now so it will be a few weeks. Sorry to be vague, but if I hear differently I'll update you.