Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    3
  • Subscribers subscribers
    4
  • Views views
    374
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ZAV 10 - Unable to open parameter file error

MigrationDeletedUser
When trying to launch a ZAV 10 app, C-Cure Administration Console, users are getting an error "**Unable to open parameter file cc800cl.pf, errno 2. (1247)". This only appears to be happening on Win7. This did work when first created, but after a few weeks the error has started to pop-up.
  • 0
    Are there any errors or warnings logged in the event logs at the same time? If this previously worked, I'm leaning towards an environmental change as being the cause of the issue; if that's the case we should also be able to see more going on than just that warning.

    If you check the virtual file system, does that cc800cl.pf file exist anywhere?
  • 0 in reply to 
    zeevromm;2258849 wrote:
    Are there any errors or warnings logged in the event logs at the same time? If this previously worked, I'm leaning towards an environmental change as being the cause of the issue; if that's the case we should also be able to see more going on than just that warning.

    If you check the virtual file system, does that cc800cl.pf file exist anywhere?


    There are jvmStart cannot be found and AdmService_PROGRESS cannot be found errors when trying to launch the app. The cc800cl.pf file is in the virtual file system.
  • 0 in reply to 
    If this was working and is not now, and you are certain nothing has changed on the client systems (or at least nothing that could interfere here), then this might be an issue with the license used when building the application. What is the expiry date of your license and was it applied prior to building this exe?

    If this isn't expiring please open an SR for this issue, if you can. This is the information the support team will require:

    - Copies of any warnings or errors around the time the issue occurs (or a copy of the application and system event logs, in .evtx format)
    - A copy of the exe you are using
    - If you can build the exe again as a diagnostic-mode executable and provide the diagnostics generated when attempting to run, that can be very helpful
    - It may also be required that you send installation media for the application and your build process, so the team can attempt to reproduce the issue in-house
    - You will also typically be asked for the .xappl file and associated Files folder, if reproducing in-house is required. This will become absolutely necessary if a ticket needs to be filed with Spoon, so sending it ahead of time is a good idea

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.