Crystal Report server issue

I have not been able to get Crystal working on IFS Cloud 23R1

Well that’s not good… can anyone verify they have it working on 23R1?

@Alex Ivkovic  here is the related post: IFS Cloud 23R1 - Crystal report setup error | IFS Community

I am also trying to figure this out. has anybody managed to get it working?

if i click fetch logs, i get ‘Currently there are no log files to fetch.’ which suggests its communicating but doesnt appear to be working. ifs documentation isnt the best either. also 23r1.

Just curious, what’d you have to set it to? The subnet of the MWS/CWS/WMS of the environment? We had this running on 10.1.0.0/16 for forever and seemingly everything except CWS works. I updated it to be the actual subnet I’m running and it’s still not helping at all. 2321 deployed currently.

I have never been able to change it permanently. After each patch or upgrade 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

And it works 
 

Add it into your yaml file. 

ifscore:
  networkpolicy:
    enabled: true
     crystalhost: 10.0.2.5
    internetAccessExceptionList:
    - ip: 10.0.0.0/16
    - ip: 193.41.170.171/32

I have it just doesn’t work! Tried it in different places etc.  Not really worrying about it too much since I can just run that and it just works 

That was always the issue for me, that and having the correct exceptions to allow the traffic.

Obviously having them set correctly to your local sub nets as well. 

We were experiencing exactly the same issue on a customer environment (23R1) and some troubleshooting within IIS on the server led me to try something I found online…

Within IIS set the application pools to ‘Enable 32bit applications” = FALSE.

I also removed the localhost value from the bindings on port 80 on the default site in IIS.

After making these two changes Crystal started working within IFS.

Also ensure that the IIS user has full access on the wwwroot folder and confirm that there is no network clash on the internal pod range versus the local network.

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
 

Initially, if the Crystal Web Service Logs can be enabled without any issue, this means the connectivity is established between crystal installed server and the application.
I am not sure how to verify the Crystal Reports. Back in the days we used a test report to view modules.
Recently, in 24R1 SU1, I am also facing the same issue since the test report failed with error “ Error in retrieving the parameters”

 

Hi All,

Is there anyone who was able to install crystal web service without updating the certificates related to below pods?
 

If the environment has created with a SSL cert, do we still need to update above parameters in the yaml file?
In my case the Crystal Web Service Logs are also enabled.
 

But unfortunately, when I view the test crystal report, it gives an error like below.

In the Fetched logs, cannot see any thing helpful either.

I have already updated the be​​​​​ crystalhost and port in yaml file as well

​​

Thanks in Advance!

Hi @rayanhimal , 

Delete the namespace and recreate it using the following command. You can find more details in this community post: https://community.ifs.com/framework-experience-infrastructure-cloud-integration-dev-tools-50/ifs-cloud-23r1-crystal-report-setup-error-39261

.\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>

Could you please let me know what you selected for the Application Pool when you installed the Crystal web service? Was it .NET v4.5 Classic or .NET v4.5?

Hi @maheshmuz,

I was able to get crystal reports working after adjusting the ifscloud-values.yaml file. There were some indentation issues which caused not to apply the new cyrstalhost and crystal port parameters.

For your question, please use .NET v4.5 which is enabled default in your default application pool.

Best Regards,

Rayan

Hi Guys,

I am having the same issue with crystal reports. When I try to activate the log on IFS I am getting the message that “ Return value to config logs not found.”, and my report still showing “Error in retrieving the parameters”.

I can access Ifs_ReportService.asmx ( no errors).

My questions:

1. What information I need to enter on CRYSTALHOST? It is like below, or I need to enter the ip of my IIS server?
   1. ifscore:
        networkpolicy:
          enabled: true
           crystalhost: 10.0.2.5
          internetAccessExceptionList:
          - ip: 10.0.0.0/16
          - ip: 193.41.170.171/32

Thanks,

Gianni Neves

Hi Gianni,

The Crystalhost must be the IP of the server which you are installing Crystal web service.

Furthermore, it is better to check whether you have any indentation issues in ifscloud-values.yaml where you added crystalhost.

Since you have followed the techdocs, I assume you have added the cystalport: 443  parameter as well. 
 

Are you using a SSL cert in the environment or it’s just a self-signed one?

Best Regards,

Rayan

@rayanhimal,

thank for the answer,. I will try to change it later today and let you know. For the certificate I create a self-signed for the Crystal web service for my tests.

Hi @rayanhimal,

I used the IP from my IIS server, but still having the same message. The interesting thing is that any change a do in my IIS server, my error message in IFS changes (like if IFS is able to talk to IIS Server).

When I “describe” the pods (IFS-REPORTING-CR, IFS_REPORTING and IFS-ODATA), it still showing the warning message “MountVolume.SetUp failed for volume "certificates" : failed to sync configmap cache: timed out waiting for the condition”. 

Thanks,

Gianni Neves

Hi @gianni.neves,

Could you please send a Screenshot of your ifscloud-values.yaml file?

Did you add the certificate information for the mentioned 3 pods in ifscloud-values.yaml file?

Best Regards,

Rayan

Hi @rayanhimal ,

I redacted some information in .yaml file, and put it into a zip file. So you can look at the complete file.

I trying to import the logs direct from IFS, and when I try to configure I am gettings this message:

Hi @gianni.neves ,

I could not find any issues in the yaml file. Probably, this is not the issue.

In the application, System Parameters, have you updated the Crystal Web Service installed machine parameter as IP or hostname?
This should be set as the IP.
 

You get above mentioned error when you set the log level to some value and clicking the OK button?

Best Regards,
Rayan

@rayanhimal ,

Thanks for the answer.

If I change for the IP address, I get I different error. The only thing I can think right now, it something wrong with my IIS server. But still, I can access the Web Service. I really short of ideas. Thanks again for your help.