Cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

VOLUME_FILE_NOT_FOUND_4 at cloning

Creator
Creator

Hi,

I am creating a Test Environment for Testing through TEM.

 

The deploy_archive utility is getting failed with error '9083 - Reference %1$s is not a valid reference'. 

 

The logs are showing the error -9101 VOLUME_FILE_NOT_FOUND_4{0000000000002a155b390b5c56b182f2}{01ba66d941e3f576e79e5afc61c9ec9e}{C:\Siemens\TC11_PROD\volume\dba_vol_9}{infodba_5441d843\0eec000_unk_95u0se87ku09f.bin}. I suppose, it is unable to locate the '.bin' file under one of the infodba's volume folder.

 

> I checked the file in Host environment where it is not present too.

> I tried to create an empty file with same name where it is failing by stating 'No Content'.

> I copied some other bin file and changed the name where it is failing by stating 'confused with file content'.

> I tried to run bmide_setupknowledgebase.bat utility to create unk files, it is failing too.

> I also have the access to the volume folders.

 

Can anyone please help me with this issue?

20 REPLIES 20

Re: VOLUME_FILE_NOT_FOUND_4 at cloning

Gears Phenom Gears Phenom
Gears Phenom

Good afternoon, maybe this is a problem with SharedMemory, try this:

 

1) stop Server manager process and delete Shared Memory Folder
%TEMP%\V11xxxxxx

2) Delete Client Metacache
generate_client_meta_cache -u=infodba -p=infodba -g=dba -t delete all

3) Generate Server Metacache
generate_metadata_cache -u=infodba -p=infodba -g=dba -force

4) Generate Client Metacache
generate_client_meta_cache -u=infodba -p=infodba -g=dba -t generate all

5) Restarted Pool manager

Re: VOLUME_FILE_NOT_FOUND_4 at cloning

Creator
Creator

Hi Arthur3,

 

Thanks for the reply.

 

But I am facing this issue during initial stage of cloning. As the installation is not complete, the pool manager is not installed.

This issue comes after volume creation, where it searches for some text and bin files under infodba's folder.

 

Here is the piece of log for more clarity:

 

Adding Volume serving FSC to bootstrap
Internal site ID already set in cloned DB
Creating the empty volumes...
select puid,pvolume_name,pnode_name,pmachine_type,pwnt_path_name,punix_path_name from PIMANVOLUME
select pfile_name,psd_path_name from PIMANFILE where rvolume_tagu='j9Zl2WltltBKvA'
select pfile_name,psd_path_name from PIMANFILE where rvolume_tagu='yIQZQkxrltBKvA'
select pfile_name,psd_path_name from PIMANFILE where rvolume_tagu='DbSleuiWltBKvA'
=====================================================
Begin Task: Log auto-archive creation
Time: Tue Jul 31 15:17:52 IST 2018
=====================================================
Setting up Teamcenter shell

Executing [set TC_ROOT=C:\Siemens\TC11_PROD\tcroot]

Executing [set TC_DATA=C:\Siemens\TC11_PROD\tcdata]

Executing ["C:\Siemens\TC11_PROD\tcdata\tc_profilevars"]
Output from command: "C:\Siemens\TC11_PROD\tcdata\tc_profilevars"
command_exit=0
Exit Status 0, elapsed time 0:00:00

Executing [set TNS_ADMIN=C:\Siemens\TC11_PROD\tcdata]

Executing [set IMAN_BYPASS_CANNED_METHODS=ALL]

Executing [set BYPASS_RULES=ON]

Executing [set NR_BYPASS=ON]

Executing [set BMF_BYPASS_ALL_EXTENSION_RULES=ON]

Executing [set TC_USE_METADATA_SHARED_MEMORY=FALSE]

Executing [set INSTALL_IN_PROGRESS_MODE=true]

Executing [set TC_KEEP_SYSTEM_LOG=true]

Executing [set TC_TMP_DIR=C:\Siemens\TC11_PROD\tcroot\logs\1807311507]

Executing [set LANGID=EN]

Executing [cd /D "C:\Siemens\TC11_PROD\tcroot\logs"]
Output from command: cd /D "C:\Siemens\TC11_PROD\tcroot\logs"
command_exit=0
Exit Status 0, elapsed time 0:00:00
...Done

Executing [echo %TC_SSO_APP_ID%]
Creating log auto-arche

Executing ["C:\Siemens\TC11_PROD\tcroot\bin\deploy_archive" -u=infodba -p=***** -g=dba -action=deploy -deploySource=tem -dir=C:\Siemens\TC11_PROD\tcroot\logs\1807311507]
Output from command: "C:\Siemens\TC11_PROD\tcroot\bin\deploy_archive" -u=infodba -p=***** -g=dba -action=deploy -deploySource=tem -dir=C:\Siemens\TC11_PROD\tcroot\logs\1807311507

