Rob, we were on v. 10.1.2.287 like you. We put in a bunch of hot fixes in hopes of taking care of the issue, but it didn't. we are currently running v. 10.1.2.425, and the project copy still fails. however, OpenText has come up with a fix, which they'll be turning into a Knowledgebase Article, but I'll post the instructions they sent us (we haven't tried it yet) below:
"How to backup and restore project databases using SQL database backups. 1) Ensure all users are logged off the project you wish to backup. a. This can be accomplished from the Server Manager tab -> Administer Projects -> Projects -> Select the project you wish to copy and selecting "Display Active Users" from the action menu. 2) Confirm if the project has an Archive because a backup of this will also need to be taken. You can confirm if a project has an Archive by selecting "Show Project Information" from the action menu. Also make note of the Project database names while on this screen. 3) From SQL server find your project database, found in step 2, right-click on it and select Tasks -> Backup. Please perform this step for the Archive database if one exists. 4) Restore the Project database and Archive database, from step 3, using a different name. Ensure that the Archive name follows the standard <New Project Database name>_ARCHIVE. 5) After you finish restoring the Project database you need to make the following modifications in SQL. NOTE: This only needs to be completed on the new Project database and not the Archive. a. Edit the IO_SYS table where SYS1 = inuse and change SYS2 = 1 to 0. b. Truncate the IO_AFP table 6) In Web Site Mangement navigate to Server Manager -> Administer Projects -> Projects -> Select "Create Project" from the Action Menu. 7) The name of the Project can be anything you wish but for ease we recommend naming it the same as the database name. The database name provided needs to be the name of the database you restored in step 4. Enable Archiving if you restored the database from previous step. After confirming the Project settings you will be prompted with "A database with this name already exists. Do you want to use this database?" Select OK. The Archive database will automatically be picked up because of name given in step 4. 8) Ensure you select the new project from the list and then navigate to SmartTree -> Administer Project Settings -> Project -> General Settings and select Edit Settings from the Action Menu. a. Enable the option "Activate logging of published assets" and select OK b. Go back into the General Settings and disable "Activate logging of published assets" and select OK Note: Some projects make use of LiveServer cleanup so it's recommended to perform this step as it will delete the LiveServer cleanup index which can harm your production environment. 9) Next navigate to Publishing Targets under Administer Project Settings and delete all Publishing Targets. This will prevent the project copy from accidentally overwriting your production site. It is also highly recommended to delete any publishing jobs that might exist from Administer Publication as well. The restoration of the Project is complete." Again, we have not had an opportunity to test this, but OpenText has it working with a copy of our project on their end. Good luck - let me know how it goes for you! brett. On Thursday, June 6, 2013 4:19:19 PM UTC-4, Rob wrote: > > Brett, > > What version of OpenText are you now? > > Rob > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
