Highlighted
Andy___H1 Super Contributor.
Super Contributor.
219 views

DP 9.09 to DP 10.30 Upgrade - Windows IS Issues

Hi all,

So we have attempted our first DP 9.09 to DP 10.30 upgrade today, and have issues. So here's our very simple environment:

  • Cell Manager - Linux - DP 9.09 to 10.30 upgrade 100% successful, CM and IS upgraded with no errors
  • Installation Server (which is also a client & GUI server) - Windows Server 2008 R2 Enterprise - DP 9.09 to 10.30 upgrade successful
  • But when fire up DP GUI, accepting new fingerprint, it fails with error message "Server could not be connected. Try again after some time"

So the error from the DP GUI had no error code anywhere, nothing. So we did some more digging. The INET service in the windows registry was not set to 5555, so we changed that. Although we changed one of the two occurrences only, not reading properly that there are two. Tried again no joy. Ended up uninstalling DP10.30 on the IS server completely, and reinstalling it from scratch, changing the windows registry again to 5555, this time realising there are two occurrences, and changed both. Same error from GUI, server could not be connected. Also ran the omnicc -secure_comm command on both Linux CM and Windows IS, connected both ways ok, sharing finger prints. Tried GUI again, no joy. Using simple "telnet {host} 5555" worked fine, in both directions, which is really confusing. The error message came up from the GUI very quickly which to us suggested a problem locally on the Windows IS server rather than on the Linux CM.

So we've ended up backing out, Linux CM is back to a VM snapshot ok, and Windows IS has had 10.30 uninstalled, 9.09 installed again, we're back to prior to the upgrade. Tested backups and all seems to be working.

In the end during the attempted upgrades we did try lots of stuff to get it working, uninstalling and reinstalling as we went along. So maybe we just did something right at the start which was wrong and it just multiplied itself and stopped everything from working from then on.

Anyone got any ideas as to what we can try next time? Our plan was:

  • DP Linux CM upgrade from 9.09 to 10.30 (assume it will work ok like it did previously)
  • DP IS/Client upgrade from 9.09 to 10.30 (assume it will work ok like it did previously)
  • DP IS change both registry settings to ensure they are 5555
  • Check connectivity both ways with telnet {host} 5555
  • Run omnicc -secure_comm on both hosts to ensure keys in place as required
  • Only then try starting the GUI for the first time

Are we missing something? To us we thought immediately either application control software blocking something, or maybe firewall blocking something, but neither showed blocks in any way.

Any help or advice, as usual, gratefully received

Thanks, Andy

0 Likes
2 Replies
Micro Focus Expert
Micro Focus Expert

Re: DP 9.09 to DP 10.30 Upgrade - Windows IS Issues

I could believe that the issue is with the users. 

When you perform an upgrade the users are migrated. In some cases the users are not correctly added and does not work. 

So to your checks, I will add this: 

  • DP Linux CM upgrade from 9.09 to 10.30 (assume it will work ok like it did previously)
  • DP IS/Client upgrade from 9.09 to 10.30 (assume it will work ok like it did previously)
  • DP IS change both registry settings to ensure they are 5555
  • Check connectivity both ways with telnet {host} 5555
  • Run omnicc -secure_comm on both hosts to ensure keys in place as required
  • Run omniusers -list and confirm that users were migrated. If not, run (/opt/omni/bin/perl /opt/omni/sbin/usermigrate.pl)
  • Add a new user for Windows: omniusers -add -type W -usergroup admin -name * -group * -client * -pass DataProtector1.
  • Only then try starting the GUI for the first time

Regards, 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.
0 Likes
Andy___H1 Super Contributor.
Super Contributor.

Re: DP 9.09 to DP 10.30 Upgrade - Windows IS Issues

Hi Victor,

Afraid the userid issue was not the fix, but we think we may have found the issue.

To confirm for the userid migration, it did migrate ok, all our users were there, in fact in this test environment we still have a user Any/Any/Any in there, so we didn't need to re-add it as it was already there. Same error as previously.

But doing some more digging, we think we may have found the issue, it looks to be related to the routing of hostname/IP addresses between CM and IS. So here's our setup for DP 9.09:

  • CM has two addresses, one management hostname (IP address = CM-ip-m) and one hostname for backup data (CM-ip-d)
  • IS has only one network, which is in the backup data IP range (IS-ip-d). However, it's HOSTS file set to CM-ip-d = CM management hostname, so a hosting/IP mismatch 
  • We can successfully connect to either management hostname or backup hostname, no issues, routes just fine
  • If I then remove the CM-ip-m entry from the HOSTS file, I can get to CM-ip-d but can't get to CM-ip-m (unable to connect to CRS)

So when we upgrade to DP 10 we have a conflict based on the routing setup where it seems to be accessing the CM via backup hostname, but trying to route back on the management address every time, which means it goes down a blackhole, and the GUI times out. We know this as post upgrade "telnet hostname 5555" will work for the data address, but not the MGMT one. We assume it's using the default gateway on the Linux server which is forcing it down the CM MGMT address when talking back to IS for GUI access. 

We've backed it out again for today as it's getting late. Hope to try again tomorrow. We are planning on putting it in again tomorrow and working with our Windows and Linux teams to get the IP routing correct so it only uses the CM-ip-d Data address for all communications and stops using the CM-ip-m address altogether for DP. 

Well that's what we think it is anyway, will report back when we know more.

Thanks, Andy   

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.