Cracking the Vault

Content Center Login "Object reference not set to an instance of an object"

In Inventor 2014, trying to login to the Content Center using the "Content Center library read only user", you will get this message.

 

 

Workarounds.

1) Create a Vault User account on the Vault Server with "Content Center Editor" role and with access to a Vault Database. Tell all users to use that account to log in to the CC Server. Note: if a licenced version of Vault is used for the CC Server, it will double the licence consumption. For this reason, use Vault Basic Server as the CC server. It is possible to detach the CC libraries from a Vault Workgroup\Professional 2014 Server and attach them to a Vault Basic 2014 Server

2) Dont "use separate server for content and Vault". Attach the Libraries to the Vault Server.

 

Development are aware of this issue, but because there is a workaround, its planned to be addressed in a future release.

Change Vault Server Log File Locations

You want to change the folder location of the ADMS, AVFS and vlog file generated by Vault Server. To do this, you must edit some .config files.

Before making any modification to the following files, ensure that you first make a copy.

To edit the config files, don't use a program that could change the format of the file, such as Microsoft Word. Instead, use a text editor such as Notepad, Notepad++ or Ultraedit (There are other text editors available, but these ones won't change the files format)

ADMSConsole

Config File:-

"C:\Program Files\Autodesk\ADMS Professional 2014\ADMS Console\Connectivity.ADMSConsole.exe.Config"

Default

   <logging>
      <add key="basefilename" value="C:\ProgramData\Autodesk\VaultServer\FileStore\ADMSConsoleLog" />
      <add key="logfileextension" value=".txt" />
      <add key="dateformat" value="-yyyyMMdd" />
      <add key="keepnumberdays" value="-1" />
    </logging>

Edited

   <logging>
      <add key="basefilename" value="C:\VaultLogs\ADMSConsoleLog" />
      <add key="logfileextension" value=".txt" />
      <add key="dateformat" value="-yyyyMMdd" />
      <add key="keepnumberdays" value="-1" />
    </logging>

 

vlogs

Config File:-

"C:\Program Files\Autodesk\ADMS Professional 2014\Server\Web\Services\Web.config"

Default

    <logging>
      <add key="basefilename" value="C:\ProgramData\Autodesk\VaultServer\FileStore\vlog" />
      <add key="logfileextension" value=".txt" />
      <add key="dateformat" value="-yyyyMMdd" />
      <add key="keepnumberdays" value="-1" />
    </logging>

Edited

    <logging>
      <add key="basefilename" value="C:\VaultLogs\vlog" />
      <add key="logfileextension" value=".txt" />
      <add key="dateformat" value="-yyyyMMdd" />
      <add key="keepnumberdays" value="-1" />
    </logging>

AVFS

Config File:-

C:\Program Files\Autodesk\ADMS Professional 2014\Server\Web\Services\Filestore

C:\Program Files\Autodesk\Vault File Server 2014\Server\Web\Services

Default

        <logging>
            <add key="basefilename" value="C:\ProgramData\Autodesk\VaultServer\FileStore\AVFS-log"/>
            <add key="logfileextension" value=".txt"/>
            <add key="dateformat" value="-yyyyMMdd"/>
            <add key="keepnumberdays" value="-1"/>
        </logging>

Edited

        <logging>
            <add key="basefilename" value="C:\VaultLogs\AVFS-log"/>
            <add key="logfileextension" value=".txt"/>
            <add key="dateformat" value="-yyyyMMdd"/>
            <add key="keepnumberdays" value="-1"/>
        </logging>

 

AVFSConsole

Config File:-

C:\Program Files\Autodesk\Vault File Server 2014\AVFS Console

Default

    <logging>
      <add key="basefilename" value="C:\ProgramData\Autodesk\VaultServer\FileStore\AVFSConsoleLog"/>
      <add key="logfileextension" value=".txt"/>
      <add key="dateformat" value="-yyyyMMdd"/>
      <add key="keepnumberdays" value="-1"/>
    </logging>

    Edited

    <logging>
      <add key="basefilename" value="C:\VaultLogs\AVFSConsoleLog"/>
      <add key="logfileextension" value=".txt"/>
      <add key="dateformat" value="-yyyyMMdd"/>
      <add key="keepnumberdays" value="-1"/>
    </logging>

 

 For the changes to become effective, you must restart the web service (IISRESET).

WebServiceError 8005

You might see this error in the AVFS logs

 

Error: Soap Exception ( mesg-id = 635197699812289386 ) 
Exception: WebServiceError [8005] (http://<ADMServername>/) 
Stacktrace: at Connectivity.Server.Proxies.ServiceAccessor`3.Execute(String remoteServer, Action`1 action) 
at Connectivity.Filestore.SiteAccessExtensions.GetCurrentEvents(SiteAccessor siteaccessor, ICollection`1 eventClasses) 
at Connectivity.Filestore.FilestoreScheduler.GetCurrentEvents(ICollection`1 eventClasses) 
at Connectivity.Server.Common.Services.Scheduler.ExecuteScheduledEvents() 
at SyncInvokeNotify(Object , Object[] , Object[] ) 
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) 
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(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) 

