Cracking the Vault

DWF Job Processor Error

Inventor 2014 and Vault Professional 2014. Checking in an ipt with a linked Inventor dwg, resulted in this error when sending the DWF creation to the job processor.

 

Retrieving the COM class factory for component with CLSID {C343ED84-A129-11D3-B799-0060B0F159EF} failed due to the following error: 8007045a A dynamic link library (DLL) initialization routine failed. (Exception from HRESULT: 0x8007045A).

 

I resolved the issue by uninstalling all older (non 2014) versions of Autodesk software. (The one exception was Autodesk Design Review 2013)

Vault Ribbon missing in AutoCAD 2014 Application

We get more and more reports that the Vault ribbon in the AutoCAD 2014 application (in various ACAD verticals) is missing:

You also noticed that the Vault integration works fine and you can login, check in/out via the menu in AutoCAD.

Solution:

1. In windows explorer navigate to: C:\Program Files\Autodesk\ApplicationPlugins\Vault.bundle

2. Make a copy of the file PackageContents.xml

3. Open the PackageContents.xml via notepad and change all following red marked values:

<?xml version="1.0" encoding="utf-8"?>
<ApplicationPackage SchemaVersion="1.0" ProductCode="{40449FE4-35F8-4B92-A2E1-7B52F77C6974}" Version="1.0.0" Name="Autodesk Vault 2014 Plugin" Description="Autodesk Vault 2014 plug-in for AutoCAD 2014" Author="Autodesk">
    <CompanyDetails Name="Autodesk" Url="http://www.autodesk.com/" Email="support@autodesk.com"/>
    <Components>
        <RuntimeRequirements OS="Win32|Win64" Platform="LDT|AIP|AIPRS|AIPSIM|Civil|AOEM|AIS|ECSCAD|ADT|ACADM|ACADE|Map|Civil3D|MEP" SeriesMin="R19.1" SeriesMax="R19.1" SupportPath="./Contents/"/>
        <ComponentEntry AppName="Vault Plugin Partial Menu" AppDescription="Vault plug-in for AutoCAD 2014" ModuleName="./Contents/VaAc.cuix" LoadOnAutoCADStartup="True"/>
    </Components>
</ApplicationPackage>

4. Save the file and restart Vault Client and your AutoCAD application.

Now the Vault ribbon in ACAD should appear.

If it doesn´t work and/or you encounter a serious problem in AutoCAD restore the original PackageContents.xml you copied in step 2.

Contribution by Elisabeth Boehm

Support for Windows 8.1 and 2012 R2

Question:

Does Autodesk support Windows 8.1 or Windows server 2012 R2 for Vault 2014 products.

 

Answer:

Currently we do not support Windows 8.1 or Windows server 2012 R2 for Vault 2014 products.

Please read the System Requirements Page for system requirements and what is currently supported. 

Do You Get Less Than 5% Memory Error?

Issue:

Vault is no longer working and in the vlogs, you see a message with the text:

Memory gates checking failed because the free memory (xxxxxx bytes) is less than 5% of total memory.

Cause: 

The issue occurs because you have less than 5% available memory free and by default, the program checks for 5%

Solution:

In Windows Explorer, navigate to C:\Program Files\Autodesk\ADMS <version> 2014\Server\Web\Services.
Open the file named web.config in notepad.
Find the line
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
Change it to be
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" minFreeMemoryPercentageToActivateService="0" />
Open a command line window and type the command IISRESET to reset IIS

Contribution by Hywell Herrero

DWFs in Duplicate Vault Folder Structure Not Created

There is currently an issue inside Vault 2014 that no DWF in the Duplicate Vault Folder Structure is created when the name of the folder has the same as the Workspace within the Inventor project.

Example: Workspace is subfolder "design" and Duplicate Vault Folder Structure is C:\design

See clarification on this screenshot:
Workaround is to use a different name in the Duplicate Vault Folder Structure.

A Change Request has been logged to address this in a future update/release.

Vault 2014 Subscription Release 1 Thin client URL

After installing Vault 2014 Subscriptrion Release 1, there will be two URL's that you can use to log from a web browser.

 

The old web client will still be available here

http://servername/AutodeskDM/webclient