***** The deploy_archive utility STARTED! *****


-log=(null)


-action=deploy


-deploySource=tem


-dir=C:\Siemens\TC11_PROD\tcroot\logs\1807311507


ifail (9083 - Reference %1$s is not a valid reference) returned from call to archiveHandler.collectDeployArchiveFiles


*****


ifail (9083 - Reference %1$s is not a valid reference) returned from call to archiveHandler.collectDeployArchiveFiles


*****


***** The deploy_archive utility FAILED! *****

command_exit=9083
Exit Status 9083, elapsed time 0:01:32
=====================================================
Task completed with the following warning: The 'deploy_archive' command encountered a problem during execution and exited with return status: 9083
Time: Tue Jul 31 15:19:27 IST 2018
=====================================================

 

 

Re: VOLUME_FILE_NOT_FOUND_4 at cloning

Creator
Creator

Hi Arthur3,

 

Thanks for the reply. But this error is coming during cloning. Pool Server is not yet installed.

After FSC creation, volumes are created and then deploy_archive utility is running.

 

Please see the following install log:

 

 

Adding Volume serving FSC to bootstrap
Internal site ID already set in cloned DB
Creating the empty volumes...
select puid,pvolume_name,pnode_name,pmachine_type,pwnt_path_name,punix_path_name from PIMANVOLUME
select pfile_name,psd_path_name from PIMANFILE where rvolume_tagu='j9Zl2WltltBKvA'
select pfile_name,psd_path_name from PIMANFILE where rvolume_tagu='yIQZQkxrltBKvA'
=====================================================
Begin Task: Log auto-archive creation
Time: Tue Jul 31 15:17:52 IST 2018
=====================================================
Setting up Teamcenter shell

Executing [set TC_ROOT=C:\Siemens\TC11_PROD\tcroot]

Executing [set TC_DATA=C:\Siemens\TC11_PROD\tcdata]

Executing ["C:\Siemens\TC11_PROD\tcdata\tc_profilevars"]
Output from command: "C:\Siemens\TC11_PROD\tcdata\tc_profilevars"
command_exit=0
Exit Status 0, elapsed time 0:00:00

Executing [set TNS_ADMIN=C:\Siemens\TC11_PROD\tcdata]

Executing [set IMAN_BYPASS_CANNED_METHODS=ALL]

Executing [set BYPASS_RULES=ON]

Executing [set NR_BYPASS=ON]

Executing [set BMF_BYPASS_ALL_EXTENSION_RULES=ON]

Executing [set TC_USE_METADATA_SHARED_MEMORY=FALSE]

Executing [set INSTALL_IN_PROGRESS_MODE=true]

Executing [set TC_KEEP_SYSTEM_LOG=true]

Executing [set TC_TMP_DIR=C:\Siemens\TC11_PROD\tcroot\logs\1807311507]

Executing [set LANGID=EN]

Executing [cd /D "C:\Siemens\TC11_PROD\tcroot\logs"]
Output from command: cd /D "C:\Siemens\TC11_PROD\tcroot\logs"
command_exit=0
Exit Status 0, elapsed time 0:00:00
...Done

Executing [echo %TC_SSO_APP_ID%]
Creating log auto-arche

Executing ["C:\Siemens\TC11_PROD\tcroot\bin\deploy_archive" -u=infodba -p=***** -g=dba -action=deploy -deploySource=tem -dir=C:\Siemens\TC11_PROD\tcroot\logs\1807311507]
Output from command: "C:\Siemens\TC11_PROD\tcroot\bin\deploy_archive" -u=infodba -p=***** -g=dba -action=deploy -deploySource=tem -dir=C:\Siemens\TC11_PROD\tcroot\logs\1807311507

***** The deploy_archive utility STARTED! *****


-log=(null)


-action=deploy


-deploySource=tem


-dir=C:\Siemens\TC11_PROD\tcroot\logs\1807311507


ifail (9083 - Reference %1$s is not a valid reference) returned from call to archiveHandler.collectDeployArchiveFiles


*****


ifail (9083 - Reference %1$s is not a valid reference) returned from call to archiveHandler.collectDeployArchiveFiles


*****


***** The deploy_archive utility FAILED! *****

command_exit=9083
Exit Status 9083, elapsed time 0:01:32
=====================================================

Re: VOLUME_FILE_NOT_FOUND_4 at cloning

Creator
Creator
Hi Arthur3,

I am facing this issue during initial stage of cloning. Pool server in not even installed yet.
This is happening after FSC creation, then volumes are created and after that deploy_archive utility is running.

