atria | A toolkit for modern C development

In Log its show "Could not find or create an instance of QuickBooks".

Here are things to look at if you are getting a "Could not start QuickBooks" error message.

• Make sure your app is built for Target x86 only.
• Make sure the Keep QuickBooks running is Un-checked in the General Preferences.
• Make sure QuickBooks and your application are running at the same user level.
• They both need to be running as a normal user or both running as administrator, but not mixed.
• If you are running in Visual Studio and trying to debug, you are probably running in a mixed permission mode. VS runs as administrator, so you will need to start QuickBooks using the Run As Administrator option.
• Make sure the Path and Filename are correct.
• QuickBooks and QBXML SDK applications are NOT designed to run as a service. They have to run in the context of a user.

reference:

https://help.developer.intuit.com/s/article/Troubleshooting-Could-not-start-QuickBooks

Could not find or create an instance of QuickBooks using InstanceFinder

You can find two avenues to pursue in "Different epoch values":

• either on the target side (if you have access), import any pending sync packet (multitool syncreplica -import -receive)
• or (my solution) re-exporting the all vob: multitool mkreplica -export -maxsize 200m -nc... and importing it

Check also the technote "Replicated VOB cannot import or export packets from scheduled jobs"

The main factor which explain a permission issue in a ClearCase interop (Windows ClearCase client - Linux ClearCase server) is the CLEARCASE_PRIMARY_GROUP environment variable.

That variable (CLEARCASE_PRIMARY_GROUP) needs to:

• be set to the primary group of the vob of the element the user is trying to checkout (primary or secondary: type cleartool describe -l vob:\YourVob to list them)
• be the same value as the primary group of the Linux user (who can successfully checkout the same element in his/her Linux ClearCase view): type id -a to see that primary group eelinnis.emea.nsn-net.net/ccusers_xhaul_athens

Make sure on Windows the user is not launching the client with another account (Administrator, or System account), and the CLEARCASE_PRIMARY_GROUP is set.
(and the number of group is not too high)

You can use the creds utility to see your credentials.

See more at "ClearCase won't allow Check-In" and use the credmap utility to verify the group assignments between Windows and Unix.

Type set CL in a CMD shell in Windows to see the actual full value of the CLEARCASE_PRIMAY_GROUP environment variable (??_EE_CLEARCASE_USERS_XHAUL_ATHENS)

You need to see if that group maps to the Linux one.

Check also the protection associated to your view. See fix_prot on Windows here.

here is simple code with which you can start:

First, you need to be root.

Stop all Clearcase services on AIX system - Stop completly Clearcase

Second, the official documentation init_ccase does mention, in addition of /etc/rc.atria { start | stop }:

• Unexports any view/VOB combinations that were exported through /etc/exports.mvfs to enable non-ClearCase access
• Unmounts all VOBs
• Kills the vob_server processes for VOBs whose storage directories are on the local host
• Kills the albd_server process, which also causes view_server, db_server, and vobrpc_server processes to exit
• Kills the lockmgr process
• (On AIX 4) Unloads the MVFS from the operating system kernel
• Unmounts the viewroot directory

So regarding MVFS and AIX 4, the "Loading and Unloading Kernel Extensions" page suggests kmod_unload command.

That would stop completely ClearCase.

The commands listed in "Uninstall ClearCase 7.1 on Linux or Unix" (section AIX), like rmvfs mvfs, would be "too much" here.