Exception(Inner): An error occurred while receiving the HTTP response to http://<ADMSservername>//AutodeskDM/Services/_impl/SiteService.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. 
Stacktrace(Inner): 
Server stack trace: 
at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason) 
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) 
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) 
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) 
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) 
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) 

Exception rethrown at [0]: 
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) 
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) 
at Connectivity.Server.Proxies.SiteService.SiteService.GetCurrentEvents(GetCurrentEventsRequest request) 
at Connectivity.Filestore.SiteAccessExtensions.<>c__DisplayClass13.<GetCurrentEvents>b__12(ServiceContext`3 context) 
at Connectivity.Server.Proxies.ServiceAccessor`3.tryexecute(String remoteServer, Action`1 action, Int32 attemptCount) 
at Connectivity.Server.Proxies.ServiceAccessor`3.Execute(String remoteServer, Action`1 action) 

Exception(Inner): The underlying connection was closed: An unexpected error occurred on a receive. 
Stacktrace(Inner): at System.Net.HttpWebRequest.GetResponse() 
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) 

Exception(Inner): Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. 
Stacktrace(Inner): at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) 
at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size) 
at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead) 

Exception(Inner): An existing connection was forcibly closed by the remote host 
Stacktrace(Inner): at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

 

If you do, ensure you have the latest Vault Service Pack and Cumulative Hotfix installed, then try

an IISRESET

If that doesnt work, try a B2bMigrate followed by a IISRESET

SiteSigninError 8004

You might see several of these messages appearing in the AVFS Logs

11.11.2013 00:01:37 ******************************************************************* Error: SiteSigninError [8004] (<SourceServername>, <DestinationServername>) Exception: SiteSigninError [8004] (<SourceServername>, <DestinationServername>)) Stacktrace:   

at Connectivity.Server.Proxies.ServiceAccessor`3.tryexecute(String remoteServer, Action`1 action, Int32 attemptCount)   

at Connectivity.Server.Proxies.ServiceAccessor`3.Execute(String remoteServer, Action`1 action)   

at Connectivity.Filestore.Licensing.GetProductTier()    at Connectivity.Filestore.Licensing.Initialize()

11.11.2013 00:01:37 ******************************************************************* Error: Soap Exception ( mesg-id = 635197248979893987 ) Exception: SiteSigninError [8004] (<SourceServername>, <DestinationServername>) Stacktrace:   

at Connectivity.Server.Proxies.ServiceAccessor`3.tryexecute(String remoteServer, Action`1 action, Int32 attemptCount)   

at Connectivity.Server.Proxies.ServiceAccessor`3.Execute(String remoteServer, Action`1 action)   

at Connectivity.Filestore.FilestoreScheduler.GetCurrentEvents(ICollection`1 eventClasses)   

at Connectivity.Server.Common.Services.Scheduler.ExecuteScheduledEvents()   

at SyncInvokeNotify(Object , Object[] , Object[] )   

at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)   

at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(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)

 

Try this

1.  Delete SiteConfiguration.xml from C:\ProgramData\Autodesk\VaultServer\Configuration
2.  Perform an IIS reset.
3.  Try your command again. 

The XML should be regenerated with a correct key and allow the action to continue.

 

Thanks to Andy Spivey for sharing this solution

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.

Vault 2013 Service Pack 1 Update 1 or Update 2?

After installing Vault 2013 Service Pack 1 Update 1, you click on Help>About from the Pull down menu's

 

You notice that that under Build 17.2.9.0 you see "Update 2"

 

 

This should read "Update 1"

Its minor, but possibly confusing. The build number indicates the installed versio. Autodesk development are not currently intending to address this. However, it will be addressed if the opportunity arises in another update\fix.

Installation of SP1 on localized Vault Basic Server 2014 fails with error applying transforms

There is currently an issue in all locallized (Non English) Environments with Vault Basic Server 2014 (for example German OS and German Vault Basic Server) that the installation of SP1 (for Server) fails with the following error message (the German message):

English Error Message: error applying transforms. verify that the specified transform paths are valid

German Error Message: Fehler bei der Anwendung von Transformen. Stellen sie sicher, dass die angegebenen Transformpfade gültig sind.

The issue dosn´t occur on pure English environments

Update 26th August: a new version of SP1 has been republished and the installation should work fine now.

If you still encounter this problem (with the SP1 of 23th August) please log a support case.

RestrictionsOccurred [1387]

This message can appear in the vlogs.

 

Error: Soap Exception ( mesg-id = 635071590603372501 ) 
Exception: RestrictionsOccurred [1387] 
Stacktrace: 
Server stack trace: 
at Connectivity.Product.BusinessLogic.ItemBL.CheckRestrictionsByItemIterationIds(ProductRestrictionCodes[] restrictionCodes, Int64[] itemIterationIds) 
at Connectivity.Product.BusinessLogic.ItemBL.EditItemRevisionInternal(Int64 itemRevId, Boolean bypassWIPRestriction, String comment) 
at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target) 
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) 

Exception rethrown at [0]: 
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) 
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) 
at Connectivity.Product.Services.ItemService.EditItemRevision(Int64 itemRevId) 
at Connectivity.Web.Services.v18.ItemService.EditItem(Int64 itemRevisionId) 
at SyncInvokeEditItem(Object , Object[] , Object[] ) 
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) 
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(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) 

