Vault Pro 2015 - Receiving Error 109 on Item Update

[Esky99!]

We are receiving Error 109 on updating some items.

It states the Server Log file needs to be investigated.

Is this a known issue?

Thanks

[Esky99!]

Refer to Server Log attached

[minkd]

I suggest opening a product support case to figure this one out.

-Dave

[tmoney2007]

I'll save you a little time... "Are you up to date with your service packs and hot fixes?" "Check all the files out and back in again and retry"

There's something wrong with a record in the table where some of the BOM information stored (is what it looks like).

When I try to troubleshoot these issues, I generally try to assign/update the items for the children of the assembly, on of those will probably fail with the same error. Then go to all the children of that assembly and repeat.  Eventually you may get to a part or assembly where something looks off or you'll reach the bottom of the file structure. If you check that one out and back in, it may fix it.

The thing to remember about items is that assigning the item to an assembly will trigger Vault to check if any of the children are out of date and update them as well.  There is a more than fair chance that the file causing this problem ISN'T the assembly you are trying to assign, but something at some level below.

If you get a real solution from support, please post it up here.  My company has been implementing item master and it has been a nightmare.

[Esky99!]

Thanks for your comments.

Totally aware of all of your comments. We have been using item master since product stream was first released.

Issue on this item has only arisen since installing 2015.

I have pinpointed the sub assembly in question. I am going to unlock each item and update each part and assembly within. Hoping this will fix the issue.

I've been told someone logged in as admin within inventor vault and checked out all files and saved them while they were locked in item master. I will need to unlock all items to update. Nightmare.

I'll also await comments from Autodesk.

[Esky99!]

Hi Dave

There is a product support case number on this.

Any chance in chasing this up. Getting a bit urgent now.

Thanks

Paul

[minkd]

I'm sorry that Product Support hasn't gotten back to you yet.  It is possible that they are swamped right now and hopefully they will be getting to you soon. When they do get in contact with you, make sure you get them the vlog you posted here; and they may ask for a copy of the db from a recent backup so they can try to reproduce the issue. I'm guessing they will want the backup because they likely won't be able to reproduce the problem otherwise.

-Dave

[Esky99!]

Hi Dave

Still no response here.

This one is urgent. I have other message listings that arent so urgent. But this one is.

Thanks
Paul

[minkd]

I have no ability to affect the order or priority of cases in Product Support. All I can suggest is to contact them again and make sure they understand the severity of your situation.

-Dave

[Esky99!]

Hi Dave

All good for time being. I have a workaround until Autodesk team fix issue.

Regards
Paul

[mthomas]

We're now experiencing this issue to since moving to 2015, so far only a handful of items but who knows how many are affected.

It's been logged with Autodesk Tech Support [PID: 09631692]

What "workaround" are you using?

Mike

[Esky99!]

Details removed as Autodesk is working on a fix.

[mthomas]

Its gone from a small problem to an epidemic very quickly, the number of items that we can not update nor change state has become too long to list.

[johannes.bauer]

Mike, please open a case with product support so we can have a look at your issues.
Thanks.

[mthomas]

It was logged last week PID: 09631692

[Esky99!]

If this doesn't rate as a critical issue, I'm not sure what does........

[johannes.bauer]

sorry did not see that.
thank you!

[davide.orlando]

Hello! Can you help me? Several of our customers have this problem, how can I fix it temporarily? there is already a hotfix?

Thank you for your help!

[Esky99!]

Hi

Unfortunately I cannot help you. There is no current work around.

Autodesk DEV team are aware and currently working tirelessly to get a fix for this. The sooner the better.

Its a real problem for us, as our item master is linked to our ERP system. We have had to manually switch off the link and add and remove items manually as required.

[davide.orlando]

Good Morning,
you have news about the problem? 

We have done the following tests you suggested:

1. Checkout and open the file, save all and checkin into Vault.
   --> Assign Item
2. Select in the Menü <Actions> <Clear item and CO locks> <OK>
   --> Assign Item
3. Launch Autodesk Data Managment Server
   Detach the Vault Database
   Detach the Knowledge Vault Master (KVM) Database
   IISRESET
   Attach the KVM Database
   Attach the Vault Database
4. Take a look of the Attach for controle the WindowsRights.

But have not solved the problem.

Thanks..