Quantcast
Channel: Data Protector Practitioners Forum topics
Viewing all articles
Browse latest Browse all 3189

(DP) Support Tip: After an upgrade/patch CRS service does not start, debug shows shared mem errors

$
0
0

Configuration :

A Windows Data Protector (DP) Cell  Manger (CM).

 

Problem :

On the CM after an version upgrade, a DP patch installation or a DP Hotfix installation the CRS service or DP sessions do not start.

The debug.log file or DP debug trace files show shared memory problems similar to :

invalid shared memory size (size != 9303448)

 

Possible Solution :

 

DP upgrade :

* make sure that no DP sessions are running and ensure no sessions will start.

* make sure all GUIs are closed.

* Stop the DP services.

* Start Task manager End Process any remaining DP processes.

* Restart the DP services.

* if there is still a problem with upgrade, reboot the CM server before restarting the upgrade process.

* preferably use the local administrator user account instead of a domain account for upgrade.

 

DP patch installation :

* make sure that no sessions are running and no sessions will start.

* make sure all GUIs are closed.

* Stop the DP services.

* Start Task manager End Process any remaining DP processes.

* if still problem with patch installation, reboot the CM server before restarting the patch installation.

* preferably use the local administrator user account instead of domain account for installation.

 

DP Hotfix installation :

* make sure that hotfix is built for exact DP version and patch level you have installed.

* some hotfixes require all GUIs are closed.

* some hotfixes require installation when the DP services are stopped, if this is required, Stop the DP services.

* Start Task manager End Process any remaining DP processes.

* if still problem with hotfix install, reboot the Server before retrying the hotfix installation.

 


Viewing all articles
Browse latest Browse all 3189

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>