Vault 2013.Error 1316. File iterations could not be assigned to an item.

[Maxim-CADman77]

Seems like long time nobody suffer from error 1316.

We now have one file (Configuration member Inventor 2012) with inability to Assign Item.

SQL maintenance plan is set properly.

Any ideas?

[Richard.Rankin]

Hi,

We have seen an issue like this reported in Vault Professional 2013, but it was addressed after a customer provided the files causing the issue to Autodesk. 

It sounds like this is a similar issue, (but obviously different as the other issue was addressed in SP1) so is it possible to share the file(s) involved to Autodesk Support?

Richard

[Maxim-CADman77]

Richard, unfortunately this particular file is an assembly of top-most
intellectual property unit of our company thus can't be shared even with
Autodesk TechSupport.

Seems like issue can't be solved unless it happen one more time on some
less secret data.

[Maxim-CADman77]

I wonder can entry from vlog be of some help to determine the reason of the issue?

06.05.2013 23:35:06 *******************************************************************
Error: Soap Exception ( mesg-id = 635034801061737132 )
Exception: PromoteFileIterationsFailed [1316]
Stacktrace:
Server stack trace:
at Connectivity.Product.Services.ItemService.ProcessBOMBlobs(Hashtable allboms, ArrayList newBoms)
at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

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.ProcessBOMBlobs(Hashtable allboms, ArrayList newBoms)
at Connectivity.Web.Services.v17.ItemService.AddPromoteComponents(Int64[] fileIds)

Exception(Inner): Index was outside the bounds of the array.
Stacktrace(Inner): at Connectivity.Product.Services.ItemService.ProcessBOMBlobs(Hashtable allboms, ArrayList newBoms)

[Anonymous]

Just in case, IAM re-assembled  "from scratch" using that same components and checked-in to Vault creates no problem on assign item operation.

[Anonymous]

Has anyone found any resolutions to this besides "rebuilding" the assembly?  I have two users getting this error with some iAssemblies.  Any help would be great!

[cadsupport]

Hi Richard, we are facing the same problem here on our Baselinetests with Vault 2014. We changed the status of a big assembly from Released to Work in Progress, without increasing the revision number. Upon update of this item, we get am 1316. Best regards Erik

[Richard.Rankin]

For others seeing this, in one situation we found that this helped.

Error 1316 Cracking The Vault

[spascual]

http://forums.autodesk.com/t5/vault-general-discussion/error-1316-file-iterations-could-not-be-assig...