1 3 4 5 6 7 Previous Next 161 Replies Latest reply on Jul 2, 2009 4:28 PM by crwchief6 Go to original post
      • 125. Re: V9 Upgrades - Let's here the stories
        savell

        70 or 80 seconds - wow, we aren't in the same ballpark. When I said ours were slower, I estimate that typically the node details screen took 2-3 seconds under 8.5.1, and 5-6 seconds under 9.0 (but I can't back the old numbers up with hard data). Any of the other screens (i.e. interfaces) seem to be unchanged in performance terms from the previous release.


        For the UnDP poller loading, does the process show memory growth during this hour? Process memory growth may actually show that it's still loading and not stalled or hung.


        I'm be interested to see the result of both issues.


        On another v9 observation...


        The way MapMaker now expands the list of devices (once a vendor is selected) is very annoying. For a large list of Cisco devices it can take several minutes for the list to populate. I can see that for some users this may make the inital load faster - but it's bad news for the larger installations.


        Dave.

        • 126. Re: V9 Upgrades - Let's here the stories
          Hock

          The web loading seem excessive slow with even the login page.


           Has it got to do with the UDP issue that will be fixed in SP2?

          • 127. Re: V9 Upgrades - Let's here the stories
            BryanBecker


            70 or 80 seconds - wow, we aren't in the same ballpark. When I said ours were slower, I estimate that typically the node details screen took 2-3 seconds under 8.5.1, and 5-6 seconds under 9.0 (but I can't back the old numbers up with hard data). Any of the other screens (i.e. interfaces) seem to be unchanged in performance terms from the previous release.

            For the UnDP poller loading, does the process show memory growth during this hour? Process memory growth may actually show that it's still loading and not stalled or hung.

            I'm be interested to see the result of both issues.

            On another v9 observation...

            The way MapMaker now expands the list of devices (once a vendor is selected) is very annoying. For a large list of Cisco devices it can take several minutes for the list to populate. I can see that for some users this may make the inital load faster - but it's bad news for the larger installations.

            Dave.

             

             

            Web Site - only node details seems to be affected.  Interfaces, etc load up in 1-3 seconds.  We did find a large amount of "white" space in the DB leftover from a previous running of NetFlow.  The DB was up to 140GB with only 7GB actually used.  We ran a shrink and got it down to 37GB.

            UnDP - Yes I do see the memory usage grow as it's loading but still takes a very long time to load.

            MapMaker - I think this was changed in V8.5...I hate it too.

            BB

            • 128. Re: V9 Upgrades - Let's here the stories
              BryanBecker

              I think we have identified the issue...fixing it I'm not sure.  It seems that after I removed the custom mib gauges/charts for node details the node details paged loads in like 3-5 seconds.  I'm not sure of the conflict from custom mib poller to UnDP but something isn't right.  I sent support the files so hopefully something can turn up.  UnDP does load in about 2 minutes now which seems to be faster than before.

              BB

              • 129. Re: V9 Upgrades - Let's here the stories
                Network_Guru

                I upgraded my SL2000 server last week.
                The upgrade took 30 minutes and went without a hitch.
                The website has been running fine since the upgrade.


                The issue I have is the links to the charts no longer work in report scheduler.
                I am e-mailing out charts of connected VPN users, but the new asp.net URL format no longer allows me to retrieve the chart with Report Scheduler and mail it out weekly:

                Previous to the upgrade the URL looked like this:
                http://orion-sl2000/NetPerfMon/ViewChart.asp?Chart=CustomOIDChart&NetObject=N:2515&CustomPollerID={FBB9360E-A013-4EEF-8A9A-5EFB690BC559}&SubsetColor=FF0000&RYSubsetColor=0&Period=Last%207%20Days&SampleSize=15M&Title=VPN+users+%2D+last+7+days&ReBuild=TRUE&FontSize=Medium&Width=640&Height=0 

                The URL now looks like this:
                http://orion-sl2000/Orion/Controls/ChartImagePipe.aspx?ChartID=customChart$ctl01$chart_Base&KxRx=0x09556
                but no chart is displayed.


                This is a show-stopper for my SLX upgrade.
                If I can't e-mail charts, there is no way I can upgrade to V9.

                • 130. Re: V9 Upgrades - Let's here the stories
                  tdanner

                  This will be fixed in the next service pack. There will be a new URL for charts that (like the old one) supplies all of the parameters needed to generate the chart instead of using ChartImagePipe.aspx and relying on the asp.net session.

                  • 131. Re: V9 Upgrades - Let's here the stories
                    spandey

                    I have no seen this issue any where else, so I think I'm just doing something wrong.  We got a new server for Orion so I decided to just install the new version 9.  The install went fairly smoothly.  The only issue I'm really seeing now is that I had a number of reports that I created and had published to the website.  None of these reports show up any longer.  (Yes, I moved them from the old server! :))  If I open report writer on the server all of the reports (canned and custom) are there.  If I open a custom report that doesn't show up on the web site everything looks as it should.  The box is checked that says to publish to the web.  I've stopped and started resources on the server and I've even rebooted the server and I cannot get the reports to show up on the web.

                     What am I doing wrong?

                    • 132. Re: V9 Upgrades - Let's here the stories
                      mark wiggans


                        I've stopped and started resources on the server and I've even rebooted the server and I cannot get the reports to show up on the web.

                       What am I doing wrong?

                      Have you tried to manually copy the file:
                      C:\Program Files\SolarWinds\Orion\OrionReportWriter.Schema to the webserver?
                      • 133. Re: V9 Upgrades - Let's here the stories
                        spandey
                        Have you tried to manually copy the file:
                        C:\Program Files\SolarWinds\Orion\OrionReportWriter.Schema to the webserver?

                         I had not tried to manually copy the schema so I did try it and still nothing.  None of the custom reports are publishing to the web.  If I recreate the report they do publish but that's going to become pretty tedious.

                        • 136. Re: V9 Upgrades - Let's here the stories
                          spandey

                           I've also noticed that my alerting is no longer working. 



                          Okay, ignore that comment.  I figured out alerting.  The problem was between the chair and the keyboard.

                          • 137. Re: V9 Upgrades - Let's here the stories
                            KennyLamb

                            problems with V9 Upgrade... initially had issues with the DB permissions, etc - this was sorted by reading this thread and removing the registry entries under SOFTWARE\SolarWinds.Net\ConfigurationWizard\ConfiguredModules\


                            This allowed the ConfigurationWizard to get past the DB config but we then this an issue when trying to install the Universal Device Poller it comes back with a message advising:


                            An error occured configuring SolarWinds Universal Device Poller: Unable to determine Job Engine Location. Please check the ConfigurationWizard.log file for details.


                            After repairing, running SP1, repairing, etc, etc - decided to install and configure without the Universal Device Poller - this at least allowed me to finish the upgrade, etc and get Orion back up and running.


                            Support case# 53629 and have been in discussions with Support regarding this issue - will post update as and when...  


                             


                            • 138. Re: V9 Upgrades - Let's here the stories
                              tdanner

                              Sarah,

                              It could be that the solarwinds_website user lacks permission to see the report files you copied. To check this, open the file properties in Explorer and look at the security tab. Compare the settings for a file that does show up on the website with the settings for one that doesn't.

                              • 139. Re: V9 Upgrades - Let's here the stories
                                spandey

                                Sarah,

                                It could be that the solarwinds_website user lacks permission to see the report files you copied. To check this, open the file properties in Explorer and look at the security tab. Compare the settings for a file that does show up on the website with the settings for one that doesn't.

                                 



                                Tim - I've been in contact with SW support.  I've checked permissions for the solarwinds_website user as well as the iusr_(machine name) user.  I have also re-run the website configuration wizard to recreate the COM+ object.  I've cleared website cache and restarted IIS on the webserver.  I'm working to schedule a GoTo meeting for hopefully tomorrow.  I'll post what I find out.  It looks like I'm having some issues with alerting as well.  Thanks!!  :)

                                • 140. Re: V9 Upgrades - Let's here the stories
                                  tdanner

                                  Kenny,

                                  It's looking for C:\Program Files\Common Files\SolarWinds\JobEngine\SWJobEngineSvc.exe. Does this file exist? If not, do any of the directories in that path exist?

                                  This is installed by the "SolarWinds Job Engine v1.1" package. I know you've already done a bunch of repairing, but is that package installed in Add/Remove Programs?

                                  • 141. Re: V9 Upgrades - Let's here the stories
                                    skierjmh

                                    Sarah,

                                    We ran into issues with the site as well (we're doing pass through authentication via AD) and had to initially give the Server\Users group Modify\Write access, restart IIS, check the site, remove the permissions, restart IIS, then check the site again. Running the configuration wizard breaks all of this of course and it has to be redone.

                                    side note - jeffco rules (live there), or anything Colorado for that matter...

                                    • 142. Re: V9 Upgrades - Let's here the stories
                                      KennyLamb

                                      Tim,


                                       Thanks for the reply - we do not have the file in the JobEngine directory, in fact it is nowhere in the SolarWinds directory - see attached.


                                      We do not have the "SolarWinds Job Engine v1.1" package mentioned in Add/Remove Programs - is there any way of installing this package as a standalone applicaiton, without going through all the full SolarWinds install??


                                      This install has been upgraded various times since V7 - therefore the Orion App is located in the "Network Performance Monitor V7" directory.

                                      • 143. Re: V9 Upgrades - Let's here the stories
                                        tdanner

                                        The JobEngine directory under your NPMv7 directory belongs to APM. That's Job Engine 1.0. Job Engine 1.1 lives under Program Files\Common Files. They coexist side-by-side. Job Engine 1.0 is only used by APM 1.0. Orion 9.0 and EOC 1.0 both use Job Engine 1.1, as will APM 2.0. (Sorry for all that detail - I just wanted to give enough background to explain why the files you see do belong there but aren't what you need to get Orion working.)

                                        The Job Engine 1.1 installer should be on your server under C:\Document and Settings\All Users\Application Data\SolarWinds\Installers\JobEngine.msi. This is a pretty quick install - it doesn't have a zillion little files like Orion does.

                                        • 144. Re: V9 Upgrades - Let's here the stories
                                          justinh

                                          I just upgraded to 9.  It went very well, except for two things.

                                          I had to do a repair on APM to get it working, and then I had to repair the NPM install to get UnDP working.

                                          Other than that, quite smooth and very fast.  No more 15 minute wait while configuring the database.

                                          Justin
                                           

                                          • 145. Re: V9 Upgrades - Let's here the stories
                                            KennyLamb

                                            Tim - top man, hit the nail on the head.... That has done the trick, UnDP all configured and working.


                                            Many, many thanks


                                            Kenny


                                            • 146. Re: V9 Upgrades - Let's here the stories
                                              tdvojmoc

                                              The JobEngine directory under your NPMv7 directory belongs to APM. That's Job Engine 1.0. Job Engine 1.1 lives under Program Files\Common Files. They coexist side-by-side. Job Engine 1.0 is only used by APM 1.0. Orion 9.0 and EOC 1.0 both use Job Engine 1.1, as will APM 2.0. (Sorry for all that detail - I just wanted to give enough background to explain why the files you see do belong there but aren't what you need to get Orion working.)

                                               



                                              I like background. Please, keep it coming. Thanks.

                                              • 147. Re: V9 Upgrades - Let's here the stories
                                                spandey

                                                Okay, so here's the deal on my reports not working.  I finally opened a ticket with support.  They said that this happens sometimes during upgrades, but it's fairly rare.  I moved the database from one server to another and he said that that may have had something to do with it as well.  Anyway, I was able to copy the reports out of the reports folder and paste them on to my desktop and then delete the contents of the reports folder and then copy everything back in again.  Then they all published to the web.  Simple, yet so complicated.


                                                 On another note, I originally had my alerts temporarily disabled and I figured that was the reason that I was not receiving alerts (and I'm sure it had something to do with it). But now that I've fixed that, still.. none of my alerts work.  I was hoping it would be a simple matter of recreating the alerts to fix this problem but not the case.  I've recreated 2 alerts from scratch.  If I use the test alert option, the test sends just fine but if I literally unplug something out of the network that I'm alerting on, I get nothing.  This has been the single most frustrating upgrade for this software.  I've never had issues before. 

                                                • 148. Re: V9 Upgrades - Let's here the stories
                                                  rlawsha

                                                  I had the same problem with alerts. In my case the solution was: Open NPM, click ALERTS button, remove checkmark from box labeled, "Temporarily Disable alll actions for ALL Basic Alerts". How it got checked in the first place is beyond me.

                                                  • 149. Re: V9 Upgrades - Let's here the stories
                                                    spandey

                                                    I had the same problem with alerts. In my case the solution was: Open NPM, click ALERTS button, remove checkmark from box labeled, "Temporarily Disable alll actions for ALL Basic Alerts". How it got checked in the first place is beyond me.

                                                     



                                                    Yes, same here, but even after I removed that check they still don't work.

                                                    1 3 4 5 6 7 Previous Next