The new Thin Client URL is as follows

http://servername/AutodeskTC

 

This information is documented in the help

Autodesk Vault 2014 Subscription Release 1

This is for customers who are on Vault Subscription. For more information see the "New in Vault 2014 Subscription Release 1"

 

Autodesk Vault Thin Client 2014:

• The new Autodesk Vault Thin Client 2014 has been completely redesigned to provide a superior experience when accessing a Vault through a web browser. The redesign includes Enhanced user interfaces, Customizable view functionalities, New BOM interface, and Enhanced report printing. See Autodesk Vault Thin Client 2014 for more information.

"Edited Out of Turn" Workflow Improvement:

• In previous releases, we received feedback regarding unmanageable situations where Inventor recomputable updates were involved in creating Edited out of Turn files. With this subscription release, we address the situation by having the vault add-in reflect the last downloaded state with modifier information, and allowing the user to continue with his/her workflows following a save operation, like the following operations:
• Check In – The system shall not include the files that are not checked out to the user (as per the current behavior).
• Check Out – The system shall only allow files that are of the latest Revision (or newer version on local disk) to be checked out (as per the current behavior).
• Revert to Latest in Inventor – The user has to continue using the Revert to Latest command if he/she does not have the latest Revision on disk (regardless of local disk modification) to check out the files.

Revit Integration Enhancements

• Revit Project Information Property support: Vault now supports the Project Information properties of Revit models, which can be mapped to Vault UDPs and automatically imported which can then be used for easy searching and property editing in Vault.
• Import from Vault: The new Import from Vault feature lets you import RVT, DWG and DWF files stored in the Vault into the current Revit project.
• Load Group: The Revit add-in now supports loading Model groups, Detail groups, and Attached Detail groups from the Vault into the current project. This allows Revit users to select or exclude specific groups within a file.
• New Lifecycle, Revisions, and Categories support: The Revit add-in now supports change state, revise file, and change category workflows, making it easier for you to manage this information about your design right from inside Revit. Enhanced tooltips show you state information for your files in Vault.
• Shared Parameters support: Revit users can now point to a shared parameters file stored in the Vault, making it easier to activate shared parameters.
• Improved Load Family From Vault workflows: Revit users can now load all of the family types in a selected family in one click, making it faster to retrieve all of the family types needed for a project. Additionally, the Load Family from Vault dialog makes it easier for users to find the family types used most often by defaulting to the last folder location from which a family type was loaded.
• New Mapping User Interface on the Vault Options dialog: The Mapping tab on the Vault Options dialog has been enhanced to streamline common workflows.
• New Login Interface and Connection Status: The Log in and Log out buttons on the Revit Vault ribbon have been combined to create a single toggle button. Users can view their connection status by hovering their mouse over the button.
• Link more file types: You can now link DGN, SAT, and SKP files from the Vault.
• Maintain Link to DWF: Previously when linking to a DWF or DWFx file, the link was read-only and users would have to manually check out DWF markups to modify them. Now if a user checks out a file that has a DWF link, the DWF file is automatically checked out as well. When the file is closed, the DWF link is automatically checked back into the vault.

If you have any thoughts, comments or queries on this, please log them via the Vault Discussion groups or log a Support case with Autodesk.

Event IDs 0, 1325, 1026, 1000, 5011 and Vault.

These messages were appearing on a VP2014 Server.

In the AVFS logs

03.10.2013 13:09:37 ==== Logging initiated: Core server version 18.1.8.0 ====
03.10.2013 13:09:37 Initialized licensing for product/version Autodesk Vault Professional 2014/2014.0.0.F, product-key(569F1).
03.10.2013 13:09:37 The ADSK_LICENSE_FILE='XXX;' environment variable overrides the license path in web.config.
03.10.2013 13:10:53 Acquired license(153915216) for username(Administrator), userId(2), host(xxx.xxx.xxx.xxx).

The above is repeated, multiple times.

In the Application log

