Recently "migrated " our vault to a brand new server (Windows Server 2016). Got everything working except PDMWeb2.
Installation goes without any hiccups. Add identity to the application pool. Browse to web address...Nothing..
Spinning circle of death with "waiting for <server name>". 5 minutes later I get standard the "This page can't be displayed"...
Have double checked the identity and it is correct. (I'm not getting a 503 error). Not much help
Any ideas would be greatly appreciated..
Make sure you create and login to a local Vault View on the Web2 server as the user you've identified in the IIS identity. I've missed this step myself. The back end API requires this (if memory serves).
I have done this already. Double and triple checked this. Still no luck...
At first I though it might be a firewall issue. But have proven that its not the case..
Hi Brian,
I had that issue also and needed a long time to find out what is the problem for endless waiting time. Its a problem with runtimes 2013/2012 just uninstall / reinstall new. Also disable firewall for testing and check if you set up permission for ISS login as admin (auto login in PDM administration). You can look in PDM admin under help > web server guides for instruction. Hope this helps you and all other
SPR 1063460 - 'Update the Web2 Prerequisites in the installation guide with C++ 2013 & 2012 Runtimes in order to use 2018 Web2 - Without them the Login page will hang and 'IIS Worker Process' shows high CPU'
Thanks. Worked like a charm..
Hi Brian,
I had that issue also and needed a long time to find out what is the problem for endless waiting time. Its a problem with runtimes 2013/2012 just uninstall / reinstall new. Also disable firewall for testing and check if you set up permission for ISS login as admin (auto login in PDM administration). You can look in PDM admin under help > web server guides for instruction. Hope this helps you and all other
SPR 1063460 - 'Update the Web2 Prerequisites in the installation guide with C++ 2013 & 2012 Runtimes in order to use 2018 Web2 - Without them the Login page will hang and 'IIS Worker Process' shows high CPU'