So I have a crystal report that causes Logicity 1.9.0003 w/ CR Runtime 13.0.24.2970 to freeze upon logging into the server to pull data. It opens the parameter window and then hangs and you have to close the program. The odd thing here is that our previous version of Logicity (1.7.0018 w/ CR Runtime 13.0.8.1216) opens the report fine.

Does anyone have any ideas of things I should check or try? The crash happens and I have only the following log information to go off

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files (x86)\SaberLogic\Logicity\Logicity Desktop.exe

Problem signature
Problem Event Name: AppHangB1
Application Name: Logicity Desktop.exe
Application Version: 1.9.0.0
Application Timestamp: 5c4885d3
Hang Signature: 38d3
Hang Type: 134217984
OS Version: 10.0.17763.2.0.0.256.48
Locale ID: 4105
Additional Hang Signature 1: 38d3641d32fae4ff49933cff4b5912e1
Additional Hang Signature 2: 6a74
Additional Hang Signature 3: 6a7469975bb5e2393d3f37fb3f31d466
Additional Hang Signature 4: 38d3
Additional Hang Signature 5: 38d3641d32fae4ff49933cff4b5912e1
Additional Hang Signature 6: 6a74
Additional Hang Signature 7: 6a7469975bb5e2393d3f37fb3f31d466

Extra information about the problem
Bucket ID: 4f487c7161fc495a13de0423fadc9793 (1431586284129523603)

I have the same issue with version 1.8. I purchased an upgrade to 1.9 hoping that would fix it but get the same behavior. How did you solve this?

We havn't been able to solve this issue yet. Getting to a point where we may be moving away from Logicity.

We did track down one report using a function called HasValue, that when removed the report stopped crashing, but we have other reports without that function that crash in a similar fashion.

Did you build the reports under an older version of Crystal? We are using the latest runtime, and it looks like hasvalue may have been deprecated, I am not sure if you have any other functions that are a bit older like that. We can get you an older version if that would be helpful, but you may need to test your reports in the latest version of Crystal:
www.tek-tips.com/viewthread.cfm?qid=1495228

Thanks!
Brian

I have been able to solve it in my reports by removing and re-adding each parameter one by one. Whatever the problem is I can re-add the parameter with the same settings and it works. No rhyme or reason it seems to what kind of parameter causes it though.

Thanks for the info Teh_Tourist.

Our reports guy ended up fixing the problem, although not sure why it happens, but what he did was similar. There was a parameter taking a number data type, what he did was convert it to take a string, and then converted it back into a number within the formula. This stopped Logicity from crashing when trying to open the report.