Hi @CovMayurJ 

I have just installed Crystal on 23R1 and have the same issue. If you edit the WEB.CONFIG file in C:\inetpub\wwwroot\IFSCRWebSetup and comment out the custom errors node

    <customErrors mode="On" defaultRedirect="metadata_request.html" />

and make it this

<!-- <customErrors mode="On" defaultRedirect="metadata_request.html" /> -->

Note, you need to restart the web service after altering this file.

When browsing from the server the web service is installed on, you will get a better more detailed error message.  In my case i get this, so I dont have a solution, but at least I have more detail. 

I am having similar issues. Can anyone confirm that Crystal is working for them in 23R1? I have built and taken down 3 printer servers trying to get this to work 

hi @Alex Ivkovic 

 

From IFS Cloud 23R1 onwards, network policies are enabled by default. Therefore you need to add the crystal web service machine IP address which needs to be included in the cloud values yaml file (ifscore.networkpolicy.crystalhost).

https://docs.ifs.com/techdocs/23r1/070_remote_deploy/400_installation_options/005_operational_reporting/110_configure_crystal_web_service/010_setup_cws/#defining_virtual_directory_for_multiple_web_service_instances

https://docs.ifs.com/techdocs/23r1/070_remote_deploy/010_installing_fresh_system/200_installing_ifs_cloud/035_ifs_cloud_ifsinstaller/030_installation_parameters/

This is not an error. Metadata publishing is disabled for security reasons from IFS Cloud 23R1 and you'll be redirected to this html page when you're accessing Ifs_ReportService.asmx.

Please refer below for installation parameter execution order. (arguments passed in the command line are given priority than the ifscloud-values.yaml file)

https://docs.ifs.com/techdocs/23r1/070_remote_deploy/010_installing_fresh_system/200_installing_ifs_cloud/035_ifs_cloud_ifsinstaller/030_installation_parameters/#the_parameters_order

--set networkpolicy.crystalhost=172.16.161.23 needs to be corrected as --set ifscore.networkpolicy.crystalhost=172.16.161.23

.\installer.cmd --set action=mtinstaller --values ..\..\..\..\config\ifscloud-values.yaml --values C:\ifsroot\deliveries\23.1.4\InstallationFiles\ifsinstaller\solutionset.yaml --set ifscore.networkpolicy.crystalhost=<crystal_host>

Would 

networkpolicy:
    enabled: false

In ifscloud-values.yaml override that? 

"I'm not sure whether it would override, but if it doesn't, you can manually add them in the ifscloud-values.yaml file."

parameter needs to be in installation values yaml (ifscloud-values.yaml) for it to be persistent. However, make sure it's property indented as below.

ifscore:
  networkpolicy:
    enabled: true
    crystalhost: 10.0.45.6

And run pods restart 

Is there a way to test if this is working? I have done this and I’m still getting the error 

Hi @Alex Ivkovic ,

Could you please attach (ifscloud-values.yaml) herewith, need to add parameter entries after passwords section. 
 

Thank YOU

Takesha

It is attached to the case however I did add the parameter shown above and I don’t believe it’s the issue as the Middle tier is able to communicate with the print server to some extent

Our problem turned out to be that"LocalNetworkIpRange":in the main-config.json file was incorrect. 

Hi @Alex Ivkovic , Could you please share the steps that you followed to get it working after identifying the incorrect "LocalNetworkIpRange":in the main-config.json?

Thank you.

For some reason I have yet to figure out changing it in “main-config.json” doesn’t seem to be fixing it.

I run 

.\installer.cmd --set action=mtinstaller `
--values C:\IFS\PROD\UB1-MWS-2314RU\ifsroot\config\ifscloud-values.yaml `
--values solutionset.yaml `
--set ifscore.networkpolicy.crystalhost=XXX.XXX.XXX.XXX

but I do have to re-run it every time I install a delivery.

Thank you @Alex Ivkovic,

I’m still getting the same error when browsing ASMX from IIS. I also noted a mismatch in "LocalNetworkIpRange" in main-config.json. So I edited main-config.json and recreated the Kubernetes cluster. After that I executed 

.\installer.cmd --set action=mtinstaller `
--set ifscore.networkpolicy.crystalhost=XXX.XXX.XXX.XXX

What did you do, when you notice the incorrect configuration of “LocalNetworkIpRange" and were you able to browse ASMX without any errors after the changes?

I’m assuming you  replaced XXX with the appropriate IP address? 

Here’s a test you can run

Run  kubectl get pods -A

Note the name of the pod with reporting-cr

Run kubectl exec -i -t  {ifsapp-reporting-cr-5ff95c59cc-vcd77 -c ifsapp-reporting-cr} -n {cdfprod} -- /bin/bash 

replacing the appropriate variables  

Then  curl -v http://192.168.0.132/IFSCRWebSetup/Ifs_ReportService.asmx

Changing the IP to your print server

If it says connect time out that’s not good, it will be pretty clear when you have connected to the page. 

Hi,

I am having the same issue since we upgraded to 23.2.1

did you manage to resolve this? 

thanks

Gary 

I’ve posted what helped for me in this post here.  This fixed the same issue we were encountering on 23R1.

Crystal Report server issue | IFS Community

Hi All, How can I verify if the Crystal Web Service is running correctly?

Previously, we could confirm its status by accessing ifs_ReportService.asmx, but now we're encountering a message indicating that the ASMX web service is disabled. Do we need to install something to resolve this issue?

Additionally, the new documentation mentions configuring an SSL certificate in IIS and specific pods. Is it mandatory to perform this configuration to ensure the Crystal Web Service is running correctly?

https://docs.ifs.com/techdocs/24r1/070_remote_deploy/400_installation_options/005_operational_reporting/110_configure_crystal_web_service/010_setup_cws/#prerequisites
 

Hi Guys,

Did everything on IFS documentation and community forum, but still getting the error below:

Maybe something wrong with the certificate. When I DESCRIBE the pods I suppose to install the certificate, I can see the message below:

Thanks