Please see the following install log:

=====================================================
Adding Volume serving FSC to bootstrap
Internal site ID already set in cloned DB
Creating the empty volumes...
select puid,pvolume_name,pnode_name,pmachine_type,pwnt_path_name,punix_path_name from PIMANVOLUME
select pfile_name,psd_path_name from PIMANFILE where rvolume_tagu='j9Zl2WltltBKvA'
select pfile_name,psd_path_name from PIMANFILE where rvolume_tagu='yIQZQkxrltBKvA'
=====================================================
Begin Task: Log auto-archive creation
Time: Tue Jul 31 15:17:52 IST 2018
=====================================================
Setting up Teamcenter shell

Executing [set TC_ROOT=C:\Siemens\TC11_PROD\tcroot]

Executing [set TC_DATA=C:\Siemens\TC11_PROD\tcdata]

Executing ["C:\Siemens\TC11_PROD\tcdata\tc_profilevars"]
Output from command: "C:\Siemens\TC11_PROD\tcdata\tc_profilevars"
command_exit=0
Exit Status 0, elapsed time 0:00:00

Executing [set TNS_ADMIN=C:\Siemens\TC11_PROD\tcdata]

Executing [set IMAN_BYPASS_CANNED_METHODS=ALL]

Executing [set BYPASS_RULES=ON]

Executing [set NR_BYPASS=ON]

Executing [set BMF_BYPASS_ALL_EXTENSION_RULES=ON]

Executing [set TC_USE_METADATA_SHARED_MEMORY=FALSE]

Executing [set INSTALL_IN_PROGRESS_MODE=true]

Executing [set TC_KEEP_SYSTEM_LOG=true]

Executing [set TC_TMP_DIR=C:\Siemens\TC11_PROD\tcroot\logs\1807311507]

Executing [set LANGID=EN]

Executing [cd /D "C:\Siemens\TC11_PROD\tcroot\logs"]
Output from command: cd /D "C:\Siemens\TC11_PROD\tcroot\logs"
command_exit=0
Exit Status 0, elapsed time 0:00:00
...Done

Executing [echo %TC_SSO_APP_ID%]
Creating log auto-arche

Executing ["C:\Siemens\TC11_PROD\tcroot\bin\deploy_archive" -u=infodba -p=***** -g=dba -action=deploy -deploySource=tem -dir=C:\Siemens\TC11_PROD\tcroot\logs\1807311507]
Output from command: "C:\Siemens\TC11_PROD\tcroot\bin\deploy_archive" -u=infodba -p=***** -g=dba -action=deploy -deploySource=tem -dir=C:\Siemens\TC11_PROD\tcroot\logs\1807311507

***** The deploy_archive utility STARTED! *****


-log=(null)


-action=deploy


-deploySource=tem


-dir=C:\Siemens\TC11_PROD\tcroot\logs\1807311507


ifail (9083 - Reference %1$s is not a valid reference) returned from call to archiveHandler.collectDeployArchiveFiles


*****


ifail (9083 - Reference %1$s is not a valid reference) returned from call to archiveHandler.collectDeployArchiveFiles


*****


***** The deploy_archive utility FAILED! *****

command_exit=9083
Exit Status 9083, elapsed time 0:01:32
=====================================================

Re: VOLUME_FILE_NOT_FOUND_4 at cloning

Creator
Creator

Hi @ArthurRM,

 

This issue is coming during initial stage of cloning. Pool server is not even installed yet.

First FSC is created, then volumes are created and then deploy_archive utility is running.

The error is coming at this point.

Re: VOLUME_FILE_NOT_FOUND_4 at cloning

Solution Partner Honored Contributor Solution Partner Honored Contributor
Solution Partner Honored Contributor
Can you give more information on how you are cloning? Usually you install all the same software (and features minus your custom template) as the environment you are going to clone then throw away the database instance, volumes and tc_data. Copy the db, voluems and TC_DATA from the environment you want to clone to the cloned environment and adjust the volume location(s) using sql and values in tc_profilevars.bat before attempting a connection.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: VOLUME_FILE_NOT_FOUND_4 at cloning

Creator
Creator

Hi  @RandyEllsworth ,

 

 

 

 

 

Re: VOLUME_FILE_NOT_FOUND_4 at cloning

Solution Partner Honored Contributor Solution Partner Honored Contributor
Solution Partner Honored Contributor
Your DB has the volume location stored in it and you'll need to change the location, server name, etc. before using TEM. I have not used TEM to create a Test environment before but I have been cloning successfully for over a decade.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: VOLUME_FILE_NOT_FOUND_4 at cloning

Legend
Legend