Vault – Renaming Computer hazard

Ok, I blew it.  I recently had a fight with my domain server, and lost.  I ended up renaming my computer to work around it.  It’s never been a problem in the past.  Well, at least I didn’t realize it was.

ADMS is getting its content from an SQL server on a site.  That site is my computer, and when renamed, it was lost.  My entire ADMS and Vault was gone for all applications.

Autodesk had this to say about the errors

Issue

During the installation of Vault or Productstream Server (ADMS), you received the following pre-check error message:

The SQL Server instance you have selected is not enabled with Autodesk Productstream Replicator. To enable it, upgrade site '<computername>'. Contact your reseller for Autodesk Producstream Replicator.

Solution

This error is the result of renaming the computer or adding it to a domain while the previous version of ADMS was installed even though replication has never been enabled on this particular computer.

This can be resolved by uninstalling SQL 2005, using Add or Remove Programs (Windows), and then reinstalling it either manually or automatically using the Vault/Productstream Server installation.

Alternatively, you can run the ADMS Console in command line mode and use the -OSiteRename switch. For detailed instructions, refer to the ADMS Console Help menu (available by pressing the F1 function key).

oSiteRename

 

Publish Content for Bolted Connection Part 4

Content Center Family Editing

We need to change some settings in the Content Center Family just written.  Navigate through he Content Center Editor to the new Family.  Right Click, and select the Family Table option.  The family parameters dialog will appear. 

The following are examples that I used, however you will undoubtedly have differences and variations at your company that need to be adopted.

 

Publish Content for Bolted Connection Part 3

Content Center Category Review

We need do some snooping.  We need to know where we are publishing the content.  The Countersunk Bolts Category is our target.  It would be ideal to publish our content to the sub category of ‘Wood Screws’ but alas, this cannot be.  You see the Design Accelerator has a limitation (I’ve heard this before….limitations), in that it will not use content below a certain sub-category.

 

The Bolted Connection Generator will only read from the Categories:

• Countersunk
• Hex Head
• Hex Head – Flanged
• Round Head
• Set Screws

We cannot file our content appropriately and get the desired outcome.  Once again we have to hack up a beautiful landscape, but the benefits are worth it. (I am still convinced that I will find the directing XML, and modify the strings to go deeper.)

The publishing process will take our part, and store it with the iPart members as members of the new Content Center family.  The family will take on the properties of the parent category, and we need to know about that criteria.  We have to direct the publishing to map the iPart parameters to the appropriate category fields. 

Let’s take a look at the Category Properties for the Fasteners->Bolts->Countersunk sub-category.  You should see the list of data contained in the category, that gets passed down to the individual families contained therein.  It’s a form of inheritance.  Notice the Mapping field, and the Optional and Required options.  The required settings are brought in from the parent category, and cannot be left out of the mapping.

Part 1 of Create Read/Write Content Center Library

We have moved to http://johnevansdesign.net