Sometimes you discover thing, you did not expect…or even nobody has talked about before. One of those things is the Azure Portal Cache Background Some time ago i was at a customer implementing Azure Site Recovery. I configured ASR like i always did, but at the selection of the configured vCenter Server there was a…
While installing System Center 2012 R2 Data Protection Manager there are many possible issues.
But today i found a new issue, while installing at customer site is found a new issue…
While installing we got the following error (ID 812):
Let´s have a look into dpmsetup.log:
* Exception : => System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.x.x:443
Now i was really surprised that DPM is trying to connect ba port 443. The rporting Services are properly configured for usage with port 80and are running well.
After some research and some failed installations we had an idea. We had reconfigured the names of the reporting services website so that they are more specific. So “DPM_Reports” was used instead of “Reports_INSTANCENAME”.
After undoing this change the instalation worked well.
SO: Let the reporting services as preconfigured! 😉