System Profile
...
Environment Access Information
DEV
User (admin):
Pass:
Unc: \\wwwappsmssdev\wwwappsroot\saf-sec-sur\4\cpscs-apcis-ws
Url: http://wwwappsmssdev/saf-sec-sur/4/cpscs-apcis-ws/ApcisProxyWs.asmx
Url:
ACC
User (admin):
Pass:
Unc: \\tctestmaster\wwwappsroot\Saf-Sec-Sur\4\cpscs-apcis-ws\ApcisProxyWs.asmx
Url: http://wwwappstestxwwwappstest.tc.gc.ca/saf-sec-sur/4/cpscs-apcis-ws/ApcisProxyWs.asmx
Url:
PROD
User (admin):
Pass:
UNC: \\tcwwwmaster\wwwapps\Saf-Sec-Sur\4\cpscs-apcis-ws\ApcisProxyWs.asmx
Url: https://wwwappsxwwwapps.tc.gc.ca/saf-sec-sur/4/cpscs-apcis-ws/ApcisProxyWs.asmxUrl:
System Overview
Good To Know
...
// If in debug mode, use test apcis web service; otherwise, use prod (J. Green, v1.0.0, April 2014)
#if DEBUG
using TestProxyAPCIS.apcis_preprod_ws;
//using TestProxyAPCIS.apcis_test_ws;
#else
using TestProxyAPCIS.apcis_prod_ws;
#endifProblem:
The SSL certificate for apcis.tmou.org which is installed on our web servers – for the CPSCS web application - will expire on June 11, 2020.
Solution:
See the solution on CPSCS-SCEPC page: ServerCertificateExpiring
Problem:
Production service down: CPSCS, MSIS, SIRS services all stopped working
Solution:
1- Restarted App Pool that did not fix the issue so I
2- Restarted WPAS Service this also did not work I then verified the COM+ I notice that that service was hung so i
3- Restarted Component Service and then verified the COM+ and the list was empty so I
4- Restarted Server then verified everything when all came back on and all was fixed and working since your application relies on .dll’s and that the COM+ was having issues I suspect that the problem was with the Component Service being hung and a reboot fixed the issue.
2- Restarted WPAS Service this also did not work I then verified the COM+ I notice that that service was hung so i
3- Restarted Component Service and then verified the COM+ and the list was empty so I
4- Restarted Server then verified everything when all came back on and all was fixed and working since your application relies on .dll’s and that the COM+ was having issues I suspect that the problem was with the Component Service being hung and a reboot fixed the issue.