sgtwright

Thanks. Semper Fi to you as well!

My pleasure. Glad it worked out.

After opening a ticket with SolarWinds support, I am being told that this is a known issue and is being worked on by the development team. I will update this post once a fix has been communicated

After looking through the forums, it appears that many people are experiencing the same issues regarding Orion 9.5 not being able to display the wireless controller correctly. Is there a resolution to this issue yet?

For those of us who aren't SQL gurus, can you explain what you did to resolve the issue? I saw the solution you posted, but can you explain in a little more detail? Or at least something I can pass along to my SQL Server Admins? Thanks.

Thanks for the reply Denny. I will try and get a ticket opened today.

If you are running 9.0 SP2 You try this (Do not eun the config wizard afterwards): Edit \Inetpub\SolarWinds\Orion\MasterPage.master. Find this line: <form runat="server" method="post" action="#" id="aspnetForm"> Remove the action="#" part. That is, change it to this: <form runat="server" method="post" id="aspnetForm">

These are Linux servers OEMed from Cisco running Unified Call Manager. As far as I know, nothing has changed since we do not have access to make changed at the OS level of these servers. Cisco has these "locked" down except for patches and upgrades, which could be the culprit here, but I will need to check. I will post my…

UPDATE: I was able to finally get into a test account I had created in Orion which had a very simple page that only displayed a few servers on it. I modified our Network Summary page by removing the Network Wide Availability and Response Time Chart. After I did this, the page now loads almost lightning fast. I have left it…

That is correct. I can get to the login screen, but after entering credentials no one can get to the network summary page.

Denny, Thanks for the response. Sorry I didn't explain things well. In the picture I attached in my original post, the part that is circled is now missing in my charts. The picture attached is a chart I took snapshot of prior to the upgrade. After the upgrade, this is no longer there. I have attached a new chart showing…

After applying the fix from SolarWinds support. It is now working. According to support, this issue will be fixed in the next Service Pack.

Okay. I understand. Utilizing the OID you supplied, I am getting OID is not supported on two of the four servers. The two that are not working are the two with the error being reported. I hope this helps and thank you for the assistance.

This is a reply a year later than this post, but we were having the same issue as well. Turns our that our issue wasn't with Orion really. It was with the Call Manager and Subscribers themselves. Occasionally, different members of our Call Manager Cluster would go into an unknown state and Orion would give me the same…

Chris, This doesn't happen everytime. Typically, I get this error when going to the Node Management Page, then selecting "Edit Properties" from there. That is when I usually get the error. This is happening in IE and Firefox. The screenshot is below:

Denny, Thank you for the response. Seeing as how this appears to be an ongoing request (adding multiple nodes manually and several at a time) since 2004, is there any way this can get added to the enhancements request for a future release? I think this would be huge.

We too have noticed a big difference in response times upgrading from 8.1 to 8.5.1. In fact, our Network Summary page times out frequently when refreshing. Also, when clicking on a node, it will timeout frequently as well. If I could go back to 8.1 I would. I have opened a ticket with SolarWinds and apparently there is a…

Ticket has been opened for this issue (Ticket #61780). Thanks for the help, Frank

SP1 for .NET 3.5 is installed. I will submit a support ticket to obtain the work around. Thanks, Frank

I submitted a ticket (Case # 123965).

Unfortunately, I verified these and they are correct. It doesn't seem to be a permissions issue as much as it does a time out issue.

I had this same error as well. If you are using DirectLink Accounts, Try the following: Open IE and enter http://<servername>/Orion/logout.aspx (removes the login cookie and takes you to the login page) Enter Admin credentials and then go into the account management. From there, you will need to disable the DirectLink…

I was able to resolve the issue by using the good ol' Configuration Wizard and repairing the database. Looks like everything appears to be normal now.

Disregard this post. In performing my own checking (vs. having my server admin guy check it) we are using MSDE! For those who read this later, I did perform an upgrade of MSDE to SQL 2000 and all is now well. Thanks for the posts! Thanks, SgtWright

Thanks for the responses so far, but I just want to restate that I am already using SQL 2000. SolarWinds shows that the Database Engine is Microsoft SQL Server 2000. I have tried compacting the database and re-running the configuration wizard which has had no affect. Again, I am not using MSDE, but MS SQL Server 2000. I…

We are already using SQL Server. I have only had SolarWinds installed for a couple of weeks and the database is already full. Not much tweaking has been performed on the collection statistics side. Thanks, SgtWright

More Information. In the Event Viewer, I am getting several of these errors since the upgrade to 8.5.1: Event code: 4005 Event message: Forms authentication failed for the request. Reason: The ticket supplied has expired. Event time: 10/31/2007 4:17:07 PM Event time (UTC): 10/31/2007 8:17:07 PM Event ID:…

Anyone? This is now happening more and more frequently.

We are currently on 9.5 and have migrated the NetPerfMon database to a clustered SQL 2005 environment. To date, we have not had any issues to speak of.

Josh, Just want to make sure I am understanding you; the monitoring templates need to determine how many processors are on each server prior to being able to monitor the processes that are running on them? I can perform an SNMP WALK on these servers without any issues, so I know that SNMP is working correctly.…