When you perform a Project Copy task that takes a while to complete, it can be unclear whether the task is hung or simply taking a long time to complete. This articles goes over how you can further analyze the status of the Project Copy task.
Depending on the source project code base size, number of files, inventories, and associated files, it may take some time to complete a project copy. To determine the project copy status, you can check the following:
- The copy status will be shown in the project dashboard page once you select the target project from the project list.
- Every 60 seconds, this status will get refreshed and it will show the latest details.
- While the copy is in progress, each step will be shown in the project dashboard page, e.g. source code copy, settings copy, files data (server and remote files) copy, inventory copy, file(s) association and index copy. Once the copy is completed, the dashboard will refresh and show the scan summary, audit progress and other details.
You can also check the logs for more details:
- Copy statuses are logged in the core server and scanner logs. Check the scan server logs for source code and index copy.
- The rest of the logging will be available in the core logs.
To check the state of the target project in the database, you can execute the following queries:
SELECT COPY_STATE_ FROM PAS_PROJECT_COPY WHERE TARGET_PROJECT_ID_ = {target_project_id}NOTE: Replace {target_project_id} with your project's ID. This query will return ‘IN_PROGRESS’ if the copy is in progress.
SELECT STATE_ FROM PSE_SCHEDULER_TASKS WHERE PROJECT_ID_ = {target_project_id}NOTE: Replace {target_project_id} with your project's ID. This will return ‘ACTIVE’ if the copy is in progress.
Once the copy is done, both states will be updated to ‘COMPLETED’.
If you have determined that the project copy task is hung or want to stop it for any reason, you can restart Tomcat on the Core Server. This will cause the task to be set to 'FAILED'.
NOTE: Please do not set or update any field in the database manually in either of the PAS_PROJECT_COPY or PSE_SCHEDULER_TASKS tables.
If you have restarted the Core Server, once you log back into Code Insight, the project copy task will have ended, and the project dashboard of the target project will show ‘Copy is unsuccessful’.
Related Articles
WriteVirtualMachines inventory writers step may take a long time to complete 4Number of Views Compliancereader taking a long time 5Number of Views Why does cancelling a task take a long time in FlexNet Code Insight? 4Number of Views Comprehensive scan taking long time for a project 4Number of Views Known Issue: Beacon UI may take a long time to open when the beacon’s parent is accessed through a proxy 27Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago