Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Orion v7.1

I'm looking at upgrading in the next day or so and have a few questions?

Has anyone had any major problems with 7.1?
Can I put 7.1 straight on top of v7 without any problems?

Thanks

Jon

IT Infrastructure Manager
Pilgrim Hospital
UK

Find more posts tagged with

Accepted answers

All comments

psala

I put 7.1 right over 7.0 and had an issue with terminal services. Because of the way I had terminal services configured, I had to install from add remove programs. I did not do this the first time and I had many problems with the web side. I uninstalled, then re-installed through add remove programs and everything was correct. I did not lose any data in the process or have to go through an recovery steps.

Paul Sala
Network Engineer
Emerson Power Transmission

Network_Guru

According to the install notes, you should be un-installing V7.0.5 before installing 7.1, at least
that's how I did it. As always, backup your files before upgrading (see my other reply to a post on this).

-=Cheers=-
NG

lavelanet

I had 7.0.5 Eval, installed 7.1 over it , then fouund out about features in 7.2 beta and installed that over 7.1 and had no problems.

andrewcorp

Where did you get a copy of v7.2? Is it available for download?

Thanks

cshiver

Afraid I did install 7.1 over 7.0 and have had nothing but problems since then. Apparantly you need to stop all 7.0 services, run uninstall from the control panel, then install 7.1.

- Chris

BakerD

I installed 7.1 over 7 and knock on wood have not seen or had any major issues yet. I did not stop any services. I did not install the SQL part again, just NPM and I did it via a TS session. One thing that did happen was after the reboot and I went through the setup part, it wiped out some custom web pages I did. I had added http and telnet links under my node details section. This was not a custom page I created, but I edited the original node details page. Not a big deal to put them back, but something to remember next time and to look out for especially if you have done a lot of customization. Not sure what it would do to any pages created from scratch.

The new version is noticeably faster for us through the web interface. Some of our alerts are not reporting the correct data, just showing the variable call tag.

A bunch of devices listed under system manager now do not have the device icons, just blank spaces where before they showed icons. Haven't looked into that yet.

Mainly the upgrade went well and all seems to be working as before with improvement to the web interface performance, but I have not checked out any of the new stuff.

Edit:

I take that back, the last two nights it has locked up on us with the following error.

Critical Error

--------------------------------------------------------------------------------
Cannot access main SQL Server database.

Connection = Provider=SQLOLEDB.1;User ID='SolarWindsNPM';Password='*********';Persist Security Info=False;Initial Catalog=NetPerfMon;Data Source=xxxxx\SOLARWINDS;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=CATVModemMgmt;Use Encryption for Data=False;Tag with column collation when possible=False

Error = Timeout expired

oper7g

Darader, when does this lockup happen? Is it during the database maintenance job at night? If so what is the size of your db?

Cheers,
D.

BakerD

Hhmm, not sure. There is nothing recorded in the eventvwr. DB maintenance is set to run at 2:15am which I think was default and the total space usage shows 630mb. If I can figure out how to stop it from running tonight I will and see if it locks up again.

Debbi

I followed the instructions in the Release Notes (uninstall, then reinstall) but they did not remind me to backup my webengine so I lost a lot of website customizations. I should have downloaded the admin guide first and used the instructions in it. Doesn't help that I do this maintenance at 5AM so I am always a little groggy at the time!

Joakim

quote:Originally posted by darader

I installed 7.1 over 7 and knock on wood have not seen or had any major issues yet. I did not stop any services. I did not install the SQL part again, just NPM and I did it via a TS session. One thing that did happen was after the reboot and I went through the setup part, it wiped out some custom web pages I did. I had added http and telnet links under my node details section. This was not a custom page I created, but I edited the original node details page. Not a big deal to put them back, but something to remember next time and to look out for especially if you have done a lot of customization. Not sure what it would do to any pages created from scratch.

The new version is noticeably faster for us through the web interface. Some of our alerts are not reporting the correct data, just showing the variable call tag.

A bunch of devices listed under system manager now do not have the device icons, just blank spaces where before they showed icons. Haven't looked into that yet.

Mainly the upgrade went well and all seems to be working as before with improvement to the web interface performance, but I have not checked out any of the new stuff.

Edit:

I take that back, the last two nights it has locked up on us with the following error.

Critical Error

--------------------------------------------------------------------------------
Cannot access main SQL Server database.

Connection = Provider=SQLOLEDB.1;User ID='SolarWindsNPM';Password='*********';Persist Security Info=False;Initial Catalog=NetPerfMon;Data Source=xxxxx\SOLARWINDS;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=CATVModemMgmt;Use Encryption for Data=False;Tag with column collation when possible=False

Error = Timeout expired

Yeap - got that too! Happens during daytime when no jobs should be running. I´m running MSDE.

BakerD

I talked to tech support and they said they have seen that before on servers running W2K SP3 and that is what I was on. I applied SP4 yesterday morning and everything is still good this morning. I will post if anything turns up.

Edit:

SP4 did not solve the problem.