Jon,
I don't know if having a later than supported version of SE will cause the installer to fail, but I recommend you install 6.5.2.5 and try again. For RM you download SE from the RM downloads page. That is the only place you will find the odd versions of SE supported by RM. I wish RM supported the standard releases available from the SE download section.

Try that and see what happens.

Aran

Thank You both Aran and Charlie. Problem I'm having is even finding an RM download section. The release notes for RM 5.2 say what you both told me to do "download SE from RM download area of Powerlink." Seeing I didn't see a downloads section for RM, I went to the SE download section. I contacted EMC just 5 minutes ago and asked that they "grant me the necessary access to view the RM downloads section." I don't think this is anything that I'll have to pay for (I hope not at least). So, once support gets back to me, I'll hopefully be able to see the RM download section. Right now, for the letter "R" in downloads, I see RepliStor, ReportXtender and ResourcePak Base, but no Replication Manager.

Glad I could help. Let me know if that resolved the problem.

Thanks again Aran for all your help. I'm going to mark this as "answered" and credit your points, especially seeing how the release notes said to download SE 6.5.2.5 from the RM downloads. I grabbed the wrong SE, and believe this is why setup bombed. Once I obtain proper SE, if I have issues, I'll revisit this forum. However, for now I have been greatly helped. Thanks Aran and Charlie!

Jon

Jon,
Another thought occurred to me about your upgrade. If you don't have many hosts or jobs, it may be easier just to remove the old version of RM and do a clean install of RM 5.2 and 5.2 SP1.

Hi Aran,

Well, unfortuntaley I did get this same error again this morning. This came after I downloaded and installed SE 6.5.2.5 hotfix for x86 systems (from the RM download area after having my powerlink credentials updates so I could see that software) and installed the .NET 2.0 framework. I was thinking I may have to uninstall RM v 4.0, but was hoping I didn't have to. All of my nightly snap jobs will have to be recreated (which is fine) but what if I go through the hassle of uninstalling 4.0 and I still get the error? Then I'll have shot myself in the foot needlessly. Regardless, I am going to open a call with EMC support, and if I solve the issue on my owm, I will simply close the call.

Thanks Aran,
Jon

OK...I did end up having to uninstall RM v 4.0 to successfully install RM 5.2. Now, the issue I'm having is adding the storage array within RM 5.2. It sees the serial number of my CX4-120, and when I get prompted to enter a user name and password for my array, it fails with "026084 error Storage Services operation processShowStorage failed with an error as follows: Storage Services has terminated with an error." The 2nd error is: 001018 ERROR: Validation for APM00012345678 failed. Please check credentials and connectivity.
I used the same userID and password as I did when installing RM 5.2 server, when asked to supply an account to be used for scheduling. Also, in the field where I enter username and password, it lists the correct IP for SPA and SPB. Anything you can tell me is greatly appreciated.

-Jon

Message was edited by:
KCSPam

Hey there

The account username and password you need to provide RM to discover the Clariion is the Navisphere administrator account, not a domain account.

HTH
James.

Wow...how didn't I know that?? I use Navi all the time, and have discovered iSCSI NAS devices and used those credentials. I guess sometimes one just over thinks things, making it more difficult than it has to be.

Very helpful James, as my storage device was "successfully discovered" once I supplied Navi username and password.

Thanks You very much!
Jon

Good catch James, I didn't catch that reading the previous post from Jon.

Glad to hear you have it all working now Jon.

Aran

Glad all is working - yet another successful mission in support forums

we are using rm in our environment and unfortunately it involves several different groups managing the solution. is there a reason why rm requires a user with administrative access as opposed to just a manager level access? my understanding was that the main difference between managers and administrators was that the latter could manage user accounts as well.

rm should not care about managing users on a clariion.

Hi there
This is a new thread really

Would you like to create a new post and we can track and answer it there better?

The user in the console has no relation as to what user the job or client operations run as eg array credentials.

Thanks
James.