on 02-25-2019 3:44 AM
Best practice says to stop all servers besides CMS & FRS servers.
However, I've always hit a spot in the installer where it just sits and sits. It sits at the part where it says installing the samples.
Finally I decided to dig into the logs a bit more. It's looking for a promotion management server to be running on the CMS box??
First, we run a distributed environment so there is no such server on the CMS box, and
Second, the Promotion server is stopped on purpose as defined by best practices.
This isn't making sense to me?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
WebI Samples are delivered as a BIAR file, and so a running PM server is necessary for the samples to be loaded. If you don't have a PM server on that node, I'd suggest creating one temporarily just so the samples get loaded.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommendation to stop all servers prior to install comes from the experience where install is not able to stop all services and fails to update files as they are in use by those un-stopped processes.
When the samples are being imported, installer has already moved beyond the stopped servers part and should already have started SIA and all the usual servers.
If samples fail to load when you install "CMS only" node, they will load when you install the "regular" node.
At least that's how it should be, I haven't tested that scenario as I prefer to install "full stack" on every node for easier management later.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Denis! I have also learned to install full stack on all nodes in the landscape starting with 4.2.
However, just because I install all components, doesn't mean they're set to run on that node. So while the 2 mgmt tiers have all components installed, there is no PM server set up in CMC to run on these 2 nodes. So while the installer may have moved beyond the stopped servers part and has started up the servers on that node, the installer will still sit and [retry and retry and retry] forever because there's never going to be a PM server to start up on that node.
Furthermore, I just confirmed that the installation options had DE-SELECTED the Samples component. So why the installer even sat for such a long period to try to install the Samples was a complete waste of our productive downtime. I am opening a defect for this
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.