Log Name:      Application
Source:        ASP.NET 4.0.30319.0
Date:          01/10/2013 15:02:06
Event ID:      1325
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXX
Description:
An unhandled exception occurred and the process was terminated.
Application ID: /LM/W3SVC/1/ROOT/AutodeskDM/Services/Filestore
Process ID: 392
Exception: System.Runtime.CallbackException
Message: Async Callback threw an exception.
StackTrace:    at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)
   at System.ServiceModel.Activation.HostedHttpContext.HostedRequestHttpOutput.HostedResponseOutputStream.Close()
   at System.IO.BufferedStream.Dispose(Boolean disposing)
   at System.IO.Stream.Close()
   at System.ServiceModel.Channels.HttpOutput.Close()
   at System.ServiceModel.Channels.HttpRequestContext.OnClose(TimeSpan timeout)
   at System.ServiceModel.Activation.HostedHttpContext.OnClose(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestContextBase.Close(TimeSpan timeout)
   at System.ServiceModel.Dispatcher.MessageRpc.DisposeRequestContext(RequestContext context)
   at System.ServiceModel.Dispatcher.MessageRpc.CloseRequestContext()
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessageCleanup(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage8(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
   at System.ServiceModel.Dispatcher.ChannelHandler.DispatchAndReleasePump(RequestContext request, Boolean cleanThread, OperationContext currentOperationContext)
   at System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(RequestContext request, OperationContext currentOperationContext)
   at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(IAsyncResult result)
   at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
   at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)
   at System.Runtime.InputQueue`1.AsyncQueueReader.Set(Item item)
   at System.Runtime.InputQueue`1.EnqueueAndDispatch(Item item, Boolean canDispatchOnThisThread)
   at System.Runtime.InputQueue`1.EnqueueAndDispatch(T item, Action dequeuedCallback, Boolean canDispatchOnThisThread)
   at System.ServiceModel.Channels.SingletonChannelAcceptor`3.Enqueue(QueueItemType item, Action dequeuedCallback, Boolean canDispatchOnThisThread)
   at System.ServiceModel.Channels.HttpPipeline.EnqueueMessageAsyncResult.CompleteParseAndEnqueue(IAsyncResult result)
   at System.ServiceModel.Channels.HttpPipeline.EnqueueMessageAsyncResult.HandleParseIncomingMessage(IAsyncResult result)
   at System.Runtime.AsyncResult.SyncContinue(IAsyncResult result)
   at System.ServiceModel.Channels.HttpPipeline.EmptyHttpPipeline.BeginProcessInboundRequest(ReplyChannelAcceptor replyChannelAcceptor, Action dequeuedCallback, AsyncCallback callback, Object state)
   at System.ServiceModel.Channels.HttpChannelListener`1.HttpContextReceivedAsyncResult`1.ProcessHttpContextAsync()
   at System.ServiceModel.Channels.HttpChannelListener`1.BeginHttpContextReceived(HttpRequestContext context, Action acceptorCallback, AsyncCallback callback, Object state)
   at System.ServiceModel.Activation.HostedHttpTransportManager.HttpContextReceived(HostedHttpRequestAsyncResult result)
   at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.HandleRequest()
   at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.BeginRequest()
   at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.OnBeginRequest(Object state)
   at System.ServiceModel.AspNetPartialTrustHelpers.PartialTrustInvoke(ContextCallback callback, Object state)
   at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.OnBeginRequestWithFlow(Object state)
   at System.Runtime.IOThreadScheduler.ScheduledOverlapped.IOCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
   at System.Runtime.Fx.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
InnerException: System.NullReferenceException
Message: Object reference not set to an instance of an object.
StackTrace:    at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
   at System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)
   at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)

 

DWG and UDP Mapping

Issue:

My Autocad block will not map after I enable block indexing for that named block in ADMS.

Statement:

We have encountered drawings where an old (R14 and older) DWG with attributed blocks are still in use, and have never been updated/redefined.

Solution:

If you cannot map a block after you have set the ADMS block indexing, please do the below steps and try again.

1. Insert the block to the dwg (even if it’s in a different area of the DWG already)
2. Explode the block
3. Redefine the block (do not make any changes, just select the insert point and select the block data)
4. Save it as the same block name
5. Save the DWG
6. Check into Vault
7. Attempt to map the Autocad attributed block to the user defined property

If you have newer dwgs with this same issue, please redefine the block in them as well. 

 

NOTE:

You must update that block in each dwg it is used.