Welcome to the ProSphere forum!
The correct procedure is to start the VMs at the vApp level in vSphere Client (right-click the vApp and use the power off/power on options). This will ensure that the three VMs start up/shutdown in the correct order. Do not start the VMs individually.
Customer Support Services (CSS)
To add to Seamus' comments. All of the VMs should be set to start and stop at the same time. You can confirm this by right clicking the vApp, selecting Edit Settings, then Start Order. All ProSphere VMs should be in Group 1 (I would even recommend you move Collectors into that group if you have any).
I would also suggest taking a look at emc288585 which has additional information about VM configuration settings that can impact the startup and shutdown of the ProSphere virtual machines.
What is the start order? Mine is currently setup to be:Storage Resource Manager, Discovery Appliance and then Historical Database. I'm assuming that is correct? When I start power up and login, I get error that it can't connect to either the discovery appliance nor historical database. I had the VMs renamed by mistake and then named back to original name but still have same issue. Perhaps a redeploy is best option at this point.
Sorry, I did not reply to this one sooner. Did you end up trying a redeployment?
Regading the start order. All of the vms should be listed in the same start group, which means they all start at the same time.
I redeployed prosphere and the VMs are working fine. I can now discover the symmetrix array but when I click on connectivity I get "unable to locate the resource" error. The management IP listed is the one for smc. I am currently using Prosphere 1.0.
You are still using the base 1.0 version, yes? I recommend that you upgrade to the latest 1.5 release.
I recall seeing the 'unable to locate the resource' error in earlier releases but not in 1.5 to date.
Customer Support Services