The client can see this:-

 

"Operation cannot be performed because the item is locked for edit by user ‘<vaultusername>’."

In this situation, it occured whilst a user was editing an Item, but the Connectivity.VaultPro.exe was killed in Task Manager to simulate a client crash mid-way through editing the Item. The error in the vlog is generic. When the Vault client was restarted, Right clicking on the Item and selecting Edit resulted in the above message in the User Interface and the entry in the vlog.

In this situation you would need to wait 30 minutes before being able to edit the Item. The reason this locktime is enforced is because when an Item is edited, it needs to be temporarily locked to allow the user time to complete their task without the risk of another user overriding their edits. Without this lock, it would be possible that a user might start editing the Item, get distracted and then continue editing it, but when they finish editing it, another user may also have tried editing that Item. At this stage Vault could either overwrite the second users edits or display an error saying that the Item has changed. This would lead to confusion. So to prevent this from happening, if an Item is edited, it is locked until either the user cancels their edit or completes it.

I managed to reproduce this by editing an Item, then killing the process in Task Manager, mid-edit. Similar to a crash, the server would have had no message sent to it that the user has either canceled or completed their task. It assumes therefore that the user is still editing, until the 30 minute lockout expires.

DatabaseError [109]

You can sometimes see this error in the Vault Server vlog. (Note DatabaseError [109] is a generic error. The Exception(Inner) message is more indicative.)

Error: Soap Exception ( mesg-id = xxxxxxxxxxxxxxxxxxxx )
Exception: DatabaseError [109] 
Stacktrace: 
Server stack trace: 


Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Connectivity.Document.Services.FolderService.AddFile(Int64 folderId, String filename, String comment, DateTime lastWrite, FileAssociationParam[] associations, BOM bom, Stream file, FileClassification fileClass, Boolean hidden)
   at Connectivity.Web.Services.v17.DocumentService.AddFile(Int64 folderId, String fileName, String comment, DateTime lastWrite, FileAssociationParam[] associations, BOM bom, FileClassification fileClassification, Boolean hidden, ByteArray`1 fileContents)

Exception(Inner): Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
Stacktrace(Inner):    at Connectivity.Core.Database.TransactionContext.OnSqlException(SqlException e)
   at Connectivity.Core.Database.SqlAccess.ExecuteReaderInternal(SqlCommand cmd)
   at Connectivity.Core.Database.SqlAccess.ExecuteReader(CommandType commandType, String commandText, SqlParameter[] commandParameters, Int32 commandTimeout)
   at Connectivity.Core.DataAccess.OwnershipAndAccessControlCheck.ProcessReadOnly()
   at Connectivity.Core.DataAccess.DirectorExtentions.PostBuild(ArrayList builders)
   at Connectivity.Document.DataAccess.Folders.AddFile(Int64 folderId, String name, String comment, Int32 checksum, Int64 fileSize, Int64 createUserId, Nullable`1 createDate, DateTime lastWriteTime, FileAssociationParam[] associations, BOM bom, FileClassification fileClass, Boolean hidden, Boolean unmanaged)
   at Connectivity.Document.BusinessLogic.FolderBL.AddFile(Int64 folderId, String filename, String comment, Int64 createUserId, Nullable`1 createDate, DateTime lastWrite, FileAssociationParam[] associations, BOM bom, Stream file, FileClassification fileClass, Boolean hidden, Boolean unmanagedFile)
   at Connectivity.Document.BusinessLogic.FolderBL.AddFile(Int64 folderId, String filename, String comment, DateTime lastWrite, FileAssociationParam[] associations, BOM bom, Stream file, FileClassification fileClass, Boolean hidden, Boolean unmanagedFile)
   at Connectivity.Document.Services.FolderService.AddFile(Int64 folderId, String filename, String comment, DateTime lastWrite, FileAssociationParam[] associations, BOM bom, Stream file, FileClassification fileClass, Boolean hidden)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

It will also normally be accompanied by a Client Side User Interface error dialogue message.

This normally indicates a performance bottleneck issue that needs investigating.

It can be alleviated by increasing the SQL timeouts in the web.config file. Please refer the Advanced Configuration Guide for the version of Vault that you are